mirror of
https://github.com/YouHaveTrouble/minecraft-exploits-and-how-to-fix-them.git
synced 2026-05-11 22:16:58 +00:00
@@ -28,6 +28,30 @@ entities:
|
||||
tick: false
|
||||
```
|
||||
|
||||
### Book exploits
|
||||
|
||||
Books are a common target for exploitation techniques, and have been used for all sorts of nasty things in the past including duplication exploits, crash exploits, and forcing servers to run out of memory while producing massive amounts of chunk data.
|
||||
|
||||
#### Option 1
|
||||
|
||||
Moderately reducing page-max can mitigate most book exploits without affecting vanilla clients.
|
||||
|
||||
`paper-global.yml`
|
||||
```yaml
|
||||
item-validation:
|
||||
book-size:
|
||||
page-max: 1024
|
||||
```
|
||||
|
||||
#### Option 2
|
||||
|
||||
Disabling books completely prevents the most book exploits (as long as plugins don't create non-standard books). Pufferfish config option prevents players from writing to the book, therefore ruling out anything that requires player input to work.
|
||||
|
||||
`pufferfish.yml`
|
||||
```yaml
|
||||
enable-books: false
|
||||
```
|
||||
|
||||
### Collision lag machines
|
||||
|
||||
This exploit is similar to the armor stand one, but instead of armor stands, it uses entities that can be pushed by
|
||||
|
||||
Reference in New Issue
Block a user