Forums » Bugs
Station Taking Bug
While I was attacking Bractus M-14 tonight, someone sent me a key named ONCe upon a time, which evidently was a key to the station. I continued attacking, some time later before I finished killing the turrets the key was revoked. After killing all the turrets to M-14 (around 12:01ish AM PST, Friday March 11), I waited for the timer to elapse, got into position, and waited for the timer to countdown... and then when it was docking time and I attempted to dock I got a big ole message saying "You are ineligible to conquer this station".
I exited the dock and repeated the process. Same message.
I then ask in 100 why I can't take the station. [player] then smiles (in chat). I suspect they were the ones that sent me the key (obv you can check to see). And [player] says I couldn't take the station because someone gave me a key. I ask further and they state (in 100) that it is a classic gag (i.e. exploit).
So, as far as I can tell, somehow giving me a key to a station I'm actively attacking somehow makes me ineligible to take it. If that's what's going on it's a total exploit that needs to be fixed (and I'm surprised nobody, including [player] or whoever gave me the key, reported it). If something else is going on there's a bug.
Cheers.
I exited the dock and repeated the process. Same message.
I then ask in 100 why I can't take the station. [player] then smiles (in chat). I suspect they were the ones that sent me the key (obv you can check to see). And [player] says I couldn't take the station because someone gave me a key. I ask further and they state (in 100) that it is a classic gag (i.e. exploit).
So, as far as I can tell, somehow giving me a key to a station I'm actively attacking somehow makes me ineligible to take it. If that's what's going on it's a total exploit that needs to be fixed (and I'm surprised nobody, including [player] or whoever gave me the key, reported it). If something else is going on there's a bug.
Cheers.
Thanks, we will investigate.
the error message posted indicated to me what the problem was. i know because ive tried to take my own stations in the past and had to delete my own key. seemed normal and by design. i have no involvement with stations and its none of my business.
Thanks Whistler
Incarnate I have noticed this to I THINK the cause is when wally started attack the station he was keyed but when he tried to conq it the game (I think ) a Said he already had a key then didn't allow him to dock. This has been a bug for a long time.
This has been a bug for a long time.
Which begs the question, why is it only being raised now? Especially if it's actively used as an exploit to prevent conquest.
Anyway, we will investigate further.
Which begs the question, why is it only being raised now? Especially if it's actively used as an exploit to prevent conquest.
Anyway, we will investigate further.
I've had something like this happen to me a long time ago and didn't really understand what happened. I think I was attacking a station and then they Keyed me and I kept attacking the station. This made me kos there so even after revoking the key I wasn't able to dock capture it. When someone else captured it, the station changed ownership, and I received the new key I was still considered kos and being attacked and couldn't dock until I /exploded.
That being said it was years ago so I could be misrembering how it all happened. But it had to do with being keyed and kosed with the station.
That being said it was years ago so I could be misrembering how it all happened. But it had to do with being keyed and kosed with the station.
Inevitable is correct. The issue is:
- A player is attacking the station.
- The player is given a key, now making them aligned to the station, while they continue to attack it.
- Attacking a station where you have an access key results in a TempKoS response.
- TempKoS players may not dock with stations or conquer them.
This should really be dealt with by changing how the key-system works, to make any key offers into a construct that is "queued" until it is manually "accepted" or "rejected" by the given player, and that in the meantime (until they actively accept it), they do not have any change in status.
But, that's time consuming and requires considerable user-interface work, so the "dumb hack for right now" is that any key received by a person will not incur TempKoS if they attack the assets associated with that key, for two hours (wall-clock) after receiving the key.
So, that should temporarily mitigate the exploit, while we reconsider the key system design in light of on-going UI changes, etc.
Hopefully the fix will be in tonight.
- A player is attacking the station.
- The player is given a key, now making them aligned to the station, while they continue to attack it.
- Attacking a station where you have an access key results in a TempKoS response.
- TempKoS players may not dock with stations or conquer them.
This should really be dealt with by changing how the key-system works, to make any key offers into a construct that is "queued" until it is manually "accepted" or "rejected" by the given player, and that in the meantime (until they actively accept it), they do not have any change in status.
But, that's time consuming and requires considerable user-interface work, so the "dumb hack for right now" is that any key received by a person will not incur TempKoS if they attack the assets associated with that key, for two hours (wall-clock) after receiving the key.
So, that should temporarily mitigate the exploit, while we reconsider the key system design in light of on-going UI changes, etc.
Hopefully the fix will be in tonight.
Thanks for the speedy response
This has been a bug for a long time.
Which begs the question, why is it only being raised now? Especially if it's actively used as an exploit to prevent conquest.
Anyway, we will investigate further.
2 answers
1). Am lazy I notice a bug then say I'll make a post later... I never do make one
2). Well I would say but this post will just be deleted.
Which begs the question, why is it only being raised now? Especially if it's actively used as an exploit to prevent conquest.
Anyway, we will investigate further.
2 answers
1). Am lazy I notice a bug then say I'll make a post later... I never do make one
2). Well I would say but this post will just be deleted.