The Curator's Companion - anyone know what happened?
Hey all, The Curator's Companion is hidden and all it says is
Can't be bothered anymore
Anyone know what's up with that? ;)
Posted Apr 2, 2021, 5:29 PM UTC
4816
Author said in Lexy’s discord that he found a massive bug, so he’s hiding it until it’s fixed.
28
Hopefully an April Fool's joke that's lasting a bit too long and started a bit too early?
EDIT: Actually, I think he may have just integrated everything into the Completionist - Quest Tracker mod. Quests are covered in Completionist, while LOTD itself has an MCM menu for tracking museum progression.
EDIT2: ...except the moreHUD integration, which is the best part of the mod. Looks like that's gone.
27
except the moreHUD integration
That is literally the only reason I had the mod. I don't particularly want anything else.
23
Same :(
3
Maybe we'll get lucky and the author will add the moreHUD integration into Completionist. Then I could see why hiding Curator's Companion makes sense.
3
[deleted]
3
It's back up now
8
The Curators Companion is one of the reasons I bothered to use LOTD. Without the MoreHud integration, both mods are far less attractive.
6
Thank god I download it . Great mod.
5
wow I downloaded that shit just in the nick of time
5
[deleted]
3
I will never understand why mod authors do this. Just give it to the Caretaker if you can't keep up with it.
[deleted]
In this case, the mod author became aware of a potentially game breaking bug in the latest couple of versions of the mod, and felt that it was severe enough to warrant the blocking of downloads of the mod whilst they made emergency amendments.
Edit: Changed "Sunday" to "whilst" - stupid phone
If that's the case, I can understand doing that. I do find it strange however that they didn't just say as much rather than saying "Can't be bothered anymore."
Yeah, the actual comment on the Nexus page was a bit perplexing!
Any idea which versions were affected? My setup of mods is all from late last year.
I think you should be fine then, as these were quite recent versions from what I understand - the author mentioned versions 5.1.0 and 5.1.1 were affected.
Brilliant, thanks!