Nothing stops you from doing that, I still use .xml, reverted the commit just because I wasn't used to type stages on config.lua ;pI mean why not just use constants in lib instead all separate XML files? like a second config.lua
all separate files are so annoying this should never have been a feature.
there is so many things to customize.
stages.xml is deprecated, but kept for backwards compatibility. We didn't want to break everyone's servers with the change.Hi!
Why does stages.xml exist if the stages are changed in config.lua? Am I missing something?
That's the plan. We even added a XML parser in Lua so we can get rid of XML parsing from the server and keep compatibility while you migrate: Add XML parsing bindings for Lua by ranisalt · Pull Request #4108 · otland/forgottenserver (https://github.com/otland/forgottenserver/pull/4108)I mean why not just use constants in lib instead all separate XML files? like a second config.lua
all separate files are so annoying this should never have been a feature.
there is so many things to customize.
You don't need to revert the commit, you can just ignore the Lua configuration.Nothing stops you from doing that, I still use .xml, reverted the commit just because I wasn't used to type stages on config.lua ;p
well no you can just use the config.lua configuration instead as its easier. /reload configstages.xml is deprecated, but kept for backwards compatibility. We didn't want to break everyone's servers with the change.
That's the plan. We even added a XML parser in Lua so we can get rid of XML parsing from the server and keep compatibility while you migrate: Add XML parsing bindings for Lua by ranisalt · Pull Request #4108 · otland/forgottenserver (https://github.com/otland/forgottenserver/pull/4108)
You don't need to revert the commit, you can just ignore the Lua configuration.