![]() ![]() It's a superior method for override content, period. Unlike the old days where you would dump thousands of files into a bottomless pit from whence troubleshooting became difficult, the Workshop allows silo'd subfolders (one override folder per subscribed item). I'd be supportive of the Vault removing demonstrably unreasonable votes to solve that problem but that's a conversation for that forum.Īs for Steam: Steam makes overrides extraordinarily easy because you can have multiple override folders that you can turn on/off with the click of a button if your internet is fast enough. I can understand the fear of "If an end user downloads a tileset mod that breaks my cutscene camera he could downvote my module." but given the nature of overrides I think it's a non-issue. Similarly, the consequences of that are my problem, not yours. ![]() This is different from builders using override, which is frowned upon because it interferes with the client's experience in other modules, other builder's work, etc and a hak is a better solution.Īs an occasional override user (and avid patch hak user), if you disabled overrides on your module the first thing I would do would be to open it up in the toolset and uncheck that box. ![]() Given that you have to actively choose to have overrides, it seems that the onus of compatibility is on the end user, not the builder. Overrides are, by definition, a client side choice to subjectively improve on the graphics/UI/sounds/etc of the game.
0 Comments
Leave a Reply. |