Martha Stuart wrote:

PVP centric games are not designed around players who use slower PC's and slower internet connections.  Hence why conterstrike, Battlefield, COD, etc etc do not run on slower PC's/connections.  This is why you have recommended system requirements.  If your not this tall, you don't get to ride this ride.

That's true, however, Perpetuum utilizes CPU/GPU like a pig and needs to be optimized FIRST and THEN everyone else should suffer.

I mean, look - my PC can handle up to 3 clients on minimized settings - I will suffer some lags on Gammas especially etc. You might think - hey he needs better PC....BUT! running those 3 clients on min settings, I can adidtionally run 1-2 EVE clients on med and above settings - and those EVE clients will run without any problems.

How about this:

Player uses a teleport (any kind). He disappears on point A and appears on point B immediately, BUT! instead of being under Syndicate protection and stuff, he does have detection at 0-1 and masking at >9000 until one of the next happens: he turns an module on, he moves, he turns his camera, he press an exit/close client button?

In other words, he can't be seen nor see anything until he does something that obviously shows it was intended action.

Smokey, I crash sometimes as well when I use teleports, or enter terminal, or whatever. You were PvP flagged and your heavy was almost dead to a group of assaults.

Maybe no conspiracy on your part, but why did you not restart your client?

And Ville, Merkle gonna hide fleets at tps now? So far who has used this exploit? Or more politely said, who has benefitted from this unintended side effect of allowing externally flagged PvP jumping? Not our side.  And tell me since Peanut was aware of this for awhile, when exactly did he report it to the Devs? Oh right, he didn't. Why?

Its clearly not an intended mechanic. I will never use it. If I crash while jumping, in any situation, you can bet your *** I will be relogging as fast as my comp will let me.

In the immediate, please restore no external PvP flagged jumping, as it was before. Jita stated it simply, declare it an exploit and ban anyone who uses it. Inform anyone if they crash while jumping, unintended, they need to relog in immediately or they may be accused of abusing mechanics. Just make it clear. And figure out a fix in the meantime.

Burial wrote:

It has zero effect on interisland jumps. The instability ends on point with protection and the target can jump back and perform the exploit without anyone being able to lock and aggress him.

Still thinking about this... I mean the "can't teleport while in combat" solution.

Here's why.

.......

In the first choice of running away you at least know that you could escape because you are in control. But here it's game over for you, for an unknown time. They may not be able to kill you, but they sure as hell denied you doing anything.

tl;dr: I still think not allowing teleporting while in combat would solve this.

Cassius wrote:

Smokey, I crash sometimes as well when I use teleports, or enter terminal, or whatever. You were PvP flagged and your heavy was almost dead to a group of assaults.

Maybe no conspiracy on your part, but why did you not restart your client?

And Ville, Merkle gonna hide fleets at tps now? So far who has used this exploit? Or more politely said, who has benefitted from this unintended side effect of allowing externally flagged PvP jumping? Not our side.  And tell me since Peanut was aware of this for awhile, when exactly did he report it to the Devs? Oh right, he didn't. Why?

Its clearly not an intended mechanic. I will never use it. If I crash while jumping, in any situation, you can bet your *** I will be relogging as fast as my comp will let me.

In the immediate, please restore no external PvP flagged jumping, as it was before. Jita stated it simply, declare it an exploit and ban anyone who uses it. Inform anyone if they crash while jumping, unintended, they need to relog in immediately or they may be accused of abusing mechanics. Just make it clear. And figure out a fix in the meantime.

I did.... Crashed, restarted, asked in TS if it was safe to log back in, they said yes you guys had already moved off the tele, so I logged in. Had about 1/3rd armor left started repping and running down to where everyone else was.

And, the old saying.... Almost doesn't count unless it's horse shoes and hand grenades.

I did.... Crashed, restarted, asked in TS if it was safe to log back in, they said yes you guys had already moved off the tele, so I logged in. Had about 1/3rd armor left started repping and running down to where everyone else was.

And, the old saying.... Almost doesn't count unless it's horse shoes and hand grenades.

@ Devs

This is not one of those situations where we talk this out and debate back and forth.  Let me lay this out.  You have a game breaking glitch that has effectively negated a huge portion of your game.  This is not Beacon TFing, or spark tele, or gamma, or any of the other major changes you have planned that require careful thought and time to get right. 

This glitch has broken your game.  Shut down the inter island PVP flag and then fix the problem.  I don't care if it takes 6 months.  But you need to squash this glitch right now and fix it later.  This is game breaking.  i don't care if haulers and un-flagged bots can do it.  But entire fleets cannot be aloud to disappear into perfect saftey whenever the tide turns against them.

Smokeyii wrote:

I'm not afraid to lose bots in pvp.

The fact that you used an exploit to cheat and save yourself proves this to be a lie   nice try though