<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
If there is a crash which actually crashes the exe you will not get a
print out even in developer mode. The system shuts down before it can
write anything out. Vanilla 1.1 cod did not have as stringent
requirements on variables but this was found to be a major issue and
much more enforced cases on undefined variables or dead entities was
added for 1.2 cod. <br>
<br>
I sympathize with your problems. There were several cases of very hard
to track down bugs in script that would happen but we could not figure
out what was going wrong for a while. My suggestion is to check issues
with people disconnecting and how it affects your script. This was
usually the root of the problem. If you have a buddy (or two
computers) that you can test with try having the person disconnect
right in the middle of your stuff. Also dead players need to be
handled specially since many script functions do not consider them
valid. Hud elements attached to people who either die or disconnect
are the same. If you look at the vehicle code (mp\_tankdrive_gmi.gsc)
you will see that we had to jump through a lot of hoops to make sure
the hud elements for people who die or disconnect are handled correctly.<br>
<br>
Usually the thing I found best to test is to run a listen server in
developer mode while people were playing. If you could get people you
know to help test then you may get something. Also the best clue to
the hard to find crashes usually came from the people who were
playing. Something like "Oh I just got out of the tank and the server
crashed." .<br>
<br>
Hope this helps. <br>
<br>
<br>
Geoff Goas wrote:
<blockquote cite="mid20c32039041205193227c77e4b@mail.gmail.com"
type="cite">
<pre wrap="">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 <a class="moz-txt-link-rfc2396E" href="mailto:jayco1@charter.net"><jayco1@charter.net></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Nice site yer. LOL. Nice and simple...me likes!
=o)
----- Original Message -----
From: "yer" <a class="moz-txt-link-rfc2396E" href="mailto:yer@dirtysonofabitch.com"><yer@dirtysonofabitch.com></a>
To: <a class="moz-txt-link-rfc2396E" href="mailto:cod@icculus.org"><cod@icculus.org></a>
Sent: Sunday, December 05, 2004 1:45 AM
Subject: Re: [cod] any scripters out there?
</pre>
<blockquote type="cite">
<pre wrap="">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:
</pre>
<blockquote type="cite">
<pre wrap="">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?
</pre>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
<br>
</body>
</html>