BUG cries on Bugfarm Fortress and Sumo

[MaZuffeR]

Code: Select all

[15] MaZuffeR: BUG: bashusr went through my wall
[8] (): BUG someone went through a wall

bashusr died early, so I can probably do something with this recording.
Edit: but it didn't happen. Maz was center on his team, souledout, who the kill was credited for, second level wingman. () was between them. bashusr[zop] dged in the enemy team, went around maz and (), didn't try to go around souledout, tried to through the gap of the initial grind and died there. Nothing unusual, if anything, this was a clientside extrapolation bug.

According to PsYkO and bashusr[zop] it was me who went through bashusr's wall, but to me it looked like bashusr going through mine.

[Z-Man]

Maz: it may have looked like that on the clients, but the server log shows no indication of anything fishy for this event. Does anyone of you nave a recording?

Code: Select all

[1] Vanhayes: WTF
[12] [fe]Radian: takes glasses of...hands em to van
[1] Vanhayes: BUG
[15] Gusbo T.Jam esq: wow
[10] Ocram: Oo
[4] ghableska: lol
[5] chat.bot: CHEATER
[1] Vanhayes: Cyclr went threw a wall

Yes, this one was real. Cycle'o'death and one of them Psykos collided without anything happening. When Psyko arrived at the collision point, Cycle'o'death had already been there, but with a future timestamp. Cylce should have been set to a position before the collision so his rubber could try to save him, but he wasn't placed back far enough because the floating point tolerance value, for some reason undetected for a looong time, is set to 10^(-16) in the game files. That's a good value for doubles, but definitely not for floats. I fixed it, hoping there'll be no bad side effects. Floating point precision is slippery terrain.

[Z-Man]

Code: Select all

[2] SuBlImInAl.FreQ: BUG: macboy is an asshole, scroll up

That's not a bug And I don't really care what random players say about me, at least not to the extend that I'd ban someone for a single statement in the heat of battle.

Code: Select all

[0] Pez core dumped ShadowHunter for 2 points.
[0] Team blue was awarded 10 points for being last active team.
[0] Winner: Team blue
[3] ~*SP*~oO.k3nNy: LOL!
[16] ShadowHunter: what
[1] route: impossible
[16] ShadowHunter: i am inside
[9] Goodygumdrops: nice one pez
[16] ShadowHunter: and
[3] ~*SP*~oO.k3nNy: y
[5] Pez: that was weird
[3] ~*SP*~oO.k3nNy: BUG
[1] route: we found a ... BUG!!
[3] ~*SP*~oO.k3nNy: he went through wall

Analyzing it. I suppose Pez was the one going through a wall?

Code: Select all

[6] ~*SP*~joda.bot: BUG team transfer put me into 2nd position, should I not be on the outside ?

I don't have any team change of yours on the radar. Maybe the names and colors of the teams switched?

Code: Select all

[0] Slash core dumped teammate ~*SP*~joda.bot! Boo! No points for that!
[0] Ashitaka core dumped teammate [Hg]AdY-LuCiFeR! Boo! No points for that!
[11] received logout from 11.
[11] [Hg]AdY-LuCiFeR left Team gold.
[11] Killing user 11, ping 0.29897.
[0] Twisted Nerve committed suicide.
[0] Slash core dumped [Hg] Rain for 2 points.
[1] Twisted Nerve: yay
[6] ~*SP*~joda.bot --> Teammates: BUG teleport ? slide ?

If this is about your death, no. The center just turned into your direction, and your turn command came 0.009 seconds too late.

[gnorty]

I wonder how many of the "I went inside" wall crossings are to do with something different?

it always seems to happen when a) someone 180s back along their own wall and b) someone then grinds the first side of the created tunnel.

so what is the possibility of the scenario pictured below? depending on camera angles etc, it could look a LOT like a wall crossing.

[Z-Man]

Gnorty: I think all bugs of this kind are fixed; the last false going through wall cry wasn't of the described kind, as far as I could tell.

The Pez vs ShadowHunter one was real, the plot is attached. The line ends are the places of the cylce as ShadowHunter died. ShadowHunter would have died anyway, but legally, he'd have taken Pez with him.
It was another "future walls" problem, ShadowHunter passed Pez's future wall twice, and the second time, the code that should save Pez's life, using up rubber, didn't put him on the right side of Hunter's wall.

For the upcoming release and the code CVS Fortress will run, I'll just disable the "try to save player's life" code and kill the owner of the future wall outright. That's the usual outcome anyway and it is the safest thing to do. For the next release, I'll try something smarter.

[gnorty]

recording of odd warping I have been seeing on sumo lately. not sure about fortress, it is not so obvious there, and not so relaxed at start to look for it.

In essence for some reason, when playing AIs the bot warps madly at the very start, but is 100% OK ofter that. happens in perhaps 90% of rounds.

[gnorty]

this time WITH the attachment!

[Z-Man]

Thanks, it's a clientside bug, it is falsely ignoring syncs. I noticed it as well but didn't bother. I don't think human players can abuse this, only the AI, and it only does that if you mess with aiplayers.cfg, which I did on sumo. I'll have the bug fixed for 0.2.8.3 and reconfigured the sumo AI in the meantime.

[joda.bot]

Code: Select all

[6] ~*SP*~joda.bot: BUG team transfer put me into 2nd position, should I not be on the outside ?

I don't have any team change of yours on the radar. Maybe the names and colors of the teams switched?

That might be, but AFAIK I had a pending team change request, but could not change teams. Then I was moved to the other team (other players too AFAIK), but did not get a position on the outside.

But it's been quite a while and I guess I was tired at that time, so I might have mistaken many players shuffeling and a color change for it.

[Z-Man]

There weren't any team change or pending team change messages about you anywhere near the bug cry So it's either the tired theory or the team name change, which I recon would happen more often if it was possible.

Code: Select all

[0] 3
[0] 2
[10] BelAir: yea..
[6] bashusr: that's about right mk
[0] 1
[0] 0
[0] Doobie core dumped teammate BelAir! Boo! No points for that!
[13] Durka |EFP| plays for Team blue.
[0] [BK]Neochater committed suicide.
[0] flea |DpG| core dumped `~*x==BLUNT== for 2 points.
[0] Manta core dumped Doobie for 2 points.
[0] `~*x==BLUNT== core dumped flea |DpG| for 2 points.
[0] bashusr committed suicide.
[0] Team gold was awarded 10 points for conquering the enemy base.
[0] Winner: Team gold
[14] joshERR plays for Team gold.
[0] garispyder|FcK| core dumped mkzelda for 2 points.
[0] mkzelda core dumped garispyder|FcK| for 2 points.
[6] bashusr: half our team needs to be kicked
[0] Deleting objects...
[2] mkzelda: whoathat explosion
[0] Deleting grid...
[13] Durka |EFP|: not me
[6] bashusr: they're coring each other left and right
[0] Creating grid...
[2] mkzelda: happened on the other side of the wall
[10] BelAir: especially durka
[10] BelAir: just kidding
[13] Durka |EFP|: ?
[3] `~*x==BLUNT== --> Teammates: sorry my display settign got screwed...
[13] Durka |EFP|: lol!
[2] mkzelda: absolutely impossbile
[2] mkzelda: BUG: Zman?
[5] Doobie: blunt grind
[0] Go (round 2 of 10 )!

What was that about? Where Doobie and Belair on different sides of the center? Edit: no, they weren't. I looked at every death, all seemed possible enough. So what was it?

Code: Select all

[0] Lucifer core dumped Pyr0TeK for 2 points.
[0] Team gold was awarded 10 points for being last active team.
[0] Winner: Team gold
[1] Pyr0TeK: heheh
[3] Durka |EFP|: ?
[2] Lucifer: luck
[1] Pyr0TeK: odd indeed
[2] Lucifer: :)
[2] Lucifer: BUG
[2] Lucifer: just thought z-man would want to see that plot

Will look at it, it's early in the recording.
Edit: Ah, it's the merciless future wall owner killing code in action. Lucifer really was ahead of Pyrotek, put Pyrotek's simulation was more advanced when they met, and lacking a secure rollback mechanism, Pyrotek was eliminated.

[Z-Man]

Code: Select all

[0] Emlock core dumped [fe]kinked for 2 points.
[0] [fe]kinked core dumped lolsul for 2 points.
[3] lolsul: how did I end in there?
[3] lolsul: BUG

Ah, this may be what Gnorty was talking about. what basically happened here was this:

[Z-Man]

I'm ignoring joda.bot's cries on behalf of jjbean (yes, the trail stops when you use your rubber, sitting in front of a wall) and "Team Gold"'s wall passing bug, unless joda says they are important enough.

I'm also ignoring Lucifer's lag BUG, unless it was a special, singing and dancing, kind of lag.

Code: Select all

[4] wrtlprnft |mbc|: BUG the /msg code is broken again

A little more specific, please The basic functionality (msging, preference for exactly matched names, conversion to lowercase) works for me.

[Lucifer]

the lag bug I called was one of those long server hangs. But I asked afterwards and the others told me it was just me. So, I guess it's my own problem, heh.

[wrtlprnft]

Code: Select all

[4] wrtlprnft |mbc|: BUG the /msg code is broken again

A little more specific, please The basic functionality (msging, preference for exactly matched names, conversion to lowercase) works for me.

Just for the record:

19:24 <wrtlprnft> #later tell z-man never mind, read the next BUG... I was trying to msg the user "me" and it said too many matches found, which isn't supposed to happen anymore. It took me a while to realize that "me" already left

The next BUG cry was something like "BUG ignore the previous one, messed things up".

[Z-Man]

Ah, I missed that one.

Lucifer: all right, ignoring it.