I've done a lot of digging and tinkering with the game's files, I'm trying to make a "RAW" mod, that makes the game function more like the tabletop to see how it plays out. I've already removed all the extraneous surface creation, rebalanced firebolt, and a few other things - but one thing I absolutely cannot find is what controls height.
In 5e, there is no mechanical advantage or disadvantage from height, but in baldur's gate 3, a 5 foot or greater elevation confers a 3:1 advantage by giving low ground creatures "Disadvantage" on all rolls and high ground creatures "Advantage.
Has anyone, in their tinkering, found what controls this?
How to use this cheat table?
Install Cheat Engine
Double-click the .CT file in order to open it.
Click the PC icon in Cheat Engine in order to select the game process.
Keep the list.
Activate the trainer options by checking boxes or setting values from 0 to 1
1) I am just going to wait for the monk class to be released in EA before I test it.
2) not sure how your new ability isn't just given to NPCs as well.
3) You are using a tweak method that is dangerous. You can tweak a *.pak file, add it to your game (just have to follow the .pak files folder pathing.) by adding the single file loosely. This means you aren't changing the game files and if you accidently screw things up all you have to do is delete the loose file and restore the game to "factory settings" Repacking the game's data files increases the changes of totally borking your game and having to reinstall. So that is going to make people shy at trying your tweaks.
FYI to the community loose files placed in the correct folder path (you will have to add the folders manually) overRIDE *.pak files, without having to overWRITE the original files in the .pak file. Not having to repack .pak files makes tweaking saver and easier to troubleshoot, if a tweak screws things up, just delete the loose file.
1) I am just going to wait for the monk class to be released in EA before I test it.
2) not sure how your new ability isn't just given to NPCs as well.
3) You are using a tweak method that is dangerous. You can tweak a *.pak file, add it to your game (just have to follow the .pak files folder pathing.) by adding the single file loosely. This means you aren't changing the game files and if you accidently screw things up all you have to do is delete the loose file and restore the game to "factory settings" Repacking the game's data files increases the changes of totally borking your game and having to reinstall. So that is going to make people shy at trying your tweaks.
FYI to the community loose files placed in the correct folder path (you will have to add the folders manually) overRIDE *.pak files, without having to overWRITE the original files in the .pak file. Not having to repack .pak files makes tweaking saver and easier to troubleshoot, if a tweak screws things up, just delete the loose file.
thanks for your feedback. my comments:
1) i do not think they will add anything until the official release. Larian Studios has always done that way.
2) there's this instruction: data "AIFlags" "CanNotUse" for each skill in that file. it's self explanatory.
3) i take backups of original data, and beside the potential of corrupting a savegame, i dont see really whats the problem.
can you give example for the shared.pak and the folder structure you have to put?
Thanks
1) I am just going to wait for the monk class to be released in EA before I test it.
2) not sure how your new ability isn't just given to NPCs as well.
3) You are using a tweak method that is dangerous. You can tweak a *.pak file, add it to your game (just have to follow the .pak files folder pathing.) by adding the single file loosely. This means you aren't changing the game files and if you accidently screw things up all you have to do is delete the loose file and restore the game to "factory settings" Repacking the game's data files increases the changes of totally borking your game and having to reinstall. So that is going to make people shy at trying your tweaks.
FYI to the community loose files placed in the correct folder path (you will have to add the folders manually) overRIDE *.pak files, without having to overWRITE the original files in the .pak file. Not having to repack .pak files makes tweaking saver and easier to troubleshoot, if a tweak screws things up, just delete the loose file.
thanks for your feedback. my comments:
1) i do not think they will add anything until the official release. Larian Studios has always done that way.
2) there's this instruction: data "AIFlags" "CanNotUse" for each skill in that file. it's self explanatory.
3) i take backups of original data, and beside the potential of corrupting a savegame, i dont see really whats the problem.
can you give example for the shared.pak and the folder structure you have to put?
Thanks
1)Err the "panel from hell" has Swen specifically saying new Races, Companions classes and features will be added to early access and they added things for DOS2 in EA on a regular basis so not sure how you can say "Larian Studians has always done that way"
[Source]
2) yes but you are not specifically telling people this in your posts so people are likely saying "neat" but moving on. Not judging your work, just trying to explain why no feedback
3) Not everyone is comfortable repacking game files and it DOES increase the risk of borking your game. yes people should do backup but you should know by now how many people don't backup their work. Again people having to repack your tweak at least following your instructions would limit the number of people willing to try. Reducing feedback.
Yeah I can do that. [Going to really spell things out overly simply so people who are utterly unfamiliar with tweaking can learn the basics]
I added the players handbook racial ability for half-elves getting two skill picks to the game, by tweaking Progressions.lsx Found in the Shared.pak file.
When I unpacked shared.pak it created a folder structure for all the files in the shared.pak file. the first level is mods & public.
Progressions.lsx is a file that has a folder pathway of \Public\Shared\Progressions\Progressions.lsx
So knowing that shared.pak in located in the data folder of the game aka \Baldur's Gate 3\Data\ I know that any folder unpacked from a *.pak file starts in \Data\ In this case \Public\Shared\Progressions\Progressions.lsx So I would add public to the data folder, shared to the public folder, progressions to the shared folder. Finally placing the file Progression.lsx in the progression folder. (Again just overly simplifying things so newbies can follow not for your benefit freeze)
So any file tweaked from shared.pak will unpack with a specific pathway and you just have to add the folders to the data folder. Also once you have tweaked one file you will only have to add a folder or two for the next file. You can just cut and paste the whole unpacked file but that is a lot of game files the engine will be overRIDING that is doesn't need to that it MIGHT cause an issue and it is a waste of space. So i don't recommend doing that. This can get worse when you are unpacking multiple *.pak files.
So this is what my personal pathway to Progression.lsx looks like on my computer others will look different based on version and where you installed the game.
Thanks GothFather for your explanations that also benefitted me, and I'm sorry if you saw no value in my work.
-----
on the topic on toying with the animations defined in spell_target.txt file, i couldn't apply to my character multiattack spell that some enemies got (bear, automatons etc). there's simply no animations happening.
Stringing animations seems to work with ":" and can produce funny results, like extremely fast punches multiple times.
for example swinged right punch immediately following by a fast right jab then a left swing:
You don't have to repack the edits to game files, just unpack. You just create the file structure and use the loose files in there. If there's an update or something it'd be easy enough to just remove them from there and redo the changes with the new files.
1)Go to \Baldurs Gate 3\Data\ and create a new folder naming it public.
2) Enter Public and create a new folder named Shared
3) Enter shared and create a new folder named Stats
4)Enter Stats and create a new folder named Generated
5)Enter Generated and create new folder name Data
6) Copy and paste the file you want to Data.
Yes it is a hassle to manually add in all those folders but you only need the files you changed to be added to your game.
Try it and it should work.
The first shared folder is the problem. That shared folder was likely the created from the unpacked shared.pak. Also you should probably not use all the files from shared.pak as you are telling the engine to override ALL the files in Shared.pak at the same time and that could lead to problem as that is a LOT of unnecessary work for the engine.