This object is in archive! 
Make the MedievalEngineers-Dedicated.cfg XML standards compliant
Not Enough Votes
This is a request to define (if you haven't already at the KSH office) a DTD or XSD for the config file used by dedicated servers and reference it in the config file like so:
https://www.w3schools.com/xml/schema_howto.asp
This would greatly help server administrators to know which elements belong in the config file and which ones do not. Further, some game hosting centers (e.g. the one I use) initialize an ME instance with the config file for SE. Also as you make updates to the XML tags we'll be able to update our config files to match resulting in fewer server related gameplay issues simply because the config file was wrong/incompatible.
It must be I'm doing something wrong here then. So GameServers.com doesn't give access to your DS server admin tool I use at home for private LAN hosted instances. Instead they offer an online text editor (where you can edit the file manually) the user is led to believe the changes are saved directly into the MedievalEngineers-Dedicated.cfg file. This doesn't always happen (this is their issue not KSHs) so I've had to update the file manually to ensure any changes are made correctly, let alone add/remove tags Keen updates. In that case, as admins of our instance we don't get the benefit of using the Keen DS Admin tool.
The import/export procedure should work fine for me. I wasn't aware of the proper way to maintain config files that are publicly hosted.
Thank you.
Boromir
«Serialized by my Droid»
On September 24, 2018 11:56:45 AM UTC, support@support.keenswh.com wrote:
It must be I'm doing something wrong here then. So GameServers.com doesn't give access to your DS server admin tool I use at home for private LAN hosted instances. Instead they offer an online text editor (where you can edit the file manually) the user is led to believe the changes are saved directly into the MedievalEngineers-Dedicated.cfg file. This doesn't always happen (this is their issue not KSHs) so I've had to update the file manually to ensure any changes are made correctly, let alone add/remove tags Keen updates. In that case, as admins of our instance we don't get the benefit of using the Keen DS Admin tool.
The import/export procedure should work fine for me. I wasn't aware of the proper way to maintain config files that are publicly hosted.
Thank you.
Boromir
«Serialized by my Droid»
On September 24, 2018 11:56:45 AM UTC, support@support.keenswh.com wrote:
It's really not needed. The server cfg files support exactly the information presented in the configurator window. All you need to do is set options in the configurator to make an up-to-date cfg file. The configurator also supports importing and exporting so you don't have to change your local configuration. This is a thoroughly established tool with plenty of support. Why would we want to spend time creating a schema generator that would be much more difficult for 99% of people to use?
Note: Reposted due to visibility bug
It's really not needed. The server cfg files support exactly the information presented in the configurator window. All you need to do is set options in the configurator to make an up-to-date cfg file. The configurator also supports importing and exporting so you don't have to change your local configuration. This is a thoroughly established tool with plenty of support. Why would we want to spend time creating a schema generator that would be much more difficult for 99% of people to use?
Note: Reposted due to visibility bug
For what it's worth, you could drop the config file into this tool and it'll generate the XSD for you: https://www.freeformatter.com/xsd-generator.html
You would just need to add additional definitions for the range of acceptable values, mark the required tags, as well as add any other optional tags and their values. Lastly, reference the XSD in your config file.
For what it's worth, you could drop the config file into this tool and it'll generate the XSD for you: https://www.freeformatter.com/xsd-generator.html
You would just need to add additional definitions for the range of acceptable values, mark the required tags, as well as add any other optional tags and their values. Lastly, reference the XSD in your config file.
Replies have been locked on this page!