-
Notifications
You must be signed in to change notification settings - Fork 3
question: how to make all vehicles non editable as default? #95
Comments
Hello 👋. There isn't a way to make all vehicles uneditable by default currently. This is probably the job for an addon that specifically manages the editable states of vehicles, though. |
thank you for the quick reply :-) |
I am not aware of a currently existing one. I may be able to look into adding it to Carsa's Comands 🙂 |
that would be awesome! looking forward to it :-) P.S. i looked into script.lua, maybe change something by 'onVehicleSpawn' so the seteditable gets automatically called? (would be a very simple thing i think, can be wrong) |
Any advancements on this? (Don't want to be annoying or such) |
It is the meme "C'mon do something" Hope that helped. |
it indeed helped my braincells to understand. |
from your previous comments i thought that this is a feature request. And because i did not see a pull request i thought we should implement it by ourselves. I don't know what you did in that commit, but that is cursed 😄 can you provide a normal script.lua with your changes inside? |
done. i did some bugfixes and got errors. now after 1 hour and 30 minutes of coding and bugfixing, i've done it correctly (some bugs were ":" instead of "."; unnessesary symbols; wrong calling (because "editable or true" resulted as always being true, even if there was a false; and some other)...) i got it done now correctly and got it working fine. just tell me if there is more to do |
i said, fix the markdown etc and provide a normal script.lua |
Please tell me, on what line is the markdown? |
markdown is actually gone, Remaining issues:
Note: some problems listed above would have been acceptable because you are an external dev and i would have fixed your code by myself and merge it. But most of above just shows bad coding, coding without proper tooling (IDE) and testing (not just one single use case). Above is not meant offensive and i know you are new to coding, but i do not have the time to do a teaching class and fix all of the code. I hope that the list give you at least a little bit to work on. I am not the guy who just says "nope, and now get outta here". Don't let this answer stop you from offering pull requests to public projects, this or others, in the future. Sincerly, Pony |
Basically, yes, the code was all over the place. There is already a method for adding “preferences” that allows users to easily toggle a whether vehicles should be editable or not by default, for example. That being said, I can appreciate the effort. I have been busy the last while, and Stormworks is very far down on my list of priorities-but I'll try to get to this soon. |
where can i set the default state of a vehicle so it cant be edited when spawned (only despawned or removed by cleanup)? for example like on some servers, if there is already a vehicle in zone, you can only create one, but not edit the existing one(s) in the zone.
The text was updated successfully, but these errors were encountered: