flamethrower bug

[Silent Profile]

sorry if this is being talked about somewhere else.

Since the server moved the flamethrower bugs out occassionally and kills random people all across the maps.
i've seen it on village and on beach so far. didn't happen on depot today though.

I was wondering if it would be possible to limit them to zero.

With ff on people usually just team kill and drain with them anyway.
Only about three times a month does someone actual use it effectively.

What's worse maria and blatto use it a lot and they don't seem to understand why they shouldn't.
Either they don't read chat, don't care, or don't speak english.

[magus]

racist

[W0lfy Profile]

You can actually just run into most corners and flame the wall. It will kill everyone

[Silent Profile]

Well don't tell ppl how to do it....

[Tragic Profile]

I agree with silent, the flame thrower is quite annoying lately. Seems to happen randomly as well.

[xdeadeye1]

right now im warning then / kick then / ban for flame thrower.. till its fixed.

['L0, Profile]

I've dealt with this bug on my mod for good 2 weeks a while ago. I figured it out after sh!t load of frustration that it was antilag related. I solved it by rewriting flamer code completely but that's not an option since shrub is closed source.

[Jun1oR]

antilag or unlag related? the server has antilag disabled and uses unlag instead.

['L0, Profile]

I personally call it the same, probably just 1.0 mentality. And yes in this case, unlag related. Situation in my case was a little more ambiguous, since same problem appeared when I ported unlag 1.2 and antilag from 1.4 (was to 1.0 source). Problem with unlag was that's it's primary quake 3 based and didn't really consider something like flamer, while problem with 1.4 antilag was that 1.0 flamer code is different so only way to solve it was to rewrite flamer code and if memory serves me right (was 3-4 years ago) also tweak antilag a little.

There's no saying what could be without testing or seeing a source code. But in my case quite similar problems derived from antilag/unlag till flamer code was addressed. I guess only real way to test it, is to temporary disable unlag and run around with flamer or something but I doubt most of us eu's will be happy with it.

If Martin comes around, he can say more about it since he ported/rewritten flamer code first and I've used his changes for base if I recall right (been a while ago).

[W0lfy Profile]

If it's the unlag, why was there no flamer issue on the old server?

[xdeadeye1]

I messaged Martin regarding this. he hasn't gotten back with an answer yet.

[MAN-AT-ARMS]

The only reason I can think of that it didn't happen before is that the new server is running on 64-bit and the old wasn't. Not sure.

I temporarily disabled unlag code to see if that is actually the reason for the bug.

See if that does anything.

[W0lfy Profile]

The bug is still there even with unlag off. Tested it myself and saw another player do it. Can't you just ban the weapon altogether? It's a noob weapon with very little use anyway.

[magus]

turning unlag off has made no difference to the flame bug, please re-enable it- thanks.

[pinkname Profile]

Imo banning the flame is not a real solution. Flame has its uses, even if most ppl can' use it properly. But it can be said about any weapon... :X Flame can be quite good, eg. on village: it's quite "essential" when defending tavern or upper hole.

I never met this bug before, hope it can be solved.

J.