Page MenuHomeSchine - Phabricator

Starmade | changing thrust settings apply immediately
Closed, FinishedPublic

Description

Now you can change thrust settings and it immediately applies, great for testing purposes but it should only apply after rebooting your ship.

After changing it, it should also give you a red warning message inside the thrust menu that points out that you need to reboot in order to get the new changes.
A button to revert any new changes you've made without rebooting would be nice too (but not needed to close this task).

Details

Task Type
Bug
Testing Results
Affected Gamemode(s)
Single and Multi
Reproducible
Yes
Last tested (version)
0.19531 (Dev)
Category
Control Block System: Systems
First occurrence (version)
0.19523 (Dev)
Hardware/Software/System
OS-Specific
No
Hardware-Specific
No
Video Card Vendor
uncertain
Serverconfig (server.cfg)
<replace this line with the file content>
Clientconfig (settings.cfg)
<replace this line with the file content>

Event Timeline

lancake updated the task description. (Show Details)Dec 13 2015, 12:42 PM
lancake shifted this object from the S1 Public space to the S3 Starmade space.
lancake changed the visibility from "Custom Policy" to "Public (No Login Required)".
lancake changed the edit policy from "Task Author" to "Starmade (Project)".
lancake changed Category from none/unspecified to Control Block System: Systems.
lancake changed Affected Gamemode(s) from none/unspecified to Single and Multi.
lancake set First occurrence (version) to 0.19523 (Dev).
lancake changed Reproducible from uncertain to Yes.
lancake set Last tested (version) to 0.19523 (Dev).
lancake edited Serverconfig (server.cfg). (Show Details)
lancake edited Clientconfig (settings.cfg). (Show Details)
lancake added a subscriber: lancake.
lancake created this task.
lancake raised the priority of this task from to Pre-Release Quality Assurance.
Restricted Application added a project: Issue Navigation. · View Herald TranscriptDec 13 2015, 12:42 PM
Restricted Application added a subscriber: AndyP. · View Herald Transcript
lancake set Task Type to Bug.Dec 13 2015, 12:43 PM
lancake set OS-Specific to No.
lancake set Hardware-Specific to No.
lancake set Video Card Vendor to uncertain.
lancake moved this task from New / Unconfirmed to Open / Validated on the Issue Navigation board.
lancake moved this task from Open / Validated to Confirmed on the Issue Navigation board.
lancake renamed this task from changing thrust settings applied immediately to changing thrust settings apply immediately.
lancake changed the task status from Open to In Queue (Game).
lancake claimed this task.

-Confirmed-

Restricted Application edited projects, added Starmade, Game Development; removed Issue Navigation. · View Herald TranscriptDec 13 2015, 12:45 PM
schema added a subscriber: schema.Dec 13 2015, 2:03 PM

What's the reason it should only apply after reboot?

The reason it should only be applied after reboot is to stop Super-Capitals going from sluggish brawler, to lightning turn speed at a few clicks.

A ship should enter battle with those weaknesses, not spontaneously be able to change while under fire to benefit them. Macros will break combat in favour of those able to program the hotkeys to adjust thrust at a push of the button on the fly.

A Reboot-system will mean that in PvP events you can adjust thrust before the match.

Potentially instead of a reboot, confirming thruster changes will cause a vessel to have a few seconds (even 1 second will do, maybe) of "Thrust Outage", Unless, unlimited changing was to be the case to benefit "Experienced" pilots

Otherwise I agree, being able to instantly change thrust will vastly benefit those who are able to do so quickly, or via hotkey macros, if there was no temporary penalty for doing so

Ithirahad added a subscriber: Ithirahad.EditedDec 14 2015, 2:06 PM

Not sure which side of this I fall on, to be honest. Really, the only problem with this is turn speed (Particularly on larger ships), which makes me wonder if only locking in turn speed should require a reboot. Also, if changing thrust settings does require a reboot, then docking should probably also allow free modification after a short "engine cooling down" timer.

I agree with Ithirahad, I am on the fence as well, but I can see where this can be in both RP aspects and applying instantly such as in the case of Elite's "Pip" system and where it can be abused to gain a further advantage over a rival player by sudden, massive thrust vectoring and rotation changes. It will likely require a lot of user-testing, and perhaps a few PvP Events / Fleet Operations to determine what is best

schema changed the task status from In Queue (Game) to Open.Dec 15 2015, 9:35 PM

made it a time independent from reboot.

Restricted Application edited projects, added Issue Navigation; removed Game Development. · View Herald TranscriptDec 15 2015, 9:35 PM
schema changed the task status from Open to Resolved.Dec 15 2015, 9:35 PM

ah damn, i meant to do resolve

Restricted Application edited projects, added Quality Assurance; removed Issue Navigation. · View Herald TranscriptDec 15 2015, 9:35 PM
lancake closed this task as Closed.Dec 18 2015, 1:17 PM

-QA Testing-

Works well, even with thrust inheriting.

Restricted Application removed a project: Quality Assurance. · View Herald TranscriptDec 18 2015, 1:17 PM
Restricted Application removed a subscriber: AndyP. · View Herald Transcript
lancake changed Last tested (version) from 0.19523 (Dev) to 0.19531 (Dev).Dec 18 2015, 1:17 PM
Restricted Application added a project: CBS: Systems. · View Herald TranscriptMar 10 2017, 6:20 PM