Page 1 of 1
Some questions about settings in the cfg files.
Posted: Wed Sep 13, 2017 9:20 pm
by Yukiko
I am providing hints to the various config file settings in my program and I need a little help from the developers. I couldn't find adequate documentation on a few settings.
What do the following settings do and what are the advantages to having them set or not set?
In pol.cfg
Code: Select all
SingleThreadDecay
ThreadDecayStatistics
I assume this setting does what it says. If I'm wrong let me know.
In combat.cfg
What is the maximum level this can be set and what do the various levels invoke?
In pol.cfg
And last of all...
What does RPM mean in the setting WatchRPM in pol.cfg?
Thank you in advance for the help.

Re: Some questions about settings in the cfg files.
Posted: Wed Sep 13, 2017 10:22 pm
by Yukiko
I forgot one. In servspectopt.cfg
What does WatchMapCache actually do?
Re: Some questions about settings in the cfg files.
Posted: Thu Sep 14, 2017 9:15 am
by Turley
SingleThreadDecay:
I would say the preffered setting is True. In former days or without this setting active each realm has a dedicated thread with the only purpose to iterate over the complete map to find items to destroy. With this setting active it's only one thread for all realms.
ThreadDecayStatistics:
(Only used with above setting also set)
Since iterating over the complete world to find items to destroy is really a big overhead the story is not over. I added this setting to print statistics per run how many items are able to decay currently and how many items got destroyed to find the best implementation. I hope I will find time again to finish this todo. I would be glad if any shardowner who reads this activates this for a few days and sends me the log prints.
WarmodeInhibitsRegen:
Yes name is selfexplaining without other side effects (oh my god)
DebugLevel:
The current highest level is 22. All of them pretty senseless if you don't search a bug somewhere near these lines. Search for INFO_PRINT_TRACE in the sources to find the spots and what they print.
WatchRPM:
The tachometer "rotations per minute" prints some informations how busy the script scheduler was
WatchMapCache:
I guess this is a left over, atleast the variables which get printed never change, plus our map is completely in RAM there cannot be a cache miss.
Re: Some questions about settings in the cfg files.
Posted: Thu Sep 14, 2017 9:42 am
by Yukiko
Thank you Turley.