hikaricore

As a random interjection, I wanted to note that the InstallDatabases (at least with the Bash script) process offers to install updates (and attempts to,) but can not do so as they are all archived in their respective 7zip files. database/Character/Updates/Rel21/Rel20_to_BaseRel21_Updates/Rel20_to_BaseRel21_Updates.7z database/Character/Updates/Rel21/Rel21_to_BaseRel22_Updates/Rel21_to_BaseRel22_Updates.7z database/Character/Updates/Rel22/Rel21_to_BaseRel22_Updates/Rel21_to_BaseRel22_Updates.7z Just for example. Unpacking these prior to update attempt would be trivial for the bat/sh script, but it is currently not done. I know from reading elsewhere that this process will eventually be depreciated in favor of a more automated update process, so I'm not sure if dumping any time or effort into fixing this here would be worthwhile. However, if we know for a fact that we'll need to always apply the contents of Rel21_to_BaseRel22_Updates.7z after database creation, extracting the contents to Character/Updates/Rel22/ is a no-brainer. From my experiences with the latest database release and server, these were the only ones needing updated. Though it would be safe to say that it can't be presumed this will always be the case. After initially testing a build from scratch on a new server, I converted and imported an old Rel21 database and needed to update quite a bit from both World and Character, as well as at least one item from Realm. It occurs to me that one could query the database automatically after install, since we already have the db names and login details to get the current version/structure, and update from there. Though this too is mostly trivial, it would require some knowledge of both Bash and Windows command line (and/or PowerShell if applicable.) Not saying that I personally have the time to look at this at this point in my life, but IF i do happen to find a way to accomplish some or all of this (during a drunken One Piece marathon while my family is away for the holiday,) I will certainly share my findings with you folks. XD

I know I'm chiming in a little bit late here, but after running into the same problem on my own, I was able to resolve it by setting PlayerCommands to 1 in mangosd.conf. This permits the use of allowed commands such as those associated with bots, but does not allow any problematic GM commands for regular users. There may be another way to go about this, but that's what worked for me.