Kil

Yosh X-D But ye given that code snippet it looks like the issue could probably be worked around then - just add some other check to force update the last active timer.

This should probably be enabled. There was a thread a while back about the lack of AFK kicker but apparently the built-in one has some issues where it can kick active people in some cases. Probably can't fix it tho seeing as it's mostly native and barely exposed to script.

They were the cause of the infamous freeze bug. They also blocked your weapons and character movement, even though the shells were client-side (so where they were on your screen was different to where they were on others), which was a major annoyance. So they interfered with the gameplay and also stopped you being able to game play period. Hah.

Check your PMs maaan.

Moved.

Hah you're all good epicelite. Some might need to lighten up a little :-P Though you're a little late to the party; this bug has been around since like the Closed Betas heh.

Heads up, one is in the works officially. "What does it do?" We'll see. Still a WIP, so it's subject to change.

Yeah I'd be interested to know what the reasons for it being disabled was. From what I remember, the problem I encountered with it was it wouldn't warn users in much of a user-friendly way - think it was it just gave really short notice for when it was about to kick you - in which case you've been static for a while and should be kicked anyway. The built in kicker is so native that it was barely customisable on the UnrealScript side.

I've removed the out-dated/invalid information from the post.

v51

It's just a usability issue, no advantage is really gained by anyone. You don't actually end up getting anywhere faster because of this, as you are warped right back to where the server tells you you are. Also only you perceive this speedy movement, everyone else still sees you correctly. Will be due to some problem with the client movement prediction when in particular cases of vehicle contact.

Uhhh.. isn't it All Out War?

Use the "stat net" console command to see your real ping.

viewtopic.php?f=13&t=74199

Yeah that's an obvious occurrence of the SBH bug (which should hopefully be resolved in the next patch). Stealth would be pretty shit if you could see it that far

There will be a match start delay in the next build that will give people time to load up on new map, which should let almost everyone in before the match begins. If you've made sure your drives are defragged and that your not running a bunch of hogging processes in the background, there probably is not really much else you can do except for hardware upgrades. We did used to have way faster load times at the expense of higher memory usage in Open Beta 1 when we built the game in a different way, but too many people still run on very low RAM that it ended up causing crashes for a lot of people, so we've had to revert to the slower load times but lower memory usage method. Too many people trying to get their dinosaur rigs to play new games :-P

Yeah it's in the next build.

Think this is the same deal as that bug where you can get a crazy amount of points by sandwiching with vehicles. That has been fixed for the next build so this should be fixed also.

That might be something that'd be good as a mutator (Not confirming or denying it happening officially tho - we'll see )

It's a per-player limit, like AT mines. Thus they do not count towards the team mine limit.

Both of those are already done/fixed for next build. (Though labels are not on Remote C4 as they work a bit differently now in regards to the limit so there isn't a need)

Mmm, server-configurable mine limits weren't intended for people to set them to ridiculous numbers like 80... @SirPanfried: Thanks for the new player perspective feedback. Renegade is definitely a game of depth so it's interesting to see what new people specifically get hung up on/find the most irritating so we can see where we need to try and address.

Post on their forums: http://elitekamikazeteam.com/viewforum.php?f=9

What maps have yous seen it happen/had it reported on? (And for any reports on which maps; also mention if it was crash to desktop or disconnect to menu)

It's in the centre of the long-path. So no it isn't.