@kyle cool thanks ,i might take a look at that too
@nelg I checked my console.txt file for server2 this morning as I was going to grep all those commands but the file was empty
I looked through my scripts and found a line I had left in from when I was debugging rm -rf $consoletxt
when I rebooted my servers last night I have wiped all the console logs for all 6 servers
Because the commands are missing the _help in the language files, that probably means either the help is hard coded like spawn_zone or it's also missing there.
Since you have details on SPAWN_ZONE, I would suggest adding the spawn_zone_help for it and changing the command to use that instead of the hard coded version. Do that and submit a pull request. I'm sure you may have questions around all that, so it would be a good way to get your feet wet in the code.
Once you've done that, then did into some of the other areas, maybe target zone related commands
Also please note that target zone commands and SPAWN_ZONE are only in sty+ct And any forks of that, but commands like "ACCESS_LEVEL_SUBSTITUTE" are actually missing in the 0.2.8 and should be made as a PR based off of that branch and pulled into that. Then merges down into sty+ct, some of those may require an update, for instance if we Document what each of the LADDERLOG_WRITE_ commands actually write, they very between 0.2.8.* and sty+ct, as sty+ct typically has more information written to the log.
Feel free to ask for more detail on what I said, I'm not sure what you know and what you don't know, so keeping it somewhat minimal.
Also this could probably be split into a new thread.
I found this in my pi armagetron maps webserver log and was wondering if anyone knows what it is trying to accomplish ? it looks like its trying to create a cookie
Galaxip wrote: ↑Thu Apr 02, 2020 5:29 am
thanks for that nelg and thanks for your help in game
found the random crashing is mostly due to the zones, any zone appears (win, death, zombie etc) the server crashes
I think I've found all the relevant revisions to merge in from mainline, so +ap should work now. I'm told that these semi-manual merges are making my life harder, but when I'm feeling up to it I'll probably start reimplementing this stuff in 0.4. (probably never, heh .. or maybe I'll pester z-man about armagetron's network code and try to make 3dcycles work with armagetron in some fashion)
kyle wrote: ↑Tue May 12, 2020 3:44 am
merges down into sty+ct, some of those may require an update
Oh, well, that's a massive advantage of having to control what goes in then. Heh. The 0.4 ladder "spec" system is arguably superior there though, even though I'm not sure there's a consistent naming convention of the events' outputs
Galaxip wrote: ↑Tue May 12, 2020 1:43 am
i did a quick search for _help (missing help) in the armagetron commands on this build and found 102 commands with missing help
and then theres commands like spawn_zone which do have help but says nothing about naming the zone
some are obvious but others not so
I would love to fix the help file if I had the information
I know I'm basically a walking advertisement for +ap, but for the most part the commands are actually documented. Even what the ladderlog events write.