Join the Game4Freak Discord Get exclusive plugin sneak peeks, talk directly with VisEntities, never miss important updates, and unlock special discount codes!
Gamemode Honey Drop

Gamemode Honey Drop 1.2.0

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

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 -- 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
Note: Permissions are managed through Gamemode Core.

Commands

All commands are F1 console commands. An arena must be selected with edit before most commands will work.

Arena Management

  • gm.honeydrop create <title> <position|here> <radius> [maxPlayerCapacity]-- Creates a new Honey Drop arena
    • title` -- Display name for the arena
    • position` -- World coordinates or here to use your current position
    • radius` -- Arena zone radius in meters
    • maxPlayerCapacity` -- Optional. Maximum players allowed (-1 for unlimited)
  • `gm.honeydrop edit <arenaId> -- Selects an arena for editing. Required before using most other commands
  • gm.honeydrop remove -- Deletes the currently selected arena
  • gm.honeydrop regenerate -- Manually regenerates the hex tile grid for the selected arena (useful for testing grid settings)

Arena Properties

  • `gm.honeydrop set <property> <value> -- Modifies a property on the selected arena. Available properties:
    • title <string> -- Arena display name
    • enabled <true/false> -- Whether the arena accepts players
    • position <position|here> -- Arena center position
    • radius <float> -- Arena zone radius
    • gridradius <int> -- Number of tiles from center (controls grid size)
    • tilespacing <float> -- Horizontal distance between tile centers
    • levelcount <int> -- Number of vertical layers
    • levelspacing <float> -- Vertical distance between layers
    • minplayers <int> -- Minimum players required to start a round
    • warmupduration <float> -- Warmup countdown in seconds (minimum 5)
    • warmupgearset <string> -- Gear Core set name for warmup phase
    • maingearset <string> -- Gear Core set name for active gameplay
    • spectatorgearset <string> -- Gear Core set name for spectators
    • killfeed <true/false> -- Whether kill messages are shown
    • infotemplate <string> -- Template for the teleporter info display

Spawn Points

  • gm.honeydrop spawn player add <position|here> <radius> [leashRadius] -- Adds a player spawn point
  • gm.honeydrop spawn player remove <id|nearby> -- Removes a player spawn point by ID or nearest to your position
  • gm.honeydrop spawn player list -- Lists all player spawn points
  • gm.honeydrop spawn spectator add <position|here> <radius> [leashRadius] -- Adds a spectator spawn point.
  • gm.honeydrop spawn spectator remove <id|nearby> -- Removes a spectator spawn point
  • gm.honeydrop spawn spectator list -- Lists all spectator spawn points
Player spawn points are used during warmup. During the active round, players spawn on top of the hex grid's top layer tiles instead.

Teleporter

The teleporter is a zone placed inside the lobby that players walk into to join the arena.
  • gm.honeydrop teleporter create <position|here> <radius> [visibilityRange] [visibleZone]-- Creates a teleporter for the selected arena
    • visibilityRange -- Distance at which the info text is visible (default 10)
    • visibleZone -- Whether the teleporter zone dome is visible (default true)
  • gm.honeydrop teleporter remove -- Removes the teleporter
  • gm.honeydrop teleporter position <position|here> -- Moves the teleporter
  • gm.honeydrop teleporter radius <radius> -- Changes the teleporter radius
  • gm.honeydrop teleporter visibility <range> -- Changes the info text visibility range
  • gm.honeydrop teleporter visiblezone <true/false> -- Toggles the zone dome visibility

Rules & Blocked Commands

  • gm.honeydrop rule add <rule1> [rule2] ... -- Adds rules to the selected arena. See Rules for available rules
  • gm.honeydrop rule remove <rule1> [rule2] ... -- Removes rules from the selected arena
  • gm.honeydrop blockcmd add <command> -- Blocks a command inside the arena
  • gm.honeydrop blockcmd remove <command> -- Unblocks a command
  • gm.honeydrop blockcmd list -- Lists all blocked commands

Setup Guide

Quick Start

  1. Install Gamemode Core and Gamemode Honey Drop
  2. Set up a lobby in Gamemode Core if you haven't already (gm.lobby create here 50)
  3. Add lobby spawn points (gm.lobby spawn add here 2)
  4. Create a Honey Drop arena: gm.honeydrop create "Hex Arena" here 80
  5. Add player spawn points (used during warmup): gm.honeydrop spawn player add here 3
  6. Add spectator spawn points: gm.honeydrop spawn spectator add here 5 20
  7. Create a teleporter in the lobby: gm.honeydrop teleporter create here 3 15
  8. Optionally configure gear sets: gm.honeydrop set maingearset mygearset
  9. Test with the regenerate command to preview the grid: gm.honeydrop regenerate

Tuning the Grid

The grid's feel depends on four settings working together:
  • A gridradius of 5 with tilespacing of 1.5 creates a medium-sized hex platform
  • Increase gridradius for more players or longer rounds
  • Increase levelcount for more vertical layers (more chances before elimination)
  • Adjust levelspacing to control how long players fall between layers — larger values give more time to maneuver mid-air
Use gm.honeydrop regenerate after changing grid settings to preview the result without waiting for a full round.

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,
      "Warmup Gear Set": "HoneyDropWarmup",
      "Gameplay Gear Set": "HoneyDropMain",
      "Show Kill Feed": false
    }
  ]
}
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
Gear Configuration:
  • Warmup Gear Set -- Loadout for warmup phase
  • Gameplay Gear Set -- Loadout for competitive match
Display Options:
  • Show Kill Feed -- Display elimination messages
  • Information Template -- Custom teleporter info text
Spawn Points:
  • Spawn Points -- Player 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

Parent plugin

  • Gamemode Core
    Gamemode Core
    The central hub that powers all your competitive content. One lobby connecting to every arena through a unified system

Also by VisEntities

Latest updates

  1. 1.2.0

    Added spectator spawn system. Eliminated players are now teleported to dedicated spectator spawn...
  2. 1.1.2

    Fixed players being falsely eliminated at round start when staggered spawning hadn't teleported...
  3. 1.1.1

    Fixed players getting kicked when round starts. Reworked fall elimination to handle all arena...
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