Author Topic: Nightly (OS X): 31 Jan 2011 - Revision 6991  (Read 1014 times)

0 Members and 1 Guest are viewing this topic.

Offline SirKnightly

  • George or Keira?
  • 212
Nightly (OS X): 31 Jan 2011 - Revision 6991
Here is the nightly for OS X on 31 Jan 2011 - Revision 6991

Group: Inferno
fso-OSX-Inferno-20110131_r6991.tgz
MD5Sum

Code: [Select]
------------------------------------------------------------------------
r6990 | Goober5000 | 2011-01-31 03:18:21 -0600 (Mon, 31 Jan 2011) | 2 lines
Changed paths:
   M /trunk/fs2_open/code/mission/missionlog.cpp
   M /trunk/fs2_open/code/parse/sexp.cpp
   M /trunk/fs2_open/code/playerman/playercontrol.cpp
   M /trunk/fs2_open/code/ship/ship.cpp

fix for Mantis #2390
errors in handling the CARGO_NO_DEPLETE flag for ship subsystems
------------------------------------------------------------------------
r6991 | Goober5000 | 2011-01-31 04:04:37 -0600 (Mon, 31 Jan 2011) | 3 lines
Changed paths:
   M /trunk/fs2_open/code/fred2/initialstatus.cpp
   M /trunk/fs2_open/code/fred2/missionsave.cpp
   M /trunk/fs2_open/code/mission/missionlog.cpp
   M /trunk/fs2_open/code/mission/missionparse.cpp
   M /trunk/fs2_open/code/playerman/playercontrol.cpp
   M /trunk/fs2_open/code/ship/ship.cpp

--the behavior of cargo index -1 (which can only happen for capships) and cargo index 0 is substantially the same, so let's standardize on index 0... this prevents crazy stuff happening with bitwise operators on negative numbers :-/
--also, remove the restriction on capship cargo where ships must have the "scannable" flag
--because of the above constraints, "nothing" cannot be a meaningful subsys cargo, but then again, scanning a subsystem with "nothing" didn't do anything in the old code, so this doesn't change anything
------------------------------------------------------------------------