UFO: Alien Invasion Issue Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report #3059  -  Reaction fire default setting ON
Posted Oct 21, 2011 - updated Feb 23, 2015
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Bug report
  • Status
     
    Closed
  • Assigned to
     mattn
  • Progress
       
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
     H-Hour
  • Owned by
    Not owned by anyone
  • Estimated time
    Not estimated
  • Time spent
    107 weeks, 24 hours
  • Category
    General
  • Resolution
    RESOLVED
  • Priority
    2. Low
  • Reproducability
    Not determined
  • Severity
    Not determined
  • Targetted for
    icon_milestones.png Not determined
  • Complexity
    icon_customdatatype.png Not determined
  • Platform
    icon_customdatatype.png Not determined
  • Architecture
    icon_customdatatype.png Not determined
Issue description
Item 3059 imported from sourceforge.net tracker on 2013-01-28 19:58:38

Trying to check if reaction fire implementation matches specification as mentioned in 2.4 TODO:

http://ufoai.ninex.info/wiki/index.php/TODO/2.4

Specification says reaction fire should be ON by default, but current implementation has it OFF by default.
Comments Ported from Sourceforge  ⇑ top
tlh2000 (2011-10-21 17:54:09)  ⇑ top
it depends - in campaign mode it should have the setting of the last fight - see GAME_CP_InitializeBattlescape
natewr (2011-10-21 23:45:08)  ⇑ top
Ok, but default at beginning of campaign was OFF, not ON.
tlh2000 (2011-10-22 14:46:46)  ⇑ top
CL_GenerateCharacter should set the state then
aduke1 (2011-11-28 21:16:54)  ⇑ top
The priority was adjusted according to the "bug priority rules". See http://ufoai.ninex.info/wiki/index.php/Bugs#Bug_Priorities
aduke1 (2012-03-03 23:24:53)  ⇑ top
CL_GenerateCharacter is not the right place, because we need a weapon equipped in order to set RF to ON.
aduke1 (2012-10-04 23:01:43.612000)  ⇑ top
- **assigned_to**: Duke - **milestone**: --> 2.4

Steps to reproduce this issue
Nothing entered.