Noqn

aaaah good point, updated the install instructions

Yep!

No, very unlikely. Which sucks. I don't think there are any Microsoft-published games on GOG whatsoever, same with Obsidian's games since the acquisition. (Post-MS-acquisition TOW was released on GOG but was published by Private Division.) Yeah I hated that too... check this out if you haven't: https://www.nexusmods.com/pillarsofeternity2/mods/469

Yeah from what I can tell

Finally made a fix for this.... https://www.nexusmods.com/pillarsofeternity2/mods/769/ Basically, it will... Revert all the changes to Weapon Keywords from Community Patch Keywords 2.0.0 Add an Item Mod to "Keyword Weapons" that indicates that it has the Keyword and explains Enemy Immunities. Make enemy keyword immunities visible in the combat tooltip. IMO vanilla enemy immunity behavior is working correctly, it is perfectly consistent with the Keyword system. The issue is just the lack of clarity in regards to which weapons have keywords and which enemies have immunities. BEFORE AFTER Also - Optional Download for alternative Damage Types since that got positive feedback in the thread regardless. (Weapons that gain a new Damage Type also gain -1 Penetration for balance)

Hi, sorry for late reply! Could you post the .gamedatabundle file with the changes in your mod?

Nevermind, I could do it quick and dirty by comparing the parsed expression text... 2024-10-26 Users can now select "Find Similar" when clicking Conditional or Script rows. It can be written like this: *GenericAbility.ActivationPrerequisites != "" *GenericAbility.ActivationPrerequisites = "IsHealthPercentage(This, LessThanOrEqualTo, 50)" you can also use &= to find conditionals with partial matches (see more here https://gitlab.com/noqn/apotheosis/-/wikis/General-Instructions/Queries#string-selector) *GenericAbility.ActivationPrerequisites &= "IsHealthPercentage("

Agh, I hadn't thought about handling Conditionals in Queries at all... It's tricky because behind Apotheosis' scripting string representations there are some much more bothersome data models hidden away from the users. I really like this syntax: (I wonder if I could make the Scripts/Conditionals auto-completion and syntax highlighting features work within the query editor conditional strings... )

2024-10-25 Right-clicking a value in a GameData tab and selecting "Find Similar" will open the Query sidebar and search for other objects that has a matching value. I think this is going to be insanely convenient, thanks for the idea @Cmushi

Weird, it shouldn't work like that... Basically, edits to a Component are going to be "isolated" by properties. If you make an edit to a specific value in a component (e.g. ItemComponent.IsUnique) that is not going to affect anything else in that Component. However if you make an edit to a property in a component that is a Structure (has nested values e.g. AttackBaseComponent.DamageData) or is a List of Values (e.g. GrimoireComponent.Spells) it is going to overwrite ALL of that property and cause conflicts with other mods that edit that property. This is what happens to ProgressionTables, ClassProgressionTableGameData BaseProgressionTableComponent AbilityUnlocks (all the abilities in the table... editing any of them is going to overwrite the entirety of AbilityUnlocks) ... DefaultCustomAI: DruidAggressive <- editing this won't cause any conflicts with mods that edit AbilityUnlocks On the other hand, changes to TrapAccuracyPerLevel in GlobalGameSettings shouldn't be overwritten since it's a "top level property" in a Component (not within a Structure or List). GlobalGameSettings CombatSettingsComponent TrapAccuracyPerLevel <- editing this shouldn't cause conflicts with anytning else in the CombatSettingsComponent, and should only be overwritten if another mod edits this specific value If it's not being applied to the game, that's super weird, maybe caused by something else... sorry I couldn't help and sorry for late answer

No, I think the most you can do is find the corresponding CharacterStats object (under Characters) and edit some data of an existing summon from there. But you can't create a new one. Sorry as always for my late reply Great suggestion, will look at this

A bit late, but I think I've covered most of what can be done with User Scripts in the documentation now! https://gitlab.com/noqn/apotheosis/-/wikis/User-Scripts

@lalolalo9 With these last patches User Scripts API got extended and cleaned up significantly, I'll start working tomorrow on the new documentation on general use cases, and how to set up script editing with VS Code

I remember when I started trying to recreate the whole Progression Table view in Apotheosis that I couldn't make sense of what determines the in-game ability order. I double checked and the order is not consistent with IDs, not DebugNames, not in-game names, not the order the abilities were defined in abilities.gamedatabundle, and not the order their UnlockableAbility where in in the BaseProgressionTableComponent... Apotheosis orders based on the UnlockableAbility order, which will not necessarily reflect how it looks in-game. I wanted to make some drag-n-drop feature like what you ask for, but it would have to be consistent with in-game rendering first. If you're editing a Table directly, you can expand the AbilityUnlocks list, right-click and select Cut, then right-click the row where you want it and select Insert. That way it'll be rendered earlier/later in Apotheosis, but probably won't change the in-game order.

Fixed now! I forgot to write back after i patched this, sorry 2024-09-20 Fixed CTD when saving modified Global Conditionals Updates to User Script API 2024-09-15 Fixed regression causing some GameData pages not to be displayed. 2024-09-14 User Scripts can now be edited through an external editor and synced to Apotheosis. Extended User Script API. Users can now append new String Table entries directly from String Table tabs. Modded .stringtable files are now properly written indented again.

Ok first of all I'm ridiculously excited that someone is using the User Script feature Your post has made me realize the API is severely lacking some features (like adding new GameDataObjects, editing/accessing StringTable text...) Besides that, I've started working on setting up User Scripts with an external editor, which I think would help tremendously: I'll make sure to write a new Wiki page for User Scripts as well, and instructions to configure VS Code properly for this. YES Thanks I'm genuinely happy about the name, I liked how Fallout's G.E.C.K. modding kit was named after an in-universe thing and wanted something similar.

I can't edit my post for some reason, anyhow here's the changes I meant to post: Old Vailia: Aedyr: Ixtamil:

Good point, extract this to your override folder: Subrace Cultures.zip

Gotten hold of a computer now, sorry for the late replies! Ooh, excellent idea! I've limited them like this: Progression Tables only: Won't show up in Progression Tables: RecipeData only: Conversations marked ConversationDisplayType: ShipDuel Gonna check this out ops, fixed now Anyhow, new release! 2024-08-17 Progression Table, Ship Duel and Recipe-related Conditional Calls are now only available in auto-completions when appropriate. Certain Conditionals are no longer available in Progression Table auto-completions to avoid confusion with PT variants (e.g. 'HasAbility' vs. 'ProgressionTableHasAbility') ExternalVO values in new Talk Nodes are now properly initialized as empty strings.

Btw @BegrudgingDM is this fixed for you now?

2024-07-30 Users can now edit Exteral VO values in Conversation Talk Nodes. Users can now edit pre-existing vanilla Link Conditionals in Flow Charts. Added appropriate tags to Conditionals and Scripts button tooltips in Flow Chart Nodes for clarity, e.g. [On Enter Scripts]. The Query sidebar's "Clear All Text" button now uses the correct icon. Made a quick release after all Ah yeah you're right, and it's about time I made a dedicated options page

@Kvellen ah turns out I had time to go ahead and implemented your suggestions Just got a couple questions From what I can tell it feels like bad practice to put stuff in the Link Conditionals, for example having to enter duplicate conditionals if there are several links to the same node. The places I checked out where the devs have used Link Conditionals, they could've just used the Node Conditionals to the same effect. I'm considering hiding the Link Conditionals button, unless the Link already had existing Conditionals. This way the user can check out and edit vanilla conditionals but otherwise be prevented from using Link Conditionals instead of Node Conditionals. Do you think this would be a good idea or too restrictive? An example: The icon is meant to look like this btw but doesn't look very clear in small buttons. With this change I'm gonna add a tag to the the conditionals/script button tooltips for clarity, like [Conditionals] / [Link Conditionals] / [On Enter Scripts] / ... This change might be enough that Link Conditionals don't have to be hidden at all? Though less clutter is always nice. I'm going to let you decide what I should go for, I'm uncertain myself

Great suggestions, I might be away from my PC for a short while soon but I'll look into it when I get back!

I forgot to add it to the changelog but this is also probably solved now