Main Configuration
mods/BusyBee_AutoPickup/config.yml holds two blocks: database (where player toggles are
saved) and autopickup (everything about how pickup behaves). Player-facing text lives in
messages.yml instead; see Message Customization.
Default file
database:
type: "sqlite"
host: "localhost"
port: 3306
name: "autopickup"
user: "root"
password: ""
pool-size: 10
autopickup:
enabled: true
default-enabled: true
entry-expiry-ms: 5000
pickup-radius: 5
tree-detection-enabled: true
tree-pickup-radius: 15
tree-blocks:
- "Log"
- "Leaf"
# ... full list in Tree Detection
disable-in-creative: true
pickup-delay-ticks: 0
notification-type: "NOTIFICATION"
toggle-notification-type: "TITLE"
whitelist-enabled: false
blacklist-enabled: false
whitelist:
- "Ore_Copper_Shale"
- "Ingredient_Bone_Fragment"
blacklist:
- "Ingredient_Sac_Venom"
- "Ingredient_Fabric_Scrap_Linen"
autopickup keys
| Key | Default | Checked range | What it does |
|---|---|---|---|
enabled |
true |
Master switch. false stops every pickup and blocks /autopickup |
|
default-enabled |
true |
Toggle state for players who never ran /autopickup |
|
entry-expiry-ms |
5000 |
100–30000 | How long a block break or mob death is remembered, in milliseconds |
pickup-radius |
5 |
1–20 | How far (blocks) an item can spawn from the break or death |
tree-detection-enabled |
true |
Use the wider radius for tree blocks. See Tree Detection | |
tree-pickup-radius |
15 |
1–50 | Radius (blocks) for drops from tree blocks |
tree-blocks |
see Tree Detection | Block ID fragments that count as tree blocks | |
disable-in-creative |
true |
Skip players in creative mode | |
pickup-delay-ticks |
0 |
0–100 | Wait before checking a new item (20 ticks = 1 second) |
notification-type |
NOTIFICATION |
TITLE, NOTIFICATION, CHAT, NONE |
How each pickup is announced. See Notifications |
toggle-notification-type |
TITLE |
TITLE, NOTIFICATION, CHAT, NONE |
How /autopickup confirms the toggle |
whitelist-enabled |
false |
Only pick up drops matching whitelist. See Item Filters |
|
blacklist-enabled |
false |
Pick up everything except drops matching blacklist |
|
whitelist |
two examples | ID fragments for whitelist mode | |
blacklist |
two examples | ID fragments for blacklist mode |
database keys
| Key | Default | Checked range | What it does |
|---|---|---|---|
type |
sqlite |
sqlite, mysql, mariadb |
Storage backend |
host |
localhost |
MySQL/MariaDB host | |
port |
3306 |
1–65535 | MySQL/MariaDB port |
name |
autopickup |
Database name | |
user |
root |
Database user | |
password |
"" |
Database password | |
pool-size |
10 |
1–100 | Maximum pooled connections |
See Database Setup for details.
Startup check
Every time the plugin starts or reloads, it checks config.yml and logs what it finds:
- A number outside its checked range logs a warning. The value is still used as written.
- A number key that is missing or not a number is replaced with the default from the tables above.
- An unknown notification or database type logs a warning listing the valid values.
- Whitelist and blacklist both on: the blacklist is switched off.
tree-blocksgetsWillow,CherryandRedwoodadded if they're missing.
If the check changes anything at startup, config.yml is saved again. That save drops the
comments from the file; your values are kept. On a reload the check runs too, but nothing is
saved, and its fixes only take effect after the next reload or restart.
If you delete default-enabled entirely, it counts as false, not true.
Reload or restart?
/autopickup reload re-reads config.yml and messages.yml. Most changes apply straight away.
These need a full restart:
- everything under
database, because the connection pool is opened once at startup; entry-expiry-ms, because the break cache is built once at startup.