You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whenever the data of an equipped trinket item changes while the creative inventory is open, it resets the scroll position. This does not happen when data of an item in a vanilla slot changes, e.g. equipped armor or held tool.
Set up some sort of mana gain, e.g. via equipped Band of Aura.
Open creative inventory and scroll down in any tab. Whenever mana is stored in the Band of Mana, the scroll position resets to the top.
Option 2: using Elytra Slot (tested in 1.20.1 and 1.21.1)
Equip a damaged elytra with mending in the cape slot.
(1.20.1: /give @s minecraft:elytra{damage:431}, 1.21.1: /give @s minecraft:elytra[minecraft:damage=431]; then /enchant @p minecraft:mending)
Set up a way to gain XP, e.g. a command block summoning XP orbs (/summon minecraft:experience_orb ~ ~ ~ {Value:1}) on a timer (e.g. repeater loop).
Open creative inventory and scroll down in any tab. Whenever an XP orb is picked up and repairs the elytra, the scroll position resets to the top.
The text was updated successfully, but these errors were encountered:
Update: Changing NBT data also appears to cause the equipped trinket's unequip and equip events to fire. Most likely related to the changes in PR #296, which makes that very important functional change seemingly without providing a way to distinguish between that "internal reequip" and an actual player-caused trinket swap.
This seems to be the cause for VazkiiMods/Botania#4758, which worked fine with Trinkets 3.7.0 and is broken in Trinkets 3.7.2.
Whenever the data of an equipped trinket item changes while the creative inventory is open, it resets the scroll position. This does not happen when data of an item in a vanilla slot changes, e.g. equipped armor or held tool.
How to reproduce
Option 1: using Botania (1.20.1)
This was originally reported as a Botania bug.
Option 2: using Elytra Slot (tested in 1.20.1 and 1.21.1)
(1.20.1:
/give @s minecraft:elytra{damage:431}
, 1.21.1:/give @s minecraft:elytra[minecraft:damage=431]
; then/enchant @p minecraft:mending
)/summon minecraft:experience_orb ~ ~ ~ {Value:1}
) on a timer (e.g. repeater loop).The text was updated successfully, but these errors were encountered: