This is factually correct, not broken, your ally team != your team.
The reason this appears broken is because team sharing is rare these days, as such ally teams have been shortened to 'teams' and teams has been renamed to 'player'.
Go start a battle and have someone share the same ally and team numbers as you and watch as you both control the same units.
Bah, I know that, maybe I was using sarcastic language. But ally-team is a stupid construction, it means nothing sensible (if you are a team then it's assumed you are also allied, how can you e.g. be a foe-team? It makes no sense).
If you comshare then I consider that as a variant of sharing a player, not a team. I know that spring has different stance in internal functions, but there is no need to bring that crap out in the light.
Take the analogy of a football game: you have players and then you have teams. Even though there are some games where many people can control the same players (remember kick-off), it's doesnt make that player a team.
One possible concept to use could be alliance instead of ally-team.
There seems to be some issue when automatically installing Spring through ZKLobby - it gives map checksum error with every map. Some people using TasClient had this problem too so I post the solution that worked for me and potential cause here.
It seems that downloading Spring manually and installing it manually fixes the problem.
I think the issue has to do with folders: - I had Spring version 0.82 in D:\Games\Spring - the ZKLobby installed Spring into D:\Games\Spring\engine\83 - I run ZKLobby from D:\Games\Spring because my shortcut pointed here - checksum error every game - I installed Spring 83 manually into D:\Games\Spring and run ZKLobby again - now it works
Users browsing this forum: No registered users and 0 guests
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot post attachments in this forum