Ragexe RE

Every function of two Ragnarok Online client builds, named and described by us: what each one does, in plain words, at its address.

Builds 2Functions 90,897Image base 0x00400000

The builds

Each build has its own catalog: its categories, a map of where they sit in the exe, a search across every function, and a page per category listing its functions by address.

2026-02-19 RagexePE date 2026-02-11

47,061 functions in 29 categories, grouped as Game Logic, Effects, Network, UI, Systems and Library.

Browse and search it functions.tsv, 8.4 MB

2025-07-16 RagexePE date 2025-07-10

43,836 functions in 26 categories.

Browse and search it functions.tsv, 6.8 MB

Use it with an AI agent

Download the data

One functions.tsv per build, and the notes that explain it:

curl -fsSL --create-dirs -o 2026-02-19/functions.tsv https://warp.legacygamers.net/docs/ragexe_re/2026-02-19/functions.tsv
curl -fsSL --create-dirs -o 2025-07-16/functions.tsv https://warp.legacygamers.net/docs/ragexe_re/2025-07-16/functions.tsv
curl -fsSLO https://warp.legacygamers.net/docs/ragexe_re/AGENTS.md

Have it read AGENTS.md first

AGENTS.md explains the columns, how to find the function an address falls in, and how far to trust what it reads. Point the agent at the file rather than at these pages.

Ask with addresses from your own work

An address from a crash log, a debugger or your own disassembly works best:

Which function in the 2026-02-19 functions.tsv contains 0x00707160, and what does it do?

For that one it should find CEffHyperNoviceSpell__transform_and_tick_particle at 0x007070E0, 385 bytes long, in Game Core.

How far to trust it

We read each function, much of it with a model's help, then audited the results function by function. That makes the catalogs a strong guide, not ground truth.

Our analysis, not symbolsThe client ships without debug symbols, so every function name and description here is ours. Check the disassembly before you depend on a detail: a branch, an offset, a constant, a calling convention.

Descriptions are the strongest partWhat a function reads, writes and calls, in plain words. Read the description before you trust the name.

Class names are the weakest partWhere your own tools show a class from RTTI or a vtable, that wins over our name.

Addresses are from our unpackAnother unpack of the same build usually keeps code at the same addresses, but not always. Compare a few bytes, or the size, with your own image first. A different build moves nearly everything.

The files

File	What it is	Size
`<build>/functions.tsv`	Every function of one build, one row each, sorted by address. Tab separated, UTF-8, one header row.	2026-02-19 8.4 MB, 2025-07-16 6.8 MB
`AGENTS.md`	How to use the data, for an AI agent or for you.
`builds.json`	Per build: the binary's identity and hashes, and its categories (the classes each covers, count, lowest and highest address).

The columns of functions.tsv

Column	What it holds	Example
`address`	Where the function starts: `0x` and eight uppercase hex digits.	`0x007070E0`
`size`	Its length in bytes.	`385`
`name`	Our name, `Class__method` style. A trailing `_XXXXXXXX` only tells apart two functions that would share a name.	`CEffHyperNoviceSpell__transform_and_tick_particle`
`category`	Its category, and the last part of its category page's address.	`game_core`
`description`	One line: what it does.	Transforms single spell particle to camera view space using entity world-to-view matrix chain, then ticks animation frame.

Free to read and use, for research, modding and running your own server. A link back to this page is appreciated. The client and Ragnarok Online belong to Gravity Co., Ltd.; this documents the binary and contains none of it.