NWNX.INI option ignored

[DC]

Hi. I've recently upgraded NWNX2 to the version 2.6.1.1 (and the matching .dll files), on a fully-functional PW with HCR & CNR & NWNX2 in use.

Everything is working fine, more or less except:

the nwnx.ini options for odbc logging are being ignored. This info is interesting to see when needed, but I'd like to shut this logging off and can't.

[JeroenB]

That is normal. NWNX only reads in the configuration at startup time. this means that you have to restart both nwnx and nwserver when you changed a value in the configuration file.

[DC]

Thank-you but, I have done so. I think you missed what I put at the very end, my fault for hiding it down there.

The problem persists after shutting down NWNX2, the (NWN) server, and then relaunching NWNX2 (which in turn relaunches the NWN server). More than once.

Neither any change in the max log size, nor the logging option is used/honored/takes effect.

So, I changed the ODBC logging option. Shutdown NWNX2, then shutdown NWN server. Verified the nwnx.ini file still is set to 0

[Papillon]

What does your nwnx_odbc.txt log file look like ?

Mine looks like this:

[DC]

Mmm...

I'm taking care of a server where the person who put it together is just no longer available. It runs great, actually, including with the update of NWNX2 that I've done.

However, it seems the person who set things up, was using the Fast French system. I read up on that, and the author claims it can work in conjunction with yours, without problem.

Seems so.

EXCEPT... does the FF.ini over-ride the nwnx.ini settings ?

What I'm seeing in the odbc log is:

o Connect successfull.
o Got request: DESCRIBE cnr_misc
o Sent response (25 bytes): player¬varchar(64)¬¬PRI¬¬
o Got request: SELECT player FROM cnr_misc WHERE player='~' AND tag='MODULE' AND name='cnrForgePublic_DeviceLoaded'
o Sent response (1 bytes): ~
o Got request: UPDATE cnr_misc SET val='0',expire=0 WHERE player='~' AND tag='MODULE' AND name='cnrForgePublic_DeviceLoaded'

and so on, more info about CNR initializing successfully.

Then the log continues to fill up with entries for PC thirst or hunger values, etc.

o Got request: SELECT val FROM pwdata WHERE player='~' AND tag='MODULE' AND name='HUNGERLEVELFreido Fordgen

as well as many entries showing players using CNR crafting:

o Got request: SELECT val FROM cnr_misc WHERE player='MyAccount' AND tag='Brogden Gromden' AND name='CnrTradeskillXP_4''

-----------
On a Saturday, that log file's gotten as big as 8 MB before getting rolled/rotated !

I'd really rather not have that log there at all, at this point.

I just wanna shut it off

[JeroenB]

We do not support the FF system. I am even not sure if it is fully compatible with our latest releases.

[Papillon]

DC, you are using an old version of the database plugin. Maybe the one from FF or the old ODBC plugin. Get rid of the unwanted DLLs and install the ODBC2 module again.
_________________
Papillon

[DC]

Alright, thank-you. Did so.

One thing you should know that is VERY unclear is this:

are you expecting people to use the ODBC2, and then use the following in their nwnx.ini file ?


source = mysql
server = localhost
user = nwn
pwd = thepassword
db = nwn

The info here http://www.nwnx.org/index.php?id=doc_odbc2
says it should be:
[ODBC2]
server = localhost
user = nwn
pwd = thepassword
db = nwn


What about the existing NWNX2's nwnx.ini settings, where [ODBC2]
gets:
[ODBC2]
; Log file
MaxLogSize = 512 ; in KByte
LogLevel = 1 ; 0=nothing, 1=only errors, 2=everything

or whatever settings one chooses there.

See what I mean ? Which are you expecting people to use, for the latest NWNX2 ?

Thank-you (!)

PS: Please update this tutorial:
http://nwnx.org/index.php?id=tut2
it is giving erroneous info now that you no longer require nor support the FF setup and/or NWN-MySQL.dll

[Papillon]

That is the reason why prorammers just love writing documentation.... *sigh*

I'll see what I can do.
_________________
Papillon

[NoMercy]

By NWNXs nature of being GPL, people are free to take it, and improve it, or use it's code in there own products, as long as they credit the original authors and use the GPL license for the software they include it into. NWNFF is as they call in the software community, a 'fork' where the code is split and taken in a different direction by someone who usually disagrees with the direction the main project is going in.

There totally separate projects, apart from the fact there both GPL, and NWNFF uses code from an early version of NWNX to do most of it's operations.

- guess it's a kinda thing you could put in a FAQ :)

I love writing documentation, primarilly I like writing it just above every function in some horrid form of broken-english, just users hate to read that to find out what the program does :)

[DC]

Sorry : /

Forget the whole FF thing anyway.
Turns out it was NOT being used since the mod's aps_onload was the NWNX one, with the option of adding the necessary include for FF, but such was not the case here.
I found that it's NOT in use, but the plugins had been left "lying around" in the NWN directory. Hence, my confusion.

Apologies.

Now, as for your current pages for NWNX2, it's not like I went digging to find (what is now) incorrect information...

Click on your "documentation" link on your front-page, taking me to here:
http://www.nwnx.org/index.php?id=docs

Right there, click on "Tutorial 2" for "Setting up NWNX2 with MySQL"

I thing you should put a line in bold on the front page, saying something akin to "For the current version of NWNX2, all the documentation you need, and the only documentation you should use, is here" :
http://www.nwnx.org/index.php?id=doc_nwnx

That's all I'm saying

Hey, and thank-you for this. I'm sure you get more griping than thanks sometimes, I did not mean to be that way. Thank-you !

[Papillon]

No offense taken You are right about the lacking state of some of the docs on this site.
_________________
Papillon