CVS test server
I just analyzed the events on the Fortress test server leading to Luke saying:
Result: There was no real phasing on the server, what Luke saw was probab;y Bubba's bike that should have been destroyed when he timed out; What happens on the client instead is that the cycle lives on, turns (!) and drives off into infinity. None of the real cycle trails intersected without a kill.
But there IS a phasing problem; I saw it several times (but without a recording), you sometimes get it in the first seconds when all team members "cuddle up". sometimes, you end up on the wrong side. So scream "BUG" when it happens to you!
Of course, I'll have a look at the ghost cycle problem as well.
The test servers will be down again sometime tomorrow as I'll get my next attempt of installing Ubuntu over the network here.
Code: Select all
[1] luke-jr: BUG
[3] Lucifer: awww
[3] Lucifer: brb
[0]
[0] Try to conquer the opposite zone by staying inside for about two seconds!
[0] (Sorry, all official release clients show the zones in wrong colors.)
[0]
[1] luke-jr: I PHASED
But there IS a phasing problem; I saw it several times (but without a recording), you sometimes get it in the first seconds when all team members "cuddle up". sometimes, you end up on the wrong side. So scream "BUG" when it happens to you!
Of course, I'll have a look at the ghost cycle problem as well.
The test servers will be down again sometime tomorrow as I'll get my next attempt of installing Ubuntu over the network here.
- Tank Program
- Forum & Project Admin, PhD
- Posts: 6712
- Joined: Thu Dec 18, 2003 7:03 pm
I'm afraid that
a) no, I don't have a recording or even a log; this was the first session where I did not have it enabled
b) as I see it, it's the same bug: Rad Dog was your partner in this round, and he quit. His cycle got not cleaned up properly on your client, but was on the server.
I think I know what's causing this; gCycle::Kill does not request a sync message, so the information that Dog's cycle got terminated never reached your client.
a) no, I don't have a recording or even a log; this was the first session where I did not have it enabled
b) as I see it, it's the same bug: Rad Dog was your partner in this round, and he quit. His cycle got not cleaned up properly on your client, but was on the server.
I think I know what's causing this; gCycle::Kill does not request a sync message, so the information that Dog's cycle got terminated never reached your client.
Fixed the ghost bike bug. It was a combination of two bugs:
- The server would not send a sync message where the cycle is dead; the cycle got destroyed before that
- The client did not handle the destroy message properly and left the killed cycle alive
Both need to be there together for the bug to manifest.
- The server would not send a sync message where the cycle is dead; the cycle got destroyed before that
- The client did not handle the destroy message properly and left the killed cycle alive
Both need to be there together for the bug to manifest.
Umm, apparently the last statement was wrong. The thing I did for the server does not fix it alone. Sorry, you have to upgrade the client to get rid of the ghost AIs.
Meanwhile, the Fortress server has been updated to a map with four fortress zones and four teams and code that can handle them. It has crashed several times since, but I fixed the crash and it should be back online.
I'll go back to the two teams mode probably. It seems to be more fun. Plus, the four zones are really confusing for users of old clients, as their vanishing after conquest and coloring after the team does not work yet.
Meanwhile, the Fortress server has been updated to a map with four fortress zones and four teams and code that can handle them. It has crashed several times since, but I fixed the crash and it should be back online.
I'll go back to the two teams mode probably. It seems to be more fun. Plus, the four zones are really confusing for users of old clients, as their vanishing after conquest and coloring after the team does not work yet.
Code: Select all
[0] Team blue was awarded 10 points for conquering the enemy base.
[0] Team blue was awarded 10 points for conquering the enemy base.
...
[3] Joystick: BUG
[3] Joystick: captured ai zone and was awarded 10 points twice
Does anybody what these two BUG cries were about?
Code: Select all
[13] Player 1: ****
[0] Go (round 5 of 10 )!
[0] 3
[0] 2
[2] blue heart --> Teammates: grind the middle please
[0] 1
[0] 0
[0] gyl core dumped a teammate! Boo! No points for that!
[0] Washington core dumped Heeeeeeeeelp!!! for 2 points.
[0] Heeeeeeeeelp!!! core dumped a teammate! Boo! No points for that!
[0] Player 1 core dumped Washington for 2 points.
[0] Washington core dumped a teammate! Boo! No points for that!
[0] Someone [NL] core dumped a teammate! Boo! No points for that!
[0] Wejp core dumped Player 1 for 2 points.
[0] Wejp core dumped gyl for 2 points.
[0] Ryu core dumped viper for 2 points.
[0] Player 1 core dumped Wejp for 2 points.
[9] Wejp: ooh
[2] blue heart --> Teammates: wallbug
[0] kirkunit core dumped Ryu for 2 points.
[0] Team blue was awarded 10 points for being last active team.
[0] Winner: Team blue
Code: Select all
[2] tweedle_dum: hehe1
[0] Ping charity changed from 117 to 113.
[0] Mirowood [MBC] will fight for Team gold on the next respawn.
[0] Deleting objects...
[1] Hugoss: :D
[0] Deleting grid...
[0]
[11] cybersamurai GD: heh
[8] Moka: its ok
[0] Time: 76.2184 seconds
Sent: 2506158 bytes in 26325 packets (32881.3 bytes/s)
Received: 916408 bytes in 20435 packets (12023.4 bytes/s)
[0] Timestamp: 2005/10/29 01:50:04
[0] Creating grid...
[6] Garisimo: tsall good
[0] done!
[1] Hugoss: great heeeelp :D
[0] Go (round 9 of 10 )!
[0] 3
[0] 2
[3] Heeeeeeeeelp!!!: LOL!
[0] 1
[8] Moka: yay micro
[0] 0
[0] Mirowood [MBC] core dumped a teammate! Boo! No points for that!
[0] Moka core dumped a teammate! Boo! No points for that!
[0] tweedle_dum core dumped a teammate! Boo! No points for that!
[0] L0L core dumped a teammate! Boo! No points for that!
[13] MrCosma: lol
[8] Moka: well then
[8] Moka: lol
[0] Garisimo core dumped a teammate! Boo! No points for that!
[0] Garisimo core dumped Crisp for 2 points.
[0] squirl core dumped a teammate! Boo! No points for that!
[0] Hugoss core dumped tweedle_dum for 2 points.
[0] Match Winner: Team blue
[0] Overall Winner: Team blue with 100 points.
[0] L0L core dumped a teammate! Boo! No points for that!
[14] L0L: jo
[0] Garisimo core dumped Slingshot for 2 points.
[8] Moka: sorry iwas going back
[12] Slingshot: Yeah!
[6] Garisimo: LOL!
[1] Hugoss: :D
[7] Joystick: BUG
Code: Select all
[0] Zane Niobe core dumped THE ONE for 2 points.
[0] Roller1 core dumped a teammate! Boo! No points for that!
[0] TELELE core dumped Slingshot for 2 points.
[0] Team gold was awarded 10 points for conquering the enemy base.
[0] Winner: Team gold
[0] TELELE core dumped meriton for 2 points.
[0] free kill core dumped Stop Whining for 2 points.
[0] Deleting objects...
[0] Deleting grid...
[0] Creating grid...
[0] done!
[0] Go (round 8 of 10 )!
[0] 3
[0] 2
[0] 1
[0] Match Winner: Team gold
[0] Overall Winner: Team gold with 102 points.
[0] 0
[0] free kill core dumped a teammate! Boo! No points for that!
[0] Zane Niobe core dumped a teammate! Boo! No points for that!
[0] aG core dumped a teammate! Boo! No points for that!
[0] Slingshot core dumped a teammate! Boo! No points for that!
[11] free kill: BUG
[11] free kill: extra round
About the apparently delayed kick votes: They're just a combination of practically nobody participating in voting at all and unsuitably chosen timeout values. I divided them by three now and let them timeout rather than get accepted more often. No code bug.
So, if you want someone kicked, you should inform the others via chat about the reason.
So, if you want someone kicked, you should inform the others via chat about the reason.
Can I have details for this one?Was it that you tried kickvoting him, but the votes did not get through?
And this one?
Hmm, perhaps the game does not like user 7 
Code: Select all
[7] joda.bot: BUG chat bot (been here a while)
And this one?
Code: Select all
[7] iceman: come on z-man fix the bug please : BUG

My impression was that kick votes are not applied to chat bot controled players (but your previous post might explain those delays).z-man wrote:Can I have details for this one?
Code:
[7] joda.bot: BUG chat bot (been here a while)
Was it that you tried kickvoting him, but the votes did not get through?
I was not sure if the server created the chatbot without a name or if it was a regular player. I guess the first kick vote was rejected (as far as I can remember) - not sure if the second one succeeded right away, but the player was either kicked or left later.
After the first kick vote "failed", the vote could not be restarted for quite some time (which is probably on average a good idea
