Spring RTS Engine

Kill Everything: Just disables all of the gadgets and lets normal Spring rules apply.

We use this mode on our host but as soon as a com dies the player can't control it's units, so it seems to be 'com control' mode.

how does the exact option order sound ?

!setmodoptions gameendmode=killeverything ? doesn't work

deathmode=killall

ERROR




Team 9 (mrphil ) is without a Commander. Use ".luarules take" to take their units or share them a Commander.
<mrphil> mrphil gave everything to PepeAmpere[CZ].
<mrphil> mrphil gave everything to PepeAmpere[CZ].
Team 6 ([7uP]ShoX ) is without a Commander. Use ".luarules take" to take their units or share them a Commander.
No response from [7uP]ShoX for frame 42528
Player mrphil left
Lost connection to mrphil
Lost connection to player 14 (timeout)
<OMGPK> .take
Team9 (mrphil) has gone to robot heaven
<OMGPK> .luarules take
Team6 ([7uP]ShoX) was dominated
[Mephistos_Lair] mrphil has left lobby
No response from [7uP]ShoX for frame 42929
LuaUI::RunCallIn: error = 2, Update, [string "LuaUI/widgets.lua"]:1025: attempt to call global '' (a nil value)
LuaUI::RunCallIn: error = 2, IsAbove, [string "LuaUI/widgets.lua"]:1273: attempt to call global '' (a nil value)
LuaUI::RunCallIn: error = 2, IsAbove, [string "LuaUI/widgets.lua"]:1273: attempt to call global '' (a nil value)
LuaUI::RunCallIn: error = 2, IsAbove, [string "LuaUI/widgets.lua"]:1273: attempt to call global '' (a nil value)
LuaUI::RunCallIn: error = 2, IsAbove, [string "LuaUI/widgets.lua"]:1273: attempt to call global '' (a nil value)
LuaUI::RunCallIn: error = 2, IsAbove, [string "LuaUI/widgets.lua"]:1273: attempt to call global '' (a nil value)
LuaUI::RunCallIn: error = 2, IsAbove, [string "LuaUI/widgets.lua"]:1273: attempt to call global '' (a nil value)
LuaUI::RunCallIn: error = 2, IsAbove, [string "LuaUI/widgets.lua"]:1273: attempt to call global '' (a nil value)
LuaUI::RunCallIn: error = 2, DrawScreen, [string "LuaUI/widgets.lua"]:568: attempt to call method '├óÔé¼╦£├é┬Á' (a nil value)
LuaUI::RunCallIn: error = 2, AddConsoleLine, [string "LuaUI/widgets.lua"]:1085: attempt to call global '' (a nil value)
LuaUI::RunCallIn: error = 2, Update, [string "LuaUI/widgets.lua"]:1025: attempt to call global '' (a nil value)
5 errors deep in LuaUI, disabling...
5 errors deep in LuaUI, disabling...
5 errors deep in LuaUI, disabling...
5 errors deep in LuaUI, disabling...
5 errors deep in LuaUI, disabling...
5 errors deep in LuaUI, disabling...
5 errors deep in LuaUI, disabling...
5 errors deep in LuaUI, disabling...
5 errors deep in LuaUI, disabling...
5 errors deep in LuaUI, disabling...
5 errors deep in LuaUI, disabling...
5 errors deep in LuaUI, disabling...
5 errors deep in LuaUI, disabling...
5 errors deep in LuaUI, disabling...
5 errors deep in LuaUI, disabling...
5 errors deep in LuaUI, disabling...
5 errors deep in LuaUI, disabling...
5 errors deep in LuaUI, disabling...
5 errors deep in LuaUI, disabling...
5 errors deep in LuaUI, disabling...
5 errors deep in LuaUI, disabling...
5 errors deep in LuaUI, disabling...
5 errors deep in LuaUI, disabling...
5 errors deep in LuaUI, disabling...
5 errors deep in LuaUI, disabling...
5 errors deep in LuaUI, disabling...
5 errors deep in LuaUI, disabling...
5 errors deep in LuaUI, disabling...
5 errors deep in LuaUI, disabling...
5 errors deep in LuaUI, disabling...
5 errors deep in LuaUI, disabling...
5 errors deep in LuaUI, disabling...
LuaUI::RunCallIn: error = 2, Shutdown, [string "LuaUI/widgets.lua"]:234: attempt to call global '' (a nil value)
Disabled LuaUI
Type '/luaui reload' in the chat to reenable LuaUI.
===>>> Please report this error to the forum or mantis with your infolog.txt
Lost connection to [7uP]ShoX
Lost connection to player 11 (timeout)
User exited
Path cache hits 434 29%
Path cache hits 1178 14%

What was wrong about BA 6.21(besides of the knows issues that will not be fixed)?
I thought it was done..

Gota wrote:What was wrong about BA 6.21(besides of the knows issues that will not be fixed)?
I thought it was done..

Did you look at the changelog?

Just wondering why it forces you to give all your units when your com dies. I hear this is optional and default. However my question is why the feature was put in. I don't recall having a problem with the way it was before.

That infolog is caused by the ground decal dangling pointer issue, disable ground decals.

You don't, Noize does. BTW, this is General Discussion, not BA Discussion.

I'm fully aware this is general discussion. Before I draw my conclusion about BA, I'd like to hear what other people have to say.

Then discuss it in the BA thread. THis is Spring General DIscussion, not BA General DIscussion.

Spring is about a lot more than BA, mmmmmk?

If you say so

As a matter of fact, I do.

viewtopic.php?f=14&t=15346 Is what you are looking for.

oh well, I found the feature was annoying enough to post here. This feature boggles my mind.

BA was designed to be played 1v1, com ends. Since people love team games but com ends fails in those Noize asked for a different behaviour which you can see in action now, allowing people to play com ends in team games without lost coms jeopardizing the whole game. You're out but your contribution to the team stays.

Oh, so it is only on com ends? And continues works the same is it did before, right?

No, it's on continues, Spring itself kills all your units on com ends, we can't prevent that. It's a separate mod option.

It makes for a better game imo. Now if only Noize would make dgun limit fail to work in BA.

All this whining about the proper Game end setting did me remind of a post Stonewolf made ages ago on the TAU forums:

Stonewolf wrote:You are such whining girls it's not even funny. Playing TA with "rules" is undoubtably the most pathetic thing this community has ever had to endure ('no EMG' in the old modem days being a possible exception, more of a tech issue).

Though it's not what we're talking here, when I see rules like "no nukes", "no LRPC", or a worse offender "15 mins build time", etc., it just makes me want to puke, cry, and go play Quake. You hardly see "no rockets, no quads" in those games.

As for Commander Rushing, if you're playing on a small map with Commander Dead = Continues then that's your fault. IMHO it is an entirely valid and reasonable tactic to build a factory, walk over to meet the other Commanders, and start D-Gunning. Their Commander can walk back to your start. Or around. Or build a factory and RUN from his initial position. That the TA herd forces passive tactics in these situations is not to the community's credit.

If you can move and operate that unit, that unit should be under whatever operational control that player wants. Everything else is a cop-out.

I don't whine and cry like a little girly girl when I lose, or even if a Commander comes into my territory. I'm just pissed I didn't think of it first. It's up to me to run away, try to find his base, and return the favour.

It's pathetic, truly and completely pathetic, to see people whining about "Commander Ethics" in a game devoted to the complete and utter destruciton of all opponent Commanders and everything they have ever built. For crying out loud, this is a game based on trying to CAUSE EXTINCTION and you're asking "but did he do so HONOURABLY?"

There is no cheap tactic that cannot be countered somehow, Flashing, Slushing, Napping, Rushing. They might be annoying, but they're not the end of the world forever.

So basicly. You guys have to understand:

YOU ARE THE COMMANDER

WHEN YOU DIE, YOU ARE OUT OF THE GAME

But for all the pussy's out there you can still play old style Game Continues on Kill Everything. Please note that this is a very bad Spring community habbit.

NOiZE wrote:YOU ARE THE COMMANDER

WHEN YOU DIE, YOU ARE OUT OF THE GAME

Splattering this on your loadscreens warrants a 6.32 in itself.