didn't mean to move it, should show different behavior in 0.19565
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed All Stories
All Stories
All Stories
Feb 27 2016
Feb 27 2016
lancake changed the status of T1187: AI/fleet ships can move when they sometimes shouldn't from Open to In Queue (Game).
lancake moved T1187: AI/fleet ships can move when they sometimes shouldn't from New / Unconfirmed to Confirmed on the Issue Navigation board.
schema changed the status of T1186: During carrier recall, drones can dock to the wrong pick up point from In Queue (Game) to Resolved.
schema changed the status of T1185: Carrier recall first uses an old flagship position to home in from In Queue (Game) to Resolved.
schema changed the status of T1184: Carrier recall ends too soon or fails partially from In Queue (Game) to Resolved.
schema changed the status of T1152: typos and oddities in fleet GUI from In Queue (Game) to Resolved.
lancake changed the status of T1180: fleets get stuck with old orders (sometimes until they are unloaded?) from In Queue (Game) to Resolved.
lancake changed the status of T1184: Carrier recall ends too soon or fails partially from Open to In Queue (Game).
lancake changed the status of T1185: Carrier recall first uses an old flagship position to home in from Open to In Queue (Game).
lancake changed the status of T1186: During carrier recall, drones can dock to the wrong pick up point from Open to In Queue (Game).
lancake added a comment to T1186: During carrier recall, drones can dock to the wrong pick up point.
-Confirmed-
lancake moved T1186: During carrier recall, drones can dock to the wrong pick up point from New / Unconfirmed to Confirmed on the Issue Navigation board.
-Confirmed-
-Confirmed-
lancake moved T1184: Carrier recall ends too soon or fails partially from Open / Validated to Confirmed on the Issue Navigation board.
lancake moved T1185: Carrier recall first uses an old flagship position to home in from New / Unconfirmed to Confirmed on the Issue Navigation board.
lancake moved T1184: Carrier recall ends too soon or fails partially from New / Unconfirmed to Open / Validated on the Issue Navigation board.
I was in SP, with the name "Comr4deplsunban", had no problems with fleets deleting themselves
lancake moved T1168: Fleet orders not persistent after reboot. from Feedback to Open / Validated on the Issue Navigation board.
Last question is irrelevant now, issue(s) got fixed. I'll check it again some time later.
-QA Testing-
SmilingDemon changed Last tested (version) from 0.19439 to 0.19564 (DEV) on T737: Shield Supply and Drain textures are swapped.
-QA Testing-
SmilingDemon edited Tester information (Internal use only) on T1143: overheating fleet ships can't be salvaged.
SmilingDemon changed the status of T1143: overheating fleet ships can't be salvaged from Resolved to In Queue (Game).
-QA Testing-
SmilingDemon changed Last tested (version) from 0.19557 (Dev) to 0.19564 (DEV) on T1143: overheating fleet ships can't be salvaged.
SmilingDemon changed Last tested (version) from 0.1956 (Dev) to 0.19564 (DEV) on T1165: Unable to create multiple fleets.
-QA Testing-
lancake changed Last tested (version) from 0.19563 (Dev) to 0.19564 (Dev) on T1175: Fleet status shows as "idle" even when issued and completing orders..
lancake closed T1175: Fleet status shows as "idle" even when issued and completing orders. as Closed.
-QA Testing-
lancake changed Last tested (version) from 0.19558 (Dev) to 0.19564 (Dev) on T1146: assigning a new fleet member located in an adjacent sector causes alignment issues.
lancake closed T1146: assigning a new fleet member located in an adjacent sector causes alignment issues as Closed.
-QA Testing-
SmilingDemon removed First occurrence (version) on T1181: fleets don't save properly after shutdown.
SmilingDemon changed First occurrence (version) from 0.19563 (Dev) to 0.19564 (DEV) on T1181: fleets don't save properly after shutdown.
SmilingDemon changed Last tested (version) from .19562 to 0.19564 (DEV) on T1172: ships assigned to fleet lose all rail based entities on unload.
lancake changed Last tested (version) from 0.19563 (Dev) to 0.19564 (Dev) on T1179: FSM Exception after reaching destination of fleet move order.
-QA Testing-
SmilingDemon changed Last tested (version) from 0.19557 (Dev) to 0.19564 (DEV) on T1144: a completely removed fleet member stays in the list.
lancake edited Tester information (Internal use only) on T1180: fleets get stuck with old orders (sometimes until they are unloaded?).
lancake changed Last tested (version) from 0.19563 (Dev) to 0.19564 (Dev) on T1180: fleets get stuck with old orders (sometimes until they are unloaded?).
lancake changed the status of T1180: fleets get stuck with old orders (sometimes until they are unloaded?) from Resolved to In Queue (Game).
-QA Testing-
Still bloom-dependent for me.
lancake changed Last tested (version) from 0.19559 (Dev) to 0.19564 (Dev) on T1152: typos and oddities in fleet GUI.
lancake changed the status of T1152: typos and oddities in fleet GUI from Resolved to In Queue (Game).
-QA Testing-
lancake moved T1167: carrier system: shoot out rail stops entity before undocking it from Backlog / Unclassed to Confirmed fix on the Quality Assurance board.
lancake reopened T1167: carrier system: shoot out rail stops entity before undocking it as "Resolved".
-QA Testing-
-QA Testing-
SmilingDemon edited Steps to reproduce on T1172: ships assigned to fleet lose all rail based entities on unload.
SmilingDemon changed the status of T1172: ships assigned to fleet lose all rail based entities on unload from Resolved to In Queue (Game).
-QA Testing-
schema changed the status of T1183: saved waypoints can't be used for move/attack/defend fleet orders from In Queue (Game) to Resolved.
lancake added a comment to T1183: saved waypoints can't be used for move/attack/defend fleet orders.
-Confirmed-
lancake changed the status of T1183: saved waypoints can't be used for move/attack/defend fleet orders from Open to In Queue (Game).
lancake moved T1183: saved waypoints can't be used for move/attack/defend fleet orders from New / Unconfirmed to Confirmed on the Issue Navigation board.
-QA Testing-
godmars added a comment to T1160: Rank column of fleet-member table partially hidden and unresizable.
-fix comfirmed-
godmars moved T1174: UI: Docked entities appear in list of ships to add to the fleet from Backlog / Unclassed to Confirmed fix on the Quality Assurance board.
-Fix confirmed-
schema changed the status of T1175: Fleet status shows as "idle" even when issued and completing orders. from In Queue (Game) to Resolved.
schema changed the status of T1152: typos and oddities in fleet GUI from In Queue (Game) to Resolved.
schema changed the status of T1160: Rank column of fleet-member table partially hidden and unresizable from In Queue (Game) to Resolved.
schema changed the status of T1146: assigning a new fleet member located in an adjacent sector causes alignment issues from In Queue (Game) to Resolved.
schema changed the status of T1167: carrier system: shoot out rail stops entity before undocking it from In Queue (Game) to Resolved.
schema changed the status of T1172: ships assigned to fleet lose all rail based entities on unload from In Queue (Game) to Resolved.
should work now. But only on ships that have been at least loaded once from now (basically there is a new flag in the database to identify docked entities so they can move in set. It is only set when the ship gets unloaded in the new version)
schema changed the status of T1174: UI: Docked entities appear in list of ships to add to the fleet from In Queue (Game) to Resolved.
added filter for list (default on mother ships)
schema changed the status of T1180: fleets get stuck with old orders (sometimes until they are unloaded?) from In Queue (Game) to Resolved.
schema added a comment to T1173: Fleets of ships with different thrust values will not maintain formation..
would be an extra feature ill do for the next update
schema changed the status of T1143: overheating fleet ships can't be salvaged from In Queue (Game) to Resolved.
schema changed the status of T1181: fleets don't save properly after shutdown from In Queue (Game) to Resolved.
server needs to be restarted on FSMException as the state machine of that fleet is then broken
schema changed the status of T1179: FSM Exception after reaching destination of fleet move order from In Queue (Game) to Resolved.
Feb 26 2016
Feb 26 2016
lancake renamed T1181: fleets don't save properly after shutdown from fleets don't save after shutdown to fleets don't save properly after shutdown.
lancake moved T1181: fleets don't save properly after shutdown from Open / Validated to Confirmed on the Issue Navigation board.
lancake moved T1168: Fleet orders not persistent after reboot. from Open / Validated to Feedback on the Issue Navigation board.
Ok so unfortunately we have another bug that messes with this one.