MC-226898Wrong Chat box Output of command attribute get <scale>
When using command /attribute ... get <scale> or /attribute ... base get <scale>, the output is wrong on screen when a scale is added. If you use execute store, a correct number can be stored in a scoreboard after scaled, but we cannot see the correct scaled value in the chat box.
In the following example, the command executed is
/execute store result score @s 3 run attribute @s generic.attack_damage base get 3
My base attribute of damage is 1.
We can see a correct value "3" is stored on the scoreboard, but in the chat it says "1".
Which is different when using the scale features of /data
Environment
Windows 10
Linked Issues
Attachments1
Created Issue:
Wrong Chat box Output of command attribute get <scale>
When using command /attribute ... get <scale> or /attribute ... base get <scale>, the output is wrong on screen when a scale is added. If you use execute store, a correct number can be stored in a scoreboard after scaled, but we cannot see the correct scaled value in chat box.
'
In the following example, the command executed is
/execute store result score @s 3 run attribute @s generic.attack_damage base get 3
My base attribute of damage is 1.
We can see a correct value is stored on the scoreboard, but in the chat it says "1".
Which is different when using the scale features of /data
Environment
Windows 10
Attachments1
When using command /attribute ... get <scale> or /attribute ... base get <scale>, the output is wrong on screen when a scale is added. If you use execute store, a correct number can be stored in a scoreboard after scaled, but we cannot see the correct scaled value in chat box.
'
In the following example, the command executed is
/execute store result score @s 3 run attribute @s generic.attack_damage base get 3
My base attribute of damage is 1.
We can see a correct value is stored on the scoreboard, but in the chat it says "1".
Which is different when using the scale features of /data
When using command /attribute ... get <scale> or /attribute ... base get <scale>, the output is wrong on screen when a scale is added. If you use execute store, a correct number can be stored in a scoreboard after scaled, but we cannot see the correct scaled value in chat box.
In the following example, the command executed is
/execute store result score @s 3 run attribute @s generic.attack_damage base get 3
My base attribute of damage is 1.
We can see a correct value "3" is stored on the scoreboard, but in the chat it says "1".
Which is different when using the scale features of /data
When using command /attribute ... get <scale> or /attribute ... base get <scale>, the output is wrong on screen when a scale is added. If you use execute store, a correct number can be stored in a scoreboard after scaled, but we cannot see the correct scaled value in the chat box.
In the following example, the command executed is
/execute store result score @s 3 run attribute @s generic.attack_damage base get 3
My base attribute of damage is 1.
We can see a correct value "3" is stored on the scoreboard, but in the chat it says "1".
Which is different when using the scale features of /data
![[Mod] tryashtar](../../../data/avatars/users/41963.png){kind=small}
is duplicated by
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
![[Mod] markderickson](../../../data/avatars/users/18946.svg){kind=small}
Thank you for your report!
We're tracking this issue in MC-226898, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
can confirm in 1.21
Dahesor Since you are the reporter and have already added 1.21 as an affected version, there is no need for you to comment it.