I added a AutoConnector that scans your chests in range of the hopper
U have to add this in your config-files or remove the files and restart your server.
config.yml
auto_connect:
slot: 51
material: OBSERVER
name: §fAutoanlage
lore:
- §7Scannt alle Kisten in der Umgebung
- §7und erstellt automatisch Verbindungen.
- ''
- §eItems in mehreren Kisten werden übersprungen.
- §eVorhandene Verbindungen bleiben erhalten.
messages.yml
auto-scan-done: '§aAutoanlage: %count% Verbindung(en) erstellt.'
auto-scan-none: '§eAutoanlage: Keine Container in Reichweite gefunden.'
auto-scan-no-new: '§eAutoanlage: Keine neuen eindeutigen Verbindungen gefunden.'
you have to add die line in message.yml
self-connection: '§cEin Trichter kann sich nicht mit sich selbst verbinden.'
Or delete the message.yml and restart your Server!
It is now possible to choose between a physical connection and a single connection.
The processing order is as follows: first the multi-connection, and then either the single connection or the physical connection.
This update replaces the YAML-based save system (saves.yml) with a SQLite database backend (saves.db). All hopper data — including pickup radius, transport amount, single connections and multi-connections — is now stored in a structured, performant SQLite database. Existing data can be migrated in one command via /trichter import.