PZX - Revision history

Zzo38: cjb net is broke

2012-09-18T08:10:59Z

cjb net is broke

← Older revision		Revision as of 08:10, 18 September 2012
Line 1:		Line 1:
	'''PZX''', or ProngZeux, is a fork of [[MegaZeux]] written by [[zzo38]] that focuses primarily on support for [http://en.wikipedia.org/wiki/Forth_(programming_language) FORTH], a low-level, stack-driven programming language.		'''PZX''', or ProngZeux, is a fork of [[MegaZeux]] written by [[zzo38]] that focuses primarily on support for [http://en.wikipedia.org/wiki/Forth_(programming_language) FORTH], a low-level, stack-driven programming language.

	* Win32 binaries and source-codes is available at: http://zzo38computer.~~cjb.net~~/mzx1/mzx_extended/		* Win32 binaries and source-codes is available at: http://zzo38computer.org/mzx1/mzx_extended/
	* Documentation is available at: http://zzo38computer.~~cjb.net~~/mzx1/mzx_extended/doc/		* Documentation is available at: http://zzo38computer.org/mzx1/mzx_extended/doc/

	==Features==		==Features==

Zzo38 at 03:23, 27 November 2010

2010-11-27T03:23:26Z

← Older revision		Revision as of 03:23, 27 November 2010
Line 89:		Line 89:
	* EV.ENTERED ( category -- ) When the board is switched		* EV.ENTERED ( category -- ) When the board is switched
	* EV.BULLETHIT ( offset bulletoffset parameter -- category ) Indicates that a bullet is about to hit something solid		* EV.BULLETHIT ( offset bulletoffset parameter -- category ) Indicates that a bullet is about to hit something solid
			* EV.GLOBAL ( slowed slowdown -- slowed ) Called on every cycle

	These events are corresponding to specific objects (add the extended kind number to the event code):		These events are corresponding to specific objects (add the extended kind number to the event code):

Zzo38 at 05:54, 17 November 2010

2010-11-17T05:54:35Z

← Older revision		Revision as of 05:54, 17 November 2010
Line 169:		Line 169:

	1 VARIABLE NEEDS-GEM-MESSAGE		1 VARIABLE NEEDS-GEM-MESSAGE
	$81 4 A_ITEM A_PUSHABLE + 0 EXTKIND ZztGem		$81 4 A_ITEM A_PUSHABLE + A_CRUSH + A_SHOOTABLE + 0 EXTKIND ZztGem
	ZztGem EV.ITEM + :EVENT		ZztGem EV.ITEM + :EVENT
	DROP DROP 1 BISFX		DROP DROP 1 BISFX

Zzo38: ZZT Gems

2010-11-17T05:52:22Z

ZZT Gems

@@ Line 163: / Line 163: @@
+  ;
 And this signals the end of the event code, and exits compile mode.
 [[Category:MegaZeux]]

Zzo38 at 11:38, 26 June 2010

2010-06-26T11:38:02Z

← Older revision		Revision as of 11:38, 26 June 2010
Line 110:		Line 110:

	===ZZT Keys===		===ZZT Keys===
	Here is a code to implement a ZZT key:		Here is a code to implement a ZZT key (please note this is a simplified version, its only function here is to disallow you from holding multiple keys of the same color):
	INCLUDE megazeux.4th		INCLUDE megazeux.4th

Kkairos: category:mzx

2010-01-14T08:37:14Z

category:mzx

← Older revision		Revision as of 08:37, 14 January 2010
Line 163:		Line 163:
	;		;
	And this signals the end of the event code, and exits compile mode.		And this signals the end of the event code, and exits compile mode.

			[[Category:MegaZeux]]

Zzo38: documentation link

2009-09-13T00:11:57Z

documentation link

← Older revision		Revision as of 00:11, 13 September 2009
Line 1:		Line 1:
	'''PZX''', or ProngZeux, is a fork of [[MegaZeux]] written by [[zzo38]] that focuses primarily on support for [http://en.wikipedia.org/wiki/Forth_(programming_language) FORTH], a low-level, stack-driven programming language.		'''PZX''', or ProngZeux, is a fork of [[MegaZeux]] written by [[zzo38]] that focuses primarily on support for [http://en.wikipedia.org/wiki/Forth_(programming_language) FORTH], a low-level, stack-driven programming language.

			* Win32 binaries and source-codes is available at: http://zzo38computer.cjb.net/mzx1/mzx_extended/
			* Documentation is available at: http://zzo38computer.cjb.net/mzx1/mzx_extended/doc/

	==Features==		==Features==

Zzo38 at 19:39, 25 June 2009

2009-06-25T19:39:12Z

← Older revision		Revision as of 19:39, 25 June 2009
Line 106:		Line 106:
	Please note that all examples are case-insensitive, just like anything else in MegaZeux.		Please note that all examples are case-insensitive, just like anything else in MegaZeux.

	==ZZT Keys==		===ZZT Keys===
	Here is a code to implement a ZZT key:		Here is a code to implement a ZZT key:
	INCLUDE megazeux.4th		INCLUDE megazeux.4th

Zzo38 at 05:28, 20 June 2009

2009-06-20T05:28:09Z

← Older revision		Revision as of 05:28, 20 June 2009
Line 148:		Line 148:
	IF		IF
	Now we are entering a conditional block. The last value that hasn't been used yet is the success of TAKEKEY. So, the part between IF and ELSE is the true part (success taking the key away from the player), the part between ELSE and THEN is the false part (the key couldn't be taken, so it was given)		Now we are entering a conditional block. The last value that hasn't been used yet is the success of TAKEKEY. So, the part between IF and ELSE is the true part (success taking the key away from the player), the part between ELSE and THEN is the false part (the key couldn't be taken, so it was given)
			"You already have the key!" SETMESG 9 BISFX
			Gives the player a message and plays a sound effect.
			0
			Zero is the value returned from the event (the "remove" parameter), meaning the object shouldn't be removed from the screen.
			ELSE "You now have the key." SETMESG 8 BISFX
			Another message and sound effect.
			1
			Any non-zero value means the object will be removed from the screen (because the player has just picked up the key).
			THEN
			The end of a conditional block. If using the word THEN here confuses you, you can use a code to make ENDIF work instead, but the reason THEN is used is because this is a different kind of THEN than it is is BASIC, in Forth the THEN is like "do this, and then do this..." rather than "if this then this..."
			;
			And this signals the end of the event code, and exits compile mode.

Zzo38 at 05:24, 20 June 2009

2009-06-20T05:24:46Z

← Older revision		Revision as of 05:24, 20 June 2009
Line 102:		Line 102:
	* EV.BEFOREADDBOARD ( -- ? ) Before a new board is being added, the current board will be the old current board		* EV.BEFOREADDBOARD ( -- ? ) Before a new board is being added, the current board will be the old current board
	* EV.AFTERADDBOARD ( ? -- ) After a new board is added, during processing of event the current board will be the newly added board, even if it would change back afterward		* EV.AFTERADDBOARD ( ? -- ) After a new board is added, during processing of event the current board will be the newly added board, even if it would change back afterward

			==Examples of Forth Codes==
			Please note that all examples are case-insensitive, just like anything else in MegaZeux.

			==ZZT Keys==
			Here is a code to implement a ZZT key:
			INCLUDE megazeux.4th

			$80 12 A_ITEM A_PUSHABLE + 0 EXTKIND ZztKey
			ZztKey EV.ITEM + :EVENT
			DROP BOARD_COLOR + @ DUP TAKEKEY SWAP GIVEKEY DROP
			IF
			"You already have the key!" SETMESG 9 BISFX 0
			ELSE
			"You now have the key." SETMESG 8 BISFX 1
			THEN
			;
			I will explain each line and part of line one by one so that you can follow:
			INCLUDE megazeux.4th
			This loads the standard libraries of Forth codes.
			$80
			We will assign number 0x80 (128 in decimal) to the new kind of object. Only numbers 0x80 to 0xFE (128 to 254) can be used, because other numbers are used by built-ins. (Dollar signs indicate hexadecimal numbers in Forth codes)
			12
			This means it will display as character 12.
			A_ITEM A_PUSHABLE +
			This object will have the A_ITEM and A_PUSHABLE flags (meaning it is pushable by anything other than the player, and the player can interact with it).
			0
			It will not ask for a parameter when placed in the editor.
			EXTKIND ZztKey
			Creates the extended kind using the values from the stack, and calls it ZztKey. The name ZztKey is now used in the editor and can be used in Robotic codes as well. It is also usable in Forth codes as a constant.
			ZztKey EV.ITEM + :EVENT
			Adding ZztKey to EV.ITEM gets the number of the item event for the ZztKey. :EVENT tells it to start compiling an event code.
			DROP
			The top parameter passed to the EV.ITEM event is dir, which we aren't using, so we DROP it.
			BOARD_COLOR + @
			BOARD_COLOR represents the base address of the board color array. We add that to the next parameter (offset) and fetch the value, which is the color of the object (the key) at that offset.
			DUP
			We are using the color twice, so we duplicate it.
			TAKEKEY
			Attempt to take away that color of key from the player, and gets a success code.
			SWAP
			We want to pass the color, not the success code to GIVEKEY, so we SWAP it.
			GIVEKEY DROP
			Attempt to give a key of that color to the player. If the player already had that color, it was taken away so we now give it back. If that is not the case, then we still need to give a key to the player, which means the player is now picking up the key. We don't care whether or not this is successful (it always will be), so we drop the success code.
			IF
			Now we are entering a conditional block. The last value that hasn't been used yet is the success of TAKEKEY. So, the part between IF and ELSE is the true part (success taking the key away from the player), the part between ELSE and THEN is the false part (the key couldn't be taken, so it was given)