Jan 21 2019
As far as I've noticed, "carrier recall" is broken because of this. Half the ships wont obey the command and the others may go to the wrong sector, and none actually dock.... it is terrible.
Mar 19 2018
Actually the problem extends much further than OP realises. If you dock the mothership to a station using a pickup point the drones will attempt to dock in the vicinity of the pickup point on the station instead of the drone bay of the mothership even when the mothership is undocked and in an adjacent sector.
Mar 18 2018
Mar 13 2018
Aug 30 2017
Managed to cause the ship not same as self exception in v0.199.654, happened in trader controlled area.
Log 0-1 for serverlog/logstarmade/npcs included.
Could not join world directly after that exception but a restart allowed me to enter at an earlier point.
Jul 24 2017
Potentially related, recently noticed that the behaviour of AI is affected by the relative locations of the COM and the core with behaviour becomming less reliable the further apart these two are. Could be that with larger mining drones the distance between the COM and core is causing the issue. This also may be worth looking into as its own issue.
Jul 22 2017
Jul 21 2017
Jul 20 2017
Seconded, tried to perform a test (I have an idea as to what the issue might be) but couldn't do so due to drones just refusing to aknowledge any mining order.
Jul 18 2017
Jun 26 2017
Jun 12 2017
Can't do anything with the provided logs, server probably ran out of memory due to lack of restarts. Could have been a memory leak too but since this report is from a year ago, it can be closed.
Jun 9 2017
No feedback, most likely a duplicate of the issue we had before where fleets don't load when they should. They did however re-appear after unloading/loading the sector.
This should have been implemented recently.
Jun 5 2017
Jun 4 2017
May 22 2017
We've been having problems with fleets refusing to mine on LvD as well. I tested with some 3k miners. The salvage computers had salvage beams and a storage attached. Plenty of power and thrust. When issuing the command, nothing happens.
May 7 2017
The first issue has since been fixed, but the second issue of fleet ships being able to move into and out of noexit/noenter sectors still exists and is a problem. We use these flags for our quests and build accounts (players are locked into a sector with creative mode), so this is a bit of a problem for us as we've been having users using fleets to get out of these sectors.
Apr 25 2017
Apr 24 2017
Apr 23 2017
Apr 21 2017
Since all of the docking/station problems are fixed, all station have now 0 mass and dos not get damage by any weapon (the projectiles hit without dmg).
I couldnt pinpoint the ships involved, no, there was a lot going on around me. I havent loaded that world since, so I can probably try to track them down
Apr 20 2017
I ran .529 for about an hour and a half and couldnt trigger the debug script or lose any docked entities. Updating to .531 now
Just ran .199.531 on a game where I reinstalled starmade from scratch and then added my blueprints and server-database.
Apr 19 2017
ok thank you. This is likely a false positive. I uploaded another build that will fix that. It will also notify admins, if a ship is waiting for its docks for a bigger amount of time.
Does replicate mean: you could get the bug to happen again and thus upload the logs again, or does it mean you replicated the situation and the bug did not happen?
I replicated the bug again, this time in 199.527. did not get the admin error messages this time. Jumping around on their patrol path when they're about to offload does seem to be fairly reliable.