(M_XLIGHT, M_CHOPPER): Redundant, remove.
(init_mchr): Don't set them. (carrier_planes): Use m_nxlight, m_nchoppers instead.
This commit is contained in:
parent
b900866ea8
commit
57f589e2e4
4 changed files with 6 additions and 14 deletions
|
@ -62,10 +62,6 @@ init_mchr(void)
|
|||
struct mchrstr *mp;
|
||||
|
||||
for (mp = mchr; mp->m_name; mp++) {
|
||||
if (mp->m_nxlight)
|
||||
mp->m_flags |= M_XLIGHT;
|
||||
if (mp->m_nchoppers)
|
||||
mp->m_flags |= M_CHOPPER;
|
||||
if (mp->m_nplanes && !(mp->m_flags & M_MSL || mp->m_flags & M_FLY))
|
||||
mp->m_flags |= M_MSL;
|
||||
}
|
||||
|
|
|
@ -41,10 +41,8 @@
|
|||
# Available flags are in ship_chr_flags[]. info Ship-types should
|
||||
# document them all.
|
||||
#
|
||||
# Note that you can't set the flags M_XLIGHT or M_CHOPPER here. They
|
||||
# will be automatically set by init_mchr() if the ship can carry a
|
||||
# non-zero amount of those things. Also note that if nplanes > 0 and
|
||||
# flag plane is not set, then flag miss will automatically be set.
|
||||
# Note that if nplanes > 0 and flag plane is not set, then flag miss
|
||||
# will automatically be set.
|
||||
|
||||
# Do not edit this file to customize a game! Create your own custom
|
||||
# configuration file(s), best next to your econfig, and name them in
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue