Luzimia

Hello dear Mojira user and happy new year!
The Mojira website is currentrly facing an unexpected issue, but i fixed this for you, you can find on "https://github.com/Luzimia/fixedjira" a simple peice of code that fix your current Mojira page until you reload it.

Just go to the link, follow the instructions, and done!

Please note that the code is as-it and that you need to read it first, you can find information about the code itself on the GitHub link, if you have any question related to the code, please ask in the GitHub page, for questions about the actual issue, please ask here, if you want to make a Chrome extension yourself because i'm too lazy, you can (plz credit so i can be famous :3).

I'm putting the code on GitHub because our amazing moderation team want to avoid random code in the tickets, i think it's the right thing to do, always read the code before executing it, it can be dangerous, the code i provided to you is not certified by the moderation team and will be useless when the issue is fixed, if you have any doubtes about the code, contact me on GitHub or ask a moderator here, and never run code that you don't trust.
As always, i hope i helped, and have a nice day chasing bugs and helping others!

I see why the ticket was marked as duplicate, but i don't think it's entirely related to MC-110526,  my report is more like "the game's accessibility text for narrator is always english and does not match the operating system's language", i think my report was a bit misunderstood because it was poorly written.

What i was saying technically is that accessibility should by default match the os language to make sure the user understand it, plus, since installing Windows in another language will by default make the narrator use the chosen language and Minecraft is owned by Microsoft, the best thing to do is to make the default language match the os langauge if the game have it, the only way for the users needing this message at the first startup to hear it correctly is to learn english and change Windows narrator settings. And i don't think an accessibility thing should be locked in a unique language.

But i understand your point here, technically, the game is working as intended since it's english by default and inform the user that the narrator can be enabled using the current language, so it's not really a bug, but more a feature request that would be useful to correct something that look like a bug, sorry for duplicating, i will be more careful next time.

It was my first report, at least it wasn't entirely useless since it make me know how Mojira work in more details, i will try to chase some bugs and try to replicate every reports that wasn't already tested by the community.

Ok, thank you, i'm new to the Mojira community so i was a bit confused about this marked as duplicate of MC-110526 since this one is marked as "working as intended", i will try to suggest the feature to Mojang to improve the accessibility features, thank you for your precisions!

Well, it was marked as resolved even if it's not resolved since the current solution for that is to learn english and change the system language because the game only care about english persons at first startup, i will ask Mojang directly, sorry for making this ticket here, maybe the mod think it's more a feature suggestion than an actual issue.

Ok, thank you for the information and sorry for making a similar ticket.

Do you think i should suggest to Mojang to use the system language as well as the english language for that using the suggestion feature?

I think it's an error that should be fixed (even if the others say it's not an error, i still consider this as an issue in the game), when creating a new instance of the game, it always say the sentence in english with the french voice, meaning that the target of this accessibility feature is only english people, it would be a bit confusing for someone who don't speak english at all to listen to an english sentence using the wrong tts voice, this make saying that the user can enable narrator at the first start nearly useless for a lot of non-english with big vision issues.

For the narrator voice for the rest of the game, it's not a problem since you can choose the language on your system and on the game, but you can't choose the game language at startup before listening to the english text of the narrator. If i was a blind german who don't know english for example, i would open the game, and hear a strange text of another dialect with buggy german voice instead of a correct thing.

Fixing this won't hurt and can help some people, i know someone who is almost blind and can't read at all (but can still see the game a little) who use the narrator, fortunately, he know both french and english, but it's not the case of everyone, it would be cool to at least say the sentence in the system language, this will show that Mojang care about every languages for accessibility and make this game more accessible, and prevent anyone from hearing english text playing in the wrong voice any times, i think Minecraft should add a "System" language (with the name translated in the system language) that will be used by default to make the correct narrator text play on the system.

Thank you for your reply!

Yes, unfortunately, i'm not a moderator (yet), so i can't mark this as confirmed, this is my first day trying to help the Minecraft community on Mojira, i'm very shy irl, so i try to communicate more and more with the others, and i think helping others and communicating can be a good and original way to improve myself.

I hope this bug will be fixed, if you know any other people with a Mojira account, you can ask them to vote to make some visibility, and if you can, you can try to find other issues with walls and make a grouped report with all the issues you found (and that aren't already on your search result).

(Also, for the env, i don't think "Cyberpower PC w/ 12x AMD R5" is very useful, it's more the operating system and the Java version.)

Thank you for your report!

Well, your JSON look ok, and when reading the error message, i see that the types are wrong.

The error message told you that you misused the variables, with things set to integer instead of string (number instead of text), same for the "not a json array". Maybe cleaning everything in the feature and adding things per little groups can make you find where are the problems exactly so you can check on the wiki for how to use correctly this experimental feature. It does not seem to be a game issue, but i don't know well this feature and i don't have the time to fix the code and analyzing how the feature work for now, so i let moderators and the community testing.

Good luck with your project!

Thank you for your report!

I replicated the bug, and it can be confirmed, congratulation for finding the bug!

Well, this is interresting, maybe the block scan is messed up, the devs will need to review this specific code, i will maybe try to find the issues in the code and try providing fixes for this kind of issues when i have some time.

Thank you for your report!

I am not able to reproduce your issue, the arrow on my side is always visible, in any angle, is it possible to have a closer look to the arrow and even have the map so the community can try on their side? Also, have you tried things like restarting the game without the packs, viewing on another zone or map, or is your client modded (mods can replace vanilla textures and how the game render things)?

Anyways, it look like the arrow miss a 2D part, more pictures would be useful, i will wait for the images (and the video) and/or the map and try to reproduce it again, but for now, i think your issue can't be confirmed.

Thank you for your report!

I checked, and it can be confirmed by a moderator.

The attribute isn't set correctly while other attributes work fine.

I tested with the scale and it work, look like a specific issue with max_health. This look related to MC-197818 but they are talking about NBT, but maybe the actual issue is that this attribute is reset at mob spawning, this can explain why after spawning the attribute work well when you modify it, feel free to read the MC-197818 issue if you want more info.

If you want a temporary fix, you can do "/attribute @e[type=wolf, limit=1] minecraft:max_health base set 200" to modify the attribute after spawning the mob.

I can confirm, the error also happen for me when modifying permissions, it would be a good idea to say this./

"Unable to create a new world! (Protected directory.)

Please check the directory permissions of the saves directory and make sure you are allowed to edit it.

[LEARN MORE]     [OPEN SAVES]"

With "learn more" redirecting to an article talking about files protection and how to modify that, and "open saves" opening the saves directory.

Basically, the game should check at startup directories and files permissions and warn the user (for example in the top right corner with a yellow box sliding away after 7 seconds) about wrong permissions settings in the game's files.

To reproduce./

1) Make a new Minecraft instance (with a new configuration, so in another directory).

2) Open the game with sound enabled.

3) Just listen to the narrator.

I get the same issue sometimes when i keep the game opened, restarting fix everything, but i think it's still a bug and can be confirmed.

If i worked at Mojang, i would fix this by keeping track of the session validity time in the client and before it end ask to expand the session or to refresh it correctly.

Can be confirmed, i tested in 1.21.4 and 1.7.10 and the bug happen, this can be used to go under the wall, so it's a security risk for the niche domain of the "secured" locations with a roof made of walls without an edge of solid blocks.

More seriously, i think it's a minor bug, but still a bug, fixing it could be a good idea.

I can't type some characters too using Edge, same issues with any browsers using Gecko or Blink (web engine of Firefox & Chrome), until Mojang fix this issue, you can use a notepad to write the text, and then copy & past it on the input box, same for the login page. (Typing in majs is also a valid way of bypassing this issue.)

Since i want to help, i found the actual issue "

", this keydown event of <html> added by the JS execute this code.

function(event) {
  // List of single-character shortcuts in Jira to disable
  const jiraDisabledKeys = ['t', 'y', 'i', 'a', 'l', 'm', '[', '/', 'f', '.']; // Add others if needed

  // Check if the pressed key is in the disabled list
  if (jiraDisabledKeys.includes(event.key) && !event.ctrlKey && !event.metaKey)

{     event.preventDefault(); // Prevent Jira's action     event.stopPropagation(); // Stop the event from propagating further   }

  // Screen reader shortcuts (like JAWS or NVDA) will still function,
  // as they are not blocked unless JavaScript explicitly blocks them.
}

 I think a dev put this event hoping it affect only some input, but it actually execute on every HTML inputs, if this code is removed or modified, it will fix the issue.

Can a moderator show this to a dev working on the Jira server please?

Thank you and hope i helped!

I was able to reproduce it, this can be confirmed by a moderator.

(Also, hi, i'm new to the Mojira bug tracker, this is my first message, i will try to replicate bugs and find bugs on my free time, hope i will be useful!)