Skip to content

Conversation

@microlith57
Copy link
Member

since this behaviour is silly and inconsistent, and i can't think of any reason anyone would want it to happen on purpose, i think it's sensible to simply disable it globally including in vanilla maps.

tested and confirmed working in vanilla 5a.

reported here

@maddie480-bot maddie480-bot added the 1: review needed This PR needs 2 approvals to be merged (bot-managed) label Nov 22, 2025
@microlith57 microlith57 force-pushed the fix-seeker-slowdown-layer3 branch from b0d7408 to 07752c0 Compare November 22, 2025 03:10
@SnipUndercover
Copy link
Member

SnipUndercover commented Nov 29, 2025

Linking this Celestecord discussion for context.

@maddie480-bot
Copy link
Member

The pull request was approved and entered the 3-day last-call window.
If no further reviews happen, it will end on Dec 2, 2025, 6:10 PM UTC, after which the pull request will be able to be merged.

@maddie480-bot maddie480-bot added 3: last call window This PR was approved, and is in the 5-day last-call window before getting merged (bot-managed) and removed 1: review needed This PR needs 2 approvals to be merged (bot-managed) labels Nov 29, 2025
@maddie480-bot
Copy link
Member

The last-call window for this pull request ended. It can now be merged if no blockers were brought up.

@maddie480-bot maddie480-bot added 4: ready to merge This PR was approved and the last-call window is over (bot-managed) and removed 3: last call window This PR was approved, and is in the 5-day last-call window before getting merged (bot-managed) labels Dec 2, 2025
@SnipUndercover SnipUndercover merged commit f274c81 into EverestAPI:dev Dec 2, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

4: ready to merge This PR was approved and the last-call window is over (bot-managed)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants