Skip to content

[Feature Request] Define Coffin/Grave Time and Player XP per Rank #194

@v4r1n

Description

@v4r1n

Is your feature request related to a problem in GravesX? Please describe.

Please before, I suggested a function that deducts money when a player dies, and we could define the permissions separately by rank. Later, you implemented this feature in graves.yml. That's fantastic! I'm impressed and grateful.

Defining the coffin's remaining time and the player's XP will work similarly to graves.deduct.<name>. We just need to add a separate definition function for the coffin's remaining time (graves.remain.<time>) and the experience value deducted from the dead player based on the defined rank (graves.experience.<name>).

I sincerely thank the team and encourage you to continue developing this good and useful plugin.

Describe the solution you'd like

I want you to add separate permissions, similar to graves.deduct.<name>. This would allow me to set different values for different groups.

Experience Example

Valid values between 0.01 - 1.00

      experience:
        store:
          - "default:0.3"
          - "premium:0.8"

Grave Time Example

How long graves should stay alive

      grave:
        time:
          - "default:300"
          - "premium:10800"

Describe alternatives you've considered

Here are a couple of ideas for the player experience when a player dies:

  1. Bottle o' Enchanting: The game should give the player a Bottle o' Enchanting that stores all their experience (XP) in a single bottle. The player can then right-click or throw the bottle to reclaim all the XP they had before they died.
  2. Immediate Grave Redemption: The player receives their XP immediately when they open their grave.

Additional context

Please help me create placeholders that show the teleport cost for the teleport.cost function.
Exam: %gravesx_teleport_cost%

Confirmation

  • I confirm that the feature request doesn't already exist on the latest version or development build of GravesX.
  • If the issue is caused by another fork, then I expect to not get support here and my issue will be closed.
  • I am not just clicking checkboxes randomly without reading them. If I don't check this, then I did read everything.

Metadata

Metadata

Assignees

Labels

GravesX ModuleAssigned to good features that will probably become a GravesX ModuleenhancementNew feature or request

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions