Right, the delay is set to 0, but not before the server would send a
newwarning message to client that your battle computers are being
reprogrammed.  This prevents that message from being sent (I came across
this while adding a timer client-side to keep track of declare war delay.
If the server is not going to give us a delay, the delay message should
not be sent, period.)

As for bots, the whole problem with observers locking onto iggies and then
not being able to do anything (lock onto someone else, quit, etc) was due
to bots being in a permanent state of delay (their war timer is never
decremented like a player's timer).  This was partially fixed by a
previous patch of mine by not masking the PFWAR flag to observers.  This
second patch gets at the root of the problem - bots should not be flagged
PFWAR.  Of course, bots don't freeze cause they don't have to input

 On Fri, 19 May 2006, Trent Piepho wrote:

> There is no declare war delay when switching teams, the code in enter.c
> sets the delay to 0.  You still get a declare war message delay message.
> Not sure what you're talking about with the bots.  They will freeze up
> when they try to declare war?  I've never seen that happen.
> On Fri, 19 May 2006 williamb at its.caltech.edu wrote:
> > Fri May 19 01:57:53 CDT 2006  williamb at its.caltech.edu
> >   * declare_war fix
> >
> _______________________________________________
> netrek-dev mailing list
> netrek-dev at us.netrek.org
> http://mailman.us.netrek.org/listinfo/netrek-dev