Larian Studios Forums Divinity: Original Sin 2 - The Modding Dungeon Divinity - Original Sin 2 - Modding General Rant: I feel cheated about modding

They aren't immediately obvious. I actually had to ask after trying and failing.

Maybe users who hit a roadblock could make a thread in which everything that is not possible is listed? I think that could be really valuable to users who want to know what can be accomplished and what not, as well as show larian again that there is interest for these features.

Regarding the GUI: we can unpack the files with JPEXS [0] (I tried it). Maybe there is a way for us to change and compile them so the game accepts them like the people did with Skyrim. Although that would probably only allow slight modifications but not completly new GUI elements as they would probably need to call into the engine.

[0] https://www.free-decompiler.com/flash/features/

I have to agree here, some of the limitations seem just so very random. I mean resistance types are basically a single line entry with: Damage Type X decreased by Resistance type Y. And even some kind of damage type/armor type system is just a 2D table.

And the civic/magic/combat skill schools could be handled like one of the many other tree views (story editor for example). Were one entry is one school with a field for modifiers like increase duration of all entities with tag Summon by 10%.

I even searched if anyone looked at this in the first game, but nope. I could not find one discussion about how crime really works at the core.

1) you perform a "hostile" action (attack, kill, steal, pickpocked, use owned item, move owned item). This is the crime type: Assault, Murder, Theft, ... (names custom-defined by script/data; nothing is hard-coded regarding this)
2) the action is against someone that is (generally) not hostile to you (i.e., not in combat with you). This is the victim.
3) It is Osiris scripting that decides which actions under which circumstances are crimes, and then it just calls RegisterCrime() reporting the crime type (as a string), the perpetrator, the victim, evidence if any, optionally a specific position. E.g. (simplified) CharacterKilledByCharacter() -> register Murder crime
4) Others may see you perform this action (CanSee). Those are witnesses that may react to the crime. They are collected by code.
5) Others may hear you perform this action (distance check). They may start investigations. They are collected by code.
6) Some actions create leave behind evidence, such as murder (the body) or stealing (the missing item). If an NPC later on sees the crime scene, they may start an investigation at that point

Who can react to a crime?
* This is tag-based with priorities (defined in data, looked up using the crime type string that was specified when script registered the crime). MAGISTER and GUARD characters will generally get priority over anyone else. If no-one with a listed tag is found, no one will react (except for the victim itself).
* Different reactions can be specified depending on whether someone is a victim or a witness. E.g. attacking a BADASSCIVILIAN will immediately lead to combat, but attacking someone else with a BADASSCIVILIAN nearby, will make him try to arrest the perpetrator.
* Code will select who reacts to a crime (usually a witness or the victim), although script can transfer the investigation/reaction to another character (e.g. if the reaction of the victim is to call for help)How will they react?
* again tag-based. Some will flee (e.g. animals), while others may attack or arrest you.
* if they discovered a crime scene after the fact, or only heard the crime, they will start "investigating" to find the culprit. This boils down to interrogating all players they encounter in the neighbourhood. They will magically (and correctly) know whether you're guilty or not. Depending on tags and victim/non-victim status, they will then possibly allow you to bribe them, attack you, send you to prison, warn you, ...
* if they saw you performing the crime, they will directly go to one of the above behaviours without interrogating anyone (but it can be a different one compared to the one after an investigation)

Yeah, I honestly have trouble figuring out what isn't possible because of lack of documentation on some of the story functions and core elements of the game.

For example, I was looking at _crime, but I could not find how the story knew something was stolen. It just had a function call named CharacterCrimeSensibleActionNotifier or something and I see no mention of how it knows to send an event update.

I even searched if anyone looked at this in the first game, but nope. I could not find one discussion about how crime really works at the core.

Yes, I know it can be disabled.

We may see a few script parameters that will allow for a workaround to adding new talents, abilities and attributes, though it won't use the existing UI. No idea about any timeframe for this, but it's a possibility that would be a fairly simple solution to what would otherwise require a whole lot of reworking of the game's internals.

Unless I'm wrong, one big thing is that it's all possible to add entries to the skill editor via the StatsObjectDefinitions. But if you want to add ones that aren't defined there, you can't because you don't know the internal id.

Yeah that. You can add whatever you want or edit or even extend some limits through the xml files, and for what he did was ok because there was no need for any internal ids, but as you can see he's hit his own roadblock with that.

The file I speak of though is not an xml file but an sod file, but still you can add stuff there, if you know the internal ids.

I suppose though if you truly want to know the extent of what can and can't be edited, look in the xml files.

Data\Editor\Config\Stats\

Enumerations, Filters, StatObjectDefinitions.

Corrected my above post. All are xml files. They are basically what you see in the text files, but, in the case of that last one, which is what injects things into the editor, some things in the text files are left out thus making them inaccessible in the editor(really wish I was good at explaining things). Example: some statuses aren't defined there, hence you don't see them in the status data of the editor :P

OK I'm a complete idiot and BLIND AS A BAT. All the statuses are indeed in the Stats Editor. I was reading things wrong(I'm working on a particular skill I think people will like and I needed access to a status I thought wasn't defined in the editor).

Basically if you want to add something new or change something specific you can edit either of the files(xml or the text file). Given that LaughingLeader would able to add a new WeaponType, it's apparent it certainly will lead to appearing in the editor, and you can add new values to Penalty and PrecisionQualitifiers(for example, and I've done the latter) and it will be selectable in the editor.

All got clever crafty changes you wanna do gotta be done outside the editor though, but hey that's what we have to work with for now.

I'm the opposite. I personally feel like I've been given way more to play with than I expected and it's much easier than I anticipated. Want to add a new character to play as in arena mode? A simple check box click in it's properties is all that's needed for crying out loud! Same with making a monster playable in GM mode. I definitely didn't expect to be given access to every area and NPC from the campaign mode so easily either, yet they've outdone themselves and impressed me greatly with the mod support.

Yea the editor is create if you want to do D:OS2 stuff. But the usability drops of very strongly once you don't just want to add some scenery, a quest that adheres to the line of the standard quests or add a new character from the game's resources.

Currently the editor just feels like a slightly more powerful GameMaster.

Did you see this thread Dark_Ansem? I basically figured out a workaround for adding new talents, attributes, abilities. It got buried real fast tho :P

http://larian.com/forums/ubbthreads.php?ubb=showflat&Number=620903#Post620903