Posts by RiV-

  • Question about statistic api

    No, there is currently no dedicated API that provides historical highscore or leaderboard data.


    The public highscore API only exposes the current snapshot of the rankings at the time it is updated. Historical progression data is not stored or made available through any official endpoint.


    If you need this kind of data, you would have to collect and store the regular highscore snapshots yourself and build the historical dataset independently.

  • Tool Submission Template

    Contents [Hide]

    Tool Information

    Tool Name:

    Current Version:

    Author / Team:

    Website / Repository:

    Support / Contact:

    License:

    Download Link:

    Tool Classification

    Select one:

    • Browser Extension
    • Userscript
    • Desktop Application
    • Mobile Application
    • Web Tool
    • Other

    Browser / Platform Compatibility

    Supported Browsers / Platforms:

    Minimum Version Requirements:

    Supported OGame Languages / Communities

    List all currently supported OGame language versions / communities.


    Recommendation:

    Tools should preferably function independently of the selected OGame language wherever technically possible.


    Features that rely on language-specific UI text, labels, or selectors are more likely to break across communities and game updates.


    Additionally, developers are strongly encouraged to provide at least an English translation for all tool interfaces, settings, and documentation to facilitate review and support.


    Modern translation tools make adding basic multilingual support relatively low-effort, and doing so significantly improves accessibility for both reviewers and users.


    If the tool is language-dependent, please explain why.


    Tool Description

    Provide a short description of what your tool does.

    Complete Feature List

    List every feature currently included.


    Be explicit.


    Examples:


    ✅ Adds production overview panel

    ✅ Highlights inactive players

    ❌ “Various UI improvements” (too vague)

    API Usage

    Does this tool use OGame API data or ingame endpoints?


    If yes:

    Which endpoints are used?

    Expected request frequency:

    UI Modifications

    Describe all interface changes introduced by the tool.

    Include screenshots.

    Screenshots / Demo

    Provide screenshots and a working demo.

    Installation Instructions

    Explain how users install and use the tool.

    Data Handling / Privacy

    Does the tool:

    • Store user data locally?
    • Send data to external servers?
    • Use analytics / telemetry?

    Explain clearly.

    Source Availability

    • Open Source
    • Closed Source
    • Source available to reviewers upon request

    If minified/bundled, unminified source must be provided for review.

    Changelog

    Version X.Y.Z

    • Added:
    • Changed:
    • Fixed:
    • Removed:

    Compliance Declaration

    I confirm that this tool:

    • Does not automate gameplay
    • Does not provide forbidden functionality
    • Does not exceed permitted API usage
    • Complies with all current OGame Origin tool guidelines

  • Question about statistic api

    Hello,


    this confusion is caused by an incorrect description in the API documentation thread.


    The statistics endpoint was previously described as providing “historical ranking data”, which was misleading. This wording has now been corrected.


    The endpoint only returns aggregated daily report activity statistics, specifically:

    • combat report count
    • espionage report count
    • recycler report count
    • missile report count

    The data returned by your example is therefore correct.


    A personal API key does not change the type of data returned by this endpoint.


    So to answer your question directly: no, requesting an API key will not enable retrieval of ranking history through this endpoint.

  • OGame-Tools - Combat Simulator

    No longer subject to toleration requirements as of new policies. Moving to community showcase.


    Please take note that if you use userscripts or browser extensions to scrape data, those need separate toleration.

  • ProxyForGame (OGame Calculator)

    No longer subject to toleration requirements as of new policies. Moving to community showcase.


    Please take note that if you use userscripts or browser extensions to scrape data, those need separate toleration.

  • There is no cooldown on the test server

    Quote from cR3ml1s
    Quote

    There is no cooldown on the test server, so you can freely enter and leave it as needed.

    What do you mean by "There is no cooldown on the test server, so you can freely enter and leave it as needed."?

    @RiV-

    On Alpha server, you can enter and exit vacation mode whenever you want. You don't have to wait 48 hours to leave vmode after activating it.


    Quote from NBS

    but this isn't the case for Bermuda. it's still 48h cool down

    Since you can copy your own account over to Alpha, Alpha is probably the best suited server for testing anyway.

  • About last update : version 12.5.0

    We’re going in circles here, so I’m going to close this thread. The key points have already been covered.


    We understand that some of you prefer using the test server as a safe environment without attacks. However, that is not its purpose.


    The test server is intended for testing new features and changes under realistic conditions. This includes combat mechanics and their impact. Situations like the current one are part of that process.


    If you do not wish to risk being attacked while not actively testing, please make use of vacation mode. There is no cooldown on the test server, so you can freely enter and leave it as needed.


    Using the test server as a permanent “no-risk” play environment (or “testing the test server” itself) is not the objective.


    Thank you to those who contributed constructive feedback.

  • Forbidden features

    This is a general guideline for developing and submitting user-created tools and doesn’t constitute a comprehensive list. Toleration of each feature happens at the Origin team’s discretion. If in doubt, talk to the responsible ToolDevs admin before writing your code.


    Building with an AI coding agent? Add our AGENTS.md to your project before you start prompting. It turns the rules below into hard constraints your agent will refuse to cross, so it doesn't build forbidden features in the first place. Recommended, not required — and not a guarantee of toleration. See: AGENTS.md — keep your AI coding agent within the tool rules.


    Source Code Requirements: If you need or want to minify your code, you must submit the un-minified and un-obfuscated, human-readable source code to the team member reviewing your tool. Heavily obfuscated code will be rejected.


    Features Deemed Forbidden

    • Blocking or altering monetization and legal content

      This includes blocking, hiding, obscuring (e.g., via CSS opacity, sizing, or off-screen positioning), or changing the images of banners, the top advertisement bar, premium/monetization content, or menu items like Merchant, Recruit Officers, Shop, and the footer.

    • Imitating Dark Matter features

      Imitating features that are exclusively accessible with Dark Matter usage (for example, imitating the Commander’s construction queue) is strictly prohibited.

    • Automation & Macros

      Any kind of automation that executes a sequence of actions without corresponding user interaction is prohibited.

      • 1 Click/Key stroke = 1 Action: A single user click cannot trigger multiple distinct game actions (e.g., clicking once to send 10 different espionage probes to 10 targets).
      • QoL Exceptions (Case-by-Case Evaluation): Batching repetitive, non-tactical actions on your own planets (such as queuing multiple shipyard or defense orders) may be permitted as a Quality of Life feature, but is strictly evaluated on a case-by-case basis. These must not imitate Premium features (like the Commander's building queue) and must be explicitly approved by a ToolDev.
      • No Scheduling: Delayed or scheduled executions (e.g., clicking a button now to automatically send a fleet 4 hours later) are forbidden.
      • Automatic refreshing of the game page is strictly prohibited.
    • Drastic shortcuts & UI altering

      The game is meant to be played through the UI that the game itself provides. Shortcutting several page loads or clicks into a single action is prohibited. Circumventing the UI or the game flow, such as creating an alternative UI or bypassing the lobby to log in, is forbidden.

      • Exceptions: Pure comfort features are evaluated on a case-by-case basis, but tools that bypass core gameplay loops (like fleet dispatch or building selection) will not be granted exceptions.
    • Excessive background calls & Polling

      Background calls are useful for retrieving necessary information but must be reduced to an absolute minimum.

      • Tools may not use continuous, automated polling loops to constantly check the server for updates.
      • Background calls that cause uncontrolled or unwanted activity (triggering an “activity star” in the Galaxy view) or cause unnecessary server load are strictly forbidden.
    • Automated alarms & Event notifications

      Automated alarms designed to alert a player to in-game events while they are away or inactive are prohibited. This includes acoustic or visual signals for incoming attacks, finished buildings, or fleet arrivals (including desktop notifications and automated external webhooks like Discord pings).

      • (Note: Basic, immediate UI feedback confirming a user's action, such as a "settings saved" text box, is permitted).
    • Paywalls, Fees & Advertising

      Charging fees for the usage of your tool, locking features behind a "premium" paywall, requiring paid third-party subscriptions (e.g., Patreon-only access), or injecting your own advertising into the game UI is prohibited. You are free to include an optional donation button or a link to hero.li.

    • Data Privacy & Secret Scraping

      Tools may not silently scrape a user's private data (such as messages, exact fleet compositions, session tokens, or precise activity times) and transmit it to an external database or server without the user's explicit, informed consent.


    Your OGame Origin Team

  • Important for users: About toleration and tolerated tools

    When using external tools, scripts, or add-ons for OGame, your account's safety is your responsibility. To know if a tool is legal to use, apply this simple rule:


    1. Does it interact with your game? (Must be Tolerated)

    If a tool requires you to install a browser extension, add a userscript, or runs directly on your OGame tab, it MUST be officially listed in the Tolerated Tools subforum.

    • This includes tools that scrape your galaxy view, track activity, or alter your game's interface.
    • If a tool requires installation and is not on our Tolerated list (even if you found it on the Chrome Store or Discord), it is illegal to use and may result in a ban.


    2. Is it just an external website? (Free to Use)

    If the tool is simply an external website, spreadsheet, or desktop calculator where you manually type data, paste reports, or look up public stats, it does not require official toleration.

    • You are free to use these standalone resources (often shared in our Community Showcase section).
    • Warning: If an external website asks you to install a script to "auto-fill" your data, that specific script immediately falls under Rule #1 and must be Tolerated.


    Toleration & Your Risk

    Please note that "Toleration" simply means a tool does not break OGame's gameplay rules. Gameforge and the Origin Team do not verify the security, correctness, or data privacy of any third-party tool. You use all tools entirely at your own risk.



    Always Use the Latest Version

    Only the latest version of a tolerated tool posted in its official thread is legal to use. If a tool updates with hidden features not listed here, using it may result in sanctions.

  • API Access Applications – Required Procedure (Updated)

    This thread outlines the mandatory process for tools interacting with the OGame API. We have recently streamlined how API access is handled.


    1. The Standard Method: Use the Community Proxy

    For the vast majority of tools (including all new tools and standalone calculators), you no longer need to apply for a private API key. Instead, you are required to route your API calls through a community proxy.


    Please use the following proxy for your tools:

    👉 https://ogapi.faw-kes.de/


    You do not need permission to use this proxy. Simply build your tool using this endpoint.


    2. Requesting a Private API Key (Exceptions Only)

    Private API access keys are now strictly reserved for established tool developers who require the absolute reliability of direct API access (e.g., massive user bases, specific technical constraints where a proxy is insufficient).


    If you believe your tool qualifies for a direct API key, you must file a request in the “Submissions & API Requests” section with the label “API Request”.


    Conditions for requesting a private key:

    • Working Demo: You must provide a working demo of your tool currently functioning via the proxy (https://ogapi.faw-kes.de/).
    • Toleration: If your tool interacts with the game (userscripts, addons), it must already have achieved Tolerated status.
    • Justification: You must clearly explain why the standard proxy is insufficient for your tool's current traffic or functionality.

    Applications without a functional demo or proper justification will be declined.


    Summary

    • Building a new tool? Use the proxy: https://ogapi.faw-kes.de/
    • Need an exception for direct access? Post in "Submissions & API Requests" with a working demo and justification.
    • Clarify any questions with a ToolDev before requesting direct access.

  • Read first: Do I need to submit my tool? (Submission Guidelines)

    Before you post, please determine if your project requires official Origin Team toleration. We have recently updated our policies to make things easier for developers of standalone tools.


    1. Does my tool need toleration?

    • YES (Requires Toleration - Submit here):
      • Client-side & UI tools: Anything that runs within or directly on the OGame webpage (e.g., browser extensions, userscripts, add-ons).
      • Live Data Handlers: Any external server, tool, or database that receives, stores, or evaluates live data scraped from the game interface (e.g., galaxy databases, player activity trackers, espionage report aggregators).
        Note: Both the scraping script and the receiving server must be reviewed.
    • NO (Does NOT require toleration):
      • Calculators & Simulators: Standalone web tools, spreadsheets, or desktop apps that rely strictly on manually entered data (e.g., copying and pasting a report) or data pulled from the official OGame API.
      • You may post these kind of tools in: Community Showcase
    • If your project does not perfectly fit the "NO" category, or if you are unsure, assume it requires toleration. Submit it for review or contact a ToolDev privately before publishing.


    (Please also ensure your tool does not contain any mechanics listed in our Forbidden features, as these will be rejected immediately.)


    Building with an AI coding assistant? If you use an AI coding agent (Claude Code, Cursor, Copilot, etc.), add our AGENTS.md to your project before you start. It turns the forbidden-features and toleration rules into guardrails your agent follows, so it doesn't build disallowed features in the first place — making review smoother and rework rarer. Recommended, but not required, and not a guarantee of toleration. See: AGENTS.md — keep your AI coding agent within the tool rules.


    Note: If your standalone tool uses a userscript or extension to "auto-fill" or scrape data from the game, that specific script/extension DOES require toleration and must be submitted here.


    2. How to submit a tool for toleration

    To start the review process for a tool that interacts with the game, start a new thread in this section, choose the applicable label, and follow the recommended Submission Template.


    For browser extensions, please do not make your tool publicly available in browser extension stores before receiving the toleration status.


    Source Code Requirements: If you need or want to minify your code, you must submit the un-minified and un-obfuscated, human-readable source code to the team member reviewing your tool. Heavily obfuscated code will be rejected.


    3. The Review Process & Updates

    Once your tool is reviewed and tolerated, it will be moved to the "Tolerated Tools" section. If this is your first tool, and you aren't already part of the "Community Projects" group, please apply to the group so you can post in the "Tolerated Tools" section.


    Changelogs

    Your official thread in the "Tolerated Tools" section must be kept clean. Use this thread only to post your official updates and changelogs for every new version. Omitting changes or adding hidden features may result in the loss of your toleration status.


    Changelogs must be sufficiently detailed for a ToolDev to assess whether a review of the new version is required. Marketing-style descriptions ("improved experience", "major overhaul", etc.) or purely technical implementation details ("added class X", "registered handler Y") are not sufficient on their own.


    For each new feature, please describe:

    • What the feature does from a user perspective.
    • What information it accesses or collects.
    • Where that information comes from (e.g. game page, API, user input, external database).
    • Whether new background requests, polling, or automated data collection are introduced.
    • Whether any information is transmitted to external services or databases.
    • Whether the feature performs automated actions, notifications, alarms, webhooks, or similar functionality.
    • Whether the feature changes, shortcuts, or replaces parts of the normal OGame user interface or workflow.

    Bug fixes, visual adjustments, and internal code refactoring may be summarized more briefly, provided they do not alter the feature set or behavior relevant to the toleration review.


    Discussion & Feedback

    Once your tool is tolerated, you are free to open a separate thread in the "Community Showcase" section so users can ask questions, report bugs, and give feedback. You must include a clear link to your official "Tolerated Tools" thread in the opening post.


    Future Features

    Toleration is only for the current state of your tool. If you plan to add new features, confer with a responsible ToolDev first to ensure they won't break the rules.


    ⚠️ What "Toleration" Means

    Toleration simply means the Origin Team has reviewed the features and determined it does not violate OGame's rules or Terms of Service. It is NOT a guarantee that the tool works correctly, nor is it an absolute guarantee of security. Gameforge and the Origin Team do not verify the correctness of the results or provide a warranty. Users install and use all third-party tools at their own risk.

  • API request to replace acs-splitter

    From the topic "you've read of course":



    Use an API-Proxy to make a working demo. Preferably the OGApi one as that will just give you a JSON object just like the OGame API would.