EVE General Discussion

honestly I'm glad someone said it, but yeah...

that was a terrible answer

Like op said, it's because they're behind the age

Also: logs show nothing.

How shocked should I be that a GM doesn't seem to understand generally accepted game mechanics?

I probably should be far more shocked than I am, which is sad in itself.

It's pretty common sense that spamming leads to lag, but that doesn't change the fact that it was a tactic that worked, and for a very long time has been in common use. Maybe there were minor changes in some bit of code somewhere which changed how the whole thing works, intentional or not. Regardless the end result for the player is that a game mechanic changed.

It probably bears mentioning that what a CCP employee might see as a game mechanic and the definition a player might give to the same term are probably very different things. See, for me as a player, a game mechanic is simply the reality of how the game functions, which I can then build tactics AROUND to accomplish the things I wish to accomplish. These tactics are never fool proof, because no plan ever really is. On the other hand, CCP likely sees a game mechanic as transitory things which they can manipulate at any given time, for any given reason, to change the way the game functions. Both definitions are probably correct in some way.

However

When CCP goes and fiddles with things, even minor things, they often do not explain the change they made, or even acknowledge that they made a change at all. THIS IS ONE OF THE MOST FRUSTRATING ASPECTS OF BEING A PLAYER. I'm cool with you changing whatever you want whenever you want, AS LONG AS YOU TELL ME WHAT YOU CHANGED. Such "ninja-nerfs" as they're called by players are getting very tiresome and increasingly frustrating. Be upfront with what you change, regardless of whether you deem it a bug or exploit or WHATEVER, and a lot of players will be a lot less agitated when you change little things like this. I realize a lot of work goes into big releases like Crucible, but seriously if you're not keeping records of EVERYTHING you change and how much work goes into any given item, then you really should be, and there should never be a reason to hide this information from the players. No, you shouldn't give them a list of known exploits, but when an exploit is fixed, it should never, ever, be a secret.

Also, your GMs clearly need more experience playing EVE, and that experience should be well-rounded, not just shooting players 23/7 or rocks 23/7 or running manufacturing jobs or any other single thing 23/7. And if you can't manage that, maybe you should assign specific GMs with specific experience to specific areas of interest like PvP, mining, et-cetera.

edit/ps. I've been running into this bug (?) since Incarna was released. I heard about it from some hardcore lowsec PvPers, and I eventually was in lowsec and got 0wned and tested it out, and ended up podded lol (luckily with no worthwhile implants).

I think that GM message has been misinterpreted or taken out of context. After your ship is destroyed you go into a session change, namely moving from your ship to your pod. This means that you cannot jump, dock, or go through any other session change for 30 seconds (which is now 20 seconds). It is certainly not an exploit to spam the warp button.

Time dilation should not affect it.

And your pod following the command you gave your ship is most likely caused by the fact that often when you still see your ship on your screen, on the server you re already in your pod. Thus the server thinks you gave that command to your pod and not your ship, which was already removed server side.

I may not be a programmer, but I have a very solid background in both software development and EVE; I would not comment on these things if I was completely clueless. I am aware that spamming the warp button greatly increased your chances of getting out. When I was simply a player and not a GM we told our alliance grunts to do exactly that. However, it was never a full proof thing. I lost quite a few pods despite that tactic.

We also did not change that 'mechanic', not consciously. Some code may have been introduced that affects that particular behavior as a side effect, but considering that behavior is partly there because the way client/server communication works across the internet, that possible behavioral change is more likely a technical thing and not a design change.

As I said earlier, this is not a game mechanic, but the way the technology behaves. If the tech is changes, behavior might change. However, even though it is not an official design, if the behavior changed in a way that is undesirable me and my colleagues will keep an eye on things. And any solid feedback is welcome.

Just set autopilot, and activate when boned. Ship dies and autopilot instawarps the egg to saftey

Fix your game, CCP. And stop giving lame answers that try to deflect blame to your customers. The log shows that the problem is on your end.

People spend billions of ISK on implants that they PVP in because they have enough confidence in themselves (and their internet connection) to risk being podded in the event they lose their ship. They shouldn't have to worry about being podded by your ****** software, too.

If I'm in a pod, not in a bubble, not pointed, not scrammed and I hit the warp-to button, and your server receives that input, I'd damn well better warp. Not sometimes. Not most of the time. Every ******* time.

1) Given a standing start, A pod can warp before any ship gets a lock on it

2) If you click warp the instant your pod "appears" in space you can warp before anything has locked it

3) "spamming" warp was not an attempt to utilize some bug, it simply meant that the millisecond your pod appears you would have clicked to initiate warp. If you are clicking slightly before, during, and after your ship is being/been destroyed, you make it more likely you will have clicked warp the second your pod loadsThis cuts down on A) Reaction time and B) some of the weirdness that occurs when your ship pops and others may see your pod before you do. The "insta warp" refered to by some, is exactly the same warp out time you would have if you were D.A.R.Y.L and you managed to click the warp button once precisly when your pod appeared.

Incidentally, a good tackler will also be spam clicking to try to lock your pod as it appears.

4) Pre patch this method would work, as a previous poster has indicated, 99 times out of 100. There was still many ways to get podded, but preparedness and correct fits (a suitable soak) would give your implants a good survivability.

5) If post patch this does not work, then CCP have borked something.

Suggesting people were abusing the system by clicking impatiently is unfair. Similar situations whereby people click repeatedly are attempting to dock whilst under fire, and attempting to jump through a gate whilst sitting out an aggro timer under fire and when attempting to warp to a celestial whilst mwding away from a target who has them warp disrupted.

SKUNK

I could care less

SKUNK

This is right on.

My guess is that some time in the last year they changed the client as part of the war against lag, so that when you hammer a button 50 times repeatedly it does not necessarily send all of those commands to the server.

This *would* help the lag situation, but would have the side effect of loosing the guaranteed insta-warp that pods had.