You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONFIG.md
+68-1Lines changed: 68 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -336,7 +336,7 @@ feature:
336
336
337
337
**Kit Loading Features:**
338
338
- **rekit-on-respawn**: Automatically loads the player's last used kit when they respawn after death
339
-
- **rekit-on-kill**: Automatically loads the player's last used kit when they kill another player
339
+
- **rekit-on-kill**: Automatically loads the killer's last used kit when they kill another player. See [Rekit on Kill Configuration](#rekit-on-kill-configuration) for advanced options
340
340
- **broadcast-kit-messages**: Controls whether broadcast messages are sent when players load kits or enderchesets (e.g., "Player loaded a kit"). When set to `false`, these specific kit-loading broadcast messages are suppressed
341
341
342
342
**Action Broadcast Features:**
@@ -351,3 +351,70 @@ feature:
351
351
- **feed-on-enderchest-load**: Sets player hunger to full when loading an enderchest
352
352
- **set-saturation-on-enderchest-load**: Sets player saturation to full when loading an enderchest
353
353
- **remove-potion-effects-on-enderchest-load**: Removes all potion effects when loading an enderchest
354
+
355
+
---
356
+
357
+
### **Rekit on Kill Configuration**
358
+
359
+
The `rekit-on-kill` feature automatically loads the killer's last used kit when they kill another player. This feature supports world-based filtering to control where it activates, based on the killer's current world.
360
+
361
+
```yaml
362
+
feature:
363
+
rekit-on-kill:
364
+
enabled: false
365
+
# World filtering based on killer's current world
366
+
# If world-whitelist is not empty, rekit-on-kill only works in those worlds
367
+
# If world-whitelist is empty and world-blacklist is not empty, rekit-on-kill works everywhere except those worlds
368
+
# If both are empty, rekit-on-kill works in all worlds
369
+
world-whitelist: []
370
+
world-blacklist: []
371
+
```
372
+
373
+
#### Configuration Options:
374
+
375
+
- **enabled**: Set to `true` to enable the rekit-on-kill feature
376
+
- **world-whitelist**: List of world names where rekit-on-kill is allowed. If this list is not empty, the feature only works in these worlds
377
+
- **world-blacklist**: List of world names where rekit-on-kill is disabled. Only used if `world-whitelist` is empty
378
+
379
+
#### World Filtering Logic:
380
+
381
+
1. If `world-whitelist` contains worlds → only allow rekit-on-kill in those worlds
382
+
2. If `world-whitelist` is empty but `world-blacklist` contains worlds → allow rekit-on-kill everywhere except those worlds
383
+
3. If both lists are empty → allow rekit-on-kill in all worlds
384
+
385
+
#### Example Configurations:
386
+
387
+
**Enable globally (all worlds):**
388
+
```yaml
389
+
feature:
390
+
rekit-on-kill:
391
+
enabled: true
392
+
world-whitelist: []
393
+
world-blacklist: []
394
+
```
395
+
396
+
**Only enable in specific arena worlds:**
397
+
```yaml
398
+
feature:
399
+
rekit-on-kill:
400
+
enabled: true
401
+
world-whitelist:
402
+
- "pvp_arena"
403
+
- "duel_world"
404
+
world-blacklist: []
405
+
```
406
+
407
+
**Enable everywhere except spawn/lobby:**
408
+
```yaml
409
+
feature:
410
+
rekit-on-kill:
411
+
enabled: true
412
+
world-whitelist: []
413
+
world-blacklist:
414
+
- "spawn"
415
+
- "lobby"
416
+
```
417
+
418
+
#### Backwards Compatibility:
419
+
420
+
Existing configurations using the old boolean format (`rekit-on-kill: false` or `rekit-on-kill: true`) will continue to work. When the plugin updates, it will automatically add the new configuration keys with default values. No manual changes are required.
0 commit comments