Adding ephemeral detail string to Room GMCP, focing mapper to use low… #372
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.
Description
This forces the mapper to use the lowest RoomId in the set as the 0,0,0 origin. This solves the issue of drifting coordinates depending on what gets mapped first.
Changes
x,y,zoffsets based on lowest room in mapper.ephemeralto Room GMCP payload (Details) when a room is ephemeral.Examples
without changes (Force to generate dark forest first):
With changes (Still forced to generate dark forest first):