hammy275 / dungeon-dash Goto Github PK

Don't create new DDMap() instances when assigning the start, or an end corner. Fixes a bug where settings for a map have changes undone when setting a start or end.

On the event of a server crash, we won't be able to restore pre-game data. We should save this to a file, and restore it in case of a server crash.

DungeonDash should have a consistent color scheme (probably red + dark blue?). Besides that, color important things in chat.

For the AI of the shadows, the codebase currently uses a Location object, which doesn't store the pitch or yaw (as it's unneeded). However, it uses so little memory, that we might as well use it, and not have to deal with the overhead of creating Location objects from Position objects all the time.

A timer (probably in the scoreboard) to show how long your run has been so far. As a bonus, keep track of records.

There should be a config to adjust plugin settings.

• Should not require hooking into vault, but will hook into it if present
• Customizable prices in a config
• Must at least include a good number of particle trails
• A command to grant permanent access to a given cosmetic

Stand-still death is simply not fun. It was used super early in development in place of the chaser, but as of now, it's practically useless (and completely useless when #16 is added) and not fun to play with.

Since maps may have new features added, we'll want to use our own format for storing, so we can convert it up as needed.

• Save inventory on game start
• Save gamemode on game start
• Set gamemode to adventure on game start
• Restore inventory and gamemode on game end/leave
• Save health and food, and restore when leaving

For each map, admins should be able to set a minimum and maximum player count

Should include Vault integration (because of course it should!).

Rewards should be user-settable

The setting "use_chase" should be an option. It defaults to false. When false, the first player to finish wins. If true, a giant chases players through the map, with all the players who make it to the end alive winning.

For the targeting for the chaser, we already store positions from last to first. We can definitely assemble a leaderboard with those, displaying places 1-4, a ..., then your place and name. It can also display the distance they are away from the finish line, just so people can get an idea.

Make sure everything is good for 1.1.1.

Should show how many people currently queued and max player count (if there is one). Also should hide maps that are currently playing

Set the hotbar of a player to basically execute the create commands so players can setup the map using items.

May also be nice to visualize things using particles, such as the ending zone

There's a lot of problems with the checkpoint code:

• Seems to possibly be buggy
• Works on literally everything interactable (instead of just golden pressure plates)
• Checkpoints aren't reset when completing a map while in a lobby

Let's get this fixed before 1.2

GUI to join Dungeon Dash maps. Would also require letting admins set icons for the maps.

It should have the following:

• Description of the plugin
• All available commands + their associated permissions

While in the lobby, a clock should be in the last hotbar slot that allows leaving of the game when right clicked.

When editing a map, the editor should be teleported to the start of the map for QoL.

The map should check for players stepping on golden pressure plates. When stepped on, it marks a checkpoint there. On respawn, the player should end up at that checkpoint instead of at the start.

/ddash list to get a list of all available maps. Should have a permission tied to it (probably dungeondash.list)

Allow the creation of signs to join.

Move the maps location to server_dir/dungeondash_data/maps

Since a lot of other 1.2 things require it, storing player data and loading it from JSON would be a requirement to have.

At least for the time being, we won't use a database, though might want to add support for one later.

Data should be stored in server_dir/dungeondash_data/playerdata

Move all map customization to a GUI, and place access to said GUI in an item in the creation hotbar.

Needed for most other enhancements in 1.2

Chaser Options:

Mode: (default: chase (the current option)): The AI for the chaser. Options are:

• Chase: Attempts to close the gap with the player in last place. Perfect for non-stop running maps.
• Shadow: Every player gets a chaser that perfectly copies their moves. Perfect for parkour maps or maps that split into multiple directions.

Speed (default: fast (the current option): How fast the chaser moves.

• Slow: Moves slowly in Chase mode (probably ~1/3 of current speed), and moves at 50% player speed in Shadow mode.
• Medium: Moves at a medium pace in Chase mode (probably ~2/3 of current speed), and moves at around 75% player speed in Shadow mode.
• Fast (current): Moves at a fast pace very close to player sprint jumping speed. Will move at ~95% player speed in shadow mode.