Quote:
Originally Posted by Zothen
Hmm, what about the missing .path and spell files (.pl) ?
|
Missing .path files just means you don't have a .path file for that zone in your maps folder. Most zones don't have them unless you make them yourself manually.
The spell file errors are not really errors. They are a bit misleading and probably should be added to some filter so they don't show up in normal perl errors. Basically, all that means is a spell was cast that does not have a spell script in your quests/spells folder associated with it. This will be true for nearly all spells unless you are making custom spell scripts for them.
Quote:
Originally Posted by Zothen
You say the op_code errors are normal? It gives me an uneasy feeling reading a patch file (e.g. 6.2) cannot be applied. Especially if its a file called "titanium_world"... :(
|
The patch errors is just how the server figures out which client version is running on the client that is connecting. It starts checking if it matches the 6.2 opcodes, and if not, then checks Titanium and so on until it finds the matching client version.
The other opcode errors you saw are for opcodes being sent that we currently don't do anything with on the server side and can be ignored. There are literally hundreds of unknown opcodes that the client uses that we don't have setup on the server end. There isn't anything you can do about that unless you want to identify each one and write handling code for them.
Quote:
Originally Posted by Zothen
How do you shut down your server instance smoothly?
|
I use "#worldshutdown 300 30" in game to shut the server down with a timer and message to my players. Then, I run a stop script since my server runs on Linux, which then basically just kills the processes. On Windows, you should be able to just close your command prompt windows to shut your server down.
Threaded Mode
