death problem

Get Help on scripting in POL with configurations, config setups, script trouble shooting, etc.
Post Reply
Gnafu
Grandmaster Poster
Posts: 136
Joined: Thu Feb 02, 2006 7:29 am

death problem

Post by Gnafu »

I have the same problem as reported in the "strange bug" post under the "097 bug report" forum but i can't solve it.

Here some log:

Code: Select all

Abnormal end after checkpoint: File .\charactr.cpp, line 1868
Exception in: scripts/textcmd/pager/kill.eclDouble: Error starting script.
 PC < nLines: (onaryObjUnknown console command: '+'



Abnormal end after checkpoint: File .\charactr.cpp, line 1868
Exception in: pkg/foundations/combathook/combat.eclator .+ undefined: Error starting script.
 PC < nLines: (> a parameter.Waah! Admin 0x228 is dead, but taking damage?

WARNING: scripts/misc/chrdeath.ecl: Unable to find module http
Abnormal end after checkpoint: File .\charactr.cpp, line 1868
Exception in: scripts/textcmd/pager/kill.eclDouble: Error starting script.
 PC < nLines: (onaryObjsysload=1 (0) cputime=50072
I changed the chrdeath.src adding a sysmessage a syslog and a print message tu debug it but it seems not to be called, so where is the problem?
I have no charactr.cpp file...

Please help!!
Thanks

PS:
POL097-2006-10-25 Coregina (VS.NET 2003) compiled on Oct 25 2006 07:50:00 running.
User avatar
CWO
POL Expert
Posts: 1160
Joined: Sat Feb 04, 2006 5:49 pm

Post by CWO »

Admin is dead but is taking damage is saying just that, a script tried to damage someone that is already dead. This isn't a very critical error, more like a warning. Check your ecompile.cfg to make sure its checking in the right place for ems. Also, make sure you're using all of the ems from the exact core you downloaded. Always delete all .ecl files and recompile after replacing EVERY file that comes with it including ems, all executables and such, under any core change. You'll also never have a .cpp file for POL. Thats one of the files that makes up the core and only core devs have access to it. But an exception caused in it is more likely than not, something with your scripts that it didn't expect like .ecl file compiled under an older core.
Gnafu
Grandmaster Poster
Posts: 136
Joined: Thu Feb 02, 2006 7:29 am

Post by Gnafu »

Yes, that was the solution..
I must remember sometimes to add a -f in the ecompile.exe commands line -_-
Post Reply