Garde la position de chaque coffre quand les coffres verrouillés sont cachés - #9
Garde la position de chaque coffre quand les coffres verrouillés sont cachés#9Watherfoxx wants to merge 2 commits into
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 433730bb56
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| } else { | ||
| if (!CONFIG.getBoolean("show-locked-vaults", true)) { | ||
| consumer.accept(null); | ||
| consumer.accept(getHiddenLockedVaultItem(num, replacements)); |
There was a problem hiding this comment.
When show-locked-vaults is false and max-vault-amount is left at its default -1, this now adds an AIR GuiItem for each locked vault before any owned high-numbered vault. Those placeholders consume paginated slots, but the selector still disables next/previous buttons when maxVaults == -1, so a player with sparse permissions such as only axvaults.vault.80 has that vault moved onto page 2 with no way to navigate to it from the selector. Consider treating unlimited mode as pageable based on the highest emitted slot, or avoid adding placeholders beyond reachable pages.
Useful? React with 👍 / 👎.
1 participant
No description provided.