http://beta.armagetronad.net/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
BUG cries on Bugfarm Fortress and Sumo
Moderator: Z-Man
Code: Select all
[2] Mr. Bougo: BUG, passed trought newbÎe's wall
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
Code: Select all
[1] whatup: i got points after i died
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
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.
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.
This happened quite regularly after each round ended and before the next one started. This happened on Bugfarm Fortress btw.
You've gone too far, turn back!
kk didnt knew that i thought i was gettin young againz-man wrote: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
[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
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
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
You've gone too far, turn back!
Saw the same colour change, but this time Gold turned blue, maybe its the players color (i have blue defined).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
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
- Reverse Outside Corner Grinder
- Posts: 1679
- Joined: Wed Jan 04, 2006 4:42 am
- Location: 0x08048000
- Contact:
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 viewmadmax 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?
There's no place like ::1
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
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
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: ****
Code: Select all
[8] ~*SP*~joda.bot --> ~*SP*~joda.bot: BUG: ashitaka's colors are nearly invisible
Code: Select all
[2] ghableska: BUG team name changes briefly to "ghableska" between rounds
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
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
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.[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
You've gone too far, turn back!
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.z-man wrote: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
[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 [...]
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.
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.