{"data":{"id":15122,"title":"Disconnection Codes","rsi_url":"https:\/\/robertsspaceindustries.com\/comm-link\/SCW\/15122-API","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-links\/15122","api_public_url":"https:\/\/api.star-citizen.wiki\/comm-links\/15122","channel":"Undefined","category":"Undefined","series":"None","images":[],"images_count":0,"translations":{"en_EN":"We thought we\u2019d share with you more information on our disconnect codes that you can get in Star Citizen, as well as educate players on how they can better use this information to describe code-related errors in Issue Council.\n\nImportant Notes!\n** Important Note #1: Disconnection codes are symptomatic of something going wrong; they are not true diagnostics that you can use to resolve an issue. A good analogy is when someone is coughing\u2026 the cough is bad, but there could be any number of causes behind it. The cough is the disconnect code. :)\n\n** Important Note #2: The steps to obtain each Code can be quite different per situation, which is why including precise Steps To Reproduce in the Issue Council is absolutely vital to our tracking the issue down. An example of this would be two friends each getting a Code 20007\u2026 while the error code is the same, the causes for each could be completely separate and independent of each other.\n\n** Important Note #3: When entering an Issue Council report, make sure that you add the Code error you get plus a brief description in the subject, such as \u201cError Code 20007 When Loading Into Crusader\u201d.\n\nCode 10000:\nCode 10000 happens when the game client isn\u2019t able to find us due to something preventing the game client from being able to find our servers. These will almost always be an issue that is client side.\n\nCode 10001:\nCode 10001 happens when the game client is having issues connecting to the authentication service.\n\nCode 10003:\nCode 10003 occurs when the game client can connect to the authentication service but either has corrupted persistence cache data, or is unable to reach the database to get its persistent data.\n\nCode 20000\/30000:\nCode 20000\/30000 is our general timeout message. You\u2019ll get this message when your connection to the game server times out, but you\u2019re still connection to the backend platform service is still active. In almost all cases, this is due to an actual game server crash or an issue within the game that can disconnect you.\n\nAn internal example of the latter occurred on our QA environment (this never made it to public) when one client would exit the game and all other clients were forcefully disconnected.\n\nCode 20003\/30003:\nCode 20003\/30003 is a version mismatch which occurs when the server checks the version of the game installed and finds that there is an older version of the client. The way to resolve this is to Verify Files or, in very rare situations, fully reinstall the game.\n\nCode 20004\/30004:\nOur matchmaking service contains several different rules to assign clients to servers. This response occurs when the matchmaking service puts someone into a server that is full.\n\nIn most situations, the service should not assign you to a server that is already full, but we\u2019re finding edge cases where this gets returned. We\u2019ll continue to isolate, identify, and fix these as they come up.\n\nCode 20005\/30005:\nCode 20005\/30005 happens when a login attempt fails due to invalid data. Many of these can be fixed by doing launcher troubleshooting such as ensuring that the game folder has read and write permissions and running the launcher as admin to generate new login information.\n\nCode 20007\/30007:\nCode 20007\/30007s occur when the game client receives information that it isn\u2019t expecting. A good example is when a bad asset in the game exists, such as when we discovered that Cutlasses were disconnecting all clients on the internal QA server because of an invalid ID.\n\nCode 20008\/30008:\nCode 20008\/30008 is defined as an authentication error. This infrequently can mean authentication in terms of your account ID and password, but for the most part indicates a backend data mismatch.\n\nCode 20009\/30009:\nCode 20009\/30009 occurs when someone successfully connects and authenticates into a game server but times out when verifying the session.\n\nWe hope this small insight into code errors has been helpful in understanding the nature of these disconnect codes and how it can help you provide more accurate information to Issue Council reports.","de_DE":"Wir dachten, wir w\u00fcrden mit Ihnen mehr Informationen \u00fcber unsere Trennungscodes teilen, die Sie in Star Citizen erhalten k\u00f6nnen, und die Spieler dar\u00fcber informieren, wie sie diese Informationen besser nutzen k\u00f6nnen, um code-bezogene Fehler im Issue Council zu beschreiben.\n\nWichtige Hinweise!\n\n\nWichtiger Hinweis #1: Trennungscodes sind symptomatisch daf\u00fcr, dass etwas schief geht; sie sind keine echte Diagnose, mit der Sie ein Problem l\u00f6sen k\u00f6nnen. Eine gute Analogie ist, wenn jemand hustet.... der Husten ist schlecht, aber es k\u00f6nnte eine Vielzahl von Ursachen dahinter stecken. Der Husten ist der Trenncode. :)\n\nWichtiger Hinweis #2: Die Schritte, um jeden Code zu erhalten, k\u00f6nnen je nach Situation sehr unterschiedlich sein, weshalb die Aufnahme pr\u00e4ziser Schritte zur Reproduktion im Issue Council absolut notwendig ist, um das Problem zu verfolgen. Ein Beispiel daf\u00fcr w\u00e4ren zwei Freunde, die jeweils einen Code 20007 erhalten.... w\u00e4hrend der Fehlercode derselbe ist, k\u00f6nnten die Ursachen f\u00fcr jeden v\u00f6llig getrennt und unabh\u00e4ngig voneinander sein.\n\nWichtiger Hinweis #3: Wenn Sie einen Issue Council Bericht eingeben, stellen Sie sicher, dass Sie den erhaltenen Code-Fehler und eine kurze Beschreibung im Betreff hinzuf\u00fcgen, wie z.B. \"Error Code 20007 When Loading Into Crusader\". Code 10000:\nDer Code 10000 passiert, wenn der Spielclient uns nicht finden kann, weil etwas den Spielclient daran hindert, unsere Server zu finden. Diese werden fast immer ein Thema auf der Kundenseite sein.\n\nCode 10001:\nDer Code 10001 tritt auf, wenn der Spiel-Client Probleme mit der Verbindung zum Authentifizierungsdienst hat.\n\nCode 10003:\nCode 10003 tritt auf, wenn der Spiel-Client eine Verbindung zum Authentifizierungsdienst herstellen kann, aber entweder besch\u00e4digte Persistenz-Cache-Daten hat oder nicht in der Lage ist, die Datenbank zu erreichen, um ihre persistenten Daten zu erhalten.\n\nCode 20000\/3000000:\nCode 20000\/3000000 ist unsere allgemeine Timeout-Nachricht. Sie erhalten diese Meldung, wenn Ihre Verbindung zum Spielserver unterbrochen wird, aber Sie sind immer noch mit dem Backend-Plattformdienst verbunden und sind noch aktiv. In fast allen F\u00e4llen ist dies auf einen tats\u00e4chlichen Absturz des Spielservers oder ein Problem innerhalb des Spiels zur\u00fcckzuf\u00fchren, das dich trennen kann.\n\nEin internes Beispiel f\u00fcr letzteres trat in unserer QA-Umgebung auf (was es nie in die \u00d6ffentlichkeit geschafft hat), als ein Client das Spiel verlassen w\u00fcrde und alle anderen Clients gewaltsam getrennt wurden.\n\nCode 20003\/30003:\nCode 20003\/30003 ist ein Versionsfehler, der auftritt, wenn der Server die installierte Version des Spiels \u00fcberpr\u00fcft und feststellt, dass es eine \u00e4ltere Version des Clients gibt. Der Weg, dies zu beheben, ist, Dateien zu verifizieren oder, in sehr seltenen F\u00e4llen, das Spiel vollst\u00e4ndig neu zu installieren.\n\nCode 20004\/30004:\nUnser Matchmaking-Service enth\u00e4lt mehrere verschiedene Regeln, um Clients Servern zuzuordnen. Diese Antwort tritt auf, wenn der Matchmaking-Service jemanden auf einen Server bringt, der voll ist.\n\nIn den meisten Situationen sollte der Dienst Sie nicht einem Server zuweisen, der bereits voll ist, aber wir finden Randf\u00e4lle, in denen dieser zur\u00fcckgegeben wird. Wir werden diese weiterhin isolieren, identifizieren und reparieren, sobald sie auftauchen.\n\nCode 20005\/30005:\nDer Code 20005\/30005 tritt auf, wenn ein Anmeldeversuch aufgrund ung\u00fcltiger Daten fehlschl\u00e4gt. Viele davon k\u00f6nnen behoben werden, indem man die Fehlerbehebung des Launcher durchf\u00fchrt, wie z.B. das Sicherstellen, dass der Spielordner Lese- und Schreibrechte hat, und das Ausf\u00fchren des Launcher als Administrator, um neue Anmeldeinformationen zu generieren.\n\nCode 20007\/30007:\nDer Code 20007\/30007s tritt auf, wenn der Spiel-Client Informationen erh\u00e4lt, die er nicht erwartet. Ein gutes Beispiel ist, wenn ein schlechter Verm\u00f6genswert im Spiel existiert, wie z.B. als wir herausfanden, dass Entermesser alle Clients auf dem internen QA-Server wegen einer ung\u00fcltigen ID getrennt haben.\n\nCode 20008\/30008:\nDer Code 20008\/30008 ist als Authentifizierungsfehler definiert. Dies kann in seltenen F\u00e4llen eine Authentifizierung in Bezug auf Ihre Konto-ID und Ihr Passwort bedeuten, deutet aber in den meisten F\u00e4llen auf einen Datenmismatch im Backend hin.\n\nCode 20009\/30009:\nDer Code 20009\/30009 tritt auf, wenn sich jemand erfolgreich mit einem Spielserver verbindet und authentifiziert, sich aber bei der \u00dcberpr\u00fcfung der Sitzung ausschaltet.\n\nWir hoffen, dass dieser kleine Einblick in Codefehler dazu beigetragen hat, die Art dieser Trennungscodes zu verstehen und wie sie Ihnen helfen k\u00f6nnen, genauere Informationen f\u00fcr die Berichte des Issue Council bereitzustellen.","zh_CN":"We thought we\u2019d share with you more information on our disconnect codes that you can get in Star Citizen, as well as educate players on how they can better use this information to describe code-related errors in Issue Council.\n\nImportant Notes!\n** Important Note #1: Disconnection codes are symptomatic of something going wrong; they are not true diagnostics that you can use to resolve an issue. A good analogy is when someone is coughing\u2026 the cough is bad, but there could be any number of causes behind it. The cough is the disconnect code. :)\n\n** Important Note #2: The steps to obtain each Code can be quite different per situation, which is why including precise Steps To Reproduce in the Issue Council is absolutely vital to our tracking the issue down. An example of this would be two friends each getting a Code 20007\u2026 while the error code is the same, the causes for each could be completely separate and independent of each other.\n\n** Important Note #3: When entering an Issue Council report, make sure that you add the Code error you get plus a brief description in the subject, such as \u201cError Code 20007 When Loading Into Crusader\u201d.\n\nCode 10000:\nCode 10000 happens when the game client isn\u2019t able to find us due to something preventing the game client from being able to find our servers. These will almost always be an issue that is client side.\n\nCode 10001:\nCode 10001 happens when the game client is having issues connecting to the authentication service.\n\nCode 10003:\nCode 10003 occurs when the game client can connect to the authentication service but either has corrupted persistence cache data, or is unable to reach the database to get its persistent data.\n\nCode 20000\/30000:\nCode 20000\/30000 is our general timeout message. You\u2019ll get this message when your connection to the game server times out, but you\u2019re still connection to the backend platform service is still active. In almost all cases, this is due to an actual game server crash or an issue within the game that can disconnect you.\n\nAn internal example of the latter occurred on our QA environment (this never made it to public) when one client would exit the game and all other clients were forcefully disconnected.\n\nCode 20003\/30003:\nCode 20003\/30003 is a version mismatch which occurs when the server checks the version of the game installed and finds that there is an older version of the client. The way to resolve this is to Verify Files or, in very rare situations, fully reinstall the game.\n\nCode 20004\/30004:\nOur matchmaking service contains several different rules to assign clients to servers. This response occurs when the matchmaking service puts someone into a server that is full.\n\nIn most situations, the service should not assign you to a server that is already full, but we\u2019re finding edge cases where this gets returned. We\u2019ll continue to isolate, identify, and fix these as they come up.\n\nCode 20005\/30005:\nCode 20005\/30005 happens when a login attempt fails due to invalid data. Many of these can be fixed by doing launcher troubleshooting such as ensuring that the game folder has read and write permissions and running the launcher as admin to generate new login information.\n\nCode 20007\/30007:\nCode 20007\/30007s occur when the game client receives information that it isn\u2019t expecting. A good example is when a bad asset in the game exists, such as when we discovered that Cutlasses were disconnecting all clients on the internal QA server because of an invalid ID.\n\nCode 20008\/30008:\nCode 20008\/30008 is defined as an authentication error. This infrequently can mean authentication in terms of your account ID and password, but for the most part indicates a backend data mismatch.\n\nCode 20009\/30009:\nCode 20009\/30009 occurs when someone successfully connects and authenticates into a game server but times out when verifying the session.\n\nWe hope this small insight into code errors has been helpful in understanding the nature of these disconnect codes and how it can help you provide more accurate information to Issue Council reports."},"links_count":0,"comment_count":0,"created_at":"2019-11-01T00:00:00+00:00","created_at_human":"6 years ago"},"meta":{"processed_at":"2026-05-30 09:40:03","valid_relations":["images","links"],"prev_id":15121,"next_id":15123}}