This is an EXPERIMENTAL version of a BIC files manager for use by Persistent Worlds
As usual, some Warnings and Disclaimers:
USE IT AT YOUR OWN RISK
MAKE BACKUP OF YOUR SERVERVAULT FOLDER BEFORE YOU TRY IT
MAKE BACKUP OF YOUR DATABASE FOLDER BEFORE YOU TRY IT
AS IT IS NOW IT THIS TOOL IS *****UNTESTED***** AND AS SUCH MAY COMPROMISE THE STABILITY
OF YOUR SERVER
OK, now what does it do?
Charpenter usesd to be my super secret project that I planned to use on my PW. I named it first VaultKeeper and started by rewriting all of LetoScript in CSharp until I got bored and gave up.
Recently I went back to it and decided to make something simpler and focus on a few tasks.
I tell you this because you need to understand that this is a personal project that I make available to you. Hence don't expect much support from me though if you report problems they will get my attention. But if you expect me to add features, I might or might not be interested.
On another hand feel free to take the source code and fork this application so it tailors your needs.
Also note that most of Charpenter features (if not all) are provided by NWNX4. So if you look for an alternative you could consider installing NWNX4 instead.
FEATURES
Those are currently available:
Add/Remove Tail and Wings to a character
Make a character nude
Delete a character
There are many other possibilities, but until I get more confident in the stability, I will stick to these.
METHOD
Charpenter uses the Campaign Database for communication. I'm wondering if I should have used the logfile instead, however it will stay that way for now.
INSTALLATION
Charpenter comes with an executable compiled in csharp. You need to install it along with OEISHared.dll
So, either create a folder for it and copy your OEIShared.dll into it, or copy Charpenter to your NWN2 server installation directory, whichever method you like best.
Charpenter must run on the server machine. Though it might be able to work on a network but I never tested that.
Once charpenter is installed you need to locate your servervault and database folders.
You also need to specify the prefix for the database files. The default prefix is chp_ and you should leave it that way unless you have good reason to do so (ie. if your own databases share the same prefix).
When you are ready click "Start" and Charpenter will start looking for the changes to the databases prefixed with "chp_" (or whatever else you specified).
Now it's time to make your module Charpenter aware. Import the Charpenter.erf file to your module and you will get the scripts prefixed chp_ and a conversation that is provided as an example for you to modify.
You will need also to modify your module client_leave script. If you dont have one then you can use the chp_client_leave script provided.
You can use the example scripts or make your own, the example scripts are used by chp_leverconvo.
There is an example module provided. You will see two levers in the module. One uses chp_leverconvo, the second is used to reset the databases. You will need to do that at least once.
If you have changed the prefix in the application you will need to change it accordingly in the scripts, the relevant file is chp_inc_charpenter. Don't forget to Compile All files after.
OPERATION:
The module is meant to be started through a server, not with the client.
The first time you enter the module you will need to prepare the database by using the "Make ready" lever. Then you can use the conversation and start making changes to your characters.
At the end of the conversation the character will be booted and the changes applied to the bic file.
TROUBLESHOOTING:
Should you have any problem getting the conversation starting, you need to delete all the databases prefixed chp_ and use the "Make ready" lever again.
REMEMBER
MAKE BACKUPS OF YOUR SERVERVAULT AND DATABASE FOLDERS BEFORE TESTING THIS!
10 - A Masterpiece, Genuinely Groundbreaking 9 - Outstanding, a Must Have 8 - Excellent, Recommended to Anyone 7 - Very Good, Deserves a Look 6 - Good, Qualified Recommendation 5 - Fair, Solid yet Unremarkable 4 - Some Merit, Requires Improvements 3 - Poor Execution, Potential Unrealized 2 - Very Little Appeal 1 - Not Recommended to Anyone