my Melonloader console say this [23:17:42.721] [UpdatesChecker] [Incompatible] Auto Sow Mod - No NexusModID [23:17:42.721] [UpdatesChecker] [Incompatible] BackpackMod - No NexusModID [23:17:42.721] [UpdatesChecker] [Incompatible] Better Stacks - No NexusModID [23:17:42.721] [UpdatesChecker] [Incompatible] ClipboardPlus - No NexusModID [23:17:42.722] [UpdatesChecker] [Incompatible] Dealer Tracker - No NexusModID [23:17:42.722] [UpdatesChecker] [Incompatible] Employee Manager - No NexusModID [23:17:42.723] [UpdatesChecker] [Incompatible] Auto Clear Completed Deals - No NexusModID [23:17:42.723] [UpdatesChecker] [Incompatible] Mod Settings Manager - No NexusModID [23:17:42.723] [UpdatesChecker] [Incompatible] MultiplayerTrackerFix - No NexusModID [23:17:42.724] [UpdatesChecker] [Incompatible] NotepadApplication_IL2CPP - No NexusModID [23:17:42.724] [UpdatesChecker] [Incompatible] Order Overlay - No NexusModID [23:17:42.724] [UpdatesChecker] [Incompatible] POI Compass Markers - No NexusModID [23:17:42.724] [UpdatesChecker] [Incompatible] RevealCounterChance - No NexusModID [23:17:42.725] [UpdatesChecker] [Incompatible] Splitter - No NexusModID [23:17:42.725] [UpdatesChecker] [Incompatible] TrashGrabber PLUS - No NexusModID
I can already see a few issues with your mod that you might haven't considered. - You shared your API Key, which people could abuse. - There's a rate limit of 2.5k requests per day, after that it's 100 per hour
Basically the more people will use the mod, the less it will work, unless they have to enter their own API Key which not many people will do. (one player will send more than one request, for example restart, multiple mods and more)
I would suggest that you revoke your API key if it's possible and find another solution, otherwise nice idea! 🙂
Don't worry, I know the problem, it's just that for now I'm doing it like that, but later I plan to create my own API with my own site that will use the Nuxus API to avoid all this problem.
To inform you I am already working on an update which will use my own API which will use the Nexus Mods API to avoid the request limit problem I want to use a database to store the information of all the Nexus Mods mods of the game schedule I while avoiding the rate limit problem
Id have to agree with NikkuMiru. It's important to recognize that the underlying problem isn't just about the current setup—it’s about how this solution will scale long-term.
Using a custom API that still relies on Nexus’s infrastructure to pull data means you’re still bound by their rate limits. If the mod gets popular, the system will quickly hit those caps, whether you're hosting the API or not. The real issue is the volume of requests—checking every 5 minutes for hundreds of mods per user is unsustainable.
That’s 1,200 per hour, and over 28,800 requests per day.
Additionally, each user is now using their own network to send these requests, resulting in unnecessary checks and increased load on individual users' networks—even if those requests aren't needed.
You’re essentially building a layer on top of an existing service with its own limitations. Even with caching, if this becomes popular, it could put unnecessary strain on Nexus and negatively affect all users of the mod.
To avoid this, a more sustainable approach would be to reduce the request frequency (once per launch or at least staggered).
I plan to make a truck in the UpdateChecker file to make sure that everyone can use their own API to avoid this problem, otherwise I have no other solutions
But this still isn't a viable solution for the majority of users. The fact is, most players won’t want to or know how to set up their own API keys, so that option will likely be ignored. Even if users did provide their own keys, at the rate of 2,500 requests per day, that still wouldn't be enough to cover even a small portion of the required checks. With the frequency of checks every 5 minutes, you'd quickly run into rate limits, regardless of who owns the API key. The real problem is the volume of requests, and this approach doesn't address the underlying scalability issue.
Additionally, mods aren't updated that frequently, so checking every 5 minutes is excessive. Users don't need to know about updates more than once a day, or even once per launch. A more reasonable approach would be to reduce the frequency of checks, either to once per game session or at least staggered over a longer period. This would help reduce the load on both the mod and the Nexus API, making it a more sustainable solution in the long term.
19 comments
once per startup is more than enough.
[23:17:42.721] [UpdatesChecker] [Incompatible] Auto Sow Mod - No NexusModID
[23:17:42.721] [UpdatesChecker] [Incompatible] BackpackMod - No NexusModID
[23:17:42.721] [UpdatesChecker] [Incompatible] Better Stacks - No NexusModID
[23:17:42.721] [UpdatesChecker] [Incompatible] ClipboardPlus - No NexusModID
[23:17:42.722] [UpdatesChecker] [Incompatible] Dealer Tracker - No NexusModID
[23:17:42.722] [UpdatesChecker] [Incompatible] Employee Manager - No NexusModID
[23:17:42.723] [UpdatesChecker] [Incompatible] Auto Clear Completed Deals - No NexusModID
[23:17:42.723] [UpdatesChecker] [Incompatible] Mod Settings Manager - No NexusModID
[23:17:42.723] [UpdatesChecker] [Incompatible] MultiplayerTrackerFix - No NexusModID
[23:17:42.724] [UpdatesChecker] [Incompatible] NotepadApplication_IL2CPP - No NexusModID
[23:17:42.724] [UpdatesChecker] [Incompatible] Order Overlay - No NexusModID
[23:17:42.724] [UpdatesChecker] [Incompatible] POI Compass Markers - No NexusModID
[23:17:42.724] [UpdatesChecker] [Incompatible] RevealCounterChance - No NexusModID
[23:17:42.725] [UpdatesChecker] [Incompatible] Splitter - No NexusModID
[23:17:42.725] [UpdatesChecker] [Incompatible] TrashGrabber PLUS - No NexusModID
but all my mods are from Nexusmods. so dont know
- You shared your API Key, which people could abuse.
- There's a rate limit of 2.5k requests per day, after that it's 100 per hour
Basically the more people will use the mod, the less it will work, unless they have to enter their own API Key which not many people will do. (one player will send more than one request, for example restart, multiple mods and more)
I would suggest that you revoke your API key if it's possible and find another solution, otherwise nice idea! 🙂
Using a custom API that still relies on Nexus’s infrastructure to pull data means you’re still bound by their rate limits. If the mod gets popular, the system will quickly hit those caps, whether you're hosting the API or not. The real issue is the volume of requests—checking every 5 minutes for hundreds of mods per user is unsustainable.
So if even 10 people are using update checker:
Additionally, each user is now using their own network to send these requests, resulting in unnecessary checks and increased load on individual users' networks—even if those requests aren't needed.
You’re essentially building a layer on top of an existing service with its own limitations. Even with caching, if this becomes popular, it could put unnecessary strain on Nexus and negatively affect all users of the mod.
To avoid this, a more sustainable approach would be to reduce the request frequency (once per launch or at least staggered).
Additionally, mods aren't updated that frequently, so checking every 5 minutes is excessive. Users don't need to know about updates more than once a day, or even once per launch. A more reasonable approach would be to reduce the frequency of checks, either to once per game session or at least staggered over a longer period. This would help reduce the load on both the mod and the Nexus API, making it a more sustainable solution in the long term.