-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RFC: Telling stories - Ideas and related observations #11501
Comments
As for MultiFilter - the wiki claim " |
I like the idea of tileFilter supporting specific tile locations, has a lot of merit! I'm all for tile-entering triggers, would be easy to implement as long as we don't mind it triggering multiple times - if we need to keep track that's more complicated Campaigns - so far we hardly have any real scenarios, so talking about campaigns is very premature |
True, very, but having a vision leaking to the modder community may spark interest in scenario development..
Which signposts should normally do. But a repeat control for any type of event is a good to-do anyway, and - isn't there a comment saying so already? Don't we have
|
Problem Description
Imagining where support of modding to tell stories could go. Events are a step, Scenarios were a step. Loose collection of ideas... Looking for coder's input.
Related Issue Links
PR #11474
Desired Solution
<when a [mapUnitFilter] unit visits>
or somesuch? That condition could mark the entire Unique as to-be-considered together with TerrainGrantsPromotion in moveThroughTile.if (filter.startsWith("adjacent to [") && filter.endsWith("]")) return isAdjacentTo(filter.removeSurrounding("adjacent to [", "]"))
in Tile.matchesSingleFilter - could already replace Fountain of Youth's TerrainGrantsPromotion - but elsewhere in json. Possibly needing a Comment unique so Tile civilopedia is informative enough...[]
for the non filter will either only work if the outer filter brackets enclose a text ending in]
- or never work in that case but work in all others. Mind-boggling. Still thinking - should I test all cases that I can imagine and fix the wiki, or should I re-urge adoption of the nested-brackets-parser or - is there a kludge somewhere I overlooked that just makes it work regardless?Alternative Approaches
Play some other game - yea that's the ticket. 😈
The text was updated successfully, but these errors were encountered: