Incorrect map for multifaction events fix #775
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
still222
changed the title
notfood
added
fix
Just tidying up comments. No changes in code. Fixing spelling errors etc. Hopefully a little more readable now.
Changing `!MP.IsInMultiplayer` to `Multiplayer.Client == null`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#659
As that issue was not resolved, I will publish patch me and my friend used in our playthrough.
Is it ideal? Doubt. But it works, forcing all events to fire on a correct map.
I didn't notice any gameplay downsides, like: too few events, broken events, missing events etc. AI Storyteller should understand that event was broken and account for it by adding new ones instead, which are hopefully correct ones. It "tracks" incorrect attempts in the log and it shouldn't be spammy at all, we had like 1 incorrect events each ~30 minutes (highly random ofc, but could be useful to see if something wrong if it starts spamming warnings each tick)