Gamemode Honey Drop

Gamemode Honey Drop 1.0.0

Race across breaking hexagon tiles as layers collapse beneath you. Outlast all opponents to win
Documentation License Version History Discussion
Dependencies
Gamemode Core (Required), Gear Core (Required)

A competitive survival gamemode for Rust servers where players race across a multi-layered hexagonal grid that collapses beneath them. Players must outlast their opponents by avoiding falling through the breaking tiles, with the last player standing declared the winner.

Features

  • Multi-layered hexagonal grid of breaking tiles with customizable size and spacing
  • Automatic elimination when players fall below the arena
  • Spectator system for eliminated players with dedicated spawn points
  • Configurable grid settings (radius, tile spacing, layer count, vertical spacing)
  • Separate gear loadouts for warmup, gameplay, and spectator modes
  • Warmup mode with respawning before competitive match begins
  • Real-time scoreboard showing live player count and elimination feed
  • Lobby-based entry through Gamemode Core teleporter zones
  • Create and configure multiple Honey Drop arenas
  • Granular rule system for gameplay mechanics (damage, item drops, corpses, etc.)
  • Command blocking to prevent specific commands during matches
  • Optional kill feed displaying elimination messages to all players

Dependencies

Required

  • Gamemode Core (v1.10.1+) -- Core gamemode framework that provides:
    • Lobby system with teleporters
    • Player state management
    • Zone creation and collision detection
    • UI rendering system
    • Spawn point management
    • Rule enforcement

Optional

  • Gear Core -- Recommended for managing player loadouts
    • Allows defining gear sets for warmup, gameplay, and spectator modes
    • Without this plugin, players spawn with empty inventories

Permissions

  • gamemodecore.admin -- Required for all arena creation and management commands
  • gamemodecore.bypass -- Allows players to bypass gamemode restrictions
Note: Permissions are managed through Gamemode Core.

Commands

All commands require the gamemodecore.admin permission.

Arena Management

  • gm.honeydrop create <title> <position|here&gt; <radius> [maxPlayerCapacity]-- Creates a new Honey Drop arena
    • title -- Display name for the arena
    • position -- Arena center coordinates or "here" for current location
    • radius -- Arena boundary radius
    • maxPlayerCapacity -- Optional max players (-1 for unlimited)
  • gm.honeydrop edit <arenaId> -- Selects an arena for editing
  • gm.honeydrop remove -- Deletes the currently selected arena
  • gm.honeydrop regenerate -- Rebuilds the hexagon grid for the current arena

Spawn Point Management

Player Spawn Points:
  • gm.honeydrop spawn add <position|here> <radius> -- Adds a player spawn point
  • gm.honeydrop spawn remove <spawnPointId> -- Removes a player spawn point
Spectator Spawn Points:
  • gm.honeydrop spectatorspawn add <position|here> <radius> -- Adds a spectator spawn point
  • gm.honeydrop spectatorspawn remove <spawnPointId> -- Removes a spectator spawn point

Teleporter Management

  • gm.honeydrop teleporter create <position|here> <radius> [visibilityRange] [visibleZone]-- Creates a teleporter in the lobby
    • position -- Teleporter location or "here"
    • radius -- Activation radius
    • visibilityRange -- Distance at which information text is displayed (default: 10)
    • visibleZone -- Whether to show the zone sphere (default: true)
  • gm.honeydrop teleporter remove -- Removes the teleporter
  • gm.honeydrop teleporter position <position|here> -- Updates teleporter position
  • gm.honeydrop teleporter radius <radius> -- Updates teleporter radius
  • gm.honeydrop teleporter visibility <range> -- Updates information text visibility distance
  • gm.honeydrop teleporter visiblezone <true|false> -- Toggles zone sphere visibility

Rule Management

  • gm.honeydrop rule add <rule1> [rule2] [rule3]... -- Adds one or more rules to the arena
  • gm.honeydrop rule remove <rule1> [rule2] [rule3]... -- Removes one or more rules from the arena
Available Rules:
  • NoBuilding -- Prevents building within the arena
  • NoKillSelf -- Prevents suicide command
  • NoSleeping -- Prevents sleeping in the arena
  • NoCrafting -- Disables crafting
  • NoItemDropping -- Prevents dropping items
  • NoWounding -- Disables wounded state
  • NoNPCSpawn -- Prevents NPC spawning
  • NoLootSpawn -- Prevents loot container spawning
  • NoSignEditing -- Prevents editing signs
  • NoCorpseSpawn -- Prevents corpse spawning on death
  • NoPvPDamage -- Disables player vs player damage
  • NoEnvironmentDamage -- Disables environmental damage
  • NoArmoryBoxAccess -- Prevents opening armory boxes
  • NoItemContainerSpawn -- Prevents item container drops
  • NoItemWear -- Disables item condition loss
  • NoBleeding -- Disables bleeding
  • NoHunger -- Disables hunger
  • NoThirst -- Disables thirst
  • NoHeldGunDrop -- Prevents gun drops on death
  • NoDecay -- Disables entity decay

Command Blocking

  • gm.honeydrop blockcmd add <command> -- Blocks a command within the arena
  • gm.honeydrop blockcmd remove <command> -- Unblocks a command
  • gm.honeydrop blockcmd list -- Lists all blocked commands

Arena Settings

  • gm.honeydrop set <property> <value> -- Configures arena properties
Available Properties:
Basic Settings:
  • title -- Arena display name
  • enabled -- Enable/disable the arena (true/false)
Grid Configuration:
  • gridradius -- Number of tiles from center (affects arena size)
  • tilespacing -- Distance between tile centers in meters
  • levelcount -- Number of vertical layers
  • levelspacing -- Vertical distance between layers in meters
Match Settings:
  • minplayers -- Minimum players required to start
  • warmupduration -- Warmup phase duration in seconds
  • eliminationheight -- Depth below first layer where players are eliminated
Gear Sets:
  • warmupgearset -- Gear set name for warmup phase
  • maingearset -- Gear set name for main match
  • spectatorgearset -- Gear set name for spectators
Display:
  • killfeed -- Show elimination messages (true/false)
  • infotemplate -- Custom information template for teleporter

Creating Your First Arena

Step 1: Create the Arena
Code: 
gm.honeydrop create "Honey Drop Arena" here 60 16

Step 2: Generate the Grid
Code: 
gm.honeydrop regenerate

Step 3: Add Spawn Points
Player spawn points (in the arena for warmup spawning):
Code: 
gm.honeydrop spawn add here 2
Spectator spawn points (around the arena perimeter for eliminated players):
Code: 
gm.honeydrop spectatorspawn add here 1

Step 4: Create Teleporter
In the lobby:
Code: 
gm.honeydrop teleporter create here 3 15 true

Step 5: Add Rules
Code: 
gm.honeydrop rule add NoItemDropping NoWounding NoCorpseSpawn NoItemContainerSpawn

Step 6: Optional - Set Gear
Code: 
gm.honeydrop set warmupgearset "HoneyDropWarmup"
gm.honeydrop set maingearset "HoneyDropMain"
gm.honeydrop set spectatorgearset "Spectator"

Stored Data

JSON: 
{
  "Arenas": [
    {
      "Enabled": true,
      "Id": "001",
      "Title": "Honey Drop Arena",
      "Gamemode": "HoneyDrop",
      "Radius": 60.0,
      "Position": {
        "x": 100.0,
        "y": 50.0,
        "z": 200.0
      },
      "Rules": [
        "NoItemDropping",
        "NoWounding",
        "NoCorpseSpawn",
        "NoItemContainerSpawn"
      ],
      "Teleporter": {
        "Radius": 3.0,
        "Position": {
          "x": 150.0,
          "y": 30.0,
          "z": 250.0
        },
        "Information Text Visibility Range": 15.0,
        "Visible Zone": true
      },
      "Information Template": "{Title}\nGamemode: {Gamemode}\nStatus: {Status}\nTime Left: {TimeLeft}\nPlayers: {PlayerCount} / {PlayerCapacity}\n\nParticipants:\n{PlayerList}",
      "Maximum Player Capacity": 16,
      "Spawn Points": [
        {
          "Id": "001",
          "Position": {
            "x": 145.0,
            "y": 30.0,
            "z": 245.0
          },
          "Rotation": {
            "x": 0.0,
            "y": 0.0,
            "z": 0.0
          },
          "Radius": 2.0,
          "Leash Radius": 0.0
        }
      ],
      "Blocked Commands": [],
      "Hex Grid Size (Tiles From Center)": 8,
      "Tile Spacing": 1.5,
      "Number Of Vertical Layers": 5,
      "Vertical Distance Between Layers": 8.0,
      "Minimum Players To Start": 4,
      "Warmup Duration Seconds": 15.0,
      "Elimination Zone Depth (Below First Layer)": -10.0,
      "Warmup Gear Set": "HoneyDropWarmup",
      "Gameplay Gear Set": "HoneyDropMain",
      "Show Kill Feed": false,
      "Spectator Spawn Points": [
        {
          "Id": "S001",
          "Position": {
            "x": 170.0,
            "y": 60.0,
            "z": 200.0
          },
          "Rotation": {
            "x": 0.0,
            "y": 180.0,
            "z": 0.0
          },
          "Radius": 1.0,
          "Leash Radius": 0.0
        }
      ],
      "Spectator Gear Set": "Spectator"
    }
  ]
}
Arena Properties:
  • Enabled -- Whether the arena is active
  • Id -- Unique arena identifier (auto-assigned)
  • Title -- Display name shown to players
  • Gamemode -- Always "HoneyDrop"
  • Radius -- Arena boundary radius for zone detection
  • Position -- Arena center coordinates
  • Maximum Player Capacity -- Max players (-1 = unlimited)
Grid Configuration:
  • Hex Grid Size -- Grid radius (number of tiles from center)
  • Tile Spacing -- Distance between hexagon centers
  • Number Of Vertical Layers -- How many layers in the grid
  • Vertical Distance Between Layers -- Height between layers
Match Configuration:
  • Minimum Players To Start -- Players needed to begin match
  • Warmup Duration Seconds -- Practice time before competitive match
  • Elimination Zone Depth -- Negative Y offset for elimination trigger
Gear Configuration:
  • Warmup Gear Set -- Loadout for warmup phase
  • Gameplay Gear Set -- Loadout for competitive match
  • Spectator Gear Set -- Loadout for eliminated spectators
Display Options:
  • Show Kill Feed -- Display elimination messages
  • Information Template -- Custom teleporter info text
Spawn Points:
  • Spawn Points -- Player spawn locations
  • Spectator Spawn Points -- Spectator spawn locations
Rules & Commands:
  • Rules -- Active gameplay rules
  • Blocked Commands -- Commands disabled in arena

Localization

JSON: 
{
  "Score.Title": "HONEY DROP",
  "Score.PlayersRemaining": "<color=#CACF52>{0}</color> players remaining",
  "Player.Eliminated": "<color=#55AAFF>{0}</color> has been eliminated!"
}
Author
VisEntities
License duration
Unlimited
Price
12.99 USD
First release
Last update

Ratings

0.00 star(s) 0 reviews
Donate

Parent plugin

Also by VisEntities

  • About us
    Game4Freak is a Rust plugin marketplace and modding platform offering free and premium plugins for server owners looking to improve and take their servers to the next level.
  • Our
  • Your
Back
Top
Chat commands start with a /, while console commands can be entered directly in the F1 console or server console. Use find <keyword> in console to search for available commands related to the plugin. Parameters in < > are required, while [ ] are optional.
This plugin uses Oxide's permission system. Grant or revoke permissions using oxide.grant and oxide.revoke. You can assign them to individual players or groups using their Steam id or group name.
Settings are stored in the config file found under the config/ directory. You can edit this file manually, then reload the plugin to apply your changes.
Persistent data is saved in the data/ directory. This includes things like saved settings, usage stats, or player progress depending on the plugin. Deleting a data file will reset stored progress or customizations.
Language files are located in the lang/ folder. To translate messages, copy the en.json file into your target language folder (e.g. fr, de) and edit the values. Reload the plugin after changes to apply new messages.
This section lists public methods exposed by the plugin for use in other plugins. You can call these via the CallHook method. Ensure the plugin is loaded before calling its API to avoid null reference errors.
These are custom hooks that other plugins can listen for. Simply define a method with the same name and expected parameters in your plugin to handle the event. Hooks are triggered at key moments and are useful for extending or reacting to plugin behavior.
These hooks are injected into the game's code using Harmony. They let the plugin run code at key points in the game's internal logic. You can return values to block or modify behavior. Use with caution — these are powerful and can affect core mechanics.
Cart

Cart

Total -