RoseStacker 1.2.4

A mob, item, spawner, and block stacking plugin that is built for functionality and performance.

  1. Esophose
    Native Minecraft Version:
    1.13
    Tested Minecraft Versions:
    • 1.13
    • 1.14
    • 1.15
    • 1.16
    Source Code:
    https://github.com/Rosewood-Development/RoseStacker
    [​IMG]

    [​IMG]    [​IMG]    [​IMG]    [​IMG]


    [​IMG]

    RoseStacker is a stacking plugin created to stack entities, items, blocks, and spawners!

    This plugin is perfect for servers that wish to alleviate common sources of lag, whilst also gaining access to features that improve the functionality and feel of the server.



    [​IMG]




    [​IMG]

    RoseStacker already has tons of features, and sees many more added during its lifetime. In its creation, we really aimed to add everything that we thought a stacker plugin should have.

    If you have any suggestions for what you'd like to see be added to the plugin, tell us on our Discord server!

    Check out some of its features:


    [​IMG]
    • Disable mob AI.
    • Spawner GUI that shows information like spawner stats, spawn conditions, and whether or not mobs are able to spawn.
    • Mob spawn multiplier customizable based on the amount of spawners in the stack.
    • Change the minimum and maximum tick rates for spawning, which allows you to change how slowly or quickly mobs will be spawned.
    • Configurable player activation range.
    • Choose how far away entities can spawn from their spawners.
    • Edit the max amount of entities allowed near a spawner before allowing spawns to continue.
    • Explosion protection.
    • Configurable percentage or set amounts for stack loss to explosion damage.
    • Put spawners directly into a player's inventory when broken.
    • Break entire stack while sneaking.
    • Receive a bundled stack or individual spawners upon breaking a stack.
    • Drop spawners directly into inventory when broken.
    • Silk touch permission requirement, level requirement, and drop chance.


    [​IMG]
    • Merge all entities in a chunk.
    • Conditions to unstack entities.
    • Entire stack special death conditions.
    • Only stack mobs if they're not in a specific state, like being on the ground, in water, or if they are in line of sight from another mob.
    • Toggle mobs stacking only if they are spawned from a spawner.
    • Customizable stack frequency, allowing you to choose how often nearby entities get stacked.
    • Transform entire stacks of mobs, such as zombies drowning or pigs getting struck by lightning.
    • Show custom names on stacked entities.
    • Save custom attributes, like custom max health or custom damage.
    • Drop accurate items and experience when killing entire stacks.
    • Transfer knockback to the next entity in the stack upon entity death.
    • Stack mobs downwards, which is useful for mob grinders.


    [​IMG]
    • Block GUI to allow the mass placement or removal of blocks of a stack.
    • Explosion protection.
    • Configurable percentage or set amounts for stack loss to explosion damage.
    • Setting to retrieve entire stack if mined while sneaking.


    [​IMG]
    • Choose the minimum and maximum stack sizes for each stack type.
    • Commands to give bundled stacks.
    • Merge radii for entities and items.
    • Disable stacking on a per-type basis.
    • Disable the plugin on a per-world basis.
    • Editable display names.
    • Disable nametags.
    • Hide nametags if there is only one of a type in a stack.


    [​IMG]
    • Configurable range at which you can view nametags from stacks in the world.
    • Enable or disable dynamic view range for nametags.
    • Hide nametags if they aren't in line of sight of the player.


    [​IMG]
    • Fully functional reload command that will actually reload all of your files and changes.
    • Fully editable language files that allow for full plugin translation.
    • MySQL support.




    [​IMG]


    RoseStacker is compatible with Spigot 1.13+ (or any forks of Spigot).

    It also has added compatibility with some specific plugins, to further improve your configuration capabilities.

    Check out our plugin compatibility:

    [​IMG]



    [​IMG]


    To learn about the commands and permissions of RoseStacker, check out our wiki! It includes an FAQ and should be able to tell you all that you need to know.

    [​IMG]



    [​IMG]

    [​IMG] [​IMG]

    [​IMG] [​IMG]

    [​IMG] [​IMG]

    [​IMG] [​IMG]

    [​IMG] [​IMG]




    [​IMG]


    This plugin comes with a large amount of configuration, so that you can get exactly what you want out of it.

    After the initial startup and loading of the plugin, you will find a few files inside of the plugin's folder. These files include:
    config.yml block_settings.yml entity_settings.yml item_settings.yml spawner_settings.yml


    To give you a small glimpse into some of the choices you'll have, here you can see the default config.yml file:

    Code (YAML):
    #      __________                      _________ __                 __                
    #      \______   \ ____  ______ ____  /   _____//  |______    ____ |  | __ ___________
    #       |       _//  _ \/  ___// __ \ \_____  \\   __\__  \ _/ ___\|  |/ // __ \_  __ \
    #       |    |   (  <_> )___ \\  ___/ /        \|  |  / __ \\  \___|    <\  ___/|  | \/
    #       |____|_  /\____/____  >\___  >_______  /|__| (____  /\___  >__|_ \\___  >__|  
    #              \/           \/     \/        \/           \/     \/     \/    \/      

    # The locale to use in the /locale folder
    # Default: en_US
    locale
    : en_US

    # A list of worlds that the plugin is disabled in
    disabled-worlds
    :
     - disabled_world_name

    # How often should we try to stack nearby entities?
    # Higher values mean longer times between checks, but also less lag
    # If you are having issues with TPS, increase this value
    # Values are in ticks, do not set lower than 1
    # Default: 10
    stack-frequency
    : 10

    # Global entity settings
    # Changed values in entity_settings.yml will override these values
    global-entity-settings
    :

      # Should entity stacking be enabled at all?
      # Default: true
      stacking-enabled
    : true

      # The minimum number of nearby entities required to form a stack
      # Do not set this lower than 2
      # Default: 2
      min-stack-size
    : 2

      # The maximum number of entities that can be in a single stack
      # Default: 128
      max-stack-size
    : 128

      # How close do entities need to be to merge with each other?
      # Default: 5
      merge-radius
    : 5

      # Should we merge all similar entities into a single stack per chunk?
      # This setting overrides the above
      # Default: false
      merge-entire-chunk
    : false

      # Should tags be displayed above stacks to show their amount and type?
      # Default: true
      display-tags
    : true

      # Should tags be displayed if the stack only has one entity?
      # Default: false
      display-tags-single
    : false

      # Do stacks need to be hovered over for their tags to be visible?
      # Default: false
      display-tags-hover
    : false

      # Should the entity custom name be visible with the stack size?
      # Default: true
      display-tags-custom-name
    : true

      # Should the entire stack of entities always be killed when the main entity dies?
      # Default: false
      kill-entire-stack-on-death
    : false

      # Under what conditions should the entire stack be killed when the main entity dies?
      # If kill-entire-stack-on-death is true, this setting will not be used
      # Valid conditions can be found here:
      # https://hub.spigotmc.org/javadocs/spigot/org/bukkit/event/entity/EntityDamageEvent.DamageCause.html
      kill-entire-stack-on-death-conditions
    :
       - FALL

      # Should knockback be transferred to the next entity in the stack?
      # Default: true
      kill-transfer-velocity
    : true

      # Should items be dropped for all entities when an entire stack is killed at once?
      # Default: true
      drop-accurate-items
    : true

      # Should exp be dropped for all entities when an entire stack is killed at once?
      # Default: true
      drop-accurate-exp
    : true

      # Should entity attributes (custom max health, custom damage, etc.) be saved in the stack data?
      # Disabled by default, as it increases the database size to have this enabled
      # Default: false
      save-attributes
    : false

      # Should newly stacked entities be put on the bottom of the stack?
      # Default: false
      stack-to-bottom
    : false

      # Do entities need to be able to see each other to be able to stack?
      # Setting this to true will prevent entities from stacking through walls
      # Default: true
      require-line-of-sight
    : true

      # Should the entire stack of entities be transformed when the main entity is transformed?
      # This applies to pigs getting struck by lightning, zombies drowning, etc
      # Default: true
      transform-entire-stack
    : true

      # Do entities have to be on the ground in order to stack?
      # This does not apply if the mobs can fly or live in the water
      # Default: false
      only-stack-on-ground
    : false

      # Should we stack entities if they are in the water?
      # This does not apply if the mobs can fly or live in the water
      # Default: false
      dont-stack-if-in-water
    : false

      # Should we stack entities if they are leashed?
      # You will still be able to leash stacks, it will just prevent them from stacking into other stacks
      # This can cause some weird effects if disabled
      # Default: true
      dont-stack-if-leashed
    : true

      # Should we stack entities if they are invulnerable?
      # Default: true
      dont-stack-if-invulnerable
    : true

      # Should we avoid stacking entities with custom names?
      # Default: false
      dont-stack-custom-named
    : false

      # Should flying mobs always be stacked downwards?
      # This is useful for mob grinders
      # Default: false
      stack-flying-downwards
    : false

      # Should we only stack entities spawned from spawners?
      # Default: false
      only-stack-from-spawners
    : false

      # Should an entity death event be triggered for each mob in a stack?
      # If you use custom drops plugins, make sure to enable this
      # Note to developers: The death events are asynchronous
      # Default: false
      trigger-death-event-for-entire-stack-kill
    : false

    # Global item settings
    # Changed values in item_settings.yml will override these values
    global-item-settings
    :

      # Should item stacking be enabled at all?
      # Default: true
      stacking-enabled
    : true

      # The maximum number of items that can be in a single stack
      # Default: 1024
      max-stack-size
    : 1024

      # How close do items need to be to merge with each other?
      # Default: 2.5
      merge-radius
    : 2.5

      # Should tags be displayed above stacks to show their amount and type?
      # Default: true
      display-tags
    : true

      # Should tags be displayed if the stack only has one item?
      # Default: false
      display-tags-single
    : false

      # Should items with custom names be shown on their tags?
      # Default: true
      display-custom-names
    : true

      # Should the color of custom names be shown on their tags?
      # Default: true
      display-custom-names-color
    : true

      # Should items with a custom name always display their tags?
      # This mirrors vanilla behavior
      # Default: true
      display-custom-names-always
    : true

    # Global block settings
    # Changed values in block_settings.yml will override these values
    global-block-settings
    :

      # Should block stacking be enabled at all?
      # Default: true
      stacking-enabled
    : true

      # The maximum number of blocks that can be in a single stack
      # Default: 2048
      max-stack-size
    : 2048

      # Should tags be displayed above stacks to show their amount and type?
      # Default: true
      display-tags
    : true

      # Should stacked blocks be protected from explosions?
      # Default: true
      explosion-protection
    : true

      # If enabled, only the stack size will decrease from explosions, no items will be dropped
      # Default: true
      explosion-decrease-stack-size-only
    : true

      # The percentage chance of blocks getting destroyed from an explosion (0-100)
      # Default: 10.0
      explosion-destroy-chance
    : 10.0

      # The percentage of blocks in the stack that will be destroyed from an explosion
      # If a stack of 10 blocks is exploded with a chance of 50.0, 5 blocks will be saved
      # Default: 50.0
      explosion-amount-percentage
    : 50.0

      # The fixed amount of blocks in the stack to destroy
      # If this is set to 1 or greater, overrides explosion-amount-percentage
      # If a stack of 10 blocks is exploded with a fixed amount of 3, 7 blocks will be saved
      # Default: -1
      explosion-amount-fixed
    : -1

      # Should blocks be dropped directly into the player's inventory when broken?
      # Default: false
      drop-to-inventory
    : false

      # Should the entire stack be broken if the player is sneaking?
      # Default: true
      break-entire-stack-while-sneaking
    : true

      # Should the entire stack be broken into individual blocks?
      # Default: true
      break-entire-stack-into-separate
    : true

      # Should a GUI to edit the stack open when the player shift-right-clicks the stack?
      # Default: true
      gui-enabled
    : true

      # What material should be used for the border of the GUI?
      # If you want no border, set it to AIR
      # Default: BLUE_STAINED_GLASS_PANE
      gui-border-material
    : BLUE_STAINED_GLASS_PANE

    # Global spawner settings
    # Changed values in spawner_settings.yml will override these values
    global-spawner-settings
    :

      # Should spawner stacking be enabled at all?
      # Default: true
      stacking-enabled
    : true

      # The maximum number of spawners that can be in a single stack
      # Default: 32
      max-stack-size
    : 32

      # Should tags be displayed above stacks to show their amount and type?
      # Default: true
      display-tags
    : true

      # Should tags be displayed if the stack only has one spawner?
      # Default: false
      display-tags-single
    : false

      # Should mob AI be disabled for mobs spawned by spawners?
      # If you enable this, it is highly recommended to enable global-entity-settings.save-attributes
      # Enabling attribute saving will make sure all mob AIs get disabled properly
      # Default: false
      disable-mob-ai
    : false

      # How many random blocks should we check to spawn a mob before giving up?
      # Default: 50
      max-failed-spawn-attempts
    : 50

      # Should spawners be protected from explosions?
      # Default: true
      explosion-protection
    : true

      # If enabled, only the stack size will decrease from explosions, no items will be dropped
      # Default: true
      explosion-decrease-stack-size-only
    : true

      # The percentage chance of spawners getting destroyed from an explosion (0-100)
      # Default: 10.0
      explosion-destroy-chance
    : 10.0

      # The percentage of spawners in the stack that will be destroyed from an explosion
      # If a stack of 10 spawners is exploded with a chance of 50.0, 5 blocks will be saved
      # Default: 50.0
      explosion-amount-percentage
    : 50.0

      # The fixed amount of spawners in the stack to destroy
      # If this is set to 0 or greater, overrides explosion-amount-percentage
      # If a stack of 10 spawners is exploded with a fixed amount of 3, 7 blocks will be saved
      # Default: -1
      explosion-amount-fixed
    : -1

      # Should spawners be dropped directly into the player's inventory when broken?
      # Default: false
      drop-to-inventory
    : false

      # Should the entire stack be broken if the player is sneaking?
      # Default: true
      break-entire-stack-while-sneaking
    : true

      # Should the entire stack be broken into individual spawners?
      # Default: false
      break-entire-stack-into-separate
    : false

      # Should silk touch be required to pick up spawners?
      # Default: false
      silk-touch-required
    : false

      # The chance that spawners will be picked up with a silk touch tool
      # Default: 100
      silk-touch-chance
    : 100

      # Should silk touch of level II or higher be guaranteed to pick up the spawner?
      # Default: true
      silk-touch-guarantee
    : true

      # Should the permission rosestacker.silktouch be required
      # to be able to pick up spawners with silk touch?
      # Default: false
      silk-touch-require-permission
    : false

      # How many mobs should spawn per stacked spawner?
      # Default: 4
      spawn-count-stack-size-multiplier
    : 4

      # Should the amount of mobs spawned be randomized between the stack size and the max spawn amount?
      # Default: true
      spawn-count-stack-size-randomized
    : true

      # The minimum number of ticks between spawn attempts
      # Default: 200
      spawn-delay-minimum
    : 200

      # The maximum number of ticks between spawn attempts
      # Default: 800
      spawn-delay-maximum
    : 800

      # If more than this number of entities are near the spawner, it will not spawn anything
      # This only counts the individual mobs, and not the stack size
      # Can be overridden for each spawner type using the max-nearby-entities:# spawn requirement
      # Default: 6
      spawn-max-nearby-entities
    : 6

      # How close do players need to be to activate the spawner?
      # Default: 16
      spawn-player-activation-range
    : 16

      # How far away can entities be spawned from the spawner?
      # Default: 4
      spawn-range
    : 4

      # Should a GUI to view the spawner information open when the player shift-right-clicks the stack?
      # Default: true
      gui-enabled
    : true

      # How often should the time before next spawn message be updated?
      # Value is measured in ticks, do not go below 1
      # Default: 2
      gui-tick-update-rate
    : 2

      # What material should be used for the border of the GUI?
      # Default: GRAY_STAINED_GLASS_PANE
      gui-border-material
    : GRAY_STAINED_GLASS_PANE

      # What material should be used for the top right and bottom left corners of the GUI?
      # Default: LIGHT_BLUE_STAINED_GLASS_PANE
      gui-border-corner-material
    : LIGHT_BLUE_STAINED_GLASS_PANE

      # What material should be used for the corner accents of the GUI?
      # Default: BLUE_STAINED_GLASS_PANE
      gui-border-accent-material
    : BLUE_STAINED_GLASS_PANE

      # What material should the spawner stats icon be?
      # Default: BOOK
      gui-spawner-stats-material
    : BOOK

      # What material should the central icon be?
      # Default: SPAWNER
      gui-central-material
    : SPAWNER

      # What material should the valid spawn conditions icon be?
      # Default: EMERALD_BLOCK
      gui-valid-spawn-conditions-material
    : EMERALD_BLOCK

      # What material should the invalid spawn conditions icon be?
      # Default: REDSTONE_BLOCK
      gui-invalid-spawn-conditions-material
    : REDSTONE_BLOCK

    # Settings that apply to the tags above stacks
    # These settings require their respective display-tags settings to be set to true to function
    # These settings run at the same frequency as the stack-frequency setting
    # If you are seeing impacts to server performance, consider disabling these settings
    dynamic-tag-settings
    :

      # Should entity tags be hidden when the player is a certain distance away?
      # Note: This overrides global-entity-settings.display-tags-hover if enabled
      # Default: true
      entity-dynamic-tag-view-range-enabled
    : true

      # Should item tags be hidden when the player is a certain distance away?
      # Default: true
      item-dynamic-tag-view-range-enabled
    : true

      # Should block/spawner tags be hidden when the player is a certain distance away?
      # Default: true
      block-dynamic-tag-view-range-enabled
    : true

      # How far away should a player be able to see entity tags?
      # Default: 32
      entity-dynamic-tag-view-range
    : 32

      # How far away should a player be able to see item tags?
      # Default: 32
      item-dynamic-tag-view-range
    : 32

      # How far away should a player be able to see block/spawner tags?
      # Default: 32
      block-dynamic-tag-view-range
    : 32

      # Should entity tags be hidden if they are out of view?
      # Default: true
      entity-dynamic-tag-view-range-wall-detection-enabled
    : true

      # Should item tags be hidden if they are out of view?
      # Default: true
      item-dynamic-tag-view-range-wall-detection-enabled
    : true

      # Should block/spawner tags be hidden if they are out of view?
      # Default: true
      block-dynamic-tag-view-range-wall-detection-enabled
    : true

    # Miscellaneous other settings for the plugin
    misc-settings
    :

      # If CoreProtect is installed, should we log stacked block/spawner break/placing?
      # Default: true
      coreprotect-logging-enabled
    : true

      # If Clearlag is installed, should we clear stacked entities?
      # Default: true
      clearlag-clear-entities
    : true

      # If Clearlag is installed, should we clear stacked items?
      # Default: true
      clearlag-clear-items
    : true

      # Should single mobs be removed with `/rs clearall`?
      # This will also affect the clearlag-clear-entities setting above
      # Default: false
      clearall-remove-single
    : false

    # Settings for if you want to use MySQL for data management
    mysql-settings
    :

      # Enable MySQL
      # If false, SQLite will be used instead
      # Default: false
      enabled
    : false

      # MySQL Database Hostname
      # Default:
      hostname
    : ''

      # MySQL Database Port
      # Default: 3306
      port
    : 3306

      # MySQL Database Name
      # Default:
      database-name
    : ''

      # MySQL Database User Name
      # Default:
      user-name
    : ''

      # MySQL Database User Password
      # Default:
      user-password
    : ''

      # If the database connection should use SSL
      # You should enable this if your database supports SSL
      # Default: false
      use-ssl
    : false

    # That's everything! You reached the end of the configuration.
    # Enjoy the plugin!
     



    [​IMG]


    If you need any help, have found a bug, or you have any questions, please join our Discord server! We offer all support through our server.

    Feel free to use the discussion channel to talk and ask questions, or open a ticket if you've found a bug.

    [​IMG]



    [​IMG]


    Isn't the world just a little bit cooler when there are more open source plugins around? We're dedicated to keeping our code out there and and easily accessible to those who want to check it out. Feel free to look at our GitHub!

    [​IMG]




    [​IMG]


    A big thanks to everyone who supports us and uses our plugins! A lot of time and love goes into them. If you like this plugin, please consider leaving us a review, or check out our other plugins!

    [​IMG]





    [​IMG]

    [​IMG][​IMG]
    [​IMG][​IMG]


    Remember, don't use reviews if you need help! If you need help or you have a bug to report, please visit our Discord!

Recent Updates

  1. RoseStacker v1.2.4
  2. RoseStacker v1.2.3
  3. RoseStacker v1.2.2

Recent Reviews

  1. extremall
    extremall
    5/5,
    Version: 1.2.4
    I like your plugin page design. Also, the support is amazing. I get a fast response.
  2. CarrotMC
    CarrotMC
    5/5,
    Version: 1.2.4
    Fantastic plugin by a great developer. I joined the official discord server, requested support, and my issue was resolved rapidly. Definitely went above and beyond my expectations, would recommend this plugin to anyone who needs a stacker.
  3. Faun
    Faun
    5/5,
    Version: 1.2.4
    Another update to the best spawner plugin out there right now, the update fixed a lot of issues reported in the discord server. #Nicole4PresidentOfTheUniverse
  4. morose
    morose
    5/5,
    Version: 1.2.3
    Incredibly well made plugin. Active dev, pretty much no bugs, fast support/fixes, reduces lag a lot. Would reccomend :o
  5. ArranAwesome
    ArranAwesome
    5/5,
    Version: 1.2.3
    Absolutely AWESOME ⭐⭐⭐⭐⭐. Awesome to minimize lag and adds amazing features to Minecraft. The stacked spawners are amazing with no issues
  6. stard
    stard
    5/5,
    Version: 1.2.3
    Amazing plugin! Plenty features and reduces common lag!


    ================================================
  7. KickSquare_
    KickSquare_
    5/5,
    Version: 1.2.1
    Best stacking spawner on the market, I recommend it! Support on discord is super quick as well
  8. NotGeri
    NotGeri
    5/5,
    Version: 1.2.0
    In case you're looking for a stacker plugin, there's simply no better alternative. The developer is honestly just amazing in every way and the plugin functions flawlessly.
  9. iREDRUM
    iREDRUM
    5/5,
    Version: 1.2.0
    This is by far the best plugin for Spawners out there. Literally everything that you can think is there for you. The support is off the charts compared to other support. The response time of the support is mind blowing. I would not recommend any other Spawner plugin as they do not compare to this one. Everything that I needed in a spawner plugin was there.
  10. leop2
    leop2
    5/5,
    Version: 1.2.0
    Very good plugin! Does everything you'd need a stackingplugin to do! Built-in support for spawnerbreaking/placing, MySQL support, ...
    Discord-Support is also perfect!