Hold position & Pursue & Guard position buttons missing in GUI! #4303
Comments
klasskill uploaded file |
klasskill uploaded file |
klasskill commented That is the order menu, by right clicking on a unit. |
Per changed resolution from `` to |
Per changed blocking which not transferred by tractive |
Per changed blockedby which not transferred by tractive |
Per commented Hold position / pursue / guard secondary orders have been replaced by the 'hold' primary order (default key 'H'). Unfortunately, this does not yet have a button in the GUI. (Primary orders have never had buttons.) |
Per changed status from |
klasskill changed status from |
klasskill changed resolution from |
klasskill commented Replying to Warzone2100/old-trac-import#4303 (comment:2):
I don't understand, hold position means for the unit to stay where they are. Are you now saying that the only option left is hold position? |
Per commented See [8]fd88edcc2adf804dc5cf032076137f434fcf7b4 If you want it changed, make a new forum thread about it. |
Per changed status from |
Per changed resolution from `` to |
KlassKill changed status from |
KlassKill changed resolution from |
KlassKill commented http://forums.wz2100.net/viewtopic.php?f=6&t=12197 |
Per changed status from |
Per changed resolution from `` to |
KlassKill commented I do not understand? I was told to make a forum thread about it and we even had a poll on the matter and 91% of the people want this so why did you close this again? |
-Philosopher- changed status from |
-Philosopher- changed resolution from |
-Philosopher- commented Recently, I have been involved in the campaign testing process (http://forums.wz2100.net/viewtopic.php?f=1&t=12714). Much has been done to correct past issues in the conversion to jscam. However, it'll take more than just correcting the scripts to make the campaign play the way that it should (i.e. approximating how it used to). Each campaign stage is a puzzle to be solved, and removing the pursue/guard/hold features removes key pieces of the solution to many. They are also fundamental and characteristic aspects of the game (in any mode). I've done the homework and read through the threads referenced above. Nothing in them makes clear what the original issue was that caused them to be removed, and whatever it was (I personally never experienced any problems with these features), it almost certainly wasn't as bad as not having the features at all. Could this please be revisited? There is much support for reinstating these features and I believe another public release without them would gain little traction, thus somewhat negating all the hard work being done to correct the campaign scripts. My request is (1) the features be restored to the state they were in the last good version they were present, and then (2) whatever issues were affecting them be subsequently fixed. I'm more than happy to give my time testing any changes, etc. Here is some further supporting discussion from the current work on bug-fixing jscam. A few posts either side of these probably give the best context: Suspected knock-on effects of removing this functionality include: Please contact me if you need example save games where lack of these features creates difficulties that weren't previously present and that the "new" hold function doesn't resolve. |
Forgon changed priority from |
Forgon changed status from |
Forgon changed owner from `` to |
WZ2100ModsFAn changed _comment0 which not transferred by tractive |
WZ2100ModsFAn commented Is the hold order going to be fixed? I heard that it does not work the way it originally did. Hopefully this is not too old. |
Berserk Cyborg changed priority from |
Berserk Cyborg changed status from |
Berserk Cyborg changed resolution from `` to |
Berserk Cyborg committed [29] In Warzone2100/warzone2100@29d3696:
|
resolution_fixed
type_bug
| by klasskillThis is a huge bug!
Those options are gone from the GUI on master and they are still highly useful!
You can't check what the units are set to now with those gone from the menu.
Issue migrated from trac:4303 at 2022-04-16 11:51:02 -0700
The text was updated successfully, but these errors were encountered: