Installation and first start

What the server needs, what the plugin creates on its first start, and how to check that it works.

Installation

  1. Copy EndlessVehicles into the plugins/ folder (and, if you use them, Vault with an economy plugin and WorldGuard).
  2. Start the server once: the plugin creates the plugins/EndlessVehicles/ folder with only the license-key.yml file, then stops.
  3. Write the key in license-key.yml and restart. Until the license is verified the plugin creates no other file and does nothing.
  4. On restart the plugin creates database.yml and connects to MySQL: set host, user and password, and restart again if the connection fails. Only once connected does it create tables, config.yml and every other file.

Files created on the first start

File or folderContent
config.ymlGeneral 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.ymlAll chat messages.
blocked-blocks.ymlBlocks vehicles cannot climb.
company-garages.ymlTitle and icon of company garages.
vehicles-registry.ymlCategory of models that do not state one.
gas-stations.ymlFuel pumps created with /fuelsetup.
vehicle-storages.ymlStorage areas created with /vehicle-storage.

Quick check

  1. With ev.admin run /veicolo models: it should list the loaded models.
  2. Run /veicolo spawn sample_car, get on (right click) and drive with W, A, S, D.
  3. 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.