Closed ohlidalp closed 5 months ago
I'm fixing the addonpart conflicts - I figured I need to block the user from selecting conflicting addonparts at all, preferably with some visual markers. This is what I have right now - the graphics are not final and there's a huge lag when opening the menu. To be improved.
Markers are finished:
addonpart_filename
directive (optional whitelist)The modder can add any number of addonpart_filename <foo.truck>
directives (case-insensitive). If none are specified, any filename goes.
Matching by GUID is still the primary method, this only helps in cases where the GUID is shared by too many trucks (not uncommon).
Unfortunately adding flares doesn't seem to work for me: MV4_PolicePackage.zip Adding the flares after flexbodies introduces the flexbody errors.
Expected result:
https://github.com/RigsOfRods/rigs-of-rods/assets/46073351/28546f74-ec4a-4fd8-969b-f6280f8411a0
CTRL+2
activates the lightbar and CTRL+3
for the front/rear flashers.
I fixed the discarding incomplete boolean token 'f'
warnings - it was a tokenizer bug.
EDIT: Another fix - I forgot to update the condition around block = keyword;
, causing the parser to interpret all flare lines as whatever was before (flexbodies in this case).
Finally I fixed the case where the flare used material from the addonpart ZIP - same story as with props and flexbodies, I just forgot to handle it the first time.
Added managed materials tweaks:
I fixed the remaining 2 glitches:
Highlights:
addonpart_filename <foo.truck>
to whitelist only some vehicles if GUID is too broad.filename <foo.truck>
to filter the "Saved tuneups" list by vehicle filename, since GUID is too broad and some vehicles don't even have one.Changes made so far:
flare/flare2/addonpart_unwanted_flare
in .addonpart, protected/forceremoved states in .tuneup, including UI. Tweaks were omitted.addonpart_unwanted_exhausts
in .addonpart, protectd/forceremoved states in .tuneup, including UI. Tweaks and defining new exhausts in .addonpart were omitted.GenericDocument
tokenizer - IfOPTION_ALLOW_NAKED_STRINGS
was used, strings starting liketrue/false
, for examplef
ort
alone, would get discarded.Additional discovered issues: