Skip to content

Added defeat/grind conditions - #89

Draft
Valkhiya wants to merge 23 commits into
CodeTriangle:combat-logicfrom
Valkhiya:combat-logic
Draft

Added defeat/grind conditions#89
Valkhiya wants to merge 23 commits into
CodeTriangle:combat-logicfrom
Valkhiya:combat-logic

Conversation

@Valkhiya

Copy link
Copy Markdown
Contributor

Added conditions to all chests, quests, cutscenes, with the exception of dungeon regions and chests because of potential upcoming changes to those that would mean having to redo all of it.

Valkhiya added 7 commits July 26, 2026 11:55
Split some temple regions to accomodate for defeat logic:
open4.6 -> open4.6 / open4.6.5
open7.2 -> open7.1.5 / open7.2
open7.5 -> open7.4.5 / open7.5
zirvitar was basically redone entirely and I'm gonna move the chests and cutscenes so it makes sense
@CodeTriangleCodeTriangle added this to the 0.10 milestone Jul 29, 2026

@CodeTriangleCodeTriangle left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did a quick check over the changes. Am interested to hear your thoughts.

Comment threaddata/in/chests.json
"Cold",
1
]
["defeat", "Neutral Virus", "Heat Virus", "Cold Virus"]

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder about turning this into region along with Wasteland: Spiral Cliff Center. Usually a region with 2 locations would seem spurious, but it might be good for a condition that takes so long to check. What are your thoughts?

[ "or",
[ "grind", "Young Frobbit" ],
[ "grind", "White Frobbit" ]
]

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder about the correct way to do or conditions. To cut down on individual grind calls, maybe it could be helpful to have a ["grindAny", ...] condition that indicates that you must be able to kill at least one of the given enemies, if you think that would be helpful?

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That would certainly make some things simpler yeah. It's not required for that many quests, but it would make things simpler. It would also be extremely useful for when we implement tradesanity.

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As a point of order, when we implement tradesanity I was actually thinking we'd do it with a new kind of condition, where the trade would specify a list of items required, and then there would be another file that associates items with conditions to get those items.

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gotcha. Still would be useful to have that for the item conditions.

"condition": [[ "region", "open", "open10.Grove" ]],
"condition": [
[ "region", "open", "open10.Grove" ],
[ "defeat", "Tunnel Gelleric", "Tunnel Argeby", "Tunnel Angler" ]

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I actually don't think the Tunnel enemies are in the data.

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you mean in the crosscode data files, I found them under enemies/jungle/special/quest_td_X.json

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nah, in the CCMWR files, in data/in/{dlc/,}enemies.json. That's where the conditions for acquiring each enemy are.

@CodeTriangle

Copy link
Copy Markdown
Owner

Also, it seems you aren't finished. Could you convert this PR into a draft until you're ready for it to be merged?

@Valkhiya
Valkhiya marked this pull request as draft August 1, 2026 22:08
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@Valkhiya@CodeTriangle