Recent changes to bugs

Adding Colored Channel Names

2003-06-18T06:28:31Z

This is a pretty easily fixed glitch (but a really serious
one). If anyone adds a channel with an alias that has a
color code in it, the MUX will run fine until the next
reboot. The comsys.db goes bad and you are unable to
start until you either revert to a backup or start from a
blank. Here is an example:

addcom [ansi(hw,)]=Public

I can't remember if you had to @fo that or not. This one
is courtesy of Ashen-Shugar when I was talking with him
a few weeks back about some TinyMUX vunerabilities.

DSInfo Channel

2003-06-18T06:23:12Z

Below is an excerpt from UPGRADING from the root
btechmux directory:

- DropShip landings and takeoff attempts, aborts and
successes are now logged to the 'DSInfo' channel,
rather than 'MechDebugInfo'. The format has also
changed to omit the colon (':') as @triggering on that in
scode is tricky. Scode that triggered on these messages
should be updated. DropShip deaths are now logged to
both MechDebugInfo and DSInfo. Newly logged, also to
DSInfo, are map enter/leave events for DropShips.

However, this channel doesn't exist in the example DB.
The README object sitting in #0 states that all channels
used by hardcode are created by default.

This is very minor, but it's one of those things that could
be easily overlooked.

Ice Elevation Calculated Wrong

2003-03-12T08:24:09Z

Following is from +bug 909 on 3030:

This is an observation of me standing at 5 5 on map
wyv.gulch.When I target the hex 4 8 I get the error
saying there is no los while hexes in between are lvl 0
plain and lvl 1 ice.After I break the ice at 4 7 and that
hex turned into water I could fire as I should be able to.
This takes me to the conclusion that ice elevation is
calculated as positive not 0 like water as it should
be.In other words a lvl 9 ice hex is not a lvl 9 deep lake
that has an ice layer on surface - instead it is a lvl 9
tower made of ice. Makes me remember Die Another
Day.

Repairs for 'reseal' shows limited info

2003-01-02T21:00:56Z

Plr Time Location +
Description
-------------------------------------------------------------------------
-----
13 89
-------------------------------------------------------------------------
-----
Note: Time = Time remaining in minutes. Plr = Tech's
dbref

notice the lack of location and action? :)

Physicals and PSkill XP

2002-11-29T19:51:42Z

You don't get PSkill XP for physical attacks.

Like, um, d'oh.

TSM and Heatcutoff

2002-11-29T14:47:37Z

TSM is bugged.

More to the point, HeatCutoff is lame to a level that is
mindboggling.

Having a command that allows a pilot to sit there and
pick his nose while the system happily maintains a 9
heat level for him so he can boost his speed eternally is
not only lame, but dumb.

If we're going to have such a munchy command then
there should be MASC-like consequences for having it
on too long... i.e., leg damage, blown actuators, etc...

Allowing mechs such as the MAD-5L to maintain a
speed 86 for how ever long it wants is foolish.

HULLDOWN command bugged

2002-11-21T13:59:07Z

Quote from _bug: 797

You are able to start the HULLDOWN command when
the Quad is still running. This leads to an 118 speed
hulldown BSN. But when beeing HULLDOWN you can't
turn nor move. So I would expect the HULLDOWN
commands used during the unit moves requests an pilot
roll or denies the work till the unit is slowed down like
the enterbase command.

Enemy freqs when captured

2002-11-21T13:57:35Z

It seems that if someone gives a listchannels command
right before he gets captured, the output he gets will be
the list of the mech that captured him, givin a pilot
enemy freqs.

Fall damage

2002-11-21T13:53:23Z

Quote from +bug 741:

The other day skie and I were remarking about the odd
damage that one took when falling especially into
water... So we looked it up and then found the
code... and then rewrote the code to make it work
properly... This code fragment belongs in mech_move.c
about line 1000

if !InWater mech && MechRTerrain mech !=
HIGHWATER
damage = MechRTons mech /1024 + 5 / 10 *
levels + 1
else
damage = MechRTons mech /1024 + 5 / 10 *
levels + 1 + MechZ mech / 2

SoB

Blind recon by IDF BTH

2002-11-21T13:51:31Z

Quote from +bug 733:

Ok I know this has to be a bug but I dont know how you
would fix it.. With LRM IDF you can lock a hex and
know if an enemy is there or not just by the bth.. So if
you know the enemies approach roads you can just
lock one of the hexes on it adn just keep watching your
IDF BTH to know when an enemy passes through
the hex. Kinda cheesy and yes I did it though i think we
need to find a way to remove it.. perhaps make IDF fire
not show bth's?? Bout the only way I can
think of to stop it..