IntellectualSites / IntellectualSites/FastAsyncWorldEdit

FastAscynWorldEdit "Use Inventory" option does not work as intended

Open
#2,534 6 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Backburner Bug Low Priority
Dominant language
Java
Stars
806
Forks
394
Avg merge
22h 19m
Merged PRs (30d)
14

Description

Server Implementation

Paper

Server Version

1.20.2

Describe the bug

When enabling the use-inventory option in worldedit-config.yml, players can still use infinite blocks and items after having the permission fawe.permpack.basic.

To Reproduce
  1. Enable use-inventory
  2. Grant player fawe permissions
  3. Player can use infinite blocks and items, not taking account their own inventory
Expected behaviour
  1. Enable use-inventory
  2. Players can only use WorldEdit using blocks and items from their own inventory
Screenshots / Videos

No response

Error log (if applicable)

No response

Fawe Debugpaste

https://athion.net/ISPaster/paste/view/f965c21b626e464ab9f83af7c5c489e2

Fawe Version

2.8.5-SNAPSHOT-639;a4a1126

Checklist
Anything else?

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue on Paper 1.20.2 with use-inventory enabled and fawe.permpack.basic granted, then trace the handling of those settings and permissions. Done means WorldEdit operations consume only blocks and items from the player's inventory instead of remaining infinite.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
game-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.