mojira.dev
MC-202355

Damage screen tilt is de-synced, defaulting to tilt left

In version 1.2.5 and earlier, your screen would tilt towards the direction you took damage from, acting as a bit of a directional damage indicator.  As of 1.3, due to the change made where single player games now run as an internal server, the client and server are de-synced, the server no longer sending the angle of attack to the client, and therefore the client defaults to tilting only sideways to the left whenever you take damage now.

The code for this to work is still in the game today, unchanged for 8 years since 1.2.5, and can be quite easily fixed, as I made a video showing this off in far more depth and explanation, and we (Charles and I) actually managed to fix this as a Forge mod with relative ease for most later versions of Minecraft, including 1.16.3.

Here is the video in question:  https://youtu.be/pAJPc71YOnY

Related issues

Attachments

Comments

migrated
[media][media]
Arisa Bot

⚠️ Please do not mark Unreleased Versions as affected. You don't have access to them yet.

-- I am a bot. This action was performed automatically! Please report any issues in Discord or Reddit

galaxy_2alex

The game is heavily modified in the video, so please make sure you also provide footage of this occurring with an entirely unmodified game.

migrated

There is footage later on in the same video showing it off in vanilla.

galaxy_2alex

https://youtu.be/pAJPc71YOnY?t=159

In the future, please provide the video link in a way that directly cuts to the non-modified parts, thank you.

migrated

The entire video is important, showing off in great detail and breakdown of the issue at hand, and how we fixed it, all information I felt was relevant to this issue, despite having a modified game client which doesn't effect the issue at all, since anyone who's played Minecraft in the last 8 years knows the screen always tilts towards the left when taking damage, I assumed this was common knowledge.  That is why I didn't bother running later versions of Minecraft in pure vanilla, but showed off version 1.2.5 in vanilla, showing where the directional damage screen tilt actually last worked.

I also explain in the video that this only ever worked in single player, never online.  But due to the internal server change 1.3 added where single player now runs as an internal server, that bug from multiplayer was transferred to single player.

Everything is quite explained in the video.

tryashtar

Duplicate of MC-26678?

galaxy_2alex

Indeed, thank you. This has been marked as "Won't Fix" by the developers.

migrated

Is there any reason given why it's resolved as "won't fix"?  And are we sure it was actually the official developers themselves who marked it this way?  Looking at the original ticket, it still shows as "unassigned", and doesn't say exactly who resolved it.  Mojang has also changed quite a lot over the years, it's possible this is something they'd like to fix now, if it gets brought to their attention properly.  Again, the code for this is still in the game, all the way up to 1.16.3.

wobst.michael

It has been resolved as Won't fix by @unknown last month.

migrated

ok but thats not a reason why it wont be fixed. thats just saying they said it.

its a super simple fix, for an intended feature. fix it.

ShrekTehOgrelord

This bug affects bedrock too btw

I dont wanna see a bug being fixed in java while bedrock doesnt get that fix

migrated

I know this has been marked as Won't fix, but as a player who find primary enjoyment from Player vs Player combat, I would really like to see it fixed in a later update.  I know it's not an essential update, but it's a nice quality of life change that would be a godsend in the PVP community.

galaxy_2alex

The bug tracker should not be used for discussions like this, please head over to the Discord or Subreddit linked below.

Quick Links:
📓 Issue Guidelines – 🛠 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
💬 Mojira Subreddit – 💬 Mojira Discord

migrated

So are we just being shut down?? this feels very passive aggressive

migrated

You guys are too serious about your job "template/format" for speaking and ways things work. On both threads people have asked why this isn't going to be fixed and you guys (mods) only given as answer "marked as wont fix by devs" so...do you guys not actually know why the developers said wont fix ? Also that video was 7 minutes long can you guys really not watch the whole thing ? Also I dont see how this place can't be for discussion about bugs/issues the website is literally easily made to be that way. If you guys didn't want people to comments you should have made it so only mods or people specified by post creator able to comment. 

 

Also it isn't resolved, you guys just dont want to fix it yet its a simple issue (im talking to devs). I know that you mods are probably just mods of the website but like damn "wont fix" a bug like damn you have all the money and the time in the world to do it and it would enhance the gaming experience too. I was nostalgic about it. 

PS : All I'm trying to say is that it comes out as rude and like you guys dont actually cares about bugs in the game. Any bugs that affect visuals/gameplay should be fixed in my opinion. 

 

Edit : I have seen the subreddit for it and MANY of the comments asked for this to be fixed with the main arguments being 1 - its easy to fix 2 - its a bug that has been there for years 3 - people want it back 4 - you could make a toggle in options on/off for it. 

migrated

This is a feature I really hope to see make a return one day, it would be helpful for pvp players in knowing damage direction, and casual players for more immersion.

 

I wish there was a way for us users/players to push back against the "resolved" tag, as a won't-fix is dumb for something that was a feature from the beginning, and as others have mentioned, it's not a difficult one to fix.

violine1101

I repeat, the bug tracker is not for discussions. Please use the reddit thread for that instead.

galaxy_2alex

Any comment after this will be removed, because a) this report has been closed as a Duplicate, and b) Discussions like this do not take place here but on the Subreddit and Discord (this is the Reddit thread). If you are worried about the developers not seeing your concern, don't be: They only recently closed MC-26678 as "Won't Fix" so it's on their mind, plus they are probably being harassed about it on social media.

But just as a reminder: MC-26678 was closed with the resolution reason "Won't Fix", which means that, while this behaviour is not desirable, the developers have said that they will not or cannot fix it.

migrated

(Unassigned)

Community Consensus

(Unassigned)

1.16.3, 1.16.4 Pre-release 1

Retrieved