MultiDH

What is MultiDH?

MultiDH is an addon for the plugin DecentHolograms.
It allows you to create copies of a pre-existing hologram that get updated whenever you update the original hologram via /dh reload (You may also do /multidh reload to force a reload on MultiDH's end).

This should allow you an easy way to update multiple holograms displaying the same info, without having to edit n individual ones.

How does it work?

To use MultiDH, you first open the config.yml located within plugins/MultiDH/. In this file should you find two settings: holograms and initDelay.

For our purpose is only holograms relevant. To add copies of an existing hologram, add a new entry that looks similar to the following:

holograms:
  - name: 'myhologram'
    locations:
      - 'world:0.500:100.0:0.500'

name is the name of the original Hologram used in DecentHolograms and locations would be a list of locations matching the format DecentHolograms uses (<world>:<x>:<y>:<z>).

After you've set the hologram(s) and the locations of their copies, save the file and run /multidh reload.
You should now have holograms appear at the specified locations displaying the same content as the original. Any changes made to the original will be reflected on the copies as soon as /dh reload is executed.

Notes:

• The Hologram copies are non-persistent, meaning they do not create a file and won't reappear after a server restart without the plugin.
• The Hologram copies use the name format <name>_multidh_<index> (i.e. example_multidh_0). While unlikely, make sure no other holograms on the server share this name pattern.

Known issues and limitations

There are a few known issues and limitations that the plugin has to work its way around.

Hologram Copies disappear and reappear on reload

Due to a bug/glitch in DecentHolograms that causes holograms to be duplicated rather than updated does MultiDH delete all previous holograms it made and re-creates them to update their data.

Plugin reports it can't load holograms at startup

Due to a lack of a Hologram-related event can MultiDH not know when a Hologram is loaded by DecentHolograms.
In addition is DecentHolograms loading its holograms after the server completed its startup. This causes a race condition where MultiDH tries to load holograms before DecentHologram has even started loading them.

To avoid this issue does MultiDH intentionally delay its loading for a few seconds after the server is done loading. The default delay is 3 seconds and cannot be set lower. Depending on the number of Holograms in DecentHolograms and the server's overall performance will you need to increase the delay in the initDelay setting.