Developer Mode - Revision history

Ruh at 20:25, 28 June 2025

2025-06-28T20:25:30Z

← Older revision		Revision as of 20:25, 28 June 2025
Line 1:		Line 1:
	[[File:Debug mode enabled jak1.png\|thumb\|Collision renderer being toggled on in The Precursor Legacy via advanced debugging tools.]]		[[File:Debug mode enabled jak1.png\|thumb\|Collision renderer being toggled on in The Precursor Legacy via advanced debugging tools.]]
	'''Developer mode''' is activated when the game boots with additional memory allocation, enabling advanced debugging tools that can be accessed via in-game menus. These debugging tools are available in the original Jak and Daxter trilogy, as well as Jak X: Combat Racing.		'''Developer mode''', often called '''dev mode''' for short, is activated when the game boots with additional memory allocation, enabling advanced debugging tools that can be accessed via in-game menus. These debugging tools are available in the original Jak and Daxter trilogy, as well as Jak X: Combat Racing.

	== Technical ==		== Technical ==

Ruh at 20:08, 28 June 2025

2025-06-28T20:08:31Z

← Older revision		Revision as of 20:08, 28 June 2025
Line 5:		Line 5:
	Activation of developer mode is toggled independently from the [[Cheat Mode\|cheat mode]] variable. It relies entirely on whether extra memory is allocated for debugging tools or not.		Activation of developer mode is toggled independently from the [[Cheat Mode\|cheat mode]] variable. It relies entirely on whether extra memory is allocated for debugging tools or not.

	The easiest way to play the game with debugging tools enabled is to boot the game using the 'Play in Debug Mode' boot option in the [https://opengoal.dev OpenGOAL launcher]]. Other methods include emulating the game with xTVaser's PCSX2 128MB build or booting the game in a PlayStation 2 TOOL (DTL-T10000H) development console.		The easiest way to play the game with debugging tools enabled is to boot the game using the 'Play in Debug Mode' boot option in the [https://opengoal.dev OpenGOAL launcher]. Other methods include emulating the game with xTVaser's PCSX2 128MB build or booting the game in a PlayStation 2 TOOL (DTL-T10000H) development console.

	== Discovery ==		== Discovery ==

	{{Glitches}}		{{Glitches}}

Ruh: /* Technical */

2025-06-28T20:08:25Z

Technical

← Older revision		Revision as of 20:08, 28 June 2025
Line 4:		Line 4:
	== Technical ==		== Technical ==
	Activation of developer mode is toggled independently from the [[Cheat Mode\|cheat mode]] variable. It relies entirely on whether extra memory is allocated for debugging tools or not.		Activation of developer mode is toggled independently from the [[Cheat Mode\|cheat mode]] variable. It relies entirely on whether extra memory is allocated for debugging tools or not.

			The easiest way to play the game with debugging tools enabled is to boot the game using the 'Play in Debug Mode' boot option in the [https://opengoal.dev OpenGOAL launcher]]. Other methods include emulating the game with xTVaser's PCSX2 128MB build or booting the game in a PlayStation 2 TOOL (DTL-T10000H) development console.

	== Discovery ==		== Discovery ==

	{{Glitches}}		{{Glitches}}

Ruh at 20:04, 28 June 2025

2025-06-28T20:04:30Z

← Older revision		Revision as of 20:04, 28 June 2025
Line 3:		Line 3:

	== Technical ==		== Technical ==
			Activation of developer mode is toggled independently from the [[Cheat Mode\|cheat mode]] variable. It relies entirely on whether extra memory is allocated for debugging tools or not.

	== Discovery ==		== Discovery ==

	{{Glitches}}		{{Glitches}}

Ruh at 20:01, 28 June 2025

2025-06-28T20:01:39Z

← Older revision		Revision as of 20:01, 28 June 2025
Line 1:		Line 1:
	[[File:Debug mode enabled jak1.png\|thumb\|Collision renderer being toggled on in The Precursor Legacy via advanced debugging tools.]]		[[File:Debug mode enabled jak1.png\|thumb\|Collision renderer being toggled on in The Precursor Legacy via advanced debugging tools.]]
	'''Developer mode''' is activated when the game boots with additional memory allocation, enabling advanced debugging tools that can be accessed via in-game menus. These debugging tools are available in the original Jak and Daxter trilogy, as well as Jak X: Combat Racing.		'''Developer mode''' is activated when the game boots with additional memory allocation, enabling advanced debugging tools that can be accessed via in-game menus. These debugging tools are available in the original Jak and Daxter trilogy, as well as Jak X: Combat Racing.

			== Technical ==

			== Discovery ==

			{{Glitches}}

Ruh: Created page with "Collision renderer being toggled on in The Precursor Legacy via advanced debugging tools. '''Developer mode''' is activated when the game boots with additional memory allocation, enabling advanced debugging tools that can be accessed via in-game menus. These debugging tools are available in the original Jak and Daxter trilogy, as well as Jak X: Combat Racing."

2025-06-28T20:01:09Z

Created page with "thumb|Collision renderer being toggled on in The Precursor Legacy via advanced debugging tools. '''Developer mode''' is activated when the game boots with additional memory allocation, enabling advanced debugging tools that can be accessed via in-game menus. These debugging tools are available in the original Jak and Daxter trilogy, as well as Jak X: Combat Racing."

New page

[[File:Debug mode enabled jak1.png|thumb|Collision renderer being toggled on in The Precursor Legacy via advanced debugging tools.]]
'''Developer mode''' is activated when the game boots with additional memory allocation, enabling advanced debugging tools that can be accessed via in-game menus. These debugging tools are available in the original Jak and Daxter trilogy, as well as Jak X: Combat Racing.