You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"Bug": Any custom trail added has blending off globally, regardless of level settings (vanilla trails are unaffected)
Suggestion: There could possibly be a way to config every custom trail to edit 2 attributes:
Allow Tint (if off: trails can't be tinted by player colors, if on: they're tinted by P2 color like most of vanilla trails. off by default)
Allow Blending (self explanatory, on by default)
Maybe this could be configurable via a .json file or something associated to each trail (created for each trail on load if it doesn't exist), and maybe add 2 checkboxes to the trail pop-up that allow for easy modification of these 2 attributes in-game. Although in this case these attributes would most likely be only modified by pack makers that surely know how to edit a file (lol)
The text was updated successfully, but these errors were encountered:
blend on doesn't enable blending, but keeps the functionality of a normal trail. however turning blend off makes it behave like an abnormally-long trail for some reason
(could be a sick 3rd attribute though ngl to make long-ass trails like trail 5 & 6 in vanilla)
tint functions normally without issues though, blend's just a little odd
"Bug": Any custom trail added has blending off globally, regardless of level settings (vanilla trails are unaffected)
Suggestion: There could possibly be a way to config every custom trail to edit 2 attributes:
Maybe this could be configurable via a .json file or something associated to each trail (created for each trail on load if it doesn't exist), and maybe add 2 checkboxes to the trail pop-up that allow for easy modification of these 2 attributes in-game. Although in this case these attributes would most likely be only modified by pack makers that surely know how to edit a file (lol)
The text was updated successfully, but these errors were encountered: