Rayman Designer hacking - Revision history

Hunchman801: Fixed links to redirects

2025-08-20T06:29:41Z

Fixed links to redirects

Hunchman801: Fixed links to redirects

2025-05-29T09:31:27Z

Fixed links to redirects

← Older revision		Revision as of 09:31, 29 May 2025
Line 214:		Line 214:

	<gallery widths="316px" heights="200px" class="sprite">		<gallery widths="316px" heights="200px" class="sprite">
	GiantLavaBall.png\|A giant [[lava ~~ball~~]], acting as scenery.		GiantLavaBall.png\|A giant [[lava rock]], acting as scenery.
	BetaClouds.png\|[[Cloud]]s with a face (known from the Atari Jaguar version). The ones to the right act like disappearing clouds.		BetaClouds.png\|[[Cloud]]s with a face (known from the Atari Jaguar version). The ones to the right act like disappearing clouds.
	SmallLivingstonePlum.png\|A [[little Livingstone]] on a bouncing [[plum]].		SmallLivingstonePlum.png\|A [[little Livingstone]] on a bouncing [[plum]].
Line 265:		Line 265:
	Through some editing of the game, the following things have been discovered:		Through some editing of the game, the following things have been discovered:

	*If events are placed in groups beyond group 9, it is found that these groups have the same names as the game's levels. This reveals the names of six additional levels. It seems that they have been cut from the final game (or never been finished): "The Gates of the Jungle" ([[The Dream Forest]]), "Diabolical Tunes" ([[Band Land]]), "The Fire Avalanche" ([[~~The~~ Blue Mountains]]), "Miniature Madness" ([[Picture City]]), "Cloud of Doom" ([[The Caves of Skops]]) and "Dessert Anyone?" ([[Candy Château]]).		*If events are placed in groups beyond group 9, it is found that these groups have the same names as the game's levels. This reveals the names of six additional levels. It seems that they have been cut from the final game (or never been finished): "The Gates of the Jungle" ([[The Dream Forest]]), "Diabolical Tunes" ([[Band Land]]), "The Fire Avalanche" ([[Blue Mountains]]), "Miniature Madness" ([[Picture City]]), "Cloud of Doom" ([[The Caves of Skops]]) and "Dessert Anyone?" ([[Candy Château]]).

	*A sprite from [[Rayman 2 (2D prototype)\|the 2D version of ''Rayman 2'']] could be found in the sprite files (a small platform that looks like a teleporter).		*A sprite from [[Rayman 2 (cancelled prototype)\|the 2D version of ''Rayman 2'']] could be found in the sprite files (a small platform that looks like a teleporter).

	*The spritefiles also contain a considerable amount of content from the ''[[Rayman Junior]]'' (such as the world map icons) and some never-before-seen sprites.		*The spritefiles also contain a considerable amount of content from the ''[[Rayman Junior]]'' (such as the world map icons) and some never-before-seen sprites.

Hunchman801: Code clean-up, formatting and standardization

2025-04-09T12:51:07Z

Code clean-up, formatting and standardization

← Older revision		Revision as of 12:51, 9 April 2025
Line 2:		Line 2:

	==Graphics==		==Graphics==

	=== Tiles ===		=== Tiles ===
	In every world-folder (for example "[[The Dream Forest\|jungle]]" or "[[Band Land\|music]]") of the game, there is a .PCX graphic file. It contains all the graphic tiles which are used by the Mapper and the levels created from it. Tiles can be changed and added, but the following should not be changed:		In every world-folder (for example "[[The Dream Forest\|jungle]]" or "[[Band Land\|music]]") of the game, there is a .PCX graphic file. It contains all the graphic tiles which are used by the Mapper and the levels created from it. Tiles can be changed and added, but the following should not be changed:
Line 21:		Line 20:

	==[[Event (Rayman Designer)\|Events]]==		==[[Event (Rayman Designer)\|Events]]==

	=== Editing events ===		=== Editing events ===
	In every world-folder of the game, there is a file called EVE.MLT. It contains the manifest of the events of the current world and can be modified using a text editor. The events are structured in this way:		In every world-folder of the game, there is a file called EVE.MLT. It contains the manifest of the events of the current world and can be modified using a text editor. The events are structured in this way:

Hunchman801: clean up

2023-09-25T14:51:00Z

clean up

← Older revision		Revision as of 14:51, 25 September 2023
Line 260:		Line 260:
	==The Extended ''Rayman Designer'' Editor==		==The Extended ''Rayman Designer'' Editor==

	This is an unofficial tool that makes ''[[Rayman Designer]]'' modding much easier. It also comes with a large content package which includes a great deal of content from ''[[Rayman 1\|Rayman]]'' and ''[[Rayman Junior]]'' that was not available in ''Rayman Designer'', and also some new unofficial content.		This is an unofficial tool that makes ''[[Rayman Designer]]'' modding much easier. It also comes with a large content package which includes a great deal of content from ''[[Rayman 1\|Rayman]]'' and ''[[Rayman Junior]]'' that was not available in ''Rayman Designer'', and also some new unofficial content.

	*Download: http://www.rayman-fanpage.de/character/raymans_world_designer/RDeditor.exe		*Download: http://www.rayman-fanpage.de/character/raymans_world_designer/RDeditor.exe
Line 271:		Line 271:
	*A sprite from [[Rayman 2 (2D prototype)\|the 2D version of ''Rayman 2'']] could be found in the sprite files (a small platform that looks like a teleporter).		*A sprite from [[Rayman 2 (2D prototype)\|the 2D version of ''Rayman 2'']] could be found in the sprite files (a small platform that looks like a teleporter).

	*The spritefiles also contain a considerable amount of content from the ''[[Rayman Junior]]'' (such as the world map icons) and some never-before-seen sprites.		*The spritefiles also contain a considerable amount of content from the ''[[Rayman Junior]]'' (such as the world map icons) and some never-before-seen sprites.

	{{Rayman 1}}		{{Rayman 1}}
	[[Category:Other]]		[[Category:Other]]

Hunchman801 at 13:29, 4 July 2022

2022-07-04T13:29:27Z

← Older revision		Revision as of 13:29, 4 July 2022
Line 218:		Line 218:
	GiantLavaBall.png\|A giant [[lava ball]], acting as scenery.		GiantLavaBall.png\|A giant [[lava ball]], acting as scenery.
	BetaClouds.png\|[[Cloud]]s with a face (known from the Atari Jaguar version). The ones to the right act like disappearing clouds.		BetaClouds.png\|[[Cloud]]s with a face (known from the Atari Jaguar version). The ones to the right act like disappearing clouds.
	SmallLivingstonePlum.png\|A [[~~small~~ Livingstone]] on a bouncing [[plum]].		SmallLivingstonePlum.png\|A [[little Livingstone]] on a bouncing [[plum]].
	Big rock.png\|A giant [[rock]].		Big rock.png\|A giant [[rock]].
	Bouncing Mr. Sax obstacle.png\|A [[wrong note]] from [[Mr Sax]]. Here it can be punched to move like a [[plum]].		Bouncing Mr. Sax obstacle.png\|A [[wrong note]] from [[Mr Sax]]. Here it can be punched to move like a [[plum]].

Ray502 at 17:51, 7 February 2022

2022-02-07T17:51:32Z

← Older revision		Revision as of 17:51, 7 February 2022
Line 273:		Line 273:
	*The spritefiles also contain a considerable amount of content from the ''[[Rayman Junior]]'' (such as the world map icons) and some never-before-seen sprites.		*The spritefiles also contain a considerable amount of content from the ''[[Rayman Junior]]'' (such as the world map icons) and some never-before-seen sprites.

			{{Rayman 1}}
	[[Category:Other]]		[[Category:Other]]

RayCarrot at 15:47, 7 February 2022

2022-02-07T15:47:01Z

← Older revision		Revision as of 15:47, 7 February 2022
Line 67:		Line 67:
	'''Event commands'''		'''Event commands'''

	The event commands will repeat themselves when they come to the end. The complete list is as follows:		The event commands will repeat themselves when they come to the end. Ones marked as self-handled will have different behavior depending on the object type and current state. The command names come from leftover debug information in the GameBoy Advance version. The complete list is as follows:

	{\| class="wikitable"		{\| class="wikitable"
Line 77:		Line 77:
	\| 0, {arg1}		\| 0, {arg1}
	\| GO_LEFT		\| GO_LEFT
	\| ~~Sprite~~ moves left ~~({arg1} = time in milliseconds, max. 254)~~		\| (Self-handled) Object moves left
	\|-		\|-
	\| 1, {arg1}		\| 1, {arg1}
	\| GO_RIGHT		\| GO_RIGHT
	\| ~~Sprite~~ moves right ~~({arg1} = time in milliseconds, max. 254)~~		\| (Self-handled) Object moves right
	\|-		\|-
	\| 2		\| 2
	\| GO_WAIT		\| GO_WAIT
	\| ?		\| (Self-handled) Object stops moving
	\|-		\|-
	\| 3, {arg1}		\| 3, {arg1}
	\| GO_UP		\| GO_UP
	\| Sprite moves up ~~({arg1} = time in milliseconds, max. 254)~~		\| (Self-handled) Sprite moves up
	\|-		\|-
	\| 4, {arg1}		\| 4, {arg1}
	\| GO_DOWN		\| GO_DOWN
	\| Sprite moves down ~~({arg1} = time in milliseconds, max. 254)~~		\| (Self-handled) Sprite moves down
	\|-		\|-
	\| 5, {arg1}		\| 5, {arg1}
	\| GO_SUBSTATE		\| GO_SUBSTATE
	\| Set SubEtat (~~sprite coord. b~~) to {arg1}		\| Set object SubEtat (secondary state) to {arg1}
	\|-		\|-
	\| 6, {arg1}		\| 6, {arg1}
	\| GO_SKIP		\| GO_SKIP
	\| Skips {arg1} ~~arguments~~		\| Skips {arg1} commands
	\|-		\|-
	\| 7		\| 7
	\| GO_ADD		\| GO_ADD
	\| ?		\| (Self-handled) ?
	\|-		\|-
	\| 8, {arg1}		\| 8, {arg1}
	\| GO_STATE		\| GO_STATE
	\| Set Etat (~~sprite coord. a~~) to {arg1}		\| Set object Etat (primary state) to {arg1}
	\|-		\|-
	\| 9, {arg1}		\| 9, {arg1}
Line 137:		Line 137:
	\| 15, {arg1}		\| 15, {arg1}
	\| GO_BRANCHTRUE		\| GO_BRANCHTRUE
	\| Skips to label {arg1} if true		\| Skips to label {arg1} if TEST is true
	\|-		\|-
	\| 16, {arg1}		\| 16, {arg1}
	\| GO_BRANCHFALSE		\| GO_BRANCHFALSE
	\| Skips to label {arg1} if false		\| Skips to label {arg1} if TEST is false
	\|-		\|-
	\| 17, {arg1}[, {arg2}]		\| 17, {arg1}[, {arg2}]
Line 153:		Line 153:
	\| 19, {arg1}		\| 19, {arg1}
	\| GO_WAITSTATE		\| GO_WAITSTATE
	\| Waits {arg1} ~~seconds~~		\| Waits {arg1}
	\|-		\|-
	\| 20, {arg1}, {arg2}, {arg3}		\| 20, {arg1}, {arg2}, {arg3}
	\| GO_SPEED		\| GO_SPEED
	\| Moves ~~for~~ {arg1} ~~seconds (max. 254)~~ with speed X {arg2} and Y {arg3}		\| (Self-handled) Moves {arg1} with speed X {arg2} and Y {arg3}
	\|-		\|-
	\| 21, {arg1}, {arg2}		\| 21, {arg1}, {arg2}
Line 181:		Line 181:
	\| 26, {arg1}		\| 26, {arg1}
	\| RESERVED_GO_GOTOT		\| RESERVED_GO_GOTOT
	\| Skips to LabelOffsets[{arg1}] if true		\| Skips to LabelOffsets[{arg1}] if TEST is true
	\|-		\|-
	\| 27, {arg1}		\| 27, {arg1}
	\| RESERVED_GO_GOTOF		\| RESERVED_GO_GOTOF
	\| Skips to LabelOffsets[{arg1}] if false		\| Skips to LabelOffsets[{arg1}] if TEST is false
	\|-		\|-
	\| 28, {arg1}		\| 28, {arg1}
Line 197:		Line 197:
	\| 30		\| 30
	\| GO_NOP		\| GO_NOP
	\| ?		\| (Self-handled) ?
	\|-		\|-
	\| 31, {arg1}		\| 31, {arg1}
	\| GO_SKIPTRUE		\| GO_SKIPTRUE
	\| Skips {arg1} commands if true		\| Skips {arg1} commands if TEST is true
	\|-		\|-
	\| 32, {arg1}		\| 32, {arg1}
	\| GO_SKIPFALSE		\| GO_SKIPFALSE
	\| Skips {arg1} commands if false		\| Skips {arg1} commands if TEST is false
	\|-		\|-
	\| 33, {arg1}		\| 33, {arg1}
	\| INVALID_CMD		\| INVALID_CMD
	\| Terminates the commands and loops back, {arg1} is always 0xFF which is used as the command ~~array~~ terminator		\| Terminates the commands and loops back, {arg1} is always 0xFF which is used as the command buffer terminator
	\|-
	~~\| 66, {arg1}~~
	~~\| INVALID_CMD_DEMO~~
	~~\| Used in the PS1 demos~~
	\|}		\|}

Hunchman801: Integrated event command data from https://github.com/BinarySerializer/BinarySerializer.Ray1/blob/main/src/BinarySerializer.Ray1/DataTypes/Common/CMD/CommandType.cs

2022-02-07T12:51:31Z

Integrated event command data from https://github.com/BinarySerializer/BinarySerializer.Ray1/blob/main/src/BinarySerializer.Ray1/DataTypes/Common/CMD/CommandType.cs

Show changes

RayCarrot: Some corrections

2020-10-01T12:31:45Z

Some corrections

← Older revision		Revision as of 12:31, 1 October 2020
Line 23:		Line 23:

	=== Editing events ===		=== Editing events ===
	In every world-folder of the game, there is a file called EVE.MLT. It contains the manifest of the events of the current world and can be modified using a text editor~~. The manifest is written in an in-house engine command format~~. The events are structured in this way:		In every world-folder of the game, there is a file called EVE.MLT. It contains the manifest of the events of the current world and can be modified using a text editor. The events are structured in this way:


	{\| width="auto" align="center" style="border-style:dotted;border-width:1mm;border-color:green;text-align:left"		{\| width="auto" align="center" style="border-style:dotted;border-width:1mm;border-color:green;text-align:left"
	\|œdef,~~eventID~~,DES_FILE,~~z-index~~,		\|œdef,ms_name,DES_FILE,display_prio,
	FILE.ETA,		FILE.ETA,

	eventCommands		eventCommands,

	~~33,255~~,

	main_X_pos, main_Y_pos,		main_X_pos, main_Y_pos,
Line 47:		Line 45:
	'''Caption:'''		'''Caption:'''

	*œdef = ~~define; this must come first~~		*œdef = defines the beginning of an event definition
	*~~eventID~~ = the event ID. This is used to specify the event in the editor as well as to get the localized name.		*ms_name = the internal event name. This is used to specify the event in the editor as well as to get the localized name.
	*DES_FILE = name of the graphic file which should be used for the event (without the extension ".DES")		*DES_FILE = name of the graphic file which should be used for the event (without the extension ".DES")
	*~~z-index~~ = the ~~z-index~~, specifying the order the sprite should be drawn on screen (a value between 1-7)		*display_prio = the display priority, specifying the order the sprite should be drawn on screen (a value between 1-7)
	*FILE.ETA = name of the state file which should be used		*FILE.ETA = name of the state file which should be used
	*eventCommands = the non-compiled event commands (these have to use local offsets due to not having been compiled with label offsets yet)		*eventCommands = the non-compiled event commands (these have to use local offsets due to not having been compiled with label offsets yet)
	*33,255 = the command termination (33 is invalid command with the argument 0xFF)		*main_X_pos = main x coordinate of the event (irrelevant since the player places the object themselves)
	*main_X_pos = main x coordinate of the event		*main_Y_pos = main y coordinate of the event (irrelevant since the player places the object themselves)
	*main_Y_pos = main y coordinate of the event
	*etat = the primary event state		*etat = the primary event state
	*sub_etat = the secondary event state		*sub_etat = the secondary event state
	*Offset_BX = is the x ~~coordinate~~ of the ~~point on the sprite on which Rayman can stand (if "Follow_enabled" is 1)~~		*Offset_BX = the x position of the pivot
	*Offset_BY = is the ~~y1 coordinate~~ of the ~~point on the sprite on which Rayman can stand (if "Follow_enabled" is 1)~~		*Offset_BY = the y position of the pivot
	*Offset_HY = is the y2 coordinate of the point on the sprite on which Rayman can stand (if "Follow_enabled" is 1)		*Offset_HY = the y coordinate of the point on the sprite on which Rayman can stand if Follow_enabled is true, relative to the follow_sprite
	*Follow_enabled = whether or not Rayman can stand on this event ("follow" its movement), either 0 or 1		*Follow_enabled = indicates whether or not Rayman can stand on this event ("follow" its movement), either 0 or 1 (true or false)
	*follow_sprite = the sprite index which the player can stand on		*follow_sprite = the sprite index which the player can stand on if Follow_enabled is true
	*hitpoints = for enemies like [[hunter]]s, how much [[resistance]] the event has. However, for many events this number has a different meaning, such as specifying if the sprite should appear flipped.		*hitpoints = for enemies like [[hunter]]s, how much [[resistance]] the event has. However, for many events this number has a different meaning, such as specifying if the sprite should appear flipped, the palette offset etc.
	*obj_type = this is the event object type. All types are hard-coded in the engine and specifies how the event should be treated.		*obj_type = this is the event object type. All types are hard-coded in the engine and specifies how the event should be treated.
	*hit_sprite = ~~unsure~~		*hit_sprite = if below 253 it specifies the sprite which is treated as a hitbox. If above 253 it specifies the event uses the hitbox belonging to the obj_type.
	*group = in which group the event can be found in the Events Editor. For example, the "Enemies" group is group 5.		*group = in which group the event can be found in the Events Editor. For example, the "Enemies" group is group 5.

Line 89:		Line 86:

	A complete list of the event commands can be found here:		A complete list of the event commands can be found here:
	* https://github.com/Adsolution/Ray1Map/blob/master/Assets/Scripts/DataTypes/Common/~~Serializable~~/~~Events~~/~~EventCommand~~.cs		* https://github.com/Adsolution/Ray1Map/blob/master/Assets/Scripts/DataTypes/Rayman1/Common/Events/Commands/R1_EventCommandType.cs

	=== Unused events ===		=== Unused events ===

Hunchman801 at 08:57, 31 March 2020

2020-03-31T08:57:30Z

← Older revision		Revision as of 08:57, 31 March 2020
Line 14:		Line 14:

	=== Sprites ===		=== Sprites ===
	All animated sprites of the game (for example, [[Rayman]] himself and enemies) are stored in the .DES files, short for dessin, French for drawing. These files are packed in the .WLD, AllFix and BigRay files, which are stored in the "pcmap" folder. The .DES files contain the image data and animation information.		All animated sprites of the game (for example, [[Rayman]] himself and enemies) are stored in the .DES files, short for ''dessin'', French for drawing. These files are packed in the .WLD, AllFix and BigRay files, which are stored in the "pcmap" folder. The .DES files contain the image data and animation information.

	ETA files, short for état, French for state, are stored in the same files. They contain information about the event states, specified by Etat and SubEtat.		ETA files, short for ''état'', French for state, are stored in the same files. They contain information about the event states, specified by Etat and SubEtat.

	The file names for the .DES and .ETA files are only included in ''[[Rayman Designer]]'' and its spin-offs. In all previous games they are only refereed to by the index they're loaded into the game.		The file names for the .DES and .ETA files are only included in ''[[Rayman Designer]]'' and its spin-offs. In all previous games they are only refereed to by the index they're loaded into the game.
Line 68:		Line 68:
	*group = in which group the event can be found in the Events Editor. For example, the "Enemies" group is group 5.		*group = in which group the event can be found in the Events Editor. For example, the "Enemies" group is group 5.

	'''Event ~~Commands~~'''		'''Event commands'''

	The event commands will repeat ~~itself~~ when ~~it comes~~ to the end.		The event commands will repeat themselves when they come to the end.

	*0, x, -> sprite moves right (x = time in milliseconds, max. 254)		*0, x, -> sprite moves right (x = time in milliseconds, max. 254)
Line 88:		Line 88:
	*20, t, x, y, -> sprite moves for t milliseconds (max. 254) with velocity given by x and y.		*20, t, x, y, -> sprite moves for t milliseconds (max. 254) with velocity given by x and y.

	A complete list of the event commands can be found here: https://github.com/Adsolution/Ray1Map/blob/master/Assets/Scripts/DataTypes/Common/Serializable/Events/EventCommand.cs		A complete list of the event commands can be found here:
			* https://github.com/Adsolution/Ray1Map/blob/master/Assets/Scripts/DataTypes/Common/Serializable/Events/EventCommand.cs

	=== Unused events ===		=== Unused events ===

← Older revision		Revision as of 13:29, 4 July 2022
Line 218:		Line 218:
	GiantLavaBall.png\|A giant [[lava ball]], acting as scenery.		GiantLavaBall.png\|A giant [[lava ball]], acting as scenery.
	BetaClouds.png\|[[Cloud]]s with a face (known from the Atari Jaguar version). The ones to the right act like disappearing clouds.		BetaClouds.png\|[[Cloud]]s with a face (known from the Atari Jaguar version). The ones to the right act like disappearing clouds.
	SmallLivingstonePlum.png\|A [[~~small~~ Livingstone]] on a bouncing [[plum]].		SmallLivingstonePlum.png\|A [[little Livingstone]] on a bouncing [[plum]].
	Big rock.png\|A giant [[rock]].		Big rock.png\|A giant [[rock]].
	Bouncing Mr. Sax obstacle.png\|A [[wrong note]] from [[Mr Sax]]. Here it can be punched to move like a [[plum]].		Bouncing Mr. Sax obstacle.png\|A [[wrong note]] from [[Mr Sax]]. Here it can be punched to move like a [[plum]].

← Older revision		Revision as of 06:29, 20 August 2025
Line 220:		Line 220:
	Bouncing Mr. Sax obstacle.png\|A [[wrong note]] from [[Mr Sax]]. Here it can be punched to move like a [[plum]].		Bouncing Mr. Sax obstacle.png\|A [[wrong note]] from [[Mr Sax]]. Here it can be punched to move like a [[plum]].
	Clocks.png\|The clocks from the [[continue]] screen, acting as scenery.		Clocks.png\|The clocks from the [[continue]] screen, acting as scenery.
	Insta-kill events.png\|Several red insta-kill events, previously seen in ''[[Rayman ~~Junior~~]]''.		Insta-kill events.png\|Several red insta-kill events, previously seen in ''[[Maths and English with Rayman]]''.
	Road signs.png\|A bunch of colored road signs, acting as scenery.		Road signs.png\|A bunch of colored road signs, acting as scenery.
	Tarayzan Designer.png\|[[Tarayzan]] as a functioning event, except for the text not displaying when he gives [[Rayman]] the [[Magic seed\|seed]].		Tarayzan Designer.png\|[[Tarayzan]] as a functioning event, except for the text not displaying when he gives [[Rayman]] the [[Magic seed\|seed]].
Line 258:		Line 258:
	==The Extended ''Rayman Designer'' Editor==		==The Extended ''Rayman Designer'' Editor==

	This is an unofficial tool that makes ''[[Rayman Designer]]'' modding much easier. It also comes with a large content package which includes a great deal of content from ''[[Rayman 1\|Rayman]]'' and ''[[Rayman ~~Junior~~]]'' that was not available in ''Rayman Designer'', and also some new unofficial content.		This is an unofficial tool that makes ''[[Rayman Designer]]'' modding much easier. It also comes with a large content package which includes a great deal of content from ''[[Rayman 1\|Rayman]]'' and ''[[Maths and English with Rayman]]'' that was not available in ''Rayman Designer'', and also some new unofficial content.

	*Download: http://www.rayman-fanpage.de/character/raymans_world_designer/RDeditor.exe		*Download: http://www.rayman-fanpage.de/character/raymans_world_designer/RDeditor.exe
Line 269:		Line 269:
	*A sprite from [[Rayman 2 (cancelled prototype)\|the 2D version of ''Rayman 2'']] could be found in the sprite files (a small platform that looks like a teleporter).		*A sprite from [[Rayman 2 (cancelled prototype)\|the 2D version of ''Rayman 2'']] could be found in the sprite files (a small platform that looks like a teleporter).

	*The spritefiles also contain a considerable amount of content from the ''[[Rayman ~~Junior~~]]'' (such as the world map icons) and some never-before-seen sprites.		*The spritefiles also contain a considerable amount of content from the ''[[Maths and English with Rayman]]'' (such as the world map icons) and some never-before-seen sprites.

	{{Rayman 1}}		{{Rayman 1}}
	[[Category:Other]]		[[Category:Other]]