Spring RTS Engine

In the past 7 games, early ingame, there has been alot of ragequitting.
I am making a suggestion that ragequitting must have a reason for otherwise must be penilised. A registry system showing
Games Played, Won, Lost, spectated, Disconnections and player premature exits should be implimented, to show what players should really be apart of a game if someone wants a really good game of those not known to ragequit or can stabilly play a game.

This cleans up gameplay a bit and grants those who want a good game.

Thoughts?

Well, you never know. It wouldn't be correct, because every time I have gone into a battle and said "This should be 30 mins or less" I end up being wrong, and it turns into a giant stalemate or something, then I have to quit because of a RL reason for hoping the battle would be 30 mins or less.

Any automatized system just won't work, ragequitters should be remembered by hosts, the way it is now.

More advanced banning options for hosts is needed though.

The solution is... oh i wont bother

I dont know about anyone else but I've been crashing like 2 out of 3 games lately, I guess thats sort of besides the point...but damn..it sure sucks.

PRO_rANDY wrote:The solution is... oh i wont bother

Let me say it ,


here it goes....






.......


















.....










Play 1v1.

People will just create new accounts.

Ragequitting is control-a control-d. Not just losing connection or having to give your stuff (though having to give your stuff often makes people go 'I CANT HANDLE THIS *RAGE*')

The spring community is pretty small. There are dozens, hundreds of ways you can stuff up a game. It is a gentlemans agreement only that stops every game devolving into a comdroping comblowing boy-pile fuckfest. Whats really needed is more of an article on etiquette than anything else, not that anyone would read it...

Snipawolf wrote:Well, you never know. It wouldn't be correct, because every time I have gone into a battle and said "This should be 30 mins or less" I end up being wrong, and it turns into a giant stalemate or something, then I have to quit because of a RL reason for hoping the battle would be 30 mins or less.

Don't join battles if you don't have time to play them...

or... play 1v1

If the opposition has annihilated your base and you ctrl-a ctrl-d that is not a ragequit, it is just a quick way of starting a new game so they don't have to search for your mines. An automatic system would not be able to distinguish between a ragequit or a surrender. The community is small enough to remember repeat ragequitters.

Unless you are the last player alive, its generally better to give your stuff up than decide for your team when the 'we've lost' point is.

Though, there is a difference between 'oh, i thought the game was over' annd 'GOD DAMN NOOBS! WHY CANT YOU HOLD THE LINE WHILE I PORC ADV SOLARS! ARGH I CANT STAND PLAYING WITH NOOBS!'

Hellspawn wrote:

PRO_rANDY wrote:The solution is... oh i wont bother

Play 1v1.

At least one question where the answer isn't "use Lua"

lies lua cud stop rage quitting my sending a trojan to the person who rage quit :} im sure lua could do that

cos lua is the answer to all of lifes problems

Otherside wrote:lies lua cud stop rage quitting my sending a trojan to the person who rage quit :} im sure lua could do that

cos lua is the answer to all of lifes problems

+1

Otherside, stfu.

back in my day, noone ragequit evar

now get off mah lawnz

Which mod is producing the most rage quits?

Maybe therein lies the problem?

LOL LUA can do anything, LUA saves the world, LUA is jesus.

dont play with BA with noobs

Disable self-destruct perhaps?

RavingManiac wrote:Disable self-destruct perhaps?

yea cos that would help