-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added VehicleModel definitions. #19
base: master
Are you sure you want to change the base?
Conversation
OK, I'll replicate my comments from discord here just for completeness:
|
I don't think vehicle models should be ignored. It should also be defined in the same way like weapons to achieve cleaner, more transparent code. It’s a pain to update game modes (and libraries) - but as you said it can be disabled so it’s optional.
Can you be more specific what I did wrong?
I’ve removed it.
I think it’s fixed now.
The model definitions are based on the vehicle original entries from the .gxt files. |
this pr is a horrible addition... it will make a lot of issues with original syntax (tag mismatch)... |
Do you know what is horrible? Search for 'samp vehicle models' then find a |
i am complaining about that change for modelid parameters' tag |
I would leave the list of vehicles, but I think As for the list of vehicles and the ability to use a certain constant name instead of a model, which already has a certain meaning, I consider it a good practice. But it shouldn’t be mandatory, otherwise it will simply become useless if you have to “rigidly” adapt the code to it. |
What we can do for now is use: #define VEHICLE_MODEL: _: Instead of the define as-is. This way we get the advantages of named constants and natives marked as requiring model IDs, but without actually having the tags yet. And further down the line switching this out becomes almost trivial. The PR does still need the |
+1(kinda bump ig) |
No description provided.