Page MenuHomeSchine - Phabricator
Create Task
Maniphest T1897

Starmade | broken logic behaviour of rails and dockers when getting destroyed
Confirmed task for development, NormalPublic
Actions

Description

Test setup is a core with one of each rail block type and Activators next to each of these plus another core with a Rail Docker and an adjacent Activator. Destroying the Docker with a Laser always deactivates both Activators next to Docker and next to Rail (with the exception of the Rail Turret Axis, but that's another bug, T1896). Destroying the Rail blocks, however, doesn't deactivate the Activator next to the Rail, only the other Activator next to the Rail Docker.

Details

Task Type
Bug
Testing Results
Affected Gamemode(s)
Single and Multi
Reproducible
Yes
Last tested (version)
0.199.188
Category
Control Block System: Rails/Docking
First occurrence (version)
0.199.172
Hardware/Software/System
OS-Specific
No
Hardware-Specific
No
Video Card Vendor
uncertain
Steps to reproduce
  1. get a ship core with rail docker and activator next to it
  2. get another ship to dock to, put an activator next to its rail
  3. dock the ship

both activators should turn on

a) kill the rail the ship is docked to, only 1 activator deactivates
b) kill the rail docker, both activators deactivate

Tester information (Internal use only)

Changed steps to reproduce, should be clear.

If a rail where something is docked to, gets destroyed. It won't turn off the activator block next to it. bug
If a rail docker that is docked to something, gets destroyed. Both the activator next to it, and the one next to the docked rail will turn off. -> OK

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

Related Objects

Event Timeline

Malacodor created this task.Sep 6 2016, 1:05 PM
lancake moved this task from New / Unconfirmed to Confirmed on the Issue Navigation board.Sep 6 2016, 9:47 PM
lancake added a subscriber: lancake.
lancake claimed this task.

-validated- & -confirmed-

Don't need to test much, you did it all for me ^^

lancake shifted this object from the S1 Public space to the S3 Starmade space.Sep 6 2016, 9:52 PM
lancake changed the visibility from "Custom Policy" to "Public (No Login Required)".
lancake changed the edit policy from "Task Author" to "Starmade (Project)".
lancake edited Steps to reproduce. (Show Details)
lancake edited Tester information (Internal use only). (Show Details)
lancake changed Last tested (version) from 0.199.172 to 0.199.188.
lancake set First occurrence (version) to 0.199.172.
lancake renamed this task from Inconsistent logic behaviour of Rails and Dockers when getting destroyed to inconsistent logic behaviour of rails and dockers when getting destroyed.
lancake changed the task status from Open to In Queue (Game).
Restricted Application edited projects, added Game Development; removed Issue Navigation. · View Herald TranscriptSep 6 2016, 9:52 PM
AndyP changed the task status from In Queue (Game) to In Queue.Mar 10 2017, 5:11 PM
Restricted Application added a project: CBS: Rails. · View Herald TranscriptMar 10 2017, 5:11 PM
AndyP moved this task from Backlog / Unclassed to Beta on the CBS: Rails board.Mar 11 2017, 9:23 PM
AndyP renamed this task from inconsistent logic behaviour of rails and dockers when getting destroyed to broken logic behaviour of rails and dockers when getting destroyed.
AndyP triaged this task as Normal priority.