Quote:
Originally Posted by knowom
Is this a bit like WSUS offline slipstream updates applied to EQemu? Basically take for example EQemu repack and ensure it stays up to date automatically as the peqDB changes in the future?
Another words combined together a slipstream installation and patching system. I kind of assume it was partly made both to update old DB's easily, but also to ensure your repack stays up to date and doesn't require constant maintenance for users?
|
No, its not supposed to be a WSUS type of setup. Most people upgrading a server are connected to the internet at the time because they need to pull down new source files to even compile and this script runs no differently.
This is for everyone, to keep databases consistent and also provide us a graceful medium to apply updates effectively.
Yeah sure its being but right in the middle of normal workflow, but if you're up to date you don't notice anything.
At its core its meant to keep a database update with the binary you are running, it fetches updates from github and runs whatever is appropriate.
With it, we also can start providing pre-patch options in it too. Like for example enabling bots at the database level or enabling mercenaries, turning on and off rules and such can be made plug and play with this as well. Lots to evolve with.