0 of 0
About this mod
This script is essentially aimed at making the W3STRINGS encoding / decoding process easier and more intuitive for mod creators.
- Requirements
- Permissions and credits
- Changelogs
DISCLAIMER:
Programming is not my profession, just a hobby. So to any of you fellow PowerShell nerds, feel free to modify and enhance my script in whatever ways you wish. And this isn't the most efficient script, definitely could have been able to condense it heavily by creating more variables or functions, but I'm content with the output.
USAGE / INSTALLATION:
The only two requirements for this script:
Once both of those requirements are met, right click on 'DEEN.ps1' and select "Run with PowerShell" to use.
GENERAL:
UPDATE:
My Other Mods / Tools:
Programming is not my profession, just a hobby. So to any of you fellow PowerShell nerds, feel free to modify and enhance my script in whatever ways you wish. And this isn't the most efficient script, definitely could have been able to condense it heavily by creating more variables or functions, but I'm content with the output.
USAGE / INSTALLATION:
The only two requirements for this script:
- Have the W3STRINGS executable downloaded.
- Open up the script (with whatever program of your choice; Notepad, Notepad++, PowerShell ISE, etc.) and set the '$W3STRINGS' variable to the path of your W3STRINGS executable.
Once both of those requirements are met, right click on 'DEEN.ps1' and select "Run with PowerShell" to use.
GENERAL:
- The script is split up into two main functions: DEcoding and ENcoding (hence DEEN -- because that sounds better than ENDE).
- The screenshots show the majority of usage, as well as how to easily decode all the W3STRINGS your entire Witcher 3 directory (including mods, DLC, etc).
- For modding beginners (like myself), I recommend checking out the CDPR forums on the W3STRINGS program -- to get a rough idea of how it works (predominantly the id-space).
- So I'm a novice mod creator, and have started messing with W3STRINGS -- this lead me to realize I wasn't a fan of the whole process with the executable, and thought that maybe that process deterred other users from delving deeper into modding (also I saw the 4 year old W3STRINGS decoding PowerShell script and thought to myself that I could do better). So that lead me to working on this dude with the aim of making the process more intuitive, fast, and easy (like many others who have made tools similar to this).
- I've done a decent amount of testing and am confident that there aren't many (if any) noticeable bugs, the inputs are case insensitive, and that the script can handle files / directories that include spaces and special characters (e.g., brackets [ ] ). For custom outputs (which I recommend using), It'll create the folders you input (if that folder doesn't already exist), it'll format your encoding output for easy copy and paste functionality (instead of having to copy, paste, and rename each string instance), recreate the directories that contain the files you're encoding / decoding, etc.
UPDATE:
- I haven't done a ton of testing with v3.0, so if you come across any issues just leave a comment letting me know.
- You will get an error when using the rename function IF there already exists a file that has the renamed name.
- When using the ID-space detection, the script only detects ONE ID-space. So if you recursively select a directory that has multiple mods -- all using different ID-spaces -- then only the mods with that detected ID-space will encode properly.
- IF YOU CAN THINK OF ANY IMPROVEMENTS OR FEATURES YOU WOULD LIKE ADDED, LEAVE THEM IN THE COMMENTS. I WOULD LIKE TO KEEP WORKING ON THIS SCRIPT AND IMPROVE IT -- IT'S FUN, I'M JUST RUNNING OUT OF IDEAS.
My Other Mods / Tools: