2 réponses à ce sujet

[Surek]

I have an idea / suggestion. I come from a builder background not a cc background.

After using the tool-set for 10+ years I still have no idea what content I could use server side only.

I think it would be extremely helpful not only to myself but to new people who join the NWN community for the first time. If someone could put a list together outlining what cc can be used server side only I think this would be super helpful to builders.

 

Maybe this is all obvious to other people but I'm a bit slow and still confused about somethings.
I would also think including 2das in that list would also be helpful. I would make that list myself but like I said I really don't know what goes where besides the obvious like tile-sets.

Again just an idea / suggestion I had.

 

In case I was not clear on what I'm asking. An example would be sky-boxes, portraits, load-screens.
If include these things on my server do others who join my server need to have them in order to play.

Thanks for listening

[The Amethyst Dragon]

If it's something a player would see in the game, it must be downloaded by that player before he or she can play, usually contained in a hak file (or sometimes in the NWN/override folder). Game files for anything a player sees or uses are not transmitted by the server to the player, they are instead read by the game directly from the player's hard drive.

 

You can have a hak that is pretty much empty for players that a builder can put module resources into server-side, but such a hak is limited in what it can contain: scripts, blueprints, 2da files that are only read by a module script, and a couple other limited use files.

 

Anything used by both the server and player client, such as 2da files for classes, skills, and spells, or tileset walkmesh files, must be the same in a hak on both the server and player computers. If they don't match, you could have crashing issues.

[kalbaern]

If it's something a player would see in the game, it must be downloaded by that player before he or she can play, usually contained in a hak file (or sometimes in the NWN/override folder). Game files for anything a player sees or uses are not transmitted by the server to the player, they are instead read by the game directly from the player's hard drive.

 

You can have a hak that is pretty much empty for players that a builder can put module resources into server-side, but such a hak is limited in what it can contain: scripts, blueprints, 2da files that are only read by a module script, and a couple other limited use files.

 

Anything used by both the server and player client, such as 2da files for classes, skills, and spells, or tileset walkmesh files, must be the same in a hak on both the server and player computers. If they don't match, you could have crashing issues.

To expand on the topic ... sometimes, with 2da files, it'll depend on what you do as to who needs what. You can change stack sizes in the base item 2da or even the weights of items and its only needed serverside. If however you do something like make wands holdable, the players now need the file.

 

This is a topic that pops up every few years and I'm not sure if any of us have ever compiled a list of all the things you can do serverside and those that both players and the server need. I suggest you experiment as you go ... ask if needed on a specific resource ... and have fun playing around with things to suit your own tastes.