[cod] any scripters out there?

[Geoff Goas]

I need to be more clear. I have had problems in script before in which
even if I run the linux server in development mode, I still do not get
an error report in any of the logs, it will just crash. It also seems
that I will get undefined errors when not running in developer mode,
which never used to be the case in vanilla CoD.


On Sun, 5 Dec 2004 06:13:54 -0600, Jay Vasallo <jayco1 at charter.net> wrote:
> Nice site yer. LOL. Nice and simple...me likes!
> =o)
> 
> 
> 
> 
> ----- Original Message -----
> From: "yer" <yer at dirtysonofabitch.com>
> To: <cod at icculus.org>
> Sent: Sunday, December 05, 2004 1:45 AM
> Subject: Re: [cod] any scripters out there?
> 
> > This is specifically what developer mode is for.  It allows you to work
> > out the kinks in the script without having the overhead of the printouts
> > and extra developer stuff in the non developer mode.  What you should do
> > if you are having issues like this is to run your server using developer
> > mode for a few days.  Sometimes bugs dont show up until you get a bunch of
> > people playing under "normal" game play circumstances.
> >
> > Geoff Goas wrote:
> >
> >>this is something that really ticks me off about the UO linux binary,
> >>which may also be a problem present in 1.4 (but i dont think so, never
> >>had this problem with 1.1).
> >>
> >>if i missed a check (isdefined() for example) in my script, and the
> >>server executes the function with an undefined variable, or if you are
> >>doing custom hud elements and the hudelem you are trying to work with
> >>is undefined, the server will just crash out without any hint of error
> >>in the game log or the console log.
> >>
> >>this doesn't happen all the time, but it happens. it is very
> >>frustrating especially when you have just tested out the script
> >>locally (with developer mode ON) and then you upload the script to
> >>your <b>full</b> server then it crashes unexpectedly.
> >>
> >>then you're left scratching your head trying to figure out what went
> >>wrong.
> >>
> >>can this be taken care of in the patch?
> >>
> >>
> >>
> >
> >
> >
> 
>