Add TRR enemy support #682
Merged
Conversation
This file contains 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
TRGE had support for level sequencing randomization, but this has been found to cause too many crashes, so I've made the methods do nothing in case they're somehow called. Fixed secret wording in view.
Environment mods to support it everywhere are not possible yet.
…Rando into issue-614-trr-enemies
Some files were being missed for TRR.
rr-
approved these changes
May 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Part of #614.
Checklist
Description
Quite a big change, but ultimately this reduces a lot of duplication between the enemy logic for all games. The original main logic in
TR1EnemyRandomizer,TR2EnemyRandomizerandTR3EnemyRandomizerhas been moved out to the new allocator classes, and so this is now shared between classic and remastered. The individual randomizers keep specific logic, like how to add unarmed level extras for tough levels, or performing cloning or mesh swaps, which is currently only possible in classic.The remaster import logic is practically identical to classic, the main difference being we merge the PDP/MAP data once it's completed. Texture limits are increased too, so that means running the same seed in classic and remaster will most likely give different results for TR2, but this isn't really a concern.
The main point of duplication remains the threaded behaviour, so again that will be tackled later under #569.