9

Ability to store long type number using "/execute store"

Even though "execute store" can use to store long type number into an entity nbt, it can't take long type number and store it to another long type

As an example, there is two command block
The first command block located at 0 0 0 and the other one above it at 0 1 0
If I run these command below sequentially

/data merge block 0 0 0 {LastExecution:9223372036854775807L}
/execute store result block 0 1 0 LastExecution long 1 run data get block 0 0 0 LastExecution

instead of having 9223372036854775807, the LastExecution nbt from the second command block at 0 1 0 is having ‭2147483647‬ which is the max value of integer number

I hope it will get reworked

Registered User shared this idea

• July 17, 2018 07:31
• Report a Concern

Please sign in to leave a comment.

• 0

  Registered User commented

  Comment actions Permalink

  • January 11, 2021 07:00
  • Report a Concern
  • Comment actions Permalink

  The whole point of /execute store result is not that you're moving or copying NBT data, it is that you're running the /data get command, seeing the result it produces, and storing the result in your desired position. It just so happens that the result of `/data get is the value of the NBT tag.

  
  

  In order to accomplish what you are adding for in your suggestion, the entire commands system would need to be redesigned so that results of commands are all long integer values. It would be very haphazardly to attempt to "make an exception" for just this one case.

  
  

  Please consider taking a look at /data modify—it is the preferred way of copying NBT data and works for these long numbers.