How mrantares/robrowserlegacy works
ROBrowser Legacy is a browser-based Ragnarok Online client. A player starts the client, loads game assets locally or from a remote client, connects through a WebSocket proxy to a game server, and uses the client’s login, character, and map experiences. The map experience combines packet-driven game state, domain data, rendering, audio, controls, and UI. The repository also includes asset and graphics viewers, plugins, and desktop/PWA entry points. The graph preserves these documented capabilities; several internal connections are dashed because the available excerpts do not verify their call paths.
Main entry points: MapEngine.js Map gameplay · main.js Client entry · NetworkManager.js Packet networking · FileManager.js Asset loading
Components 32
Client applications
- Client entry
src/main.js - PWA setup
applications/pwa/Config.js - Desktop shell
applications/electron/main.js - Asset viewers
src/App/GrfViewer.js - Map viewer
src/App/MapViewer.js - Model viewer
src/App/ModelViewer.js - Effect viewer
src/App/EffectViewer.js - STR viewer
src/App/StrViewer.js - Granny viewer
src/App/GrannyModelViewer.js
Gameplay runtime
- Login flow
src/Engine/LoginEngine.js - Character flow
src/Engine/CharEngine.js - Map gameplay
src/Engine/MapEngine.js - Map features
src/Engine/MapEngine - Storage protocol
src/Engine/MapEngine/Storage.js - Plugin manager
src/Plugins/PluginManager.js
Game content
- Asset loading
src/Core/FileManager.js - Game data
src/DB/DBManager.js
Presentation
- WebGL renderer
src/Renderer/Renderer.js - Entity rendering
src/Renderer/EntityManager.js - Effects
src/Renderer/EffectManager.js - Game interface
src/UI/UIManager.js - Storage window
src/UI/Components/Storage/StorageCommon.js - Input controls
src/Controls/KeyEventHandler.js - Audio
src/Audio/SoundManager.js
External integration
- Packet networking
src/Network/NetworkManager.js - Protocol versions
src/Network/PacketVerManager.js - Packet definitions
src/Network/PacketRegister.js
Other components
- Player
- WebSocket proxy
- Game server
- Game assets
- Remote client
Connections 31
- Player → Client entry: starts
- Player → Game assets: loads locally
- Client entry → Asset loading: loads assets
- Asset loading → Game assets: reads assets
- Asset loading → Remote client: requests assets
- Client entry → Login flow: starts session
- Login flow → Character flow: continues to
- Character flow → Map gameplay: enters gameplay
- Map gameplay → Map features: dispatches features
src/Engine/MapEngine.js - Map gameplay → Packet networking: exchanges packets
- Packet networking → WebSocket proxy: uses WebSockets
- WebSocket proxy → Game server: translates TCP
- Packet networking → Protocol versions: selects protocol
src/Network/NetworkManager.js - Packet networking → Packet definitions: registers packets
src/Network/NetworkManager.js - Map gameplay → Game data: uses game data
- Map gameplay → WebGL renderer: updates scene
- WebGL renderer → Entity rendering: renders entities
- WebGL renderer → Effects: renders effects
- Map gameplay → Game interface: opens interface
- Storage protocol → Storage window: updates storage
- Input controls → Map gameplay: sends actions
- Map gameplay → Audio: triggers audio
- Player → PWA setup: uses PWA
- Player → Desktop shell: uses desktop app
- Client entry → Plugin manager: loads plugins
- Player → Asset viewers: opens GRF viewer
- Player → Map viewer: opens map viewer
- Player → Model viewer: opens model viewer
- Player → Effect viewer: opens effect viewer
- Player → STR viewer: opens STR viewer
- Player → Granny viewer: opens Granny viewer