Page MenuHomeSchine - Phabricator
Create Task
Maniphest T1296

Starmade | Drone Recall to motherships not in a fleet offers mixed results.
Closed, RejectedPublic
Actions

Description

In order for drone recall to work properly the mothership must be the flagship the fleet of drones you want to be able to recal. However, while messing around with fleet mechanics, I have discovered that recalling drones to a mothership that is not in a fleet offers mixed results. The drone fleet's flagship will not respond to commands, but other ships in the fleet will return to carrier with varying degrees of success.

This can also be duplicated using a mothership that is in a fleet, but not the flagship.

Not incredibly important, but this appears to be a bug nonetheless.

Details

Task Type
Bug
Testing Results
Affected Gamemode(s)
none/unspecified
Reproducible
Yes
Last tested (version)
0.19624
Category
Control Block System: Rails/Docking
First occurrence (version)
0.19624
Hardware/Software/System
OS-Specific
No
Hardware-Specific
No
Video Card Vendor
uncertain
Video Card Model
GTX 750
User/Reporter/Contact
Username on Registry
Jstenholt
Steps to reproduce

Create a fleet of drones as you would normally and dock them to pickup points.

Remove mothership from fleet.

Launch drones and initiate drone recall command.

Serverconfig (server.cfg)
<replace this line with the file content>
Clientconfig (settings.cfg)
<replace this line with the file content>

Event Timeline

jstenholt updated the task description. (Show Details)Apr 1 2016, 12:30 AM
jstenholt changed Category from none/unspecified to Control Block System: Rails/Docking.
jstenholt set First occurrence (version) to .19624.
jstenholt set Video Card Model to GTX 750.
jstenholt edited Serverconfig (server.cfg). (Show Details)
jstenholt edited Clientconfig (settings.cfg). (Show Details)
jstenholt set Username on Registry to Jstenholt.
jstenholt set Last tested (version) to .19624.
jstenholt edited Steps to reproduce. (Show Details)
jstenholt added a subscriber: jstenholt.
jstenholt created this task.
Restricted Application added a project: Issue Navigation. · View Herald TranscriptApr 1 2016, 12:30 AM
lancake added a subscriber: lancake.Apr 1 2016, 11:37 AM
lancake claimed this task.

-Rejected-

It's the result of an unfinished mechanic, not a bug.
When you initiate a recall order, all ships in the fleet that have a Pick up Area set, will fly to those coordinates of the top most ship in the fleet list (the flag ship).
If that flag ship isn't the carrier, those local coordinates will most likely not line up with any of the pick up blocks on it, if there are any of them at all.

Technically if all fleet ships are the same, it doesn't matter who is the flagship since those saved local pick up area coordinates will lead to the same place on all of the ships.

This system is going to be expanded upon with sub fleets, basically a carrier fleet within a fleet. Ideally those ships would know the exact ship they're supposed to dock to, and wouldn't try to recall if another was assigned to them.

lancake shifted this object from the S1 Public space to the S3 Starmade space.Apr 1 2016, 11:37 AM
lancake changed the visibility from "Custom Policy" to "Public (No Login Required)".
lancake changed the edit policy from "Task Author" to "Starmade (Project)".
lancake set Task Type to Bug.
lancake changed First occurrence (version) from .19624 to 0.19624.
lancake set OS-Specific to No.
lancake set Hardware-Specific to No.
lancake set Video Card Vendor to uncertain.
lancake set Affected Gamemode(s) to none/unspecified.
lancake set Reproducible to Yes.
lancake changed Last tested (version) from .19624 to 0.19624.
lancake closed this task as Rejected.
lancake triaged this task as Normal priority.
Restricted Application edited projects, added Starmade; removed Issue Navigation. · View Herald TranscriptApr 1 2016, 11:37 AM
AndyP moved this task from Unclassed to Archived on the Starmade board.Apr 9 2016, 11:13 AM
Restricted Application added a project: CBS: Rails. · View Herald TranscriptMar 10 2017, 6:14 PM