#Quick Navigation buttons overlapping the custom wardrobe of skyhanni

25 messages · Page 1 of 1 (latest)

twin raft
#

I have this issue since i switched from 1.21.5 to 1.21.8, this doesnt happened before and i use constantly the quick nav buttons so it would be a bit annoying to turn them off just for this little thing

Does this have any solution yet? Or its just a Skyhanni thing?

onyx pier
#

If you talk about your wardrobe it's skyhanni

twin raft
#

so its only an skyhanni issue?

onyx pier
#

It's that if we're talking about the same thing

twin raft
#

yeah its that, but my real problem is the quick nav buttons that keep appearing after i open the wardrobe of skyhanni

#

but i guess it may be a thing of skyhanni itself

onyx pier
#

Ok i see these buttons come from skyblocker

#

You can deactivate them normally

#

Here if you need, but idk any fix for that issue exept deactivate one of them

twin raft
#

crap :/ well i guess i will need to wait for an update of the mods

#

i actually use those buttons so it will be a bit annoying but i can cope with that

onyx pier
#

Skyhanni wardrobe is pretty useless imo

tacit hound
#

-# you can use skycubed for fancy wardrobe that is compatible with skyblocker

twin raft
#

oh its working!! thanks

amber star
#

they replace the inv screen, so we think it’s still an inv screen so we slap our buttons on it

proud carbon
pseudo tangle
proud carbon
#

this would require rewriting more stuff than im comfortable doing right now

#

your suggestion reads like a "how to make it compatbile", i just search for a quick "they dont overlap" workaround right now

pseudo tangle
#

well fully custom screens shouldn’t override screens intended to function as chest menus, our custom spirit leap overlay is an example of this

#

idk how you render the screen but the render background method is where the buttons are rendered

#

you could also change the coordinates that your wardrobe is rendering at so the buttons are placed in an area where they don’t overlap

#

there’s always the classic api and reflection method but I would prefer to avoid that if there are better solutions available (which I think there are)

proud carbon
#

good points, sounds like we dont need to write an api for you to listen to. we can do this on our end