Logging Stopping?
I am experimenting with things on a local test environment. I can log in, interact, do normal things, etc etc. What I cannot do is get the logging to continually work. The logging stops after the first error or a ~50 new lines in the zone_* logfile.
Is there some painfully obvious missed step or something specific that is required to get quest logging to stay running? I am trying to debug quest scripts but with logging stopping after a singular error or ~50 lines, I am forced to restart server to test each new script change (instead of just #reloadquest). As you can imagine, it's slow and cumbersome this way. Any tips? :-) -Hate |
How are you testing? What logging method are you talking about? Are you inserting log file entries into the code and then compiling?
|
Apologies. The basic logging that seems to occur by default. Goes into the "logs" directory with a variety of file names.
I was trying to watch for the errors spit out in the zone_*.log files about the quest script. I have not done anything to the code other than the DivineSave change listed in the SpellSupport section. -Hate |
If the error logs are stopping, perhaps a disk issue. If you are testing perl scripts, you can also use shouts/says/etc. if you can't get logs to work.
|
Testing Quest Scripts 101:
#1 open a command prompt and type: perl -c somescriptname.pl #2 If errors, fix them, go back to #1. If no errors go to #3 #3 The script compiles fine but is not acting as expected. Add in quest::shout("some message"); at various points in the routines to output what is happening. #4 based on the shouts, edit your script. do not forget to #reloadpl 1 in game. # Go to #1 |
Quote:
and if you're going to write complex scripts on a regular basis, i'd recommend learning to write subroutines and classes which behave as the interfaces found embedded in the server do. the classes don't have to be completely mirrored. just give them the methods you need for testing. it may seem like a daunting task, but you'll learn a hell of a lot about perl and the server while putting it all together. eventually, you won't need to have access to a running server to develop your scripts. example with timers and entity variables roughly emulated: Code:
use 5.012; http://modernperlbooks.com/books/modern_perl/ |
All times are GMT -4. The time now is 06:17 PM. |
Powered by vBulletin®, Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.