Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Yeah this is by design as per the original markup!Just something I noticed and I foresee it being something that folks run into
if you have the new RGManager launched and hit the "X" to exit
View attachment 63853
And then try and launch RedGuides RGManager again, nothing happens
View attachment 63854
Because the "X" didn't exit, and RGManager is still in sys tray
View attachment 63855
yeah my point was more about trying to launch it should bring it back up if it is already loaded, so perfect!It would probably be a good idea to add in to the mutex and maximize the window, I'll get on that!
Bug Fixes:
-Fixed an issue where deleted resources still showed in the associated resource grids.
Thanks for the feedback!First impressions, not a fan at all (except the map addition).
Don't take this personal as I couldn't do much better my self. Just sharing my feedback on the project. Giving the ability in current form for the end user to unintentionally stop downloading a plugin, macro, or Lua is a bad idea and will cause more confusion / support posts than it will help I feel.
- Color scheme makes the text harder to read as there is less contrast in dark mode; then WAY washed out in light mode. .
- Its providing WAY more information than I need to just get updated. Which makes it feel cluttered.
- Old client gives you the option to go straight to the resource in question by clicking on the name. Not seeing that option but I do see an option to quickly un-watch something by accident (which causes it to crash).
- No separation between macro, Lua, plugin in one place like the previous client has.
Not seeing that option but I do see an option to quickly un-watch something by accident (which causes it to crash).
Giving the ability in current form for the end user to unintentionally stop downloading a plugin, macro, or Lua is a bad idea and will cause more confusion / support posts than it will help I feel.
Also don't worry about it, I am not one to shy away from criticism.Don't take this personal as I couldn't do much better my self.
I’m making assumptions based on the icon and column that says unwatch. I’m assuming if a user were to click on that they would no longer be watching that resource. If that truly is the case then they could unwittingly remove their plugins, Lua, etc. from the patcher.Thanks for the feedback!
Could you please elaborate on these two points when you get the chance?
What were the steps performed that caused the application to crash while unwatching?
What are the steps performed to unintentionally stop downloading a resource?
Again, thanks for the feedback! Keep in mind this is a beta and development is still ongoing so expect there to be issues. On top of this, missing features can always be added as long as they're approved, so I appreciate it when folks let me know there's something lacking the old launcher had!
No problem!I’m making assumptions based on the icon and column that says unwatch. I’m assuming if a user were to click on that they would no longer be watching that resource. If that truly is the case then they could unwittingly remove their plugins, Lua, etc. from the patcher.
As for the crash. When I clicked the unwatch option I got a pop up that I should have saved (sorry). It acted like the app crashed and then came back. It didn’t seem to actually do anything other than simulate what appeared to be a crash recovery and continue to work.
Currently at work typing on mobile. Sorry for any typos.
It does not, it just unwatches the resource from an API standpoint (which will also remove it only from the Watched Resources grid). It won't prevent you from being able to access the resource via the Manager.Maybe my ignorance here but if I unwatch a Lua resource, does that not stop it from downloading via the patcher like the current one does?
If so how does a user choose what is downloaded / not downloaded?
Will have a patch addressing this via the issues we discussed (hopefully) by tomorrow evening assuming all goes well!i got stuck on this for the past like 18 hours (i left it over night)
View attachment 63911
trying to hit the refresh and i get the error
View attachment 63912
just decided to exit and reload it
View attachment 63913
Changes:
-Handling for in-use files associated with downloads has been refactored and are now handled prior to execution.
-Updater handling for RGManager/ResourceHandler cleanup has been refactored.
Bug Fixes:
-Fixed a bug where refreshing could potentially hang if the SEQ offsets path was modified manually outside of RGManager.
Bug Fixes:
-Fixed a bug where a handled safe failure could potentially be called outside of it's block causing an unnecessary error message to display on pipeline failure.
Do you have any files in the install directory set to read-only?So... Not sure whether I just have a weird file structure that it doesn't like, but I have to go to settings every time I start this, and tell it where to find MQ/EQ. It doesn't save the settings. Once I point it to the directories, it no longer wants to do a new install, and the launch MQ button is available. For reference, my MQ install is in: C:\veryvanilla, EQ install in Users\public\daybreak game company\installed games\everquest. once pointed, that stays there, until a reset happens, at which point those fields are once more blank.
Having the MQ launch button available means that the existing resource properly exists and it's path is being read so we can eliminate that as an issue.So... Not sure whether I just have a weird file structure that it doesn't like, but I have to go to settings every time I start this, and tell it where to find MQ/EQ. It doesn't save the settings. Once I point it to the directories, it no longer wants to do a new install, and the launch MQ button is available. For reference, my MQ install is in: C:\veryvanilla, EQ install in Users\public\daybreak game company\installed games\everquest. once pointed, that stays there, until a reset happens, at which point those fields are once more blank.
Bug Fixes:
-Fixed a bug where MQStatus could potentially throw a null after updating between (RGManager) patches due to a previous change in initialization/structure.
If you're referring to process name obfuscation, both RGManager and MacroQuest perform this identically:While it's probably not a huge deal, can the RedGuides Manager be renamed like the MQ program is? If you leave that running and they choose to scan. Pretty easy to tie together using HWIDs etc, or am I wrong?
Not a problem! Always good to make me do a double take, you never know when I've forgotten something!Yep, that's what I was looking at. Sorry Ionis thanks!
/goes back to hiding..
Yeah! We can definitely change the stylization of the watch icons.can the watch icons maybe change to green if watching? they are hard to decern the \ through it when its that grey on grey.
this is intended to replace legacy launcher. Please use and give feedback if you can, so we can have a better launcherSo my speciality of asking the silly question
What is the aim of this utility as opposed to the existing launcher? ( read through here and cant see that anywhere - although I may as usual have missed it ! )
So my speciality of asking the silly question
What is the aim of this utility as opposed to the existing launcher? ( read through here and cant see that anywhere - although I may as usual have missed it ! )
Yep exactly.this is intended to replace legacy launcher. Please use and give feedback if you can, so we can have a better launcher
Not sure if it is a guide, but it might be a good start:would be awesome sauce if someone would kindly post a quick "how to" back up config ( ie things like autologin profiles etc )
happy to jump on it and break it thereafter :P
MQ launch button is not present until after I point the manager to the path. Once pointed in right direction, everything is fine, until I restart manager, and only option present is the install MQ button. Seems as if the path variable is never being saved/written out to ini, so each startup it just looks to whatever is its default path. And no files that I can find are set to read-only.Having the MQ launch button available means that the existing resource properly exists and it's path is being read so we can eliminate that as an issue.
The path being blank does, indeed, mean that the settings aren't appropriately saving when the application exits it's environment.
Do me a favor:
1. Launch RGManager
2. Fill in the path fields
3. Fully exit RGManager (if Minimize on Close is enable, click the X -> bottom right toolbar -> right click the RGManager symbol and click exit)
4. Relaunch RGManager
Tell me if that paths show up after a full refresh of the settings. If not, it may be, as manydills said, a file protections issue preventing modification and we can take a stab at that if we need to.
Let me know!
Strange but I appreciate the detailed breakdown!MQ launch button is not present until after I point the manager to the path. Once pointed in right direction, everything is fine, until I restart manager, and only option present is the install MQ button. Seems as if the path variable is never being saved/written out to ini, so each startup it just looks to whatever is its default path. And no files that I can find are set to read-only.
Hadn't run that machine for a week or so, since the toon I play there got a 7 day vacay, started up manager, it updated, and this time if found the path.... Voodoo, I tell ya!
That allows me to backup a lot of stuffNot sure if it is a guide, but it might be a good start:
Idea - - A little discussion on backing up up your "stuff"!
Both here and on the Daybreak forums you will regularly see someone post that they had to reinstall Windows and they lost all their settings. It's one of those royal pita times to try and get all your stuff figured out and customized again! And there's really no reason for it! Backing up your EQ...www.redguides.com
Bug Fixes:
-Fixed an issue causing multiple button base event handlers to populate when changing the status of the current MQ compile (down, out of date, up to date).