BUG cries on Bugfarm Fortress and Sumo

wrtlprnft · Post by **wrtlprnft** » Thu Jun 08, 2006 8:14 pm

omega wrote:ty zman u the dude!

where can i get 0.2.8.2. On downloads gcc its 2.8.1.1.

can i have a link pls

http://beta.armagetronad.net/

Website · Post by **Z-Man** » Tue Jun 13, 2006 2:12 pm

[2] Mr. Bougo: BUG, passed trought newbÎe's wall

Thorugh the last 2.5 meters of it that are cut away for cycles that have used up all of their rubber (as dead newbie had here) not displayed correctly on your 0.2.8.1 or earlier client, yes. That's the effect that makes chasing your own tail less dangerous. Upgrade to 0.2.8.2 and your display will be correct.

Website · Post by **Z-Man** » Tue Jun 13, 2006 4:59 pm

Code: Select all

[16] ~*SP*~oO.k3nNy: AAAH
[16] ~*SP*~oO.k3nNy: BUG
[11] MACRO: hey hey hey no  fowl language here
[1] Ketty: :)
[16] ~*SP*~oO.k3nNy: vote system doesnt work again

No, it works perfectly

You weren't online for long enough. You need to be on the server for five minutes, and you were there for about 3 or four at the time of the cry.

Code: Select all

[1] whatup: i got points after i died

Not a bug. When someone gets trapped by your wall, you still get points.

Code: Select all

[0] ~*SP*~ Xell core dumped [fe] Ossi for 30 points.
[0] [fe] Ossi core dumped ~*SP*~ Xell for 30 points.
[0] Match Winner: [fe] Ossi
[0] Overall Winner: [fe] Ossi with 600 points.
[0] whatup was awarded 60 points for conquering [fe] Ossi's base.
[0] whatup was awarded 60 points for conquering ~*SP*~ Xell's base.
[1] whatup: wow
[1] whatup: i win
[1] whatup: come on
[1] whatup: BUG

No, you were too late, Ossi reached the limit before you. There was another one like that.

To those who weren't seeing the zones: what client version were you using? There was a known, old bug on the client side a while ago that should be fixed now. I don't think you guys have a clientside recording?

Due to the recording bug, all fortress cries of last week are mostly useless. Sorry, I'll need to ignore them.

Van-hayes · Post by **Van-hayes** » Wed Jun 14, 2006 1:19 am

http://img83.imageshack.us/my.php?image ... t952cs.png
This happened quite regularly after each round ended and before the next one started. This happened on Bugfarm Fortress btw.

oO.k3nNy · Post by **oO.k3nNy** » Wed Jun 14, 2006 3:08 am

z-man wrote:
Code: Select all
[16] ~*SP*~oO.k3nNy: AAAH
[16] ~*SP*~oO.k3nNy: BUG
[11] MACRO: hey hey hey no  fowl language here
[1] Ketty: :)
[16] ~*SP*~oO.k3nNy: vote system doesnt work again
No, it works perfectly You weren't online for long enough. You need to be on the server for five minutes, and you were there for about 3 or four at the time of the cry.

kk didnt knew that

i thought i was gettin young again

Website · Post by **Z-Man** » Wed Jun 14, 2006 6:33 am

Vanhayes: what "this"? The overlap of console and score table, the unbalanced teams or the... strange team name? I didn't know this feature was already active

Van-hayes · Post by **Van-hayes** » Wed Jun 14, 2006 7:00 am

Heh I just saw this new Team name option and put something in. As for what "this" is, It's when one round ended and before the new round ended, maybe like 2 seconds at most, the team I was on would take on my colour scheme and team name. No one else said they saw this but I wasn't sure because it went by so fast.

This is a SS of what it should have looked like, and did look like untill the end of rounds.

http://img128.imageshack.us/my.php?imag ... t948pr.png

Website · Post by **Z-Man** » Wed Jun 14, 2006 7:26 am

Ah, that's probably a client bug

The server doesn't know about the team name, and it gets updated temporarily on your client only and overwritten by the official name/color from the server. I'll assign this to Joda.

madmax · Post by **madmax** » Wed Jun 14, 2006 12:05 pm

Van-hayes wrote:Heh I just saw this new Team name option and put something in. As for what "this" is, It's when one round ended and before the new round ended, maybe like 2 seconds at most, the team I was on would take on my colour scheme and team name. No one else said they saw this but I wasn't sure because it went by so fast.

This is a SS of what it should have looked like, and did look like untill the end of rounds.

http://img128.imageshack.us/my.php?imag ... t948pr.png

Saw the same colour change, but this time Gold turned blue, maybe its the players color (i have blue defined).

Another thing, i 'cried' for a bug: the Enemies/friends counter was wrong, there were two players on blue and one on gold, but the meter showed (when following a blue player) 2 enemies.
On the other versions those counters changed according to the player you were following, right? This still happens with the new Alpha?

wrtlprnft · Post by **wrtlprnft** » Wed Jun 14, 2006 1:17 pm

madmax wrote:Another thing, i 'cried' for a bug: the Enemies/friends counter was wrong, there were two players on blue and one on gold, but the meter showed (when following a blue player) 2 enemies.
On the other versions those counters changed according to the player you were following, right? This still happens with the new Alpha?

The old behaviour with the meaning of the enemies/friends meter changing according to the player you're watching after you're dead was confusing to new players, so I changed it to always display it from your team's view

Website · Post by **Z-Man** » Fri Jun 16, 2006 11:32 am

Code: Select all

[1] New user: 1
[1] whatup renamed it's team to whatup.
[1] whatup entered the game.
...
[0] Armagetron renamed it's team to armagetron.
[0] Armagetron entered the game.
...
[1] whatup wants to play for armagetron on the next respawn.
...
[2] New user: 2
[0] whatup was awarded 60 points for conquering armagetron's base.
[2] |Hg|Hay-Lin Reg renamed it's team to |hg|hay-lin_reg.
[2] |Hg|Hay-Lin Reg entered the game.
< next round starts>
...
[0] whatup plays for armagetron.
[0] Armagetron left armagetron.
[0] whatup renamed it's team to whatup.
[1] whatup: BUG
[1] whatup: TWO WHATUP EAMS
[1] whatup: BUG
[1] whatup: TWO TEAMS ARE CALLED WHATUP

Well, you switched teams to armagetron on purpose, leaving your own team. Empty teams take some seconds before they effectively deleted, so every time you do such a thing, you end up with one team too many. In this special case, joining an AI team caused the team to be renamed for your right away. It's not a bug, unless the empty whatup team was left around for several rounds afterwards.

Website · Post by **Z-Man** » Mon Jun 19, 2006 10:23 am

Code: Select all

[0] ~*SP*~PsYkO was awarded 30 points for conquering nemostultae's base.
[0] nemostultae was eradicated by its collapsing zone.
[16] nemostultae: er
[10] ~*SP*~PsYkO: i got nemo's :D
[16] nemostultae: what
[16] nemostultae: why did it kill me
[16] nemostultae: BUG last round
[16] nemostultae: I was the last surviving in my zone and I left, it collapsed, and I died

PsYkO touched your zone in passing, was the last player to do so, and hadn't died at that point. Maybe there should be a timeout?

Code: Select all

[11] whatup: is that ur phone numbe
[0] whatup committed suicide.
[11] whatup: ****
[11] whatup: CHATBOTS
[11] whatup: BUG:
[11] whatup: ZMAN, THE CHATBOTS SUCK
[11] whatup: MAKE THEM MORE INTELILGENT
[11] whatup: ****

NO. EITHER CHAT OR PLAY.

Code: Select all

[8] ~*SP*~joda.bot --> ~*SP*~joda.bot: BUG: ashitaka's colors are nearly invisible

Why? Too dark? This would be a clientside thingy.

Code: Select all

[2] ghableska: BUG team name changes briefly to "ghableska" between rounds

Another one of those clientside bugs in 0.3.0_alpha.

Code: Select all

[10] Vanhayes2 entered as spectator.
[10] Vanhayes2: BUG
[0] User 8 timed out.
[8] Vanhayes left Team gold.
[8] Killing user 8, ping 0.162753.
[0] Vanhayes2 renamed to Vanhayes.
[10] Vanhayes: my client crashed but vanhayes was still here

Well, the server can't know your client crashed, so it's assuming the old client with the old player is still there. What client crash, btw?

Code: Select all

[0] 2020 core dumped G5 for 2 points.
[6] G5: ???????????
[6] G5: I just died ...
[6] G5: I didnt turn ... no wall ... BUG

You were in contact with 2020's trail not too far ago, that's why he got the credid. The reason of your death was a small kink in the wall of your teammate from an adjust to a wall that was gone at that time.

Van-hayes · Post by **Van-hayes** » Mon Jun 19, 2006 5:56 pm

[10] Vanhayes2 entered as spectator.
[10] Vanhayes2: BUG
[0] User 8 timed out.
[8] Vanhayes left Team gold.
[8] Killing user 8, ping 0.162753.
[0] Vanhayes2 renamed to Vanhayes.
[10] Vanhayes: my client crashed but vanhayes was still here

The client crashed when I was chatting, I'm not sure why it happened, but it has happened a few times so far. I am just typeing then it closes.

Post by **dlh** » Mon Jun 19, 2006 6:27 pm

z-man wrote:
Code: Select all
[0] ~*SP*~PsYkO was awarded 30 points for conquering nemostultae's base.
[0] nemostultae was eradicated by its collapsing zone.
[16] nemostultae: er
[10] ~*SP*~PsYkO: i got nemo's :D
[...]
PsYkO touched your zone in passing, was the last player to do so, and hadn't died at that point. Maybe there should be a timeout?

He clipped my zone just barely and drove away to attack another zone. Would I have had to stay in my zone for the remainder of the round to have not been killed? If yes than I think there should be a timeout.

Website · Post by **Z-Man** » Mon Jun 19, 2006 8:58 pm

Vanhayes: we had such a chat-crash in some of the betas of 0.2.8, but it should be fixed now. Could you try to create a recording?

Nemo: done. Unfortunately, it will only get active on Bugfarm after 0.3.0 is out; Sumo is running from the 0.3.0 branch currently, and the addition was made to 0.2.8 and merged back to the trunk.