/ !\ This topic is a translated version of the one written by the French administrator Ehwo and available on the French forum. We will keep it updated regularly according to his updates.
This topic is intended provide a non-exhaustive list of known bugs in the versions deployed on live servers.
- > If you encounter a new bug that is not on this list, before reporting it, please clear your browser cache and disable any scripts and/or add-ons. If the bug persists once this has been done, you can report it to us by opening a topic here Bugs and/or a ticket here Support.
-> This topic only concerns game servers. For public test servers (PTS), please go to Bug Reporting and Suggestions.
-> This topic only concerns the browser version of OGame and not the mobile application.
List of known bugs
| Bugs related to fleets and movement |
| 1 | After relocating a planet, the moon remains in its original position. | The issue is usually resolved within a few days. If this is not the case, report the situation by ticket. |
| 2 | After relocating, the planet and its moon appear in their new positions in Galaxy View, but shortcuts in the Fleet Menu still target the old location. | The issue is usually resolved within a few days. If this is not the case, report the situation by ticket. |
| 3 | Error when dispatching a fleet: "Not enough resources." | Leave a few units of each resource at the dock when sending. |
| 4 | RIP fleets sometimes return earlier than expected (or even instantly) | No known solution. |
| 5 | Some fleets do not appear in the Fleet or Fleet Movement menu when arriving at or returning to one of your positions. | Make any kind of floating movement towards the position in question to update it. |
| 6 | Some fleets fail to initiate their return journey after impact, especially when targeting a destroyed position. | Send a ticket, and a solution will be suggested. |
| 7 | Some fleets get stuck on their return in a position that belongs to you, i.e. blocked and visible in the fleet movements but not at the shipyard or fleet screen. | Wait, the fleet will eventually land. Alternatively you can create a ticket so a GO can force your account in vacation mode until the fleet lands. |
| 8 | When a fleet arrives, population and/or food can be reset to 0. | No known solution. |
| Bugs related to interface and display issues | ||
| 1 | Unread message notification appears, but no messages are present in the inbox. | Wait 7 days for the message to be automatically deleted. |
| 2 | Espionage reports sometimes do not show the entire defense present. | No known solution. Send a ticket. |
| 3 | The IPM reports are poorly translated on the attacking side. | No known solution. |
| 4 | The names, contact details and icons of the planets and moons are shifted upwards compared to the rest of the text in the messages. | No known solution. |
| 5 | Having full fleet slots prevents IPM'S from being sent from the tooltip of the planets and moons in Galaxy View. | To target planets, you can always use the "Missile attack" button on the right in Galaxy View. |
| 6 | The title color in the CR is sometimes inconsistent with the fight's outcome. | No known solution. |
| 7 | In the summary table of lifeforms bonuses, some headings use the names of Kaelesh technologies rather than their description. | No known solution. |
| 8 | When a lifeform technology is in
progress; if the lifeform of the planet is different from that of the
lifeform technology, the cost of the next level shown is in fact that of the current research level instead. |
No known solution. |
| 9 | Trying to deactivate vacation mode without waiting for the end of its cooldown generates a generic error message rather than displaying the popup explaining how vacation mode works. | No known solution. |
| Bugs related to game mechanics and construction | ||
| 1 | Sometimes a construction order in the queue does not start, displaying a message indicating insufficient resources, despite having enough. | None known. To avoid problems when using Krakens or Newtrons, it is not advisable to use them across several construction orders. |
| 2 | It is possible to fill the Silo with missiles beyond its maximum capacity by using the second Mecha construction queue. | Any use of this bug will of course be sanctioned for a Bug-Using violation. |
| 3 | The cancel button in the detailed view of the Kaelesh Lifeform technologies does not work. | The cancel button available in the construction queue works. |
| Bugs related to events and rewards | ||
| 1 | During reward events, the game indicates that you are not receiving the bonus rewards from the Officers even though they are active. | Disregard the message, it is false. An easy way to check is to see that the unearned rewards are grayed out; if the bonus rewards are not grayed out, you have earned them. |
| 2 | Some of the tasks in the new tutorial are not validated even though they have been completed. | No known solution. |
| 3 | Slowdowns and multiple issues with the progress of achievements. | No known solution. |
| Bugs related to alliance management | ||
| 1 | In some cases, excluding a member from an alliance can make the alliance management menu completely unusable. | No known solution. Send a ticket. |
| 2 | Sometimes breaking up an alliance prevents its former members from connecting to the game. | It is still possible to connect via the mobile app. The problem should resolve itself within 48 hours. Contact support to set up a VM if you are unable to play via the app. |
| Bugs related to lobby and login issues | ||
| 1 | Sometimes it is impossible to connect to the lobby, which then displays a message indicating that the credentials used are incorrect. | The Lobby filters IPs and browsing sessions that it considers suspicious. Making sure that you don't have a VPN running, changing your IP by restarting your Internet access point and/or connecting in private browsing should solve the problem. If it doesn't work, contact us via ticket. |
| 2 | Sometimes it is impossible to connect to your game server once you are in the lobby, which displays the message "An error has occurred!". | The Lobby filters IPs and browsing sessions that it considers suspicious. Making sure that you don't have a VPN running, changing your IP by restarting your Internet access point and/or connecting in private browsing should solve the problem. If it doesn't work, contact us via ticket. |
| Bugs related to special features | ||
| 1 | When the phalanx is used repeatedly, it may stop working and display: "An error occurred during your last action" | Wait until the phalanx has been updated properly before attempting to update it again. |
| 2 | Attempting to group a fleet that is too slow—even at 100% speed—in an ACS hides the ACS button instead of displaying a popup indicating the fleet is too slow when trying to send it. | No known solution. |
| 3 | The graveyard transfer script may ban a VM I > 60d account without ever transferring it | If after 24 hours the account has still not migrated to the graveyard, send us a ticket. |
