0 of 0
File information
Created by
Cross-Project CoordinationUploaded by
CrossProjectCoordinationVirus scan
Safe to use
Notifications
87 comments
https://github.com/TD-Addon/TD_DeprecatedAssets
(Download "Code", the only "release" seems ancient)
Awful thing to happen over such an infraction.
I do hope your Redoran Watchmen are recovering after being sodomised.
Folks, where's the lie?
What I'm doing is also not okay, because we are discussing something unrelated.
WTF?
You are a philosopher to think such thoughts. /agree
if td was just for tr, sure, but it sounds chaotic to develop with td considering you might get shitcanned by random updates deciding x and y misc meshes just aren't up to standards lol. i hope in the future modders consider bundling their own assets instead
Tamriel Data is a great resource for assets. It provides consistency. I do not advocate an every modder asset mess we saw in the early days of Morrowind modding.
I would suggest that the Project Tamriel teams take the approach that the OAAB Team took with the last v2.x.x release to mitigate this issue.
And daresay go one step further by "hiving off" deprecated assets to an option within the release that would give authors of other mods breathing space to update their mods in due course. This would go some way to reducing, if not eliminating, a recurrence of this issue.
This assumption assumes that there is going to be a lot of activity to begin with from said modders. If it's an actively maintained mod, that makes sense, but we're at a point where we might be months or years between a release of a dependent mod, or the the mod author is not actively modding/playing Morrowind.
I think a better mechanism works if we use semantic versioning for community asset libraries; major.minor.hotfix; Hotfix versions are just repairs, minor versions consist of additions that are backwards compatible, and major versions whenever there's a breaking change (removed assets, versus deprecated assets). That way, authors can "deprecate" assets in a minor version, informing others that the asset is no longer in use and is planned to be removed in the future, and actually remove those assets in the next major version.
How's about only changing an asset/reference when it is actually replaced - not before?
then this happened.
And here's my duct tape and bailing wire solution:
I used this old one (renamed) in conjunction with the new one one git hub - appears to work - merge patch glops it all together.
But I am following Openmw total overhaul list. I am a bit confused on what to install in your linked file. All of it? but in what order then? if not what do I use? :D Any advice I would be gratefull for.
It's a trainwreck - and I don't understand why every time Tamriel Data is updated the file reference/names have to change at the expense of staying compatible.
I still am having this issue: