Request for Extension Development Guidelines & Authorization

    Hello,
    I am planning to develop a browser extension tailored specifically for the Brazilian OGame community.
    To ensure total transparency and full compliance with Gameforge's terms, I intend to strictly adhere to the following principles:

    1. Open Source Development: The extension will be fully open source, and I plan to host the complete code repository on a public GitHub page for continuous inspection.
    2. Strictly Read-Only Functionality: The tool will operate purely as a "read-only" helper. It will only extract on-screen data to generate statistics and local utilities for the player, without simulating any clicks, automating fleet dispatches, or interacting with the game server.
    3. Testing Phase Protocol: I am ready to follow a step-by-step approval process. I can develop the initial version locally and then provide the source code and installation package for the team to test on the Public Test Servers (PTS) before officially requesting the "Tolerated Tool" status.

    Before I begin writing the first lines of code, I would like to confirm:

    • Are there any specific technical limitations or restricted APIs that I should be aware of?
    • Is there a preferred environment or standard layout you require for submitting tools for review?

  • RiV-

    Approved the thread.

  • RiV-

    Added the Label Questions

    Hello,


    Thanks for asking before writing code — that's the right order.


    One correction on your premise: "read-only" doesn't exempt a tool from toleration. Anything running on top of the game page needs review.

    Also, "read-only" isn't the reassurance you might think it is: background calls are read-only too, and there's a lot to get wrong there.


    There's no PTS pre-approval stage — review happens on the submission itself. Please read the following threads:


    And if you're developing with an AI coding agent: AGENTS.md — keep your AI coding agent within the tool rules

    Worth checking it out even if you don't, as it elaborates on the Forbidden features.


    Quote from Ahab

    Are there any specific technical limitations or restricted APIs that I should be aware of?

    For the public XML API and the reports API: OGame API


    On ingame endpoints, the AGENTS.md linked above has some examples on what to do and what not to do.

    However there is no exhaustive list. You're a developer and you're expected to have an understanding of game mechanics, ingame endpoints and their implications. If you don't, you should probably not be developing ingame extensions.


    Quote from Ahab

    Is there a preferred environment or standard layout you require for submitting tools for review?

    Everything is in the Submission guidelines above. Including the submission template.

    Hello RiV-,

    Thank you for the detailed clarifications and the references. I will definitely include AGENTS.md in my project and use the community proxy as instructed.

    Before I start testing the code locally, I have a quick question regarding the development environment:

    1. Is there a specific server (like a PTS universe) that you recommend for developing and testing the extension?
    2. Is it permissible (and safe regarding the anti-bot system) to test the early, local versions of the extension on my main playing account, or would you strongly advise creating a separate test account in a different universe to avoid any accidental bans if the code misbehaves during development?

    Thanks again for your time and guidance.

    Quote from Ahab

    Hello RiV-,

    Thank you for the detailed clarifications and the references. I will definitely include AGENTS.md in my project and use the community proxy as instructed.

    Before I start testing the code locally, I have a quick question regarding the development environment:

    1. Is there a specific server (like a PTS universe) that you recommend for developing and testing the extension?
    2. Is it permissible (and safe regarding the anti-bot system) to test the early, local versions of the extension on my main playing account, or would you strongly advise creating a separate test account in a different universe to avoid any accidental bans if the code misbehaves during development?

    Thanks again for your time and guidance.

    Hello,


    The PTS universe (Singularity) is in the Pioneers Lobby: https://lobby-pioneers.ogame.gameforge.com/


    Note that you can copy your live account over: in your live account go to Options -> Extended -> Singularity -> copy / merge. That gives you realistic data to develop against without touching the live account itself.


    To your second question: no. Don't test non-tolerated code on a live account, and not just because it might misbehave during development. A tool that hasn't been reviewed has no business running on a live universe at all — that applies to your own account exactly as much as anyone else's. Develop and test on Singularity, submit, and use it live once it's tolerated.

    Hi

    Thanks for the instructions. I tried to copy my live account to the Singularity PTS as you suggested, but in my Options -> Extended menu, the only test server available for me to copy/merge into is "en_808". Singularity does not appear as an option for my account.

    Could you let me know if it is okay to develop and test the extension on "en_808" instead? Alternatively, would it be possible for you to manually copy my account over to Singularity so I can follow your exact guidelines?

    Thank you.

    Hi,

    Ah, that makes sense! I thought there was a specific server literally named "Singularity" because the link directed me to the English servers, but now I see it is just the standard OGame lobby layout.

    thanks for all the clarifications and your patience. I will copy my account over to en_808 and start developing the extension.

    Hi again,
    I have two quick follow-up questions before I dive into the code:


    1. Are there any other channels for support, such as a Discord server or a specific place where I can ask questions and exchange ideas with other tool developers?
    2. Does the source code (classes, variables, and comments) need to be written in English? Since this extension is tailored for the Brazilian OGame community, keeping the code and documentation in Portuguese on GitHub would make it easier for local players to understand and contribute. However, if having everything in English is strongly recommended or required for your team's code review and toleration process, I will gladly write it all in English.
    Thanks again!