It sounds like your request was declined.
I only wrote about this issue because I thought if someone else experiences the same bug I did, they probably wouldn’t be compensated either. It made me wonder if I might have written my post the wrong way. Just to clarify, I completed the second room of an Abyssal Deadspace and activated the gate to enter the third room. But as soon as I entered, I spawned inside a rock and got stuck. Eventually, my ship and implants were destroyed due to a timeout.
Whether this is a bug or not, I just don’t want other players to suffer the same kind of loss I did. As for me, I’ve already let go of any hope of receiving compensation.
I think CCP made an announcement at some point that abyssals are at your own risk. There is a risk inherent to the process, which you might call a bug, and others might call a feature. Let’s pretend this is a roleplaying game. You tried to invade the mighty Triglavian Empire, eager to snatch some xenotechnologies. However, your navigator misclicked, and you teleported directly inside an asteroid. Fear not capsuleer, your crew might be gone, but you live on!
o7
Looks like I’ll need to find a new navigator lol
Anyway, thanks for taking the time to read my long post.
Fly safe o7
I think it’s off the point. “It’s not a bug that was created at the point of immobility after gate activation and timed out, so it’s not compensated according to the terms and conditions.” I don’t understand the answer in this way, so I think I wrote it because I didn’t understand what was created from the stone, but I think the priority is whether it was a bug or an intention.
The plan here:
-
Make CCP aware of the bug You got
-
Based on acknowledge, reiterate on reimbursement request.
So If you haven’t created bug report do this. And don’t touch reimbursement request until you got any progress on bug report. Maybe then You’ll have a chance.
abyssal space, doubtful
It is always good to be very clear. A decent GM will of course ask clarifying questions if needed, but who says you get a decent one …
I don’t run a lot of Abys, but the word used is as far as I know still pocket or room. Round sounds weird and confusing. Gate is also typically the ones between systems (which however also shouldn’t get you encased in rocks), however it is common enough used in Abyss that I have heard it there before too. But if you add “Took the gate from room 2 to room 3” then there is less confusion possible as to what was going on.
And I just realized a second possible meaning of “and it was created in a stone”. The next gate was inside the stone so you could not access it? (in which case”I took the gate from room 2 to room 3, but the gate in room 3 was inside a stone and inaccessible”).
A case in point how client localization will make it difficult for people using localized-language clients make themselves understood to a. CCP; b. other players not using localized clients. Relaying with CCP and with the community, they will naturally have to use English and then all kinds of weird terminology and made-up words will creep in and it will take 28 posts just to understand what a person meant by 1 word.
Localization is just always bad, but that is indeed one of the reasons.
I just accept being spawned inside the scenery and basically trapped as an occupational hazard.
Really, the vectors of all collidable objects in a scene should be available to the function that calculates the spawn in point of a player’s ship but since Abyssals are new, relative to the age of the code used for warping, we can assume they missed a bit.
It has only happened to me once in an abyssal and I have ran many, so it may be safe to say that this probably didn’t crop up during QA.
An experienced developer would have had such concerns in the back of their mind while working on the abyssal object spawning, and will have known this can happen, but may not have had any way to solve the problem - Abyssal is spawned Before warp is initiated, not after, and the developer working on abyssals may not have had access to anything to do with warp.
As it happens so infrequently, it’s probably not considered a priority.
I would certainly apologise to the player, and seek to have the problem resolved or at lelast added to the bug board, but I wouldn’t reimburse for this.
well its the abyssal space anyway.. I’ve get to see anyone actually get reimbursed for anything in the abyss.
There are warnings on top of warnings to be fair, you’re explicitly told you’re on your own. It’s a pre suck it up buttercup agreement.
Pretty sure CCP considers abyssals to be a form of gambling, and the players are fully compensated by the payouts.
Getting stuck inside things is not new at all. I’ve been stuck inside an asteroid ( in Aurcel ) and trapped in the framework of an NPC station…as I know others have too. The latter is easy to escape from ( just dock up ), the asteroid required re-logging. It’s all part of the quirky risks of the game.
A work around is to warp out of the objects. That however requires you have something to warp to,which you won’t have inside Abyss.
It is likely just hardcoded into the accel gate where it puts you. And likewise inside decor.
So when someone made the room, they went “Ok I put them out here, then I take an asteroid with max size 2km, and places 6km away, so there is room for the ±2500m the player lands at +2km asteroid without the player colliding with asteroid”.
Then later came a CCP and said hey this 2km asteroid is kinda small, let me change that to 25km.
I’d say this would be pretty naive and bad design. Totally possible though…
What I’d expect the system to be is:
-
every “room” must have dedicated warp-in point, all objects are placed around this point. Coordinates used are pure local.
-
acceleration gate leading to “room” has no idea about the room internals. It simple puts jumping ship into some global coordinates
-
procedure which instantiates “room” puts warped-in ship into warp-in point independently of any other coordinates and such
This way the complexes can be developed by different persons without any collisions.
Howerver, nobody said that current implementation is not made “proper way”. it’s just possible that someone screws up from time to time and QA… Misses it to put it politely.
That could match too.
But it was obvious the decors didnt get their positions recalculated with the size increase. That is where all the problems come from.
참고로 나의 영어가 조금 어색하게 보일수도 있겠지만 스크린샷에서도 보이다싶이 나는 한국인이고 조금 영어가 난해하게 보일수도 있다. 하지만 나는 어쨋든 다시 표현하자면 다음 포켓으로 넘어갔을 때 바위 내부에서 함선이 스폰을 했고 그 바위안에서 절대로 밖으로 안나가지고 결국 시간초과로 죽었어. 너희들의 말대로 어비셜? 당연히 위험을 감수하고 해야지. 하지만 바위 내부에 스폰을 하는 위험까지 감수하면서 어비셜을 해야해? 라는 목적으로 이 글을 쓰는것이다.
For reference, my English might look a bit awkward, but as you can see in the screenshot, I am Korean, so my writing may come across as a little unclear. Still, to restate what happened: when I moved to the next pocket, my ship spawned inside a rock. I was completely stuck there, unable to get out, and eventually died due to a timeout.
As you said, Abyssals are, of course, something you run at your own risk. But should we really have to accept the risk of spawning inside a rock as part of running Abyssals? That’s the point of this post.