seriously people calling /explode dishonorable is proof enough of what i've been saying about how stupid these honor argument is.

many cultures have for centuries concidered it more honorable to take your own life than die at the hand of an enemy, or risk capture. (best exemplified by the japaniese sebuku).

now lets start with how /explode doesn't ruin anything:

1. the BP mission: if your target /explodes kill something else (say an NPC sice the don't /explode)

2. not getting the kill: what good is one kill anyway, if you realy want the kills i doubt your story about "being attacked, [unprovoked] by someone repetedly"

this is just like the "junning should be fixed by making it harger to jump". only you know, that could be passed off as a problem.

Lord Q, The change will only affect the handful (3 that I know of) of people who start a fight and then /explode if they start to lose. Nobody else will really even notice it much.

1) I don't do BP but iirc for a while there people who /exploded could make it really hard for the other side because the bots wouldn't respawn to compensate. (I may have this wrong. As I said, I'm not really into BP)

2) Yes, there are a couple of people who will attack you, often repetitively, and then explode when they started to lose. Once is fine, and quite ignorable but when it happens for the 3rd or 4th time it stops being such an entertaining exercise.

Remove it. Or if any thing replace it with some thing less abuse-able. Or make the /exploder have to wait 30-60 seconds before buying another ship, for medical reasons, have to make sure he is still alive after using his emergency teleporter.

Again, this is supposed to be a PvP game. How are we to have PvP missions where killing players matters, when they can simply kill themselves and make the mission impossible to win?

Lord Q: Honor in game isn't based on some other cultures idea of honor. It's based on what's fun and what makes a good game. Ruining missions isn't fun, and doens't make a good game.

Lord Q doesn't quite 'get it' guys. Just leave it alone.



Kinda like his spelling.

corbon armond has struck a balance!

wait to buy a ship so that you are immobilized! briliant!

IMO it's better to design mission objectives that don't rely on a certain number of kills for victory. In the case of BP, I'd rather the objective be completely clearing the sector of all enemy ships - it makes more sense to me, in that if I'm defending my nation's space, or invading an enemy nation, I'm not going to say I've won because I've killed N number ships: if there are more enemy ships present, I'm going to keep trying to kill them. And it also makes /explode or running contributes to losing the mission, just as much as being killed does (which is another thing I think is a problem in BP now: there's really no way to lose, and I think there should be).

I'm too busy wildly strafing and dodging to stop to type in "/explode"

make yourself a bind silly

It's easy to make a bind that does a 10 second countdown before exploding, too. Too bad it's not so easy to force everyone to use that bind.

Heh, this reminds me of when they removed the /logoff during wormhole jumps. People bitched about how it was a valid if dirty tactic. Now no one even remembers it.

If they devs cut out explode, no one would remember in a month.

/me raises hand for 10 second timer.

I actually asked about this ingame the other night, why anyone would want a bind to /explode unless it was so they could attack then explode. Once it was explained that back long ago, it was needed sometimes because you got stuck, I can see it was needed. Now however it isnt. I say remove it.

I dunno... I kinda like using my seppukku bind to get home fast... somehow wasting more effort to actually do something to get myself killed seems less fun.

the 10-second timer is what I'd go for...

Ouch, this thread is hot...

I think Beolach makes the best point here.

...but I'd also be for a 10 second timer.

Aw, shucks! Thanks Phaserlight.

I'd say try the 10 second timer at least for a while, if there's still problems with people abusing /explode to prevent PKs, then remove /explode completely (maybe after trying a 30 second timer). But I'd expect a 10 second delay would probably be enough.

Just means instead of hitting it at 20% they would have to hit it at 40%.

Not if it's like the logout.

the reason for /explode is to allow an escape in the event of unforseen troubles. if exploration is ever implemented it will be essental to all ow return from systems who's wormeholes close down stranding anyone on the wrong side.

and i agree with Beolach's ideas regarding the BP mission.

"Heh, this reminds me of when they removed the /logoff during wormhole jumps. People bitched about how it was a valid if dirty tactic. Now no one even remembers it.

If they devs cut out explode, no one would remember in a month."

well i wasn't around for that but i expect there is a difference, in that /logoff has the player exit the game rather that invoking a death sequence. also using /logoff during a wormehole sequence probably (this is just a guess) allowed the player to be in limbo while the countdown progresses thereby bypassing the balancing factor.

i think that if /explode were removed people wouldn't complaine that much because it isn't that important right now. but removing it removes a very usefull tool for future expansion.

the real issue isn't that /explode exists it's that one use of it annoys the BP jocks.

[shamelessplug]
/explode is not a tool for travel. At the very least, it shouldn't be. It was created to fix issues with flying hours away from a jump point, which no longer is an issue. While it's used for travel, that's an abuse of the system.

http://www.vendetta-online.com/x/msgboard/3/10466
[/shamelessplug]
/explode is also defeating the built in game counter of wins/losses, which is PK count vs deaths.

It was built for a function, which is now defunct. At the very least it should function like /logoff