-
Notifications
You must be signed in to change notification settings - Fork 167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
storage_server doesn't have any SearchForRecords limit #547
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you. |
This should not be marked as stale - this is a bug that could overload StorageServer, which is why I reported it in the first place. |
Really, this thing has been abandoned, because none of the old devs really have the time and/or motivation to do anything on it, sad as it is to say. You're right that this is an actual issue, but unless some new dev comes along and revitalizes this... I can't see this getting fixed. Sorry. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you. |
When I was trying to dump some of the records for Daigasso! Band Brothers DX, I accidentally set my request limit way too high, and I think I crashed the production server (sorry!) - the known limit for both the Japanese and European variant of the game is 105, so maybe a max limit of ~110 (just in case) records per
SearchForRecords
request.The text was updated successfully, but these errors were encountered: