You're forgetting the most important bit: just an existing colourable version of the object in question. Virtually every RCT object also has colourable versions. Advising people to make their own objects every time they want a colourable version is just waiting for tons of duplicate objects, which can create objects down the line. You can't tell people about making objects without telling them about proper naming and the risk of duplicate objects.
Thank you for your comment, these are some great points I completely forgot about! It only makes sense to make an object recolorable yourself if it isn't already available or if you need a specific color pattern. In this case, you should definitely give the object file a different name to avoid any conflicts.
You're forgetting the most important bit: just an existing colourable version of the object in question. Virtually every RCT object also has colourable versions. Advising people to make their own objects every time they want a colourable version is just waiting for tons of duplicate objects, which can create objects down the line. You can't tell people about making objects without telling them about proper naming and the risk of duplicate objects.
Thank you for your comment, these are some great points I completely forgot about! It only makes sense to make an object recolorable yourself if it isn't already available or if you need a specific color pattern. In this case, you should definitely give the object file a different name to avoid any conflicts.