Closed Infernio closed 3 months ago
We'd lose all our endorsements, downloads and views and would have to start over.
You could at least partially negate this Con by, instead of just deleting the current pages once the new Modding Tools one is created, archiving all downloads on the current pages, then edit the descriptions to say that they will no longer be updated while linking to the new page.
That does sound like a good idea :+1:
Edit: thinking on this some more, doing that might confuse search engines (i.e. Google). I don't really want them showing the most "popular" pages (i.e. Skyrim SE/Skyrim/Oblivion) when you search wrye bash
, but rather directly link to the most current page.
The LOOT team (full disclosure: I'm a part of said team) are also thinking about doing this (though in their case, it'd be moving from SkyrimSE to Modding Tools rather than consolidating). The discoverability problem is kind of a chicken and egg situation: more projects moving there would vastly help in the discoverability by boosting the category's ranking on the Nexus front page, but most projects are probably either content where they are or are concerned precisely about things like discoverability.
If the section becomes more popular, it could actually end up helping discoverability of tools, since we'd no longer have to compete with incredibly popular mods for search ranking etc.
Another thing that would really help with this issue would be an update check on boot - that way we could do one more multi-page release, then consolidate to a single page for the release afterwards. Users would then see the update notification, along with a link to github/the new Nexus page. IIRC WB used to have an update check, but it was removed?
Edit: #57, it was an auto-updater, actually. I don't think a full updater is a good idea anyways, plus implementing an update check should be much simpler now (probably a github repo hosting JSON (cuz stdlib) info on the latest version, then ping that on boot - obviously include an option to turn that off).
Edit 2: new issue: #663
One potential problem with moving the Wrye Bash mod page to the Tools section would be that mod authors wouldn't be able to add Wrye Bash as a requirement for their mods (Nexus Mods only lets you add requirements from the same sub-site you are using):
There's nothing much we can do about that. We've requested Nexus add some kind of functionality to make cross-game tools appear on Nexus pages for games they support, but I don't know when (if ever) that will be implemented.
The current situation, with like 10 Nexus pages, simply isn't sustainable. Uploading a new version takes ages, plus all the antivirus detection hoops we have to jump through each time.
@Sabre142, could you not add it as an "off-site" requirement at least?
I authorize you folks(Members of the Wrye Bash Organization) to upload my demo from TESNexus to the Organizations repository for further study and ado. (Original code and allow you to modify how it has progressed thru the years according to LoJacks wild idea of a script). (Or whatever monkeys are involved)
Made a page for WB in the Modding Tools section: https://www.nexusmods.com/site/mods/591
We should probably add some newer images to this one, the only ones we have on the various pages are from 307 (or even older, like 307 beta days). I can't exactly do that since I'm on Linux now :P
This is done. Only thing left to do is monitor the old pages to see if we should delete the old files there or not.
I talked with the Nexus moderators/staff and I think we should maybe consolidate the Nexus pages into a single one in the 'Modding Tools' section (https://www.nexusmods.com/site). Opening this to group discussion and pinging @wrye-bash/bashers.
Pros
Cons
There are probably other pros and cons I'm forgetting.
Nexus Responses