TMWServ @run script command

[Crush]

While I recently worked on the TMWServ command handler I thought about what kind of additional commands would be useful. One thing that came to mind was that it would be very useful for events when a gm or administrator could run lua script files using an admin command like @run monsterinvasion.lua.

Of course not every script should be executable in this way and not everyone should be allowed to run every script. That's why I would suggest to limit command-triggered script execution to scripts which are in special folders. I would suggest to create a folder for every access level and search there for command-runable scripts to control who can run which scripts.

What do you think about this?

[Turmfalke]

sounds reasonable, but I guess you don't have the time to implement it?

[Crush]

I currently have the time and motivation to implement this.

[Jaxad0127]

I say go for it. This would be a nice system to have for events. We might even add some that normal players can do too, with fun effects that don't really do anything.

[Rotonen]

Also nice for in-game parsers of server-side data. For example cashflow reports of potential player run businesses.

[5t3v3]

In the future, another use for this could be a guildleader that uses such commands. For example to declare war against another guild, making each other pvp-able or whatever. Just thinking out loud...

[Crush]

I consider it quite unlikely that we will ever have lua scripts evokable by normal players on the official server. Any feature which could be implemented this way could also be implemented with a more straight-forward chat command (@pvpon vs. @run pvpon.lua) or even a graphical user interface. But I could imagine some applications for private server admins who want to implement some unique features but don't have the means to hack the client and server on the c++ level.

[Jaxad0127]

This functionality may also be useful for scripts to use because of the different context it would run under.

[Crush]

This functionality may also be useful for scripts to use because of the different context it would run under.

What exactly do you mean with that?

[Jaxad0127]

This functionality may also be useful for scripts to use because of the different context it would run under.

What exactly do you mean with that?

I'll have to see how this gets implemented.