68 réponses à ce sujet

[Rolo Kipp]

<nodding in complete justification...>

Suggestions, concerns and questions all help to shape this baby.

The more people who think this is a "good idea, but too late for...", the more I think about how to include them in beneficiaries of Foundation.

Right now I'm thinking of a prefab teaser you can add to your legacy world and customize to demonstrate the flavor and wonder of your server. It would include something of my Hypermod idea to allow easy linking to Foundation or The Hub or The Nexus or whatever we call the super server...

This would be a "lobby" or "landing page" and allow admins to promote their servers and retain control of that promotion, rather than leaving it in the hands of possibly inconsistent management :-P

This would require:

• Mod-links be aware of whether a transition is player only or character-translate.
• Foundation be capable (nwnx option) of dynamically adding mod-links
• An easy to use interface for registering mod-links. Personally, I think it would be fantastic if the registry took place in a copy of the current Foundation in the toolset, where the admin could precisely place and configure his portal and accessories (perhaps adding a PvP portal to the Arena, or a social portal disguised as a tavern), then submit his registration. A reg app extracts out what he changed and the Foundation checks for conflict/inserts portal/(new area if necessary).

I think this is a worthwhile goal for the Foundation Options development :-)

<...that other people hear voices, too>

[henesua]

OK... so I think it is worthwhile to give you all an update.

Rolo, gave me a computer today that should be able to run Ubuntu (linux). I'm learning how to install Ubuntu on it. Then I am going to figure out how to install nwserver and nwnx. This will take me some time. But once I get it together, I'll be launching into work on the character translator.

If I have to make a choice as to which server environment I am targeting I am going to choose linux. Is there anyone out there that can pick it up for windows?

[Squatting Monk]

I use Ubuntu also. If you need some help, I can give you an assist.

[henesua]

I appreciate the offer. Let me have at it once more this weekend before I bother you for specific help on getting Ubuntu running.

With regards to Foundation, the recent conversation about CEP has gotten under my skin. The lesson I take away from it is that while initiatives like Foundation (or CEP) need not start out as completely transparent and open to the community, these projects should be managed in a transparent manner once they've gotten off the ground. In the long run, the project should be responsive to its users, rather than the users responsive to the project.

My motivation for Foundation is to give NWN a shot in the arm. To do this we need to have a strong vision, and implement it well. I think the vision at this point is primarily to enable PWs to link to one another with minimal fuss, and secondarily to create a base for any PW team to build their own vision on top of.

If this is successful, then I would prefer that Foundation at that point become an open-source project. The reason is that successful projects create inertia. This inertia is great when the project has a forward trajectory, but it is a major problem when they decay. So if there is little barrier to the community taking over, and reshaping the project to their desires, it is all the better in my mind.

• So I think we should have most discussion here rather than on our own website. At the least we must have a presence where the community is. When I dig in again, I'll make a group for us.
• Documentation will be important. I like doing this with a Wiki so that anyone can maintain this. Our website will be good for this, I think. I'd like to talk with acomputerdood about it as he migrated the NWNLexicon to a wiki, and might have some wisdom to share.
• In addition to solving the character translation problem, I'd like to come to terms with what common custom content will be required.  For example the skills.2da, will that need to be fixed?  Any other 2das that will need to be similar across all PWs? I'm looking at 2das that affect the characters, and whether certain things like skills could make PWs impossible to link.
• Distribution: how to do this in an open source manner without sacrificing stability?

Modifié par henesua, 15 février 2013 - 07:53 .

[Rolo Kipp]

<opening a door...>

Allow me to (politely!) disagree on one thing. I do agree community projects should be open-sourced and open-discussed, etc. I love the wiki idea and am quite willing to work with that.

I also strongly encourage the establishment of a group here and sub-projects as they relate to Foundation.

However, I think certain discussions should be focused - primarily the dev discussions - and not discussed here. The direction of the project, yes. The public discussions about where we are and where we're going, yes.

But technical dialogue related specifically to the structure and the content should be private to the extent that people should register their interest and the discussions moderated so as to *not* get side-tracked, "derailed" or cluttered with OT pun wars (*cough* guilty *cough*).

I don't mean to make them private and secret, but to keep them on target, with only people interested and invested in promoting the project, one way or another, participating. I have no problem at all about discussing options, goals, challenges here. But I'd like to keep the nuts and bolts separate.

<...too many>

[henesua]

Oh, Rolo, I am in full agreement on that.

I see these projects as having two phases.

Phase One. The team gets together, formulates a plan/vision, and implements it.
Phase Two: The project is out in public, and once it is the tight team that got things rolling gradually gives way to the community.

[painofdungeoneternal]

Just want to mention that the name of "foundation" and some starting work was started by Grinning Fool ( who developed the 1.23 downloader ) and was using his PW Khaladine as a test case for this. ( it included NWNx plugins, toolset plugins, additional tools for DMs, etc. but was aimed as a foundation for new PWs which allowed a new admin to start off with a well built base which is easy to modify ) Really more than just a community, but a way to make launching a PW no harder than doing a single player module.

What you are doing is entirely within the scope of his prior project, even if not exactly the same, and could really be part of the same project, but yours aimed at NWN1 instead of NWN2. I'd hate to have the NWN2 work resume and have it be perceived as misappropriating the name, but also think eventually merging work so it's available for those using both versions.

Quite a few of the more advanced ideas though, really hinge upon better content management, and some ability to recreate or mod the toolset, at least they do if you want to get the admin busy creating new content, areas and stories, instead of just spending all their time learning how to be a PW admin.

Some of what I am developing for Never Launcher, is designed to eventually support these ideas. Making it so a central set of rules can be set up, governing 2da content, so that all members have certain shared characteristics which allow transferring characters, and know all PW's have certain shared content, images, files, 2da cell entries, and tlk entries, but that each PW can also add on top of this their own customizations. And further all players could connect to a foundation world and have an easy method of installing everything needed to play there. Quite a vit of this is done manually in NWN2 via close cooperation ( many NWN2 role play worlds use the same exact haks and 2da files i set up for my PVP server ( like my monster pack ), and I use their modifications, my aim has been a way to get these updates to easily sync, yet be something more modular and not as unwieldy as a terabyte sized CEP for NWN2 larger than many users hardrives. )

Translation, server vault sharing ( vaultster ), dynamic bic adjustment, and even providing a PW the ability to provide template characters for new players is going to require more than a team approach and closer to the entire community coming together for a common cause, who knows perhaps players can even jump between NWN1 and NWN2 if they so desire.

Modifié par painofdungeoneternal, 15 février 2013 - 09:51 .

[henesua]

painofdungeoneternal wrote...

Just want to mention that the name of "foundation" and some starting work was started by Grinning Fool ( who developed the 1.23 downloader ) and was using his PW Khaladine as a test case for this. ...

What you are doing is entirely within the scope of his prior project, even if not exactly the same, and could really be part of the same project, but yours aimed at NWN1 instead of NWN2. I'd hate to have the NWN2 work resume and have it be perceived as misappropriating the name...

Ooops. *looks at Rolo* The name was his idea. *pointing*

Its a good name for this, but I can come up with something else if need be. Is Grinning Fool still around? If so, we should talk with him.

painofdungeoneternal wrote...
Quite a few of the more advanced ideas though, really hinge upon better content management, and some ability to recreate or mod the toolset, at least they do if you want to get the admin busy creating new content, areas and stories, instead of just spending all their time learning how to be a PW admin.

I'm not sure this is necessary. But even so this is not on my list of things to take on. Someone else would have to step up. My thought is that these kinds of improvements are not a high priority need, certainly not as high as the work you are doing:

painofdungeoneternal wrote...
Some of what I am developing for Never Launcher, is designed to eventually support these ideas. Making it so a central set of rules can be set up, governing 2da content, so that all members have certain shared characteristics which allow transferring characters, and know all PW's have certain shared content, images, files, 2da cell entries, and tlk entries, but that each PW can also add on top of this their own customizations. And further all players could connect to a foundation world and have an easy method of installing everything needed to play there.

Yes, I think your work is critical. And I've been hinting around that something like what you are talking about could make its way into our world.

painofdungeoneternal wrote...
Translation, local vault, dynamic bic adjustment, and even providing PW the ability to provide template characters for new players is going to require a team approach, who knows perhaps players can even jump between NWN1 and NWN2 if they so desire. A lot of this gets technical, and

Yes. This stuff is on the horizon. Character translation first and we'll see where it goes from there. Much of this will require people with more technical knowledge about NWN than I care to acquire.

And this speaks more to my desire to open source this project as soon as it is ready. I'm happy to give it the spark it needs to get moving, but there are many community members with far more competence than I at implementing the solutions you hint at. You are certainly one of those people, Pain, and I eagerly anticipate the work you are doing on the launcher. I use OS X to play the game, and appreciate that you haven't forgotten the red headed step child of NWN clients. 

Meanwhile I am getting MintPPC to run on an old PPC machine, and still working on Ubuntu on the AMD box Rolo gave/lent me.

Back to work for me.

[painofdungeoneternal]

I don't think he'd mind your using the name, he is semi retired ( lurks still in NWN2CR irc chat ) and NWN2 tends to have projects mirroring those of NWN1. Really I can't see another name you would want to use, and it was always just planned and pieces, I think actually working on the games development and finding out his work on 1.24 would not be used kind of hurt things, he had a lot of good ideas.

I never had time to really focus on this, and really just want to reserve the ability to do something in this vein for NWN2, perhaps even porting what you have done, and porting what he has already done back to yours.

I'll be keeping an eye on this, and I will adjust features I am developing to support what you are trying to achieve of course. While quite a bit different on the surface, well my program actually is my set of tools for managing my NWN2 PW, and help the players thereof, so under the surface there is a lot of synergy with what you are doing, and I think we'll be collaborating quite a bit in the future.

[henesua]

OK. thanks for the encouragement, Pain. The thought that you'd be happy to collaborate is encouraging to say the least.

What I am most excited about is your work on the autoloading of dependencies for a module. If we could get something like that in NWN 1, the whole question of "to CEP or not to CEP" would be moot, and free the community from being anchored to old content. AND it would enable me to focus my efforts on organizing a custom content package that would work for multiple worlds. Things that move around with the character for example: phenotype, heads, clothing, equipment, skills, feats, spells, etc.... I'd like to just focus on a way to organize how these elements could interoperate across multiple servers with different design choices - rather than spend my time creating a better CEP with all the tilesets, placeables, creatures, visual effects etc.... that every world might want.

Instead of foucsing on one over all package it would be also easier to create themed packages that don't compete with one another. Sci-fi, modern, renaissance, high fantasy, low medieval, classical, prehistoric... etc...

Which leads me to the next thought: we need to work with the folks at WSI I think. They did some great work on their HAK set up. I do prefer what I did on Arnheim, but that content is focused for Arnheim. The beauty of WSI is that it spans multiple themes.

Modifié par henesua, 15 février 2013 - 11:56 .

[Rolo Kipp]

<feeding two birds...>

henesua wrote...

painofdungeoneternal wrote...

Just want to mention that the name of "foundation" and some starting work was started by Grinning Fool ( who developed the 1.23 downloader ) and was using his PW Khaladine as a test case for this. ...

What you are doing is entirely within the scope of his prior project, even if not exactly the same, and could really be part of the same project, but yours aimed at NWN1 instead of NWN2. I'd hate to have the NWN2 work resume and have it be perceived as misappropriating the name...

Ooops. *looks at Rolo* The name was his idea. *pointing*

Its a good name for this, but I can come up with something else if need be. Is Grinning Fool still around? If so, we should talk with him

painofdungeoneternal wrote...
I don't think he'd mind your using the name, he is semi retired ( lurks still in NWN2CR irc chat ) and NWN2 tends to have projects mirroring those of NWN1. Really I can't see another name you would want to use, and it was always just planned and pieces, I think actually working on the games development and finding out his work on 1.24 would not be used kind of hurt things, he had a lot of good ideas.

One Grinning Fool to another :-) I'll try PMing him. If you have contact info, I'd like to bend his ear a bit :-)

I actually was thinking of Asimov's Foundation series when I thought of that, but it works on so many levels that I *don't* really think there's a better name. Still, I'd like to avoid stepping on toes, if I can.

painofdungeoneternal wrote...
Quite a few of the more advanced ideas though, really hinge upon better content management, and some ability to recreate or mod the toolset, at least they do if you want to get the admin busy creating new content, areas and stories, instead of just spending all their time learning how to be a PW admin.

I'm not sure this is necessary. But even so this is not on my list of things to take on. Someone else would have to step up. My thought is that these kinds of improvements are not a high priority need, certainly not as high as the work you are doing:

To some extent, that *is* the work he is doing - content management. It starts with a builder choosing what to include in the mod he's building. Those choices need to cascade elegantly to the player using that mod (and that custom content) down the line. It also involves the use of third-party tools to merge disparate content at the 2DA/.set/.are level. Which opens up the use of third-party tools to *generate* content (My old project NP-See would develop entire chains of NPCs with relationships and history and was planned to interface with NwN... except they wouldn't give me a REXX port :-P )

painofdungeoneternal wrote...
Translation, local vault, dynamic bic adjustment, and even providing PW the ability to provide template characters for new players is going to require a team approach, who knows perhaps players can even jump between NWN1 and NWN2 if they so desire. A lot of this gets technical, and

Yes. This stuff is on the horizon. Character translation first and we'll see where it goes from there. Much of this will require people with more technical knowledge about NWN than I care to acquire.

I'm liking all of this :-)

And this speaks more to my desire to open source this project as soon as it is ready. I'm happy to give it the spark it needs to get moving, but there are many community members with far more competence than I at implementing the solutions you hint at. You are certainly one of those people, Pain, and I eagerly anticipate the work you are doing on the launcher. I use OS X to play the game, and appreciate that you haven't forgotten the red headed step child of NWN clients.

Red-heads... Mmmmm... 

Meanwhile I am getting MintPPC to run on an old PPC machine, and still working on Ubuntu on the AMD box Rolo gave/lent me.

Gave.
With the intention to piggyback my NwN community interests on it :-) I've got Mini-vault sitting right here... ;-)
Some for me, some for you :-)

<...with one bag of seeds>

[omen_shepperd]

I am highly interested in this project, I have one question
however. Could the PRC be used with this project? I for one would like to
include the PRC into the PW I am Building and after looking at the discussion I
think the PRC could offer a few things you are looking for. It has a subrace
system built in; however it does require NWNX to work properly.

I would like to offer my assistance in any way that I can
help.  I have some skill in building,
minor scripting ability, some knowhow of putting things together.

[henesua]

Omen, I am excited that you are interested in helping out. Please do. The more the merrier. We need a team to work on this.

I'd have to look at the PRC closely to determine whether it would work. My gut instinct however is that no the PRC will not be compatible without a great deal of work.

The overarching vision behind Foundation is to enable servers to easily link to one another. A framework for Skills, Feats, Spells, Item Properties etc... will need to be designed specifically for Foundation. Given that the PRC forces our hand on a number of these character related 2das, it would dominate the design, forcing us to essentially accommodate the PRC to the detriment of the project, and that is something that I am not willing to accept at this point.

That is not to say that PRC or portions of it could not be made compatible and released as an add on to the Foundation.

I'm sorry that we aren't fully engaged yet. I need to get a server up and running with NWNX first, and I am using some old hardware for the purpose which appears to be having trouble with Ubuntu 12.04 desktop. Its gonna take me some time to get that sorted.

[Shadooow]

Okay, I read the whole thread. And I see a lot of talking about module related content such as script systems, persistency but nothing about custom content in haks and how this will work to avoid issues with CEP.

Im especially interested exactly in the way to distribute the haks to the players and what will be in the haks.

Autodownloader isnt everything. If this should be same for multiple PWs and you want to allow linking PWs together, many of the custom content must be same on all PWs.

- character parts, head especially so the character's appearance wouldnt change between PWs
- item appearances, same as above though less important
- custom feats, spells - this is important, if the player get a custom feat and then join a module without the feat in its feat.2da (that would be the hakless entry module), he would lose that feat (no matter ELC is off) (not sure about custom skills and classes, these might not be removed, but certainly will not work and might cause crash)

The best would be to make the haks modular somehow. So there will be multiple haks speficially designed for this project (I doubt that it will be possible to use any CCC month hak and just go ) and builder choose which he will want so his module will not be bloated with unused stuff. However, it might not be always possible to combine it together as all the stuff must be in 2das anyway otherwise a custom top hak would be needed.

btw:

henesua wrote...

I'm just throwing these out there for discussion. The top two I figured might be controversial so I wanted to raise that now. ShaDoOoW's spell system and the DMFI chat system are things which need to be considered at the beginning because they are fundamentally integrated with the module.

Extracting the spellscripts from the CP and adding them into base PW module would be against a CP rules - unless the CP wouldnt be installed on that server. It would also be very unfiendly to the builders having a ton of scripts inside a module. I could consider to allow to use the spell system externally and redistribute it, but I think it is not neccessary really, CP should be great start for a newstart module and redistributing all the CP files is allowed as long as it stays in BIF structure. Otherwise to avoid the bloating module with script other solutions have to be used: but add scripts into hak is very bad idea so only override would work. Or the solution that uses HR Base would work althought thats a bit unfortunate solution as well. Having all spells integrated in one script has certainly lot of advantages, but also many disadvantages...

Now, some suggestion about module script systems. There is a extremelly usefull framework in PRC called event-based scripting and I think this project would need something like this. It works similarly to the tag-based scripting except of its not based on tag. But the scripts looks similarly its divided on multiple events. It works the way that scripts must be "registered" with a function "AddScriptToEvent" and unregistered.

Module, creature, area, door, placeable then use a set of basic scripts that executes all the registered scripts.

it has a disadvantage that its not very efficient, but this disadvantage can be taken care of via nwnx if the part that loop all registered scripts and executes them will be moved into low-level nwnx engine. Which I should be able to manage.

This system would allowed modularity.

[Shadooow]

omen_shepperd wrote...



I am highly interested in this project, I have one question
however. Could the PRC be used with this project? I for one would like to
include the PRC into the PW I am Building and after looking at the discussion I
think the PRC could offer a few things you are looking for. It has a subrace
system built in; however it does require NWNX to work properly.

I would like to offer my assistance in any way that I can
help.  I have some skill in building,
minor scripting ability, some knowhow of putting things together.

PRC became too large, too overhooked with various workaround to make things work and last time I tried it was totally bugged. But NWNX might changed this its some time I playing with it so it my info might be outdated.

At any way, the latest PRC contains so many spellsword classes that there is absolutely no point of playing a regular sword class if a five base classes gives you the same + spells. Those imbalanced dragon-related classes and psionic are also off. But there is inside a lot of incredible stuff and I always liked many classes and spells and overally the new possibilities, I always liked the PRC and have nothing against them - just its not really workable for a PW. I have taken some of the best classes out and rescripted them from scratch using a new "technologies". If this project would want something like a PRClite Im offering my help with creating this. I think that Archmage become much of the standard  really.

Modifié par ShaDoOoW, 17 février 2013 - 10:40 .

[henesua]

Since I blew up the computer that Rolo gifted to me, I'm behind schedule to say the least. In my defense, it had some severe problems anyway. That damn CD drive would nly read the Ubuntu live CD 1 out of 20 times. It actually only read it once. And I tried another 19 fruitless times.

Anyway, that'll be solved, but I'm not going to be using NWNX very soon. So.... I decided to spend my time getting the FOUNDATION Group together, and organizing the project. More in depth conversations will migrate to the website when that is ready. But for now lets use the Group.

Since I can't work on the translator right now I am hoping someone else can jump on that. When I have NWNX working I'll gladly join in with you.

Once I get some other things off my plate I am going to begin working on a common HAK for character appearances - armor parts, heads etc... Due to the size of these files, and all of the phenos we'll be working with this could result in a few HAKs. I'll need to dig in more before I discuss specifics, and I want to speak with the folks at Realms of Mythology as they did some very nice work on this.

Modifié par henesua, 17 février 2013 - 10:49 .

[henesua]

ShaDoOoW,
Yeah, since I don't have a rig for NWNX yet, I'm shifting to the HAK design. I'm hoping someone else can start work on the character translator.

Regarding the Community Patch, I brought it up because we need to decide as a group how to make use of it. Do we require a PW have it installed? Do we make it optional? Etc.... I am not advocating for ripping stuff out of the CP and then redistributing it. The point is that it can be very useful, and we should consider how to take advantage of it.

Regarding the Custom Content, an auto downloader will take care of a great deal. So we don't by any means need to approach the CC portion like CEP did. However you are right that to enable a PC to jump between worlds we need to have a framework for the things that are connected to the character file.

Before we approach a design for how skills, feats etc... work however we need to understand how these characters will be translated. I don't know how much control NWNX will give us to completely recreate a characters skills, feats etc.... Assuming none, we would need common skills and feats. Assuming full control, we can create a template for how these 2das are put together for each world. Example - indexes up to 1500 are common. Indexes over that amount are world specific. Or whatever, many ways to approach it.

So with regards to PRC lite. I think that is a great idea. BUT before work begins on that we should have a translator working. The character translator is the core feature. I really need to get into this ASAP, but hope that someone starts immediately since its going to be some weeks before I can hit this.

[Squatting Monk]

Just for the record: do we want the character translation to be done by the lobby module, or by the receiving server OnClientEnter?

[henesua]

By the receiving server is my thought.

Example:
Server A - sending server
Server B - receiving server

each server has its own server vault.

Transition point at Server A to Server B when used by a PC, initiates communication with Server B. Server A thus receives name and a short description of Server B, and how translation will proceed in this case. Character is given this information, and the option to transition, or not.

Server B should be given the option to reject a specific player or character. (but lets deal with that later)

Given that transition occurs:
Server A - records whatever data it needs for the PC, and then lets them go.
On arrival at Server B there are two possibilities: First time arrival for this PC, or the PC already has a character in the server vault of B.

In either case, a copy of the PC bic from Server A will probably need to be sent.
This will then either be a full translation of the PC, or a reconcilation between the PCs current status, and the character on file with Server B.

Sorry for the sloppy description. Intention is to outline my thoughts on this.

[Rolo Kipp]

<setting up transits...>

My take on translation (and this is based on 2 years of work, back when :-P) is to establish baselines for translation and then server-specific "methods" that act on them.

So Alpha-world has a certain adjustment they make for their characters. Beta-world is slightly different. And Gamma-world - Hoo-Boy! crazy-different Warhammer 40K-on-shrooms-ish ;-)

So character translates from Alpha to Beta, Alpha baselines character (with *Alpha* requirements stored!), sends bic to Beta. Beta adjusts baseline to their requirements.

Player yawns and decides to take the plunge (into utter madness) and translates to Gamma-world. Beta baselines the character and transfers bic. Gamma warps it beyond recognition.
Player faints.
Comes-to and frantically retreats to safe and sane Alpha. Gamma restores baseline, transfers bic. Alpha finds character still exists on their server vault. Gives player choice of reverting to last saved bic or updating server vault. Player decides to keep the stuff he's gained, so he updates. baseline from Gamma is adjusted to Alpha standards.

Note: the baseline adjustments include things like XP, gold, magic item value, etc. Gamma gives 1,000,000 xp for each RoUS the player hacks apart, but Alpha is capped at level 10 non-prestige characters. XP is scaled to baseline and then to server. Gold, ditto.

This means all *translate-able* items must be based on a shared baseline of blueprints and scripts. Non-translate-able items/skills/feats/races are stored for return and otherwise ignored.

At least, that's what we were working on :-P

Edit: You're quick, Magus :-)

<...and laying down baselines>

Modifié par Rolo Kipp, 17 février 2013 - 11:42 .

[henesua]

By the way, for the purposes of the translator, I think it best to proceed with the assumption that we need NWNX to implement it.

[Rolo Kipp]

<not totally...>

Don't get me wrong, I'm *very* interested in incorporating NwNx. I think it is the future if we want to keep NwN viable.

But I am not sure it's *absolutely* required.

What *is* absolutely required is a method of reading, editing and transporting the bic and initiating this from within the module.

That certainly makes NwNx the primary candidate, but I am still open to any approach that will accomplish the same goal. Or, to rephrase it, I'm still agnostic about methods ;-)

Edit: Though I agree it's probably best to decide to go with NwNx now and start actually doing something, rather than wait for me to learn Ruby or for some other project to bear fruit ;-P

<...convinced>

Modifié par Rolo Kipp, 18 février 2013 - 12:10 .

[henesua]

Rolo Kipp wrote...

Edit: Though I agree it's probably best to decide to go with NwNx now and start actually doing something, rather than wait for me to learn Ruby or for some other project to bear fruit ;-P

Exacto!

[Squatting Monk]

You may be able to hack some character changes together using Shayan's, but substantial edits are going to require NWNX functionality. Unless you wanna make a whole new utility. IMO, why go to the effort if NWNX can already do what you need?

[henesua]

I agree with you Monk. The one advantage of writing a new utility would be to enable any server to run it. Run on any OS. Any CPU etc... But NWNX has much more functionality that we can take advantage of as well so we might as well just increase interest in it, and keep those wheels turning.