6

Follow

/execute store worldborder

I'm running in issues (I mean I can't) store the value of an score in the worldborder attributes (size and even center), so it would be really cool to be able to save a value just like with a bossbar.

The mechanism could be:

/execute store result worldborder set <size/time> run <test>

/execute store result worldborder center <x/z> run <test>

/execute store result worldborder damage run <test>

/execute store result worldborder warning run <test>

Registered User shared this idea

• December 09, 2018 12:31
• Edited
• Report a Concern

Please sign in to leave a comment.

• 1

  Registered User commented

  Comment actions Permalink

  • November 10, 2020 03:44
  • Edited
  • Report a Concern
  • Comment actions Permalink

  I agree with this for the most part, but there are a few modifications that I would make, mostly to face the fact that commands can only return one number:

  • center would have to be two different options: center_x and center_z because they are two different properties.
  • damage would need to be two different options: damage_buffer and damage_amount because they are two different properties.
  • warning would have to be two different options: warning_distance and warning_time because they are two different properties.
  • For setting the main size and time, it won't be that easy because commands only return one number. I propose a setup similar to the way /title works:

    1. /execute store result worldborder time

       This will set a time for the worldborder to move, but not take any immediate action.

    2. /execute store result worldborder size

       This will start the worldborder moving to the target size, for the duration specified in the previous command for time. If a call setting the time was never made, the worldborder moves instantly.
    3. Once the worldborder finished moving, the set time is reset to 0.