isXander / isXander/Controlify

[Bug] New world "hints" cover the default placement of controller input glyph hints

Open
#339 0 comments 0 reactions 1 assignee View on GitHub

@isXander is already working on this.

Since Jun 13, 2024.

bug
Dominant language
Java
Stars
341
Forks
97
Avg merge
1h
Merged PRs (30d)
1

Description

Current Behaviour

When joining a new world, Minecraft shows the player "hints" (view attached screenshot below). These hints cover the controller input glyph hints at the default placement (ie top of the screen). These Minecrafts "hints" won't disappear until the player follows their orders - moves the mouse to look around for a set amount of time.

Expected Behaviour

Minecrafts "hints" don't cover the controllers input glyph hints.

My recommended solutions include:

  1. Offsetting...
    a) the Minecrafts "hints" [😐],
    b) or the controllers input glyph hints when covered by such notifications or other gui elements (narrator? other mods?) ...if possible [😀].
  2. Overwriting these Minecrafts "hints"...
    a) so that they don't appear when using a controller [😐],
    b) or modifying them to explain verbosely the controller input scheme [😀].
Screenshots

image

Reproduction Steps
  1. Create a new world and enter it.
  2. Try playing with a controller.
  3. Minecrafts "hints" cover the controller input glyph hints at the default position [!]
  4. The only way to make Minecrafts "hints" disappear is to follow their orders (?)
Logs

No response

Mod Version

2.0.0-beta.10+1.20.4

Controller

Xbox360 generic, Dualsense Edge

Bluetooth
  • Yes
Operating System

Linux/SteamOS

ARM
  • Yes
Additional Information

No response

Just to make sure...
  • I have made sure I am using the latest version of Controlify for the latest version of Minecraft.
  • I have made sure there are no other issues describing the same problem on the issue tracker.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.