1. True. I wrote NWNX code for Arelith using my own framework (which has now been dubbed NWNX:EE, or Nixie, depending on who you ask). I did not contribute my code to the main repository because it was incompatible. I (re)wrote everything from scratch for fun, and because I thought it could be done in a safer and more future-proof way. 2. True. 3. No. 4. No. 5. "Last known maintainers" is as little wishy-washy. I presume you're talking about virusman, who is involved indirectly with this project, or niv, who is involved directly with this project. Or you might be referring to one or more of the many others who contributed over the last ten years and continue to contribute to the 1.69 project- or how about those with their own private branches - or maybe those who worked on the Windows version, which is its own entity? The point I'm trying to make is that I don't think "brand loyalty" applies here. NWNX is just a framework to allow developers to write their own plugins. I don't own it, and neither does virusman or niv or any of the other developers who have worked on it in the past - it's an open-source community project that belongs to nobody.
Windows is a work in progress. You may want to check into the discord channels mentioned above. I believe for the time being @Sherincall is trying to get a windows nwnx-lite (sql only) implemented; if you need more advanced features, it will be some time for that problem to be tackled.
You'll get support in the #windows channel of the NWNX discord (first page of this thread). I'm yet to write some actual docs, but the shortest version is:
- copy bin/dist/.. binaries into the folder with nwserver.exe - copy nwnxlite.ini into that folder, and edit the settings - use nwnxlite.nss as the implementation for aps_include Please backup your database before doing this.
Report bugs in discord or on the github page. Pull Requests welcome as well
Wonderfull news, now any chance to get sqllite support? And no one has vcruntime140d.dll unless you have a development version, maybe you could include it? nvm, I see it requires all of visual studio, to be honest I'm not a programmer so I'll have to wait till you get a release version out
If Beamdog was really serious about this game they should not have released it on Steam without their own version of NWNX and at least to some extent updated textures and models...
The "x" in NWNX stands for "extender". By definition, it is meant for handling things outside the scope of the NWN base game, and will never be "official" - if it were official, obviously it would be a part of the game, and you wouldn't need an "extender"
Rather than pushing for an an official version of "RL developers hack game for weird hobbies and share the love", you'd be better off considering what actual features you want in the base game and campaign for those specifically. Some will probably make it in eventually as people go along, more may be buried beneath mountains of jackhammering work to be done first (eg UI overhaul), other things may just never be considered appropriate for core for a variety of reasons. Some may already be implemented, WIPs, or are in discussion on roadmap.
It's easier to talk about what people want out of those different features (and if needed, could they achieve something people want to do a different way than what they think they want?) than "we want NWNX only branded" though, you know?
(All that said, I find comments like "if they were really serious about this game they would..." difficult, because everyone who says that seems to have a different item that would have "proven" they were serious, without which they have done "practically nothing" somehow.)
Any movement/update toward a fully windows nwnxee? All I would ever need is basic char-deleter and a watchdog, not possible by beamdog as base nwn feature?
Any movement/update toward a fully windows nwnxee?
Not for the near future. It's possible (but not confirmed or promised) that Windows work may be picked back up at some point after the 64bit update. Docker is a well-supported alternative for hosting on Windows + nwnx, though.
Any movement/update toward a fully windows nwnxee?
Not for the near future. It's possible (but not confirmed or promised) that Windows work may be picked back up at some point after the 64bit update. Docker is a well-supported alternative for hosting on Windows + nwnx, though.
No such plugin exists currently. You're free to request it on github. I recommend also explaining your use case as that might help getting it prioritized, or someone might even know of a better solution.
I do have some sources from the nwnx2 windows version (Terra777) on GitHub. I am using it as a alternative to sql, when only little things should be stored externally (like vars or texts) and be changed on the fly by editing the ini file. Would it be possible for a not so quite good coder like me, to convert that into a port for nwnx:ee (I hope you know what I mean)?
Hi, can someone help me with one issue? In this line "Add nwnxlite.nss to your module. The API is compatible with the aps_include.nss available for NWN 1.69" Where I should add my script in module ? As include of aps_include.nss? Or edit aps_include.nss and replace this functions? Or something else?
@DeviC3: This is easier Open your mod, go to your game folder and look into modules. There should be a tempX (where X is a number) copy the nwnxlite.nss to this place. Do a little change to your mod and save it.
No wait... When you open the module in the toolset. Not when running within the server. The nwnxlite.nss is a script, a library with functions to forward infos to nwnx:ee.
NWNX is truly amazing and the persistent world community lives and breaths by it.
Thank you for everything!
However, I was wondering if someone could perhaps answer a couple of questions I have had for a decade now?
I have heard repeated many times to "Don't use the Bioware database because it bloats because it doesn't properly delete entries" but that's all the detail I have ever received.
So if I may inquire:
What exactly is borked with the Bioware DB and to what extent?
Does the server OS have an impact?
Could it be used in a PW if I were just using simple Boolean functions or is it just a mess?
Comments
1. True. I wrote NWNX code for Arelith using my own framework (which has now been dubbed NWNX:EE, or Nixie, depending on who you ask). I did not contribute my code to the main repository because it was incompatible. I (re)wrote everything from scratch for fun, and because I thought it could be done in a safer and more future-proof way.
2. True.
3. No.
4. No.
5. "Last known maintainers" is as little wishy-washy. I presume you're talking about virusman, who is involved indirectly with this project, or niv, who is involved directly with this project. Or you might be referring to one or more of the many others who contributed over the last ten years and continue to contribute to the 1.69 project- or how about those with their own private branches - or maybe those who worked on the Windows version, which is its own entity? The point I'm trying to make is that I don't think "brand loyalty" applies here. NWNX is just a framework to allow developers to write their own plugins. I don't own it, and neither does virusman or niv or any of the other developers who have worked on it in the past - it's an open-source community project that belongs to nobody.
-Dave
You'll get support in the #windows channel of the NWNX discord (first page of this thread). I'm yet to write some actual docs, but the shortest version is:
- copy bin/dist/.. binaries into the folder with nwserver.exe
- copy nwnxlite.ini into that folder, and edit the settings
- use nwnxlite.nss as the implementation for aps_include
Please backup your database before doing this.
Report bugs in discord or on the github page. Pull Requests welcome as well
sqlite might come later, but I'd first be adding it to core nwnx:ee, and then port over to nwnxlite.
Rather than pushing for an an official version of "RL developers hack game for weird hobbies and share the love", you'd be better off considering what actual features you want in the base game and campaign for those specifically. Some will probably make it in eventually as people go along, more may be buried beneath mountains of jackhammering work to be done first (eg UI overhaul), other things may just never be considered appropriate for core for a variety of reasons. Some may already be implemented, WIPs, or are in discussion on roadmap.
It's easier to talk about what people want out of those different features (and if needed, could they achieve something people want to do a different way than what they think they want?) than "we want NWNX only branded" though, you know?
(All that said, I find comments like "if they were really serious about this game they would..." difficult, because everyone who says that seems to have a different item that would have "proven" they were serious, without which they have done "practically nothing" somehow.)
All I would ever need is basic char-deleter and a watchdog, not possible by beamdog as base nwn feature?
Not a nwnx dev, just lurk a lot.
Would it be possible for a not so quite good coder like me, to convert that into a port for nwnx:ee (I hope you know what I mean)?
In this line "Add nwnxlite.nss to your module. The API is compatible with the aps_include.nss available for NWN 1.69"
Where I should add my script in module ? As include of aps_include.nss? Or edit aps_include.nss and replace this functions? Or something else?
This is easier
Do a little change to your mod and save it.
The nwnxlite.nss is a script, a library with functions to forward infos to nwnx:ee.
Thank you for everything!
However, I was wondering if someone could perhaps answer a couple of questions I have had for a decade now?
I have heard repeated many times to "Don't use the Bioware database because it bloats because it doesn't properly delete entries" but that's all the detail I have ever received.
So if I may inquire:
What exactly is borked with the Bioware DB and to what extent?
Does the server OS have an impact?
Could it be used in a PW if I were just using simple Boolean functions or is it just a mess?
Is there documentation of the problem somewhere?
Thanks,