Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Dusty]

Originally yes, it was a bug, but we're trying to decide how to fix it.

[Lemonade]

so a bad team will quickly get scrambled, especially if they're playing badly as it'll  be easier to cap their flag

80% of the time, the next map loads while the winning (and losing) team's douches keep pressing M1 on the previously winning team door / pressing 3 or 4, and they manage to stay in / enter the the team which stays at 1v0 until someones less stupid enters the previously losing team. Then it repeats.

[trog]

What's your point?

[Shiggyru Miyamoto]

it happens. I join on the winning team, add to my potential failure by capping, then I suddenly get switched.

[NAGN]

the way it works is that it just switches who has the lowest score, it's much more obvious now cause I fixed autobalance in normal grav

[MTK5012]

how about:

in Player object: Alarm 1 :

Code: [Select]

if object = -1 || global.Server_Respawntime <= 0 //prevent autobalance in server that instant respawn
{
if team = TEAM_BLUE
team = TEAM_RED
else
team = TEAM_BLUE
}
else
alarm [1] = 1
then in ServerBalanceTeams:
replace :

Code: [Select]

 if(balanceplayer.team==TEAM_RED) {
            balanceplayer.team = TEAM_BLUE;
        } else {
            balanceplayer.team = TEAM_RED;
        }
        
        if(balanceplayer.object != -1) {
            with(balanceplayer.object) {
                instance_destroy();
            }
            balanceplayer.object = -1;
            balanceplayer.alarm[5] = global.Server_Respawntime;
        }

with this:

Code: [Select]

with (balanceplayer)
alarm [1] =  1

just a flash idea   and im a rookie to GML

EDIT:

some fix to stop autobalance refresh
Character End Step:

Code: [Select]

with(GameServer) {
    if balancing = 0
        ServerBalanceTeams();
    }

GameServer obj
add alarm 0 that switch balancing to 0
add balancing=0 in GameServerCreate
and fix

Code: [Select]

with (balanceplayer)
alarm [1] =  1
with (GameServer)
{
balancing = 1
alarm [0] = 200 //maybe
}


[NAGN]

I think it may be fixed in 2.3... but I can't really sift through all those bugfixes to know

[MTK5012]

i post it on my signature
how ever im not tested it yet

[Haxton Sale]

Bumping, couse it's still not fixed.
Can't you just make it wait for one of the players with lowest score to die?

[trog]

Report it on launchpad.

[Haxton Sale]

It's not a real bug, so I don't think it's worth it.