Installation and first start
What the server needs, what the plugin creates on its first start, and how to check that it works.
Installation
- Copy EndlessVehicles into the
plugins/folder (and, if you use them, Vault with an economy plugin and WorldGuard). - Start the server once: the plugin creates the
plugins/EndlessVehicles/folder with only thelicense-key.ymlfile, then stops. - Write the key in
license-key.ymland restart. Until the license is verified the plugin creates no other file and does nothing. - On restart the plugin creates
database.ymland connects to MySQL: set host, user and password, and restart again if the connection fails. Only once connected does it create tables,config.ymland every other file.
Files created on the first start
| File or folder | Content |
|---|---|
config.yml | General settings, see Configuration. |
vehicles/ | One file per vehicle, in a subfolder per type. On the first start it contains one sample vehicle per type (sample_car and the others). |
gui/ | One file per menu, see Configurable menus. |
vehicle-messages/it_IT.yml | All chat messages. |
blocked-blocks.yml | Blocks vehicles cannot climb. |
company-garages.yml | Title and icon of company garages. |
vehicles-registry.yml | Category of models that do not state one. |
gas-stations.yml | Fuel pumps created with /fuelsetup. |
vehicle-storages.yml | Storage areas created with /vehicle-storage. |
Quick check
- With
ev.adminrun/veicolo models: it should list the loaded models. - Run
/veicolo spawn sample_car, get on (right click) and drive with W, A, S, D. - Open the garage with
/garage.
Changes to config.yml
config.yml is only read at startup: /veicolo reload reloads the models, blocked-blocks.yml, the menus and the driving section of config.yml; every other setting needs a restart. After changing config.yml, restart the server.