Thunderbrew - Recent changes [en]

WoW:3.3.5a

Phaneron — Sun, 24 May 2026 03:17:02 GMT

Thunderbrew

Phaneron — Sat, 09 May 2026 23:24:24 GMT

← Older revision		Revision as of 23:24, 9 May 2026
Line 8:		Line 8:
	}}		}}

	Thunderbrew was ~~created~~ as a fork of [[Whoa]]. Like Whoa, it aims to provide a <strong>faithful, fully-functional, free and open source</strong> version of the [[WoW:3.3.5a\|3.3.5a client]].		Thunderbrew is a non-commercial, open-source game preservation project for World of Warcraft: Wrath of the Lich King.

			Thunderbrew was started as a fork of [[Whoa]]. Like Whoa, it aims to provide a <strong>faithful, fully-functional, free and open source</strong> version of the [[WoW:3.3.5a\|3.3.5a client]].

	It aims to provide a more easily accessible and feature-rich version of Whoa, while retaining its original mission of high code quality and adherence to original behavior.		It aims to provide a more easily accessible and feature-rich version of Whoa, while retaining its original mission of high code quality and adherence to original behavior.

MediaWiki:Mainpage

Phaneron — Sat, 09 May 2026 23:22:11 GMT

Created page with "Thunderbrew"

New page

Thunderbrew

Thunderbrew:binana

Phaneron — Sat, 09 May 2026 19:37:59 GMT

← Older revision		Revision as of 19:37, 9 May 2026
(One intermediate revision by the same user not shown)
Line 2:		Line 2:
	{{Software		{{Software
	\|name = Binana		\|name = Binana
	\|type = Reverse-engineering ~~information~~		\|type = Reverse-engineering toolkit
	\|authors = Thunderbrew Developers		\|authors = Thunderbrew Developers
	\|license = The Unlicense		\|license = The Unlicense
Line 13:		Line 13:

	Over the years, many individuals have attempted to reverse engineer specific parts of the WoW client. These are usually siloed away into individual IDA Pro databases, making them difficult to locate, and thus more difficult to make use of for the purposes of game preservation.		Over the years, many individuals have attempted to reverse engineer specific parts of the WoW client. These are usually siloed away into individual IDA Pro databases, making them difficult to locate, and thus more difficult to make use of for the purposes of game preservation.

			Binana aims to avoid situations like this by storing RE work as machine-readable code in a public Git repository. This code can then be converted/parsed/encoded any way we like, usable in any tool you care to add support for!

	Binana is mainly targeted at version 3.3.5a of WoW. By reducing scope to a single version, the level of difficulty involved in implementing Whoa/Thunderbrew features is lowered significantly.		Binana is mainly targeted at version 3.3.5a of WoW. By reducing scope to a single version, the level of difficulty involved in implementing Whoa/Thunderbrew features is lowered significantly.

File:Pjt.gif

Phaneron — Sat, 09 May 2026 01:07:58 GMT

Phaneron uploaded File:Pjt.gif

New page

Thunderbrew:binana

Phaneron — Sat, 09 May 2026 01:04:52 GMT

← Older revision		Revision as of 01:04, 9 May 2026
(3 intermediate revisions by the same user not shown)
Line 8:		Line 8:
	}}		}}

	Binana is a centralized repository of reverse-engineering information.		Binana is a centralized repository of reverse-engineering information for various stripped binaries that are of interest to the [Thunderbrew] project.

			== Rationale ==

			Over the years, many individuals have attempted to reverse engineer specific parts of the WoW client. These are usually siloed away into individual IDA Pro databases, making them difficult to locate, and thus more difficult to make use of for the purposes of game preservation.

			Binana is mainly targeted at version 3.3.5a of WoW. By reducing scope to a single version, the level of difficulty involved in implementing Whoa/Thunderbrew features is lowered significantly.

	== Profiles ==		== Profiles ==

	~~Binana contents are split into profiles. Each~~ profile ~~contains information about~~ a ~~particular~~ binary.		A profile is a structured directory containing symbols and C headers that apply to a single binary sample.

	~~Currently~~, the ~~most fleshed-out profile is~~ <code>3.3.5a-windows-386</code>.		For instance, in the Binana repository, the <code>3.3.5a-windows-386</code> profile contains information for the i386 (x86) Windows version of the World of Warcraft client.

	=== Symbols ===		=== Symbols ===

	Each profile ~~contains~~ a ~~main.sym file~~. This ~~file~~ is ~~generated from various other~~ symbol files in the ~~profile~~.		Each profile consists of a symbol database. This database is text-based, and organized as a root <code>symbol</code> directory, and is filled with many subdirectories, which contain both <code>func.sym</code> and <code>label.sym</code> text files, pertaining to function symbols and data label symbols, respectively.

			The structure of a line (or entry) in the database is formatted thus:

			<pre>
			LabelName <hexadecimal absolute address> <f or l for function/label> [ attributes, or optional values, e.g. key=value key="value with spaces" ]
			</pre>

			A function file looks like this:

			<pre>
			FunctionName1 11223344 f end=22334455 type="void __stdcall func()"
			ClassName__MethodName 12345678 f end=23456789 type="void __thiscall func(ClassName* this, int32_t argument)"
			</pre>

			Our reverse-engineering tools cannot always detect the end address of a function (x64dbg cannot detect this at all!), so you should always give the end address of the function.

			For Binana, the convention for the end address of a function is the address that's 1 byte after the last instruction.

			For example, <code>0042830B</code> would be the end address of <code>WowConnection__AddRef</code>

			<pre>
			WowConnection__AddRef:
			00428300 b8 01 00 00 00 MOV EAX,0x1
			00428305 f0 0f c1 01 XADD.LOCK dword ptr [ECX],EAX
			00428309 40 INC EAX
			0042830a c3 RET
			------> 0042830b cc ?? CCh
			0042830c cc ?? CCh
			0042830d cc ?? CCh
			0042830e cc ?? CCh
			0042830f cc ?? CCh
			</pre>

	=== C headers ===		=== C headers ===

	A profile also contains a tree of C headers, which are used to expose type information into IDA Pro or Ghidra.		A profile also contains a tree of C headers, which are used to expose type information into IDA Pro or Ghidra.