Response Codes
Quick lookup of response codes you might have seen while using EchoBase.
This is the generic info response, with a specific message containing some information.
This error is returned when EchoBase has encountered an error with the data API that provides data from the game.
This is the most generic response code, representing an unexpected error. The default message is "Internal Error" but might include a little more information, depending on what was available at the time of the error.
This is the generic success response, with a specific message about what succeeded.
Member statuses are required.
When updating member statuses, this error can occur if no statuses are sent to the server.
Guild ID is required.
EchoBase relies on an internal Guild ID to know which guild is logged in. If you see this error, make sure cookies are enabled in your browser, and log out and log back in.
Ally Code is required.
Your ally code is needed to log in with, and is needed to specify who certain bot commands are to be run as.
Unknown donation preference '<invalid-preference>', expected one of: '<valid-preferences>'
Please use one of the valid preferences in your command.
Member does not own <unit>.
Donation preferences cannot be set for a unit if the specified member doesn't have that unit in his/her collection.
All 10 territories must be given a priority ranking.
All territories have a priority ranking by default, so please let me know if you get this error, as it shouldn't be possible without some hacking.
You have already reached the maximum number of allowed Grouping Rules.
This error indicates that you have tried to add a new grouping rule, even though you have already reached the maximum.
Ally code <allyCode> must be in a guild to use this command.
This error will happen if certain commands are sent to EchoStation with an ally code that belongs to a player that is not part of a guild.
A priority of '1' must be given to at least one territory.
This would be shown if you change all of the priorities in the TW Defense Assigner to be something other than '1'. As long as you specify at least one territory to have a priority of '1', you shouldn't get this error anymore.
Webhook Name is required.
Provide whatever name you would like - something by which you can identify your webhook URL.
Not allowed to DM member(s): <list-of-members>
This alerts which members were unable to receive Direct Messages due to their Discord settings.
Discord role is not valid for this guild.
This error means that the selected Discord role for notifications has been removed from the guild, or the role is invalid in some unknown way. Refresh your browser and try again. If that does not work, please describe your issue in the support server.
Please select a Discord Channel to post assignments to.
User(s) not in this server: <list-of-members>
This is a validation error that indicates that an EchoStation command cannot be run for anyone who is outside of the Discord server in which the command was executed.
Missing Discord permission: <discord-permission>
If the EchoStation bot was not granted the correct permission to accomplish one of its tasks, this error will specify what is missing. However, it is unknown whether the needed permission is at the Server level or the Channel level.
Guild ID is invalid.
This indicates that the guild ID that lives in your session is not tied to any known guild. Try logging out and logging back in to fix this error.
Player must be part of a guild.
Certain EchoStation commands require that the player must be a part of a guild for them to work.
Invalid webhook ID.
Webhook IDs must be a positive integer.
Discord Server ID is required.
Disconnecting a guild from a Discord server requires that the Discord server's ID be included in the request.
Phase is required.
C'mon man, just give me the phase number.
Your selected Discord Channel is no longer valid. Please choose another.
This might happen if the channel that you have chosen was deleted after the page was loaded.
Unknown guild member found: '<guild-member>' Refresh and try again.
If the guild member has been removed from the guild before including them in your request, you'll need to refresh in order to get a valid list before trying again.
Webhook URL is invalid.
Double check to make sure the entire webhook URL, and nothing else, is included! If you are sure that it is, please let me know and send me your webhook URL so I can get it working for you.
The URL should be formatted like this:
https://discordapp.com/api/webhooks/<discord-channel-id>/<really-long-string>
Your guild must be registered with EchoStation to use this command.
You must be registered with EchoStation to use this command.
Could not match member(s) to Discord: <list-of-members>
This alerts which members were unable to be matched by EchoBase, causing them to not receive Direct Messages.
Webhook not found.
This might happen if the webhook that you are trying to perform an action on has already been deleted. Refresh your page to see a fresh list of webhooks.
Discord Channel ID is not valid for this guild.
This error means that the selected Discord channel for notifications has been removed from the guild, or the channel is invalid in some unknown way. Refresh your browser and try again. If that does not work, please describe your issue in the support server.
Your Discord request is being processed, but there are <number> requests ahead of yours. Approximate wait: <duration>
EchoBase gets a lot of traffic in the hours leading up to the start of a new phase, especially during those phases that overlap between Hoth and Geonosis TBs. This becomes troublesome because Discord can't keep up with 3-4 channel posts + 50 DMs being sent multiple times per second.
To help ensure that all requests get processed, EchoBase queues them up first. If the queue size is greater than 3, it will display this Response Code.
This Response Code is informing you of a few things:
- 1.Your request is being processed. It is not lost, so there is no need to resubmit (if you do resubmit, you will get this Response Code again, reflecting your updated queue position).
- 2.Your queue position. This tells you how many requests are ahead of yours.
- 3.Approximate wait time. This is a simple calculation of multiplying the average response time of the most recent requests, with the number of requests ahead of yours.
Please wait for guild to finish syncing.
EchoBase will periodically refresh your guild's data in the background. During this time, you will not be allowed to submit for assignments, since the data has not finished being synced.
Could not find matching unit for '<unit-id>': <platoon-coordinates>
This should only happen if you load the platoon assigner, I change or remove the unitId for one of your platoon requirements, and then you submit for assignments. Reloading the page should fix the issue. However, if you are getting this error even after reloading the page, please let me know the details.
Ally Code is invalid.
Double check to make sure the entire ally code, and nothing else, is included! If you are sure that it is, please let me know and send me your ally code so I can get it working for you. Do not include any dashes.
The ally code should be formatted like this:
123456789
You must have the <echo-role> role to issue this command.
Certain EchoStation commands require a higher level of security to run. This is achieved by requiring that the command issuer must have been given the specified role in the Discord server.
Missing requirement: <platoon-coordinates> (<number> more)
This would happen if you were able to submit platoon assignments before filling out all the requirements first. Simply fill out the specified platoon requirements, and re-submit.
Webhook URL is required.
User not registered: <user>
Phase must be a value between 1 and 6.
Trying to send in an invalid phase number will not work!
The API is reporting inconsistent data for this account. Please try again later, or try with someone else's account.
This error indicates that an inconsistency was found in two different API calls concerning what should be the same data. The most common scenario for this is when you have changed guilds or left your guild, and one call reports that you are still in your old guild, but another call reports the true information.
Unfortunately, you will have to wait while the data is synced correctly by the API. All you can do is try again later or try to accomplish your task through someone else.
User(s) not in your guild: <list-of-users>
Certain EchoStation commands require that the users that would be affected by the command must share a guild with you.
This error means that the affected Discord server has been unregistered from your guild, or the server is invalid in some unknown way. Refresh your browser and try again. If that does not work, please describe your issue in the support server.
Webhook Name must be 50 characters or fewer.
Gotta set the limit somewhere.
The uploaded file must be an image.
This message will be returned if you try to send a non-image file.
The uploaded image must be in landscape mode.
The screenshot must be taken in landscape mode for it to be read properly.
The uploaded image must have a height greater than or equal to 640px.
Due to image recognition problems caused by low image resolution, please make sure the screenshots that you upload have at least a height of 640px.
Last modified 2yr ago