wielders trigger protection violations on the actual player
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 20
- Forks
- 31
- Avg merge
- 1m
- Merged PRs (30d)
- 9
Description
Situation is sometimes like this:
Player A needs a machine and adds B to his area, so B can build it for him. Later the area from B is removed again.
Once the machine is activated, B will be spammed with protection violation messages (and more, depending on the modset)
This was once fixed in https://github.com/mt-mods/pipeworks/pull/42, but got lost during https://github.com/mt-mods/pipeworks/pull/126
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare the current protection-related code with the changes in pull request #42, then review pull request #126 to identify where that fix was lost. Reproduce the area-removal and machine-activation scenario described here; done means the affected player no longer receives repeated protection violation messages after the area is removed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100