BatchExec - Printable Version +- Cuberite Forum (https://forum.cuberite.org) +-- Forum: Plugins (https://forum.cuberite.org/forum-1.html) +--- Forum: Plugin Releases (https://forum.cuberite.org/forum-2.html) +--- Thread: BatchExec (/thread-2034.html) Pages:
1
2
|
BatchExec - xoft - 07-01-2015 This plugin allows admins to execute batches of console commands that are read from a file. Source, download: https://github.com/madmaxoft/BatchExec Console commands: - batchexec <filename> - read the specified file, line by line, and execute each line as a console command RE: BatchExec - NiLSPACE - 10-08-2015 Is it possible that this would be expanded? That users could also use this. For example in the Gallery server to set the correct hitbox I currently have to use: "/ge bb show", "//expand 1 walls" and then "//expand -1" while looking away from the door. If I could simplify it by using something like "/batch hb" or "/b hb" it would speed up the process a little RE: BatchExec - xoft - 10-08-2015 There's a problem of defining the batches, if you want to make that user-configurable, too (instead of reading files, a DB should be used, probably). I'm quite unlikely to do that, though, but feel free to submit a PR RE: BatchExec - NiLSPACE - 10-19-2015 How about not making it possible to do add batches in-game, but that I make an web-admin interface where admins can add and edit the batch files? RE: BatchExec - Aberts10 - 10-20-2015 (10-19-2015, 03:54 AM)NiLSPACE Wrote: How about not making it possible to do add batches in-game, but that I make an web-admin interface where admins can add and edit the batch files? sounds good RE: BatchExec - xoft - 10-20-2015 Sounds good, but then you'd need to include a storage for the batches (most likely SQLite) with proper sequencing of the commands (one command per record? or one batch per record?) RE: BatchExec - NiLSPACE - 10-20-2015 I had a folder in the BatchExec's folder in mind. I don't really expect admin's to create more than a few of them. RE: BatchExec - xoft - 10-21-2015 That could be tricky to set up correctly. Anything in the filesystem can be vulnerable to various attacks: Code: /batchexec c:\windows\system32\win.ini RE: BatchExec - NiLSPACE - 10-21-2015 That could be fixed by something like this + (Path):match("^%w:\\") RE: BatchExec - xoft - 10-21-2015 That code is wrong, these paths will get through it: Code: ../../.././settings.ini |