Commando Archive

But I love all you pre-patch guys, and even the ones in your ranks who actually enjoy the profession.

Sorry about the thread title, I just came across another post that was a generalization that equates "griefing" to "commando", and I wanted all of you to remember that most of us know the difference, and it's not your profession, but the PKing wannabes (err, not that there's anything wrong with being a PKer, but you know what I mean). We also know that not everyone with a FT or LLC in their hand is a "griefing exploiter" just something called "the right tool for the job at hand" in certain circumstances.

My hat's off to you guys for always remaining a class act when there was no love, and when you were the flavor of the month.

I can't really say I've shared your pain, but as a BH who earned a decent amount of xp with a pre patch LLC, and who currently takes screencaps of his combat window for laughs to look at 11 "you shoot at %%%% and miss" messages in a row with his "ungodly overpowered way unfair" toy, I get just as defensive for you guys every time I see a flamethrower complaint as I do for every eyeshot complaint.

It's nice to see the DEVs sticking to their guns, and holding to the fact that balance =/ all skills being the same, but rather balance = different proffessions have different counter checks.

So to all of you that I said "I hope things improve for you" to in July, and "Congadulations" to in August, I'll say now "I'm glad things are the way they are, and if you toast me with a flamethrower please kick me for standing perfectly still so you don't miss and not spending the whole .5 seconds to run out of range!"

If they fixed the PvP system there would be less crying about griefing. Last night I experienced one of the lamest PvP battles I have ever participated in. Basically a group of rebel commandoes attacked Bestine. What happened? They set everyone on fire, and everyone else set them on fire. Both sides killed themselves intentionally to avoid the burn, and then ran right back to setting each other on fire again. I killed a lot of the commandoes knowing about their ranged weakness, but nonetheless, it was an extremely retarded battle. Heh, if we have to resort to suicides and instant-spawns, I'd rather go play UT.

If they created a time-out period in which after death one cannot participate in PvP again regardless of wounds, then there really wouldn't be a point to griefing, seeing as a simple DB would remove the player from action for awhile, with or without wounds.

Vallimar says:

If they created a time-out period in which after death one cannot participate in PvP again regardless of wounds, then there really wouldn't be a point to griefing, seeing as a simple DB would remove the player from action for awhile, with or without wounds.

all I can say is, "bump."

And this, actually: This is the best Idea I've seen on any of these forums in a long time. It makes it so that your LIFE is actually worth something in PvP, and, even if you're cloned nearby, 1 DB and you get to watch for the rest of the battle. This will improve team dynamics, by requiring that groups that want to win keep their members alive, and will, imo, make the game much more interesting when it comes to group PvP tactics. Say a time limit equal to the amount of time for TEFs to go away.

This would also go a long way towards solving one of the more annoying cheese/exploits I've run into: the combat medic TEF AOE poisons. He can poison til he dies, still, but now he cant just spam it until everyone in the city he is terrorizing decides the game isn't fun and logs, because no matter how many times you kill him, hes right there poisoning you again.

Athein,

Commando; Rebel Master Sergeant

Tarquinas

Well that's a nice idea. Though I just think the FP loss for death in PvP should be significantly greater. Say like 500-1000. 1 or 2 and the average person is probably gonna not fight for awhile.

I believe one of the potential upcoming changes to the PvP system is that when you get DBs by a PC, you spawn at the second closest cloning facility, meaning you get relocated away from your battle.

This will really help the quake-like frag fest that PvP has become lately.

Despite the fact that I don't PvP unless unavoidable (I just don't like PvP, it's not why I play the game, though I do accept it as a PART of the game), I think the timer, with all I've read about the game, is a wonderful idea.

I also think they should not only turn insurance and the need to recorver your body, I think they should make it even more expensive to insure items. Give us a reason to fight smarter, think harder, and use what little bit of tactics the game play allows to us.

Then, I think PvP would be worth taking part in.

Who knows, maybe someday, I'll change my mind.

I think the timer is a good idea. An alternate solution that I think might be better is add wounds any time you die from a PC. Maybe double the normal uncloned amount and a considerable amount of BF too (this would be regardless of whether you cloned). Make this penalty increase as well if you get killed multiple times within a given period. The problem that I think the timer would have is that large PVP battles would be over in about 5 secs. Having the wounds increase would give more time but would also prevent the unending cloning facility battles that usually take place.

I think that increasing the insurance costs is a bad idea. I dont mind the having to get your body but as it is long PVP fights are over in 2 shots. Having high insurance costs would just keep anyone from using it. I think if anything they should make the costs for insuring an item a fee that insures them for a given period of time (say you insure your gun when you die you wont have to go get it for 3 days or something).

Now is setting someone on fire and intentionally leaving them there considered "griefing" at all times? I ask this because when I was camping outside of bestine the other day I set someone on fire and he started to run up the hill to the imperial mission terminal thing, now I wasn't going to risk myself running up there to finish the job and incap him and DB him, I couldn't, it would have been death for me to do so....so what was I really suppose to do about this? Should I have gone up the hill and risked my own life to put the guy out of his potential missery and DB him before he got a whole bunch of flame wounds, or did I do the right thing in saving my own skin? My intention was not to "grief" him, it was just so that I wouldn't die myself.

The trouble with revenge tef is two parts

If you have a revenge tef active and I heal you, I inherit that tef as well. Revenge tef's should not propagate. They should only apply to the person that did the DB.

If I have an aoe attack and use it against my revenge tef, before the damage for the aoe is applied, all those in range get a tef to me and I them. AoE attacks should not work in a revenge tef situation.

If this was the case, I could Db Bob and you could heal me after without risk of a person you know nothing about attacking you from a covert status. Only I would have to worry about Bob. While I worry about Bob coming back and maybe miss him, people around me would not have to worry about Bob using an AoE attack to all.

The trouble isn't the revenge tef, but how it can transfer, how it can be applied to those close to you with an AoE attack.