the server will generate this file an each restart as a result of reading all itemdesc.cfg's. it was never made to be an input file - change your itemdesc.cfg's.
Shinigami wrote:the server will generate this file an each restart as a result of reading all itemdesc.cfg's. it was never made to be an input file - change your itemdesc.cfg's.
Shinigami
I allready have, and it still is like I haven't changed it
hmm... u've changed one of your itemdesc.cfg's? and than u've [re]started your Pol-server? and nothing was changed inside objtypes.txt? if it is so, did u've checked, that the package where your itemdesc.cfg is located was set to active (check the pkg.cfg inside same folder)?
Shinigami wrote:hmm... u've changed one of your itemdesc.cfg's? and than u've [re]started your Pol-server? and nothing was changed inside objtypes.txt? if it is so, did u've checked, that the package where your itemdesc.cfg is located was set to active (check the pkg.cfg inside same folder)?
Shinigami
No no I haven't restarted the server, I am wondering if these changes can be done without restarting
You didn't understand Shini's post. That's not a file the server is reading. That's a file the server is making for your information. It only shows the objtypes you are using in all your itemdesc.cfg. So it is just an information file for you to see e.g. in which pkg an objtype is used or which objtype is free.
Pierce wrote:You didn't understand Shini's post. That's not a file the server is reading. That's a file the server is making for your information. It only shows the objtypes you are using in all your itemdesc.cfg. So it is just an information file for you to see e.g. in which pkg an objtype is used or which objtype is free.
Yeah, but why doesn't the server see my changes in the itemdesc files without a restart?
because the server will not accept modification of itemdesc.cfg's on runtime. there are tons of reasons... main point could be data integrity and/or performance
Shinigami wrote:because the server will not accept modification of itemdesc.cfg's on runtime. there are tons of reasons... main point could be data integrity and/or performance
Shinigami
Okay, thanks, that kind sucks But still, thanks anyway