- Open source: rObrowser / rObrowser Legacy are open-source projects under their respective licenses.
- Service only: You are not buying a proprietary client or license from me—you are availing my setup/integration service to connect your rAthena server to rObrowser Legacy.
- Currency: All fees are quoted and payable in SGD.
I will provide best-effort services to:
- Configure the connection between your rAthena server and rObrowser Legacy (login/char/map via wsProxy).
- Assist with wsProxy on your VPS and basic web hosting of client assets (no encrypted GRF).
- GRF & item fixes limited to client usability (e.g., missing sprites/acts, item data/display).
- Gepard coexistence: configure in a way that respects Gepard Shield (no bypass or modification) so your rObrowser flow can coexist with a Gepard-protected server where feasible.
- Provide basic handover notes so you can maintain the setup.
Ongoing maintenance is not included unless booked separately.
- UI caveats: Many UI elements are not fully supported on the latest versions. I’ll try to fix practical issues, but there’s no guarantee all UI features will work or be restored.
- No guarantee of bug fixes: Troubleshooting is best-effort only; not all bugs can or will be fixed.
- No Gepard modification: I will not modify or bypass Gepard; compatibility depends on your configuration and upstream constraints.
- Browser/device variance: Behavior can differ across browsers/devices; full cross-browser QA is out of scope.
- Performance/CDN/DDoS/autoscaling are out of scope unless explicitly added.
- Do not rely only on the browser client; it’s mainly for players who can’t download the full client (office, school, café, etc.).
- Encourage players to use the standard downloadable client for the best experience.
- rObrowser streams resources on demand (no patcher needed). Keep your GRFs on the web host updated.
- A reasonably up-to-date rAthena build.
- Recommended packet version: 2018-06-20 (or your current version with possible reduced compatibility).
- Web server for assets (no encrypted GRF).
- VPS for your emulator and wsProxy.
- Access/credentials needed to perform the setup.
- Estimated 1–2 weeks from project start (after prerequisites & access). This is an estimate, not a guarantee, and depends on complexity.
- The ecosystem is open source and evolving. Future fixes/changes may require additional service time.
- Updates are not included unless you book them.
- Additional enhancements will be quoted in SGD (smaller servers usually cheaper).
- One-time setup/integration fee.
- Optional maintenance or future update work is separate and quoted in SGD.
- Third-party costs (hosting/CDN/domains/DDoS/paid plugins) are not included.
- Service is provided “as-is” with best-effort fixes during the engagement.
- After handover, support continues only if you book a maintenance package.
- All open-source code (rObrowser/rAthena/etc.) remains under the original licenses.
- Your server content (GRFs, assets, configs) remains yours.
- I do not sell a software license; I provide time and expertise to integrate and configure.
This is a continuation of roBrowser expanded with some features. The ROBrowser Legacy repository is not directly forked from the original due to safety concerns, but it is roBrowser in spirit and functionality.
If you wish to discuss anything related to this project, or you want to join, contact the community on Discord or in the GitHub Discussions.
For info on how to setup the client read the contents of the Getting Started doc. For the original branch’s docs please visit https://www.robrowser.com/.
All credits to the original owners/creators and the new ones.
Use <Username>_M or <Username>_F to register a male or a female account on the login screen, or use the Register/Request button to navigate to the server’s account registration page.
More live examples:
Checkout the getting started guide
Remote Client serves game assets to rObrowser via HTTP by extracting them from their GRFs. You will need to setup a remote client if you want to serve the game assets centrally from your server. rObrowser can use local game assets via the Intro screen by dragging them into the file box.
- PHP implementation: roBrowserLegacy-RemoteClient-PHP
- Other implementations:
The game server uses TCP/IP to communicate with the client, while rObrowser being a web page can’t use TCP/IP. We use the WebSocket API to communicate with a proxy server that translates the packets into TCP/IP packets. This server is called wsProxy. You will need to install and configure wsProxy to make rObrowser able to connect to a game server.
- Repo: roBrowserLegacy-wsProxy
For available plugins and information on how to install them please visit the roBrowserLegacy-plugins repository.
rObrowser was started by this awesome team and we continue it. We also manually add content from other forks that didn’t make it back to the original branch—huge shoutout to them! If you wish to contribute then check out the documentation or the code itself and submit a pull request!
- Discord: https://discord.gg/8JdHwM4Kqm
- GitHub Discussions: https://github.com/MrAntares/roBrowserLegacy/discussions
By proceeding, you confirm you’ve read and accepted these terms, including: open-source basis, service-only engagement (no software license sale), UI limitations, no guaranteed fixes, Gepard non-modification, and SGD billing.