Uhh, no steam here except the steaming duce Fdev just dropped.
Notice Fleet Carrier Update - Known Issues
No, ps4 here.
Well at least the community manager at Fdev knows what its like to be awake late at night on patch day
Bill
g'nite y'all
Bill
g'nite y'all
Same here
Until people move their carriers out ... black adder
if the black adder error is caused by too many carriers, they could have easily coded the client to prohibit trying to purchase until the number was below the limit in a system instead of causing a fatal error.
They could have forced carriers to spawn in adjacent systems and prohibit them from joining a system with too many carriers.
I dont think that's the root of the black adder error.
Also, what happened to the carrier docks outside of stations that vend carriers? weren't they a thing in beta? or are they not supposed to be located where you buy carriers?
(i'm stuck at black adder no matter what system i try to purchase from in any mode)
They could have forced carriers to spawn in adjacent systems and prohibit them from joining a system with too many carriers.
I dont think that's the root of the black adder error.
Also, what happened to the carrier docks outside of stations that vend carriers? weren't they a thing in beta? or are they not supposed to be located where you buy carriers?
(i'm stuck at black adder no matter what system i try to purchase from in any mode)
Griefers!
There are but 13 in my current system. So not sure the # of carriers is the root of the black adder problem.
Ok. So here's an idea to fix that. If a player logs out, and their carrier is parked in a vendor system, and that carrier has never jumped before (not once). Then 1 hour after they log out their carrier will initiate an admin jump. The admin jump is a jump to a random location within 100LY of the carrier's current location. The admin jump cannot be cancelled. The admin jump will put the fuel reserves of the carrier into the negative if the player has removed them. This should be effective in booting the carriers squatting in the vendor systems out so other players are able to purchase one.
OR... and this may be even easier to implement. Designate more vendor systems.
Last edited:
Have tried that multiple times. Nothing seems to work...
One issue I noticed when my FC failed to purchase is that it had the same fixed name as it did in Beta 2. I then looked in my log file and found this. Which leads me to think that those having the crash are the ones who participated in Beta 2.
{23:30:26GMT 4396.067s} Webserver request failed: code 403, details 'eeKfoiscZZPAod8DhHyfxicliHpN22JX8iAJGv2wbh3xsQIksUQxOCXmETUnM6b2L0qPIXyjlYcAL+gvdX7J3SwXwxke3AOFnB+8PcFBnlyoG9qzxdzTxDmKaVU6EkkX+S+6HoR6pP/VDM0WndwqdXrHGD6Jkqd5xZY7yIIi'
{23:30:26GMT 4396.067s} Webserver request: https://api.orerve.net:443/2.0/elit...46Am0Z8R+g6JEOi0D6bC6e2eoIs3KMktnIYFVb8gFSxU4...
Plaintext error response: {"status":403,"message":"Helper\\FleetCarrier::spawnCarrier Failed to spawn Fleet Carrier 1600684 because we are already spawned"}
{23:30:26GMT 4396.067s} Webserver request failed: code 403, details 'eeKfoiscZZPAod8DhHyfxicliHpN22JX8iAJGv2wbh3xsQIksUQxOCXmETUnM6b2L0qPIXyjlYcAL+gvdX7J3SwXwxke3AOFnB+8PcFBnlyoG9qzxdzTxDmKaVU6EkkX+S+6HoR6pP/VDM0WndwqdXrHGD6Jkqd5xZY7yIIi'
{23:30:26GMT 4396.067s} Webserver request: https://api.orerve.net:443/2.0/elit...46Am0Z8R+g6JEOi0D6bC6e2eoIs3KMktnIYFVb8gFSxU4...
Plaintext error response: {"status":403,"message":"Helper\\FleetCarrier::spawnCarrier Failed to spawn Fleet Carrier 1600684 because we are already spawned"}
Indeed.
I did briefly try beta 2
I had that error, so I restarted ED after a little wait, and then I was able to get in. Once in, I had zero problems (though I'm not trying to buy a carrier).