NWN Lexicon

[Legacy_Squatting Monk]

               I kinda disappeared for a while; life caught up with me. Trying to get back into it. Thanks for contributing, Shadow.
               
               

               

                     Modifié par Squatting Monk, 25 octobre 2012 - 11:29 .
                     
                  

            

[Legacy_Gorgon]

               I like what the community wants to accomplish with a wiki version of the Lexicon, but I'd suggest everyone uses it as it is intended. The localized 1.69 Lexicon has been a great resource tool, even with it needing major updating all round (most bugs/comments refer to v1.64-7...or older).

Honestly, I haven't even checked for an update to this in something like a year, since I use the 1.69 html when I need to remember something, but here I am checking. I think it is great that you (players who care about proper source material) are trying to provide it, but a wiki is about everyone making sure any changes are correct. Do revert or edit any that you know are wrong, or discuss the crap outta them on talk page for it until everyone is sure. No one is the authority on source material when it comes to a game we all play. They may be an expert, but never be afraid to say they are wrong. We already have a wiki for NWN like that.

And (per the last page of ideas) the Lexicon is useless if it has anything but exactly how the current version of the game works. 1.7...whut? You just lost any sort of support from a decade of persistent worlds when you go that route, or popular download module content. Stick to what the game is. Add any extras/options as separate headers for stuff like that. The home page has a (fairly accurate) definition for the word Lexicon, and if you want to add custom content to it, you should at least categorize it that way.

I'll be helping when I see something to contribute to it, but please maintain a link to the original 1.69 download guide as well (until you can update/find someone to do it too).
               
               

               

                     Modifié par A1-Gorgon, 15 novembre 2012 - 01:39 .
                     
                  

            

[Legacy_Shadooow]

               

A1-Gorgon wrote...

And (per the last page of ideas) the Lexicon is useless if it has anything but exactly how the current version of the game works. 1.7...whut? You just lost any sort of support from a decade of persistent worlds when you go that route, or popular download module content. Stick to what the game is. Add any extras/options as separate headers for stuff like that. The home page has a (fairly accurate) definition for the word Lexicon, and if you want to add custom content to it, you should at least categorize it that way.

whut? which support? It's the NWN lexicon who is supporting PWs not backwards.

What I wanted was to add a pages for few functions I created in my pet project and some constants I added, maybe even mention that function X and Y is bugged in this and this case and that there is fixed code in my pet project - or even provide source.

But due to the general aversion around my project I won't do it. I guess I take the advice of all those haters to "make my own lexicon" if anything.
               
               

               
            

[Legacy_Squatting Monk]

               

henesua wrote...

Add any extras/options as separate headers for stuff like that. The home page has a (fairly accurate) definition for the word Lexicon, and if you want to add custom content to it, you should at least categorize it that way.

QFT

ShaDoOoW wrote...

What I wanted was to add a pages for few functions I created in my pet project and some constants I added, maybe even mention that function X and Y is bugged in this and this case and that there is fixed code in my pet project - or even provide source.

But due to the general aversion around my project I won't do it. I guess I take the advice of all those haters to "make my own lexicon" if anything.

A great place to do this would be on your user page. You can put whatever you want there and even create subpages if there's too much info to reasonably keep on one page. IMO, the more information the Wiki has, the better. We just wanna make sure the information is well organized and that folks can clearly tell what is native and what is third party.

Obviously, my opinion is not the only one that matters, but I think the Lexicon should be the one-stop shop for your script documentation needs. As it stands right now, it's great for figuring out how a single function works. But the accumulated wisdom of years of scripting is largely spread out on the forums (and the Social forums search sucks balls) or filed away in the Omnibus. In the Wiki it can be consolidated and cross-referenced.

There's also lots of useful third-party systems (NWNX, anyone?) that have either minimal documentation or house their documentation on private, unmaintained sites. Adding and expanding this stuff on the Lexicon will go a long way toward making sure it's still available and useful for years to come.

But, again, this type of stuff needs to be clearly separated from the standard NWN content. Side projects a la WikiProject would be nifty if there's enough people that want to work on a particular area. In the meantime, information about non-standard NWScript should probably be confined to user pages.
               
               

               

                     Modifié par Squatting Monk, 24 novembre 2012 - 11:04 .
                     
                  

            

[Legacy_henesua]

               I wanted to add that the Wiki-fied Lexicon is Gold!

thank you, acomputerdood
               
               

               
            

[Legacy_Shadooow]

               

Squatting Monk wrote...

There's also lots of useful third-party systems (NWNX, anyone?) that have either minimal documentation or house their documentation on private, unmaintained sites. Adding and expanding this stuff on the Lexicon will go a long way toward making sure it's still available and useful for years to come.

But, again, this type of stuff needs to be clearly separated from the standard NWN content. Side projects a la WikiProject would be nifty if there's enough people that want to work on a particular area. In the meantime, information about non-standard NWScript should probably be confined to user pages.

Seems I missed your post. I think that this would be highly appreciated by manys. I can help with documenting all of that, if you create the "framework". Make the categories etc. The plugin list would be nice, there could be informations what plugins are outdated, what are their current version, where to download them, what is the NWNX2.ini settings - all I can provide. Then a category for each plugin so we could start adding function pages to that?
               
               

               
            

[Legacy_Squatting Monk]

               Before we go ahead with it and jump in and writing new articles, we might wanna nail down some guidelines. I added an article in the project namespace with what I think are some good policies. Thoughts?

In any event, I think it's good to start small. Let's add as much usable info to the main NWNX page as possible and then break off chunks into subpages as needed. Sound good?
               
               

               

                     Modifié par Squatting Monk, 02 décembre 2012 - 06:22 .
                     
                  

            

[Legacy_Shadooow]

               

Squatting Monk wrote...

Sound good?

Definitely. Good work.
               
               

               
            

[Legacy_CaveGnome]

               Hello all,

I found that the last 1.69 Lexicon version (net live and Vault download) lacks details on the 8 new tilesets added with the 1.69 Bioware update.

There is nothing on the "TILESET_RESREF_* Constant Group" table about:

Barrows interior, Castle exterior rural, Castle interior 2, City interior 2, Fort interior, Sea caves, Steamworks, Tropical. Data on the constant names and string values would be helpful i think ;-)


Edit:
Found this. Not sure it's 100% correct. But well, better than nothing...

Re-Edit:
to paraphrase Squatting Monk:
Tilesets added by the 1.67 and 1.69 patches do not have constants defined that match their values, so...

DESCRIPTION             STRING VALUE           STRREF
Barrows Interior            tbw01                        111467
Castle Exterior Rural     tno01                         111470
Castle Interior 2            tni02                          111469
City Interior 2               tni01                           111468
Fort Interior                  twc03                         111472
Sea Caves                     tdt01                          110680
Steamworks                  tsw01                         111471
Tropical                           ttz01                          110586
               
               

               

                     Modifié par CaveGnome, 21 octobre 2013 - 06:28 .
                     
                  

            

[Legacy_henesua]

                CaveGnome, where are you going online for this? The Lexicon is now a Wiki and so you can update it if you create a login for yourself.
               
               

               
            

[Legacy_CaveGnome]

               

henesua wrote...

 CaveGnome, where are you going online for this? The Lexicon is now a Wiki and so you can update it if you create a login for yourself.

Yes, this is the Lexicon i was refering to (tested the 1.69 offline version too). I know that i can edit the wiki, but prefer someone more knowledgeable in these matters check / confirm the issue first.
               
               

               

                     Modifié par CaveGnome, 19 octobre 2013 - 02:45 .
                     
                  

            

[Legacy_henesua]

               Ah, OK. Then I think the best way to do it is to post that to the Talk page of the Wiki. That way everything is at hand for someone working on it (and this will show up in the recent edits of the Wiki), and thus can be dealt with immediately by someone with the expertise and inclination.
               
               

               
            

[Legacy_Squatting Monk]

               I'll try to verify these values when I get home from work and then update the article. Thanks, Cave.

Henesua is right. Anytime you see that something is out of date, feel free to either change it yourself or post on the talk page for the article. Posting here is good for getting my attention (though I also try to keep up with recent edits), but posting on the talk page has the added benefit of making the information readily available to anyone else who needs it.
               
               

               
            

[Legacy_Squatting Monk]

               Hmm... these constants aren't in the game that I can see. Did you find them in a file somewhere, or are you just assuming the new tilesets ought to have constants like the others?
               
               

               
            

[Legacy_CaveGnome]

               

Squatting Monk wrote...

Hmm... these constants aren't in the game that I can see. Did you find them in a file somewhere, or are you just assuming the new tilesets ought to have constants like the others?

The only part i am reasonably sure is the "string value" and "strref" (tested Tropical and castle exterior rural with GetTilesetResRef()) and used NwnExplorer to find what i could). The constant part is a compilation of info i found with Omnibus and some educated guess but was unable to verify. I tried to parse some Nwn system files searching the constants with no success, but i am not a master searcher / hacker ;-) and as i don't know of a script instruction returning the constant names it was difficult to experiment. Was hoping someone with better skills could verify them, if not, perhaps we should replace these names with "UNKNOWN" entrys.
               
               

               

                     Modifié par CaveGnome, 19 octobre 2013 - 12:46 .