0 Members and 1 Guest are viewing this topic.
Concerning this mod, isn't it better to simply remove the speed classes in CTF ? Some kind of code that'll say "If Game type is CTF, then change every player's classes to RANDOM if they chose Quick Man or Slash Man"...Not only that it has been said many times, that some people want to master an unique class, others simply can't handle every classes...why forcing them to have a random class ? If people want a random class, the option's there.
It's not just the speed classes that are problems though. Flying classes, tanks[woodman mostly], and anyone with a dash can be problematic.Also, I threw the mod up on Best-Ever's wad hosting when you mentioned hosting it in "one of the popular WAD locations." Hope you don't mind!
BTW, Wint, ConsoleCommand() is being removed due to idiots abusing it. You might want to file a ticket to let the Zandronum team know about this particular use case.
Then why simply not disabling them in CTF ? It's more efficient than "reduce the luck of getting them"
>forcerandom means less variety>people who play classes just for abuse not playing classes is bad>implying that having new players' first impression of MM8BDM being a 20-minute ClassesSH stallfest is a good thing
For some reason, Force Random seems to be broken. I've encountered two main problems with it;- It can detect whether or not your class is random, and then kill you, but it doesn't change it for you. This is a problem in any game that respawns people instantly (because then you'll just die and die and etc, etc.)- It winds up kicking everybody because it floods the server with changing player info.God damn, ACS's execution environment is weird. Any tips on this?
Not really. Your options are:2. ragequit and start your own indie development house like Ijon Tichy did
Rather than having it change player info, have it do this:On Spawn/Respawn, check what is playerinfo_class (or something). If it is non-random, constantly kill that player OR force spectate.. The script should not loop, so it checks only ONCE within every spawn or respawn
Quote from: "tsukiyomaru0"Rather than having it change player info, have it do this:On Spawn/Respawn, check what is playerinfo_class (or something). If it is non-random, constantly kill that player OR force spectate.. The script should not loop, so it checks only ONCE within every spawn or respawnI had considered that, but if possible I would prefer to kill the player and set him on random automatically. I may just have to concede to that workaround, though.