Spring RTS Engine

When testing stuff, it's usefull to be able to play one team, then other, then watch both, etc...

But I can't anymore! Spring call me a hacker for merely typing /spectator after /cheat when alone in my test game!

[ 0] Player NoName connected with number 0 (client version 0.79.1.2 (0.79.1.2-0-gbb45722{@}-cmake-tdm))
[ 0] GameID: 4c6b674ab89bf2edc79eb60297174d8b
[ 125] /spectator
[ 126] Player 0 resigned and is now spectating!
[ 337] /team 0
[ 503] /spectator
[ 503] Spectator NoName tried to hack the game (spoofed TEAMMSG_RESIGN)
[ 901] /cheat
[ 901] Cheating!
[ 978] /spectator
[ 978] Spectator NoName tried to hack the game (spoofed TEAMMSG_RESIGN)

Please fix this nonsense! When I do expressly type /cheat, I want to be able to turn back and from playing a team and speccing.

Without looking at the code I'd say that's simply a missing !

If you look closer at the log, you'd see that /spectator worked once, didn't work the second time (no cheat) and didn't work the third time (with cheat). I don't know what logic it uses. But it's not just inverted one.

I have the same problem - once switched from spec to a player, you can't switch back to spec (at last in games with bots that is). Must be some new 0.79 "feature".

yuritch wrote:I have the same problem - once switched from spec to a player, you can't switch back to spec (at last in games with bots that is). Must be some new 0.79 "feature".

Yes, it protects you from beeing "resigned" by a spectator, which is usually what you want. Looks like some variables doesn't get reset properly when using "/team". That they may not work correctly is the reson for them requiring "/cheat".

That they may not work correctly is the reson for them requiring "/cheat".

No, I never said /spectator required cheat as it is now.

I said that if you are afraid that merely typing /spectator is some kind of dangerous spoof-hacking that must be stopped at all cost, then consider it a cheat. But still leave me a way to use it.

Right now I have to test stuff, and I can't because of Spring.exe is being silly and insulting my honor for no reason.

yuritch wrote:at last in games with bots that is

Maybe this, just like the problem with getting game with bots started I had previously, are due to bot not being given enough consideration in 0.79? Like, when a human plays a team, you acknowledge that this team is being played, but when a bot plays a team, then you consider that team is not being played.

zwzsg wrote:Maybe this, just like the problem with getting game with bots started I had previously, are due to bot not being given enough consideration in 0.79? Like, when a human plays a team, you acknowledge that this team is being played, but when a bot plays a team, then you consider that team is not being played.

please try latest master, i made a commit that should fix it (though it was nearly too easy to work).

tested myself today, seems to work properly now.

i hope all these restrictions are taken out when you are playing alone, because it doesnt make sense to limit your playing when you play alone...

hoijui wrote:tested myself today, seems to work properly now.

It sorta work, in that I can alternate /team X and /spectator

If I type /spectator twice, I still have the message about "Spectator Player tried to hack the game (spoofed TEAMMSG_RESIGN)". Which would technically be still a bug, except it doesn't really matter, as I can still exit spectator by typing /team X.