• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

Edit Default Datasets: A possible approach

D

Darkholme

Active member
The concern I saw was that someone could export the game dataset and have a full game system that could be passed around without the appropriate license.

I have to ask, why can't you just set up your exported game dataset to incclude the license you need: that is, if I edit WoD and export it, it requires the WoD license for someone to open it.

I'm thinking based on the videogame Neverwinter Nights and its toolsets.
If you make a module in NWN using features from the expansion, people cannot open your module if they don't have the expansion themself.
 
I think that is the way that it does operate. We have a D&D3.5 user created dataset we pass around. But it uses your HL license as a core product.
 
You can edit any part you need (except the very very low level parts) by doing a ReplaceID of the object you are replacing.

You can (and I have) modify low level parts if you determine their uniqueid and do a ReplaceID on them (I've changed out internal parts of Animal Companions this way before.)
 
You must log in or register to reply here.
Back
Top