Instalar Steam
iniciar sesión
|
idioma
简体中文 (Chino simplificado)
繁體中文 (Chino tradicional)
日本語 (Japonés)
한국어 (Coreano)
ไทย (Tailandés)
български (Búlgaro)
Čeština (Checo)
Dansk (Danés)
Deutsch (Alemán)
English (Inglés)
Español - España
Ελληνικά (Griego)
Français (Francés)
Italiano
Bahasa Indonesia (indonesio)
Magyar (Húngaro)
Nederlands (Holandés)
Norsk (Noruego)
Polski (Polaco)
Português (Portugués de Portugal)
Português - Brasil (Portugués - Brasil)
Română (Rumano)
Русский (Ruso)
Suomi (Finés)
Svenska (Sueco)
Türkçe (Turco)
Tiếng Việt (Vietnamita)
Українська (Ucraniano)
Informar de un error de traducción
For example we use aryx thrusters on our server, they are all designated as cruise drives and vanilla thrusters are for normal speeds. I can imagine multitude of different configurations just with those.
Instead of the current method where you need to load the mod into a world, exit the world, then edit the config file, and then reload the world again.
Commands would work somewhat too because you don't need to reload the world multiple times, but it's not the best possible method in my eyes because you need to config every world manually.
I could create some more extensive defaults, but that would still leave players with he need to alter the config if it doesn't suit them.
Which is why I was toying with the idea for commands. You would be able to reset the list of cruise thrusters with the command. And then add thrusters by "placing them in the world" and running /cruiseadd on them. Having a command which would list all cruise thrusters in the list would be useful too.
Therefore when you create your modpack and your world, you would just spawn in thruster blocks which you want to have defined as cruise thrusters, run /cruiseadd command on that grid on which you placed the thrusters and it would add all thruster types on that grid into the config list.
Would that better suit your needs?