https://www.digitalmzx.com/wiki/api.php?action=feedcontributions&feedformat=atom&user=Zzo38 2026-05-14T00:45:10Z User contributions MediaWiki 1.39.7 https://www.digitalmzx.com/wiki/index.php?title=MOD&diff=8553 2015-05-25T19:25:48Z

<p>Zzo38: ModPlug Tracker is now OpenMPT; link to a comparison of other programs too</p> <hr /> <div>Module files (MODs) are files that contain human-readable music data (based on pattern, page, effect and track info laid out in a spreadsheet-like manner) and sound samples. They are used to play music in [[MegaZeux]] games.<br /> <br /> Files with the extension of .MOD are the simplest and oldest of these formats. Until version 2.48b, the only options for music in MegaZeux were ProTracker-format .MOD files (limited to 4 channels and 31 samples). The switch to [[Bells, Whistles, and Sound Boards|BWSB]] for the music engine allowed several new formats, including Ultimate SoundTracker format .MODs and the popular S3M format. Most new formats had to be converted to an intermediary format called .[[GDM]] (short for '''G'''eneral '''D'''igi'''M'''usic).<br /> <br /> MegaZeux switched to the [[ModPlug]] music engine at 2.80, allowing the popular formats XM and IT (as well as several others) to play natively. GDMs were no longer needed, and in fact have to be converted to S3M format for ModPlug to play them.<br /> <br /> MegaZeux currently plays modules with one of two possible sound engines: ''ModPlug'', the default engine, and ''[[MikMod]]'', an alternative module engine used when running MegaZeux on more limited platforms. For compatibility reasons, all MZX versions past 2.81h will only play the module formats both engines can play (MOD, S3M, XM, IT, STM, MTM, 669, ULT, FAR, MED, DSM, OKT and AMF).<br /> <br /> Programs used to create modules are called ''trackers''. Popular trackers include ModPlug Tracker (OpenMPT) and Skale. See [https://devlabs.linuxassist.net/projects/amigamml/wiki/Compare_features] for a list of some others.<br /> <br /> ===See Also===<br /> *[[S3M]], the ScreamTracker 3.0 music format<br /> *[[SAM]], the file format used for sound effects<br /> *[[OGG|OGG Vorbis]], a lossy audio format supported since 2.81<br /> <br /> [[Category:MegaZeux]]</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=Board&diff=7990 2012-11-02T18:13:25Z

<p>Zzo38: </p> <hr /> <div>A '''Board''' is basically a playing field for which the game can take place in.<br /> <br /> ==Limitations==<br /> *Boards can range in size from 1x1 to a massive 32767x32767<br /> **Extremely large boards will consume a massive block of memory. A board with the maximum dimensions would consume over 3 GB of memory, not including the overlay.<br /> **The board scan is a somewhat expensive routine that scans every square of the board every cycle for built-ins. The larger the board, the bigger the performance impact it can have on your game on slower computers. <br /> *For a few [[Built-in|built-in objects]], there is a limit to how many can be placed on one board.<br /> **All boards must have one and only one instance of the player object.<br /> **Signs and scrolls together are capped to 255 per board.<br /> **No more than 255 sensors.<br /> **No more than 255 robots.<br /> <br /> <br /> [[Category:MegaZeux]]</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=File:Ascmzxto.png&diff=7989 2012-10-20T04:55:24Z

<p>Zzo38: </p> <hr /> <div>Super ASCII MZX Town!<br /> <br /> {{MZXpd<br /> |game = [[Super ASCII MZX Town]]<br /> |author = zzo38<br /> |date = 2009-2011<br /> }}</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=Template:MZXpd&diff=7988 2012-10-20T04:55:18Z

<p>Zzo38: Created page with &quot;&lt;noinclude&gt; {| style=&quot;background: transparent; float: left;&quot; |&lt;pre&gt;{{MZXpd |game = |author = |date = }}&lt;/pre&gt; |} Category:Template &lt;/noinclude&gt; &lt;div class=&quot;tag&quot; style=...&quot;</p> <hr /> <div>&lt;noinclude&gt;<br /> <br /> {| style=&quot;background: transparent; float: left;&quot; <br /> |&lt;pre&gt;{{MZXpd<br /> |game = <br /> |author = <br /> |date = <br /> }}&lt;/pre&gt;<br /> |}<br /> <br /> [[Category:Template]]<br /> &lt;/noinclude&gt;<br /> <br /> &lt;div class=&quot;tag&quot; style=&quot;margin:0.5em auto;width:40%;clear:both;background-color:transparent;border:2px solid #8888aa; padding:4px;font-size:85%;min-height:64px;vertical-align:center&quot; id=&quot;imageLicense&quot;&gt;<br /> <br /> &lt;div style=&quot;float:left&quot; id=&quot;icon&quot;&gt;[[Image:NoCopyright.png|32px|MZXrighted]]&lt;/div&gt;<br /> <br /> &lt;div style=&quot;text-align:left;margin-left:68px&quot; id=&quot;text&quot;&gt;<br /> This picture from a [[MegaZeux]] game is public domain.<br /> : Game name: {{{game}}}&lt;br&gt;Author: {{{author}}}&lt;br&gt;Date: {{{date}}}<br /> &lt;/div&gt;<br /> &lt;/div&gt;</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=Zzo38&diff=7987 2012-10-20T04:39:03Z

<p>Zzo38: cjb net is broke</p> <hr /> <div>'''zzo38''' is something of an enigma to the community. Nobody is quite sure if they are a real person or the [[Identity deception|alternative account]] of somebody else, and there doesn't seem to be any evidence pointing in either direction. Typical characteristics of &quot;classic&quot; zzo38 include horribly broken English such as &quot;Old mesiges ar being crosed out.&quot;[http://en.wikipedia.org/w/index.php?title=User_talk:Zzo38&amp;oldid=21293425] and &quot;I think I like the old un-frenly serch more beter.&quot; [http://www.digitalmzx.net/forums/index.php?s=&amp;showtopic=6023&amp;view=findpost&amp;p=77256] and a general lack of effort in things that he does, though that seems to be quite a different story when looking at his more recent activities. (There is some speculation that the &quot;classic&quot; zzo38 may be a joke, a conspiracy, or a different person. But a few of the old stuff is still on the same web-site, so we cannot be exactly sure.)<br /> <br /> zzo38 released several ZZT and MZX games, including [[Cooking Game]], and [[Super ASCII MZX Town]], and also a [[PZX|fork of MegaZeux with different features]].<br /> <br /> Recently&lt;sup&gt;[please specify]&lt;/sup&gt;, zzo has reappeared on the DigitalMZX forums with vastly improved grammar and an apparent fascination with Mahjong games and Forth codes.<br /> <br /> ==MegaZeux Games==<br /> * [[Super ASCII MZX Town]]<br /> <br /> ==External Links==<br /> *[gopher://zzo38computer.org/ ZZO38COMPUTER (Gopher)]<br /> *[http://zzo38computer.org/mzx1/ MegaZeux games]<br /> <br /> {{WeaselStub}}<br /> {{NeedsPeerReview}}</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=Board&diff=7986 2012-10-20T04:36:33Z

<p>Zzo38: </p> <hr /> <div>A '''Board''' is basically a playing field for which the game can take place in.<br /> <br /> ==Limitations==<br /> *Boards can range in size from 1x1 to a massive 32767x32767<br /> **Extremely large boards will consume a massive block of memory. A board with the maximum dimensions would consume over 3 GB of memory, not including the overlay.<br /> **The board scan is a somewhat expensive routine that scans every square of the board every cycle for built-ins. The larger the board, the bigger the performance impact it can have on your game on slower computers. <br /> *For a few [[Built-in|built-in objects]], there is a limit to how many can be placed on one board.<br /> **All boards must have one and only one instance of the player object.<br /> **Robots and scrolls together are capped to 255 per board.<br /> **No more than 255 sensors.<br /> **No more than 255 robots.<br /> <br /> <br /> [[Category:MegaZeux]]</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=PZX&diff=7980 2012-09-18T08:10:59Z

<p>Zzo38: cjb net is broke</p> <hr /> <div>'''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.<br /> <br /> * Win32 binaries and source-codes is available at: http://zzo38computer.org/mzx1/mzx_extended/<br /> * Documentation is available at: http://zzo38computer.org/mzx1/mzx_extended/doc/<br /> <br /> ==Features==<br /> The biggest contribution of this particular fork is FORTH support. Other changes include the ability to use the old ALT+D function in the editor (only zzo38 seems to remember what this is or use the function to begin with), deferred expressions, extended kinds, new overlay modes and SMZX modes of dubious utility (including the one that draws overlay on the outside of the viewport instead of inside, one that draws only the overlay and not the board, an SMZX mode that uses 16 colors per character (reducing the resolution per character to 4x7), and a blinking text mode), meanings for the other bits in lava_walk, and displacement overlay modes which allow adjustment of the overlay by individual pixels.<br /> <br /> zzo38 also corrected a long standing, esoteric bug in the handling of built-in spider webs, which has been merged (with changes) into the existing codebase.<br /> <br /> To make backward compatibility, the way it works, is if the first line of the global robot is a comment with a greater than sign at beginning (optionally followed by a filename), it will activate PZX mode. If there is a filename, that is the file containing the Forth codes.<br /> <br /> ===Deferred Expressions===<br /> A deferred expression is sort of like having function calls for calling another expression. The operator &lt;tt&gt;,&lt;/tt&gt; sets the current parameter value to the left side and then evaluates the right side, the operator &lt;tt&gt;p&lt;/tt&gt; gets the current parameter, and the operator &lt;tt&gt;`&lt;/tt&gt; allows you to use a deferred expression.<br /> <br /> Because parentheses are used to evaluate expression, it uses square brackets to mean a deferred expression. It will convert &lt;tt&gt;[]&lt;/tt&gt; to &lt;tt&gt;()&lt;/tt&gt; when accessing a deferred expression.<br /> <br /> The &lt;tt&gt;`&lt;/tt&gt; operator is two of &lt;tt&gt;`&lt;/tt&gt; with the name of string in between (including the dollar sign), and it call the deferred expression. You can also use &lt;tt&gt;`&lt;/tt&gt; operator with &lt;tt&gt;*&lt;/tt&gt; followed by a Forth word instead of a string, in which case it will instead call that Forth word to determine the value of the expression.<br /> <br /> ===Extended Kinds===<br /> You can create extended kinds 0x80 to 0xFE (128 to 254) using Forth codes.<br /> <br /> In order to create a extended kind you must indicate:<br /> * The number assigned to it<br /> * The character used to represent it (255 means use the parameter, like a CustomBlock does, and negative number mean various other things)<br /> * The A_ flags associated with it<br /> * How the parameter is decided (the parameter type can come from any built-in)<br /> * The name<br /> And then you can optionally define events for it, such as what happens when it is shot, updated, touched by the player, underneath the player, and so on. Which events are used depends on the A_ flags, although it is possible to have A_ flags without the corresponding events (for example, the simplest way to prevent the player from pushing something that is normally pushable is to give the object the A_ITEM flag without a corresponding event).<br /> <br /> Some new A_ flags have been implemented:<br /> * A_BREAKABLE<br /> * A_USERFLAG<br /> * A_CRUSH<br /> * A_INVISIBLE<br /> * A_ELEMENT (3 bits, and in Forth codes you use AE_WATER and so on instead of typing A_ELEMENT)<br /> <br /> ===Overlay Modes===<br /> Mode 4 makes it draw the overlay outside of the viewport instead of on the inside of the viewport.<br /> <br /> Mode 65 and 66 makes it to not draw the board, and only draw the overlay. (This feature actually already existed in MegaZeux, but there was previously no access to it during the game.)<br /> <br /> Mode 0x7? prevents it from drawing anything at all, allowing Forth codes direct access to the text_video.<br /> <br /> There are also displacement overlay modes 0xA?, 0xB?, 0xE?, which allows pixel-accuracy for drawing characters, and also can make individual pixels transparent (so you can see the character drawn underneath).<br /> <br /> ===Graphics Modes===<br /> Modes 0 to 3 are same as normal MegaZeux. Mode 64 to 67 are the mode for 16 colors per character. Mode 141 makes blinking text.<br /> <br /> ==Use of Attribute Flags==<br /> The flags are as follows (any combination can be used, except for a few exceptions):<br /> * A_PUSHNS: Allows object to be pushed north/south<br /> * A_PUSHEW: Allows object ot be push east/west<br /> * A_PUSHABLE: Object can be pushed in any direction (Do not combine with A_PUSHNS or A_PUSHEW)<br /> * A_ITEM: Calls EV.ITEM event when player touches it. Player will not automatically push or stand on this object<br /> * A_UPDATE: EV.UPDATE event will be called every step unless freeze time is active<br /> * A_HURTS: Causes damage when player hits it<br /> * A_UNDER: Things can stand on this<br /> * A_ENTRANCE: Parameter is a board number, if the player steps here it will teleport the player to that board<br /> * A_EXPLODE: Object is explosive<br /> * A_BLOW_UP: Object can blow up<br /> * A_SHOOTABLE: Player bullets and neutral bullets can destroy this<br /> * A_BREAKABLE: Any bullets can destroy this (Do not combine with A_SHOOTABLE or A_SPEC_SHOT)<br /> * A_ENEMY: Used in various purposes by MegaZeux<br /> * A_AFFECTSTOOD: Calls EV.AFFECTSTOOD event every step if the player is standing here<br /> * A_SPEC_SHOT: Calls EV.SHOT event if hit by a bullet<br /> * A_SPEC_PUSH: Object can be pushed in any direction<br /> * A_SPEC_BOMB: Calls EV.BOMB event when explosion hits it<br /> * A_SPEC_STOOD: Player can stand here, even if other things can't<br /> * A_USERFLAG: Does nothing<br /> * A_CRUSH: Object can be crushed like in ZZT<br /> * A_INVISIBLE: Draws using under color, or draws black if this is the under object<br /> * A_SEEBLIND: Object is visible even if the player is blind<br /> <br /> There are also element flags (up to one of these flags can be used):<br /> * AE_WATER: Things that are not allowed to move onto water won't move onto here<br /> * AE_FIRE: Things that are not allowed to move onto fire won't move onto here<br /> * AE_LAVA: Things that are not allowed to move onto lava won't move onto here, also cannot be pushed or pushed onto<br /> * AE_GOOP: Things that are not allowed to move onto goop won't move onto here, also cannot be pushed or pushed onto<br /> * AE_THINWEB: Spiders that can move on thin webs are allowed to step here<br /> * AE_THICKWEB: Spiders that can move on thick webs are allowed to step here<br /> * AE_PLAYER: Cannot be pushed by things that react with the player<br /> <br /> ==Use of Events==<br /> The following events exist in game and are not corresponding to any particular object:<br /> * EV.PLAYERMOVING ( dir edge offset -- cancel ) Called to determine whether or not the player is allowed to move<br /> * EV.KEYBOARD ( key -- canceldefault ) Called when a key is pushed, can tell it to cancel the default function of that key<br /> * EV.LOADED ( category -- ) When game is started or restored<br /> * EV.ENTERED ( category -- ) When the board is switched<br /> * EV.BULLETHIT ( offset bulletoffset parameter -- category ) Indicates that a bullet is about to hit something solid<br /> * EV.GLOBAL ( slowed slowdown -- slowed ) Called on every cycle<br /> <br /> These events are corresponding to specific objects (add the extended kind number to the event code):<br /> * EV.PUSH ( offset dir category distance -- ) Called when an object is being pushed<br /> * EV.ITEM ( offset dir -- remove ) Called when the player touches an object with A_ITEM flag<br /> * EV.AFFECTSTOOD ( offset -- ) The player is stand on object with A_AFFECTSTOOD<br /> * EV.UPDATE ( offset -- ) Something with A_UPDATE is being updated<br /> * EV.SHOT ( offset bulletoffset dir bullettype -- ) Something with A_SPEC_SHOT is being hit by a bullet<br /> * EV.BOMB ( offset -- ) Something with A_SPEC_BOMB is hit by an explosion<br /> * EV.LAZER ( lazeroffset offset dir -- blocking ) Object hit by lazer beam, can block lazer or allow beam to be transmitted through<br /> * EV.ARRIVE ( offset -- ) Another object has arrived on top of this object<br /> * EV.TESTPUSH ( offset dir category distance -- cancel ) Testing whether or not an object is allowed to be pushed<br /> <br /> The following events are used in the editor:<br /> * EV.EDITORKEY ( color thing param offset key keymod -- color thing param offset canceldefault ) A key is pushed during editing<br /> * EV.BEFOREADDBOARD ( -- ? ) Before a new board is being added, the current board will be the old current board<br /> * 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<br /> <br /> ==Examples of Forth Codes==<br /> Please note that all examples are case-insensitive, just like anything else in MegaZeux.<br /> <br /> ===ZZT Keys===<br /> 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):<br /> INCLUDE megazeux.4th<br /> <br /> $80 12 A_ITEM A_PUSHABLE + 0 EXTKIND ZztKey<br /> ZztKey EV.ITEM + :EVENT<br /> DROP BOARD_COLOR + @ DUP TAKEKEY SWAP GIVEKEY DROP<br /> IF<br /> &quot;You already have the key!&quot; SETMESG 9 BISFX 0<br /> ELSE<br /> &quot;You now have the key.&quot; SETMESG 8 BISFX 1<br /> THEN<br /> ;<br /> I will explain each line and part of line one by one so that you can follow:<br /> INCLUDE megazeux.4th<br /> This loads the standard libraries of Forth codes.<br /> $80<br /> 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)<br /> 12<br /> This means it will display as character 12.<br /> A_ITEM A_PUSHABLE +<br /> 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).<br /> 0<br /> It will not ask for a parameter when placed in the editor.<br /> EXTKIND ZztKey<br /> 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.<br /> ZztKey EV.ITEM + :EVENT<br /> Adding ZztKey to EV.ITEM gets the number of the item event for the ZztKey. :EVENT tells it to start compiling an event code.<br /> DROP<br /> The top parameter passed to the EV.ITEM event is dir, which we aren't using, so we DROP it.<br /> BOARD_COLOR + @<br /> 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.<br /> DUP<br /> We are using the color twice, so we duplicate it.<br /> TAKEKEY<br /> Attempt to take away that color of key from the player, and gets a success code.<br /> SWAP<br /> We want to pass the color, not the success code to GIVEKEY, so we SWAP it.<br /> GIVEKEY DROP<br /> 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.<br /> IF<br /> 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)<br /> &quot;You already have the key!&quot; SETMESG 9 BISFX<br /> Gives the player a message and plays a sound effect.<br /> 0<br /> Zero is the value returned from the event (the &quot;remove&quot; parameter), meaning the object shouldn't be removed from the screen.<br /> ELSE &quot;You now have the key.&quot; SETMESG 8 BISFX<br /> Another message and sound effect.<br /> 1<br /> Any non-zero value means the object will be removed from the screen (because the player has just picked up the key).<br /> THEN<br /> 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 &quot;do this, and then do this...&quot; rather than &quot;if this then this...&quot;<br /> ;<br /> And this signals the end of the event code, and exits compile mode.<br /> <br /> ===ZZT Gems===<br /> INCLUDE megazeux.4th<br /> : GIVE DUP COUNTER@ ROT + SWAP COUNTER! ;<br /> <br /> 1 VARIABLE NEEDS-GEM-MESSAGE<br /> $81 4 A_ITEM A_PUSHABLE + A_CRUSH + A_SHOOTABLE + 0 EXTKIND ZztGem<br /> ZztGem EV.ITEM + :EVENT<br /> DROP DROP 1 BISFX<br /> 1 &quot;GEMS&quot; GIVE 1 &quot;HEALTH&quot; GIVE 10 &quot;SCORE&quot; GIVE<br /> NEEDS-GEM-MESSAGE @ IF<br /> &quot;Gems give you health!&quot; SETMESG<br /> 0 NEEDS-GEM-MESSAGE !<br /> THEN 1<br /> ;<br /> <br /> [[Category:MegaZeux]]</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=Super_ASCII_MZX_Town/Hint_Part_I&diff=7772 2011-12-26T21:43:56Z

<p>Zzo38: </p> <hr /> <div>== (General purpose hints) ==<br /> * Ensure make multiple save files. Sometimes you might realize you forgot something and have to restore an earlier file.<br /> * You get points for conserved resources.<br /> * Do not shoot everyone in the game, you can waste ammunition like that and lose points for conserved resources.<br /> * If you want to set music modes, push space bar on the title screen, and then select the option.<br /> <br /> == BANISH DETONATE SUMMON KILL ==<br /> * The words &quot;Banish! Detonate! Summon! Kill!&quot; do have a purpose.<br /> * There is a way to go through the water even in the wrong direction.<br /> * You need some but not all of the potions.<br /> * Collect the potions at the right time instead of the wrong time.<br /> * Dragons cannot be pushed and cannot go over water.<br /> * Don't step on the king's lava please.<br /> * Some potions must be collected not only at the right time but also in the right place.<br /> <br /> == CASTLE ==<br /> * Did you remember a key?<br /> * Some monster is safe, some is danger. (Color is irrelevant)<br /> * Make a map if it will help you.<br /> <br /> == CODE ROOM ==<br /> * Cover the blue floor with the boxes.<br /> * The message at the bottom of the screen is refering to the area of the board covered by the message.<br /> * You can use the keyboard commands (push H for help) to be able to see what the message is covering.<br /> <br /> == DRAGON FIGHTING ROOM ==<br /> * Do you know a trick in MegaZeux?<br /> * Do you know how to leave?<br /> * Do you know which one is a real key?<br /> <br /> == FINAL ==<br /> * You get permanent fire walking in this level.<br /> * There are two possible solutions to the multiplication.<br /> * Don't block the exit.<br /> * BIG_MONSTER is good and you should not fight them please.<br /> <br /> == FOREST ==<br /> * Push the switch in corner to open the gate.<br /> * Clear the path properly.<br /> * Pay attention to timer!<br /> * Pay attention to duplication!<br /> * Freeze time potion is best used when leaving back where you came from.<br /> <br /> == GAME OF FOUR BOMBS ==<br /> * The &quot;S&quot; is sensor.<br /> * Remember, Jesus saves.<br /> * Lit bombs are still pushable too.<br /> * Don't get trapped in the room containing the key.<br /> <br /> == GEM TRADER ==<br /> * If you trade many gems at once, the money you earn is more.<br /> <br /> == GREEN CAVE IN TOWER ==<br /> * Think ahead.<br /> * The brown passages will trap you, although there is a way to get by.<br /> * The passage only teleports you if in plain view of the player. Otherwise it is just like another floor.<br /> * Ensure you can activate the red and purple passages too; you will need them.<br /> <br /> == INAPPROPRIATE KEYS SOLD HERE ==<br /> * You do need the treasure chest, but not immediately.<br /> * Slime-blob will need to move to, in order to help you to complete this game.<br /> * Use the direction according to what is blocked.<br /> <br /> == KEYCARD TELEPORTERS ==<br /> * Put the keycard and push the button for exiting to a different place.<br /> * Remove the keycard and push buttons, too.<br /> <br /> == MAZE OF LOCKOO MIRRORS ==<br /> * You cannot change display mode here, although you can do so once you leave.<br /> * You need to collect all the potions. Some order might be better than others, though.<br /> * You can use gun/bomb in case it help you know where exactly you are standing.<br /> <br /> == MINE ==<br /> * You can't eat a skull.<br /> * Ghost can push rocks too, and can go over water freely.<br /> * You will need the red key.<br /> * The purple key is to the east and you will need to fly over the water to get there.<br /> * Look at the robotic codes for this level if you want to... it won't necessarily help unless you can really understand this game!<br /> * When you go inside the cave, maybe you should make a map to keep track of where you are going.<br /> <br /> == MONSTER HOUSE ==<br /> * One of the dragons does not want to hurt you but does want your autograph.<br /> * You have nothing for writing autograph with.<br /> * Don't waste all of your money at the store; you will need some in here too.<br /> * Don't let otyughs killed by safety pins, guns, or bombs.<br /> * Some room can wrap around.<br /> * There is some window that you can fall out of.<br /> * Landlord's Game is the predecessor to Monopoly.<br /> <br /> == MUSIC IS THE KEY ==<br /> * The light purple music notes is sensor.<br /> * Killing enemies potions are bad for you.<br /> * The various objects can be pushed, some of them only indirectly.<br /> <br /> == PLEASE LEAVE BEFORE I ARREST YOU ==<br /> * There is a secret passage.<br /> * Understand how the missiles are going.<br /> <br /> == PUZZLE WITH THROWING BOMBS ==<br /> * The sliders can be changed direction only a limited number of times.<br /> * Ensure you know what you will need the sliders for.<br /> * The &quot;#&quot; can cause a chain explosive.<br /> * Dr.Gray can be killed by bombs and he holds the purple key (it is the only thing he owns which isn't gray).<br /> <br /> == SIMPLE GAME BOMBS AND TRANSPORTS ==<br /> * Everything is what it seems with no invisible walls and fake walls and robots and so on, with one simple exception (obvious if you just look and think about it).<br /> * If you understand this game, you will know what the ring is even before trying it.<br /> <br /> == START ROOM ==<br /> * Go the store, and buy some more.<br /> * You will need to open the purple door.<br /> <br /> == UNSCRAMBLE THE WORD OR PHRASE ==<br /> * It is two words. The first word is a kind of word which will always be capitalized.<br /> * Don't get the letters you need to be trapped.<br /> <br /> == WELCOME IN HELL ==<br /> * Don't be greedy too much.<br /> * Remember the information given by the scrolls.<br /> * Does a dog have buddha nature? If you answer yes or no, you lose your own buddha nature.<br /> * The telephone is ringing!<br /> * Don't let the wind make you fall into the lava. Pay attention to wind warning.<br /> <br /> == ZZT KEY ==<br /> * Think ahead really.<br /> * Remember keys can be pushed too.<br /> * You cannot collect a key if you already have one.<br /> * Ensure not to get trapped by flowing water.<br /> * Remember you will need a last blue key. (It is not downstairs!)</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=Super_ASCII_MZX_Town/Hint_Part_I&diff=7771 2011-12-25T21:05:22Z

<p>Zzo38: </p> <hr /> <div>== (General purpose hints) ==<br /> * Ensure make multiple save files. Sometimes you might realize you forgot something and have to restore an earlier file.<br /> * You get points for conserved resources.<br /> * Do not shoot everyone in the game, you can waste ammunition like that and lose points for conserved resources.<br /> * If you want to set music modes, push space bar on the title screen, and then select the option.<br /> <br /> == BANISH DETONATE SUMMON KILL ==<br /> * The words &quot;Banish! Detonate! Summon! Kill!&quot; do have a purpose.<br /> * There is a way to go through the water even in the wrong direction.<br /> * You need some but not all of the potions.<br /> * Collect the potions at the right time instead of the wrong time.<br /> * Dragons cannot be pushed and cannot go over water.<br /> * Don't step on the king's lava please.<br /> * Some potions must be collected not only at the right time but also in the right place.<br /> <br /> == CASTLE ==<br /> * Did you remember a key?<br /> * Some monster is safe, some is danger. (Color is irrelevant)<br /> * Make a map if it will help you.<br /> <br /> == CODE ROOM ==<br /> * Cover the blue floor with the boxes.<br /> * The message at the bottom of the screen is refering to the area of the board covered by the message.<br /> * You can use the keyboard commands (push H for help) to be able to see what the message is covering.<br /> <br /> == DRAGON FIGHTING ROOM ==<br /> * Do you know a trick in MegaZeux?<br /> * Do you know how to leave?<br /> * Do you know which one is a real key?<br /> <br /> == FINAL ==<br /> * You get permanent fire walking in this level.<br /> * There are two possible solutions to the multiplication.<br /> * Don't block the exit.<br /> * BIG_MONSTER is good and you should not fight them please.<br /> <br /> == FOREST ==<br /> * Push the switch in corner to open the gate.<br /> * Clear the path properly.<br /> * Pay attention to timer!<br /> * Pay attention to duplication!<br /> * Freeze time potion is best used when leaving back where you came from.<br /> <br /> == GAME OF FOUR BOMBS ==<br /> * The &quot;S&quot; is sensor.<br /> * Remember, Jesus saves.<br /> * Lit bombs are still pushable too.<br /> * Don't get trapped in the room containing the key.<br /> <br /> == GEM TRADER ==<br /> * If you trade many gems at once, the money you earn is more.<br /> <br /> == GREEN CAVE IN TOWER ==<br /> * Think ahead.<br /> * The brown passages will trap you, although there is a way to get by.<br /> * The passage only teleports you if in plain view of the player. Otherwise it is just like another floor.<br /> * Ensure you can activate the red and purple passages too; you will need them.<br /> <br /> == INAPPROPRIATE KEYS SOLD HERE ==<br /> * You do need the treasure chest, but not immediately.<br /> * Slime-blob will need to move to, in order to help you to complete this game.<br /> * Use the direction according to what is blocked.<br /> <br /> == KEYCARD TELEPORTERS ==<br /> * Put the keycard and push the button for exiting to a different place.<br /> * Remove the keycard and push buttons, too.<br /> <br /> == MAZE OF LOCKOO MIRRORS ==<br /> * You cannot change display mode here, although you can do so once you leave.<br /> * You need to collect all the potions. Some order might be better than others, though.<br /> * You can use gun/bomb in case it help you know where exactly you are standing.<br /> <br /> == MINE ==<br /> * You can't eat a skull.<br /> * Ghost can push rocks too, and can go over water freely.<br /> * You will need the red key.<br /> * The purple key is to the east and you will need to fly over the water to get there.<br /> * Look at the robotic codes for this level if you want to... it won't necessarily help unless you can really understand this game!<br /> * When you go inside the cave, maybe you should make a map to keep track of where you are going.<br /> <br /> == MONSTER HOUSE ==<br /> * One of the dragons does not want to hurt you but does want your autograph.<br /> * You have nothing for writing autograph with.<br /> * Don't waste all of your money at the store; you will need some in here too.<br /> * Don't let otyughs killed by safety pins, guns, or bombs.<br /> * Some room can wrap around.<br /> * There is some window that you can fall out of.<br /> * Landlord's Game is the predecessor to Monopoly.<br /> <br /> == MUSIC IS THE KEY ==<br /> * The light purple music notes is sensor.<br /> * Killing enemies potions are bad for you.<br /> * The various objects can be pushed, some of them only indirectly.<br /> <br /> == PLEASE LEAVE BEFORE I ARREST YOU ==<br /> * There is a secret passage.<br /> * Understand how the missiles are going.<br /> <br /> == PUZZLE WITH THROWING BOMBS ==<br /> * The sliders can be changed direction only a limited number of times.<br /> * Ensure you know what you will need the sliders for.<br /> * The &quot;#&quot; can cause a chain explosive.<br /> * Dr.Gray can be killed by bombs and he holds the purple key (it is the only thing he owns which isn't gray).<br /> <br /> == SIMPLE GAME BOMBS AND TRANSPORTS ==<br /> * Everything is what it seems with no invisible walls and fake walls and robots and so on, with one simple exception (obvious if you just look and think about it).<br /> * If you understand this game, you will know what the ring is even before trying it.<br /> <br /> == START ROOM ==<br /> * You will need to open the purple door here.<br /> * Go the store, and buy some more.<br /> <br /> == UNSCRAMBLE THE WORD OR PHRASE ==<br /> * It is two words. The first word is a kind of word which will always be capitalized.<br /> * Don't get the letters you need to be trapped.<br /> <br /> == WELCOME IN HELL ==<br /> * Don't be greedy too much.<br /> * Remember the information given by the scrolls.<br /> * Does a dog have buddha nature? If you answer yes or no, you lose your own buddha nature.<br /> * The telephone is ringing!<br /> * Don't let the wind make you fall into the lava. Pay attention to wind warning.<br /> <br /> == ZZT KEY ==<br /> * Think ahead really.<br /> * Remember keys can be pushed too.<br /> * You cannot collect a key if you already have one.<br /> * Ensure not to get trapped by flowing water.<br /> * Remember you will need a last blue key. (It is not downstairs!)</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=Super_ASCII_MZX_Town/Hint_Part_I&diff=7770 2011-12-25T20:07:57Z

<p>Zzo38: Created page with &quot;== (General purpose hints) ==&quot;</p> <hr /> <div>== (General purpose hints) ==</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=Super_ASCII_MZX_Town&diff=7769 2011-12-25T20:07:28Z

<p>Zzo38: </p> <hr /> <div>{{Game| title = Super ASCII MZX Town<br /> |image = Ascmzxto.png<br /> |creator = [[zzo38]]<br /> |company = <br /> |released = 2009-2011<br /> |genre = <br /> }}<br /> <br /> [[Super ASCII MZX Town]] is a pure ASCII game made by zzo38. Part I uses normal MegaZeux, but Part II (and any subsequent sequels) requires PZX features, so you have to use the same forked version of MegaZeux that zzo38 wrote. These game are not the ordinary slider puzzle. It's different. Unlike other MegaZeux games, in this game you actually have to think about it. And remember also you might try for a high score when completing the game. You can try just to complete the game, or you can try to complete the game with a higher score.<br /> <br /> == Part I ==<br /> You have to get all of the purple keys to reach the final level, where you will see BIG_MONSTER. You also need the keycards to teleport to a different place. This game also has a dark engine and a high-score system. And you get a lot of bonus points for conserved ammo/bombs/gems/health/etc. There is 91 boards in this game (including the title screen).<br /> <br /> == Part II ==<br /> This game is the sequel to Part I. This one also has some platform game levels, and a better dark engine also. This game uses many Forth codes and Robotic codes. And there is magic keycards in this game. Again, you have to get all of the purple keys to reach the final level, where you will see BIG_MONSTER; but it is different this time!<br /> <br /> == Criticize ==<br /> These game have many criticism &lt;sup&gt;[citation needed]&lt;/sup&gt;:<br /> * The sliders on the title screen are not real sliders.<br /> * Most of the levels have yellow borders.<br /> * There is no URL to download this game.<br /> * The scoring system is really bad.<br /> * In one level you have to go through a corridor of lava with a windy potion and then quickly retreat from danger.<br /> * Half of the levels in this game are impossible to complete.<br /> * You have to go through the water in the wrong direction; but this is, of course, impossible.<br /> * Killing enemies potions are good for you.<br /> * This game is bad because Hitler played it.<br /> * This game is for DOS computers only.<br /> * Some of the puzzles do not work correctly except on the author's computer.<br /> * Torches in Part I work correctly, while torches in Part II do not work correctly.<br /> * MagicGems are exactly like ZZT gems.<br /> * BIG_MONSTER is bad and you should kill them, please.<br /> * The award of completing this game is torture.<br /> <br /> The author would like to assure you that all of these statements are incorrect; but the administration of Digital MZX assures the readers of this page that these statements are in fact correct, and that the author of this game is either lying or making a mistake, or that we have not yet found the actual author of this game.<br /> <br /> == Hints ==<br /> In case you have question or want hint, you can make sections for it in here, or read in case someone already put something here.<br /> * [[Super ASCII MZX Town/Hint Part I|Part I]]<br /> <br /> [[Category:Games]]</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=Super_ASCII_MZX_Town&diff=7768 2011-12-24T23:18:08Z

<p>Zzo38: </p> <hr /> <div>{{Game| title = Super ASCII MZX Town<br /> |image = Ascmzxto.png<br /> |creator = [[zzo38]]<br /> |company = <br /> |released = 2009<br /> |genre = We don't use &quot;genre&quot; here.<br /> }}<br /> <br /> [[Super ASCII MZX Town]] is a pure ASCII game made by zzo38. Part I uses normal MegaZeux, but Part II (and any subsequent sequels) requires PZX features, so you have to use the same forked version of MegaZeux that zzo38 wrote. These game are not the ordinary slider puzzle. It's different. Unlike other MegaZeux games, in this game you actually have to think about it. And remember also you might try for a high score when completing the game. You can try just to complete the game, or you can try to complete the game with a higher score.<br /> <br /> == Part I ==<br /> You have to get all of the purple keys to reach the final level, where you will see BIG_MONSTER. You also need the keycards to teleport to a different place. This game also has a dark engine and a high-score system. And you get a lot of bonus points for conserved ammo/bombs/gems/health/etc. There is 91 boards in this game (including the title screen).<br /> <br /> == Part II ==<br /> This game is the sequel to Part I. This one also has some platform game levels, and a better dark engine also. This game uses many Forth codes and Robotic codes. And there is magic keycards in this game. Again, you have to get all of the purple keys to reach the final level, where you will see BIG_MONSTER; but it is different this time!<br /> <br /> == Criticize ==<br /> These game have many criticism &lt;sup&gt;[citation needed]&lt;/sup&gt;:<br /> * The sliders on the title screen are not real sliders.<br /> * Most of the levels have yellow borders.<br /> * There is no URL to download this game.<br /> * The scoring system is really bad.<br /> * In one level you have to go through a corridor of lava with a windy potion and then quickly retreat from danger.<br /> * Half of the levels in this game are impossible to complete.<br /> * You have to go through the water in the wrong direction; but this is, of course, impossible.<br /> * Killing enemies potions are good for you.<br /> * This game is bad because Hitler played it.<br /> * This game is for DOS computers only.<br /> * Some of the puzzles do not work correctly except on the author's computer.<br /> * Torches in Part I work correctly, while torches in Part II do not work correctly.<br /> * MagicGems are exactly like ZZT gems.<br /> * BIG_MONSTER is bad and you should kill them, please.<br /> * The award of completing this game is torture.<br /> <br /> The author would like to assure you that all of these statements are incorrect; but the administration of Digital MZX assures the readers of this page that these statements are in fact correct, and that the author of this game is either lying or making a mistake, or that we have not yet found the actual author of this game.<br /> <br /> == Hints ==<br /> In case you have question or want hint, you can make sections for it in here, or read in case someone already put something here.<br /> <br /> [[Category:Games]]</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=Zzo38&diff=7767 2011-12-04T00:41:09Z

<p>Zzo38: The root page of the HTTP site just redirect to gopher anyways so I removed that link (subdirectories might still work, however)</p> <hr /> <div>'''zzo38''' is something of an enigma to the community. Nobody is quite sure if they are a real person or the [[Identity deception|alternative account]] of somebody else, and there doesn't seem to be any evidence pointing in either direction. Typical characteristics of &quot;classic&quot; zzo38 include horribly broken English such as &quot;Old mesiges ar being crosed out.&quot;[http://en.wikipedia.org/w/index.php?title=User_talk:Zzo38&amp;oldid=21293425] and &quot;I think I like the old un-frenly serch more beter.&quot; [http://www.digitalmzx.net/forums/index.php?s=&amp;showtopic=6023&amp;view=findpost&amp;p=77256] and a general lack of effort in things that he does, though that seems to be quite a different story when looking at his more recent activities. (There is some speculation that the &quot;classic&quot; zzo38 may be a joke, a conspiracy, or a different person. But a few of the old stuff is still on the same web-site, so we cannot be exactly sure.)<br /> <br /> zzo38 released several ZZT and MZX games, including [[Cooking Game]], and [[Super ASCII MZX Town]], and also a [[PZX|fork of MegaZeux with different features]].<br /> <br /> Recently&lt;sup&gt;[please specify]&lt;/sup&gt;, zzo has reappeared on the DigitalMZX forums with vastly improved grammar and an apparent fascination with Mahjong games and Forth codes.<br /> <br /> ==MegaZeux Games==<br /> * [[Super ASCII MZX Town]]<br /> <br /> ==External Links==<br /> *[gopher://zzo38computer.cjb.net/ ZZO38COMPUTER (Gopher)]<br /> *[http://zzo38computer.cjb.net/mzx1/ MegaZeux games]<br /> <br /> {{WeaselStub}}<br /> {{NeedsPeerReview}}</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=Talk:Main_Page&diff=7707 2011-05-27T22:21:22Z

<p>Zzo38: </p> <hr /> <div>No one should need to edit this page. Talk about something else.<br /> <br /> The front page has been under construction for years now? I think it would be pretty cool if we had featured articles and images. --[[User:T-Bone6|T-Bone6]] 16:14, 3 August 2010 (UTC)<br /> <br /> If it is under construction, shouldn't that mean someone has to type something on it? --[[User:Zzo38|Zzo38]] 15:21, 27 May 2011 (PDT)</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=Super_ASCII_MZX_Town&diff=7608 2010-12-13T06:11:12Z

<p>Zzo38: </p> <hr /> <div>{{Game| title = Super ASCII MZX Town<br /> |image = Ascmzxto.png<br /> |creator = [[zzo38]]<br /> |company = <br /> |released = 2009<br /> |genre = We don't use &quot;genre&quot; here.<br /> }}<br /> <br /> [[Super ASCII MZX Town]] is a pure ASCII game made by zzo38. Part I uses normal MegaZeux, but Part II (and any subsequent sequels) requires PZX features, so you have to use the same forked version of MegaZeux that zzo38 wrote. These game are not the ordinary slider puzzle. It's different. Unlike other MegaZeux games, in this game you actually have to think about it. And remember also you might try for a high score when completing the game. You can try just to complete the game, or you can try to complete the game with a higher score.<br /> <br /> == Part I ==<br /> You have to get all of the purple keys to reach the final level, where you will see BIG_MONSTER. You also need the keycards to teleport to a different place. This game also has a dark engine and a high-score system. And you get a lot of bonus points for conserved ammo/bombs/gems/health/etc. There is 91 boards in this game (including the title screen).<br /> <br /> == Part II ==<br /> This game is the sequel to Part I. This one also has some platform game levels, and a better dark engine also. This game uses many Forth codes and Robotic codes. And there is magic keycards in this game. Again, you have to get all of the purple keys to reach the final level, where you will see BIG_MONSTER; but it is different this time!<br /> <br /> == Criticize ==<br /> These game have many criticism &lt;sup&gt;[citation needed]&lt;/sup&gt;:<br /> * The sliders on the title screen are not real sliders.<br /> * Most of the levels have yellow borders.<br /> * There is no URL to download this game.<br /> * The scoring system is really bad.<br /> * In one level you have to go through a corridor of lava with a windy potion and then quickly retreat from danger.<br /> * Half of the levels in this game are impossible to complete.<br /> * You have to go through the water in the wrong direction; but this is, of course, impossible.<br /> * Killing enemies potions are good for you.<br /> * This game is bad because Hitler played it.<br /> * This game is for DOS computers only.<br /> * Some of the puzzles do not work correctly except on the author's computer.<br /> * Torches in Part I work correctly, while torches in Part II do not work correctly.<br /> * MagicGems are exactly like ZZT gems.<br /> * BIG_MONSTER is bad and you should kill them, please.<br /> * The award of completing this game is torture.<br /> <br /> The author would like to assure you that all of these statements are incorrect; but the administration of Digital MZX assures the readers of this page that these statements are in fact correct, and that the author of this game is either lying or making a mistake, or that we have not yet found the actual author of this game.<br /> <br /> [[Category:Games]]</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=Help:Editing_Guidelines&diff=7607 2010-12-09T01:03:53Z

<p>Zzo38: </p> <hr /> <div>If you would like to help contribute to the MZX Wiki please keep the following rules and guidelines in mind:<br /> <br /> #If you're unsure about how to use a wiki feature, check how it's done on [http://en.wikipedia.org/wiki/Main_Page Wikipedia].<br /> #If you wish to use content from another source, [http://en.wikipedia.org/wiki/Paraphrase paraphrase] it rather than copying it word-for-word.<br /> #Make sure that the information you are submitting is correct.<br /> #Use [[Help:Basic Markup|wiki mark-up]] rather than HTML tags.<br /> #Make the MZX Wiki easier to navigate by linking related articles together.<br /> #Be mindful of the &quot;minor edit&quot; function and use it where appropriate.<br /> #Always preview an article before submitting!<br /> #If an article could be referred to under multiple names or as an acronym, create redirect pages to make it easier to find.<br /> #All intrawiki links are case-sensitive (except for the first letter). Make sure to test your links in the preview screen prior to saving the page!<br /> <br /> Happy editing!</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=Super_ASCII_MZX_Town&diff=7606 2010-12-08T00:44:52Z

<p>Zzo38: </p> <hr /> <div>{{Game| title = Super ASCII MZX Town<br /> |image = Ascmzxto.png<br /> |creator = [[zzo38]]<br /> |company = <br /> |released = 2009<br /> |genre = We don't use &quot;genre&quot; here.<br /> }}<br /> <br /> [[Super ASCII MZX Town]] is a pure ASCII game made by zzo38. Part I uses normal MegaZeux, but Part II (and any subsequent sequels) requires PZX features, so you have to use the same forked version of MegaZeux that zzo38 wrote. These game are not the ordinary slider puzzle. It's different. Unlike other MegaZeux games, in this game you actually have to think about it. And remember also you might try for a high score when completing the game. You can try just to complete the game, or you can try to complete the game with a higher score.<br /> <br /> == Part I ==<br /> You have to get all of the purple keys to reach the final level, where you will see BIG_MONSTER. You also need the keycards to teleport to a different place. This game also has a dark engine and a high-score system. And you get a lot of bonus points for conserved ammo/bombs/gems/health/etc. There is 91 boards in this game (including the title screen).<br /> <br /> == Part II ==<br /> This game is the sequel to Part I. This one also has some platform game levels, and a better dark engine also. This game uses many Forth codes and Robotic codes. And there is magic keycards in this game.<br /> <br /> == Criticize ==<br /> These game have many criticism &lt;sup&gt;[citation needed]&lt;/sup&gt;:<br /> * The sliders on the title screen are not real sliders.<br /> * Most of the levels have yellow borders.<br /> * There is no URL to download this game.<br /> * The scoring system is really bad.<br /> * In one level you have to go through a corridor of lava with a windy potion and then quickly retreat from danger.<br /> * Half of the levels in this game are impossible to complete.<br /> * You have to go through the water in the wrong direction; but this is, of course, impossible.<br /> * Killing enemies potions are good for you.<br /> * This game is bad because Hitler played it.<br /> * This game is for DOS computers only.<br /> * Some of the puzzles do not work correctly except on the author's computer.<br /> * Torches in Part I work correctly, while torches in Part II do not work correctly.<br /> * MagicGems are exactly like ZZT gems.<br /> * BIG_MONSTER is bad and you should kill them, please.<br /> * The award of completing this game is torture.<br /> <br /> The author would like to assure you that all of these statements are incorrect; but the administration of Digital MZX assures the readers of this page that these statements are in fact correct, and that the author of this game is either lying or making a mistake, or that we have not yet found the actual author of this game.<br /> <br /> [[Category:Games]]</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=Super_ASCII_MZX_Town&diff=7602 2010-11-27T03:34:00Z

<p>Zzo38: </p> <hr /> <div>{{Game| title = Super ASCII MZX Town<br /> |image = Ascmzxto.png<br /> |creator = [[zzo38]]<br /> |company = <br /> |released = 2009<br /> |genre = We don't use &quot;genre&quot; here.<br /> }}<br /> <br /> [[Super ASCII MZX Town]] is a pure ASCII game made by zzo38. Part I uses normal MegaZeux, but Part II (and any subsequent sequels) requires PZX features, so you have to use the same forked version of MegaZeux that zzo38 wrote. These game are not the ordinary slider puzzle. It's different. Unlike other MegaZeux games, in this game you actually have to think about it. And remember also you might try for a high score when completing the game. You can try just to complete the game, or you can try to complete the game with a higher score.<br /> <br /> == Part I ==<br /> You have to get all of the purple keys to reach the final level, where you will see BIG_MONSTER. You also need the keycards to teleport to a different place. This game also has a dark engine and a high-score system. And you get a lot of bonus points for conserved ammo/bombs/gems/health/etc. There is 91 boards in this game (including the title screen).<br /> <br /> == Part II ==<br /> This game is the sequel to Part I. This one also has some platform game levels, and a better dark engine also. This game uses many Forth codes and Robotic codes. And there is magic keycards in this game.<br /> <br /> == Criticize ==<br /> These game have many criticism:<br /> * The sliders on the title screen are not real sliders.<br /> * Most of the levels have yellow borders.<br /> * There is no URL to download this game.<br /> * The scoring system is really bad.<br /> * In one level you have to go through a corridor of lava with a windy potion and then quickly retreat from danger.<br /> * Half of the levels in this game are impossible to complete.<br /> * You have to go through the water in the wrong direction; but this is, of course, impossible.<br /> * Killing enemies potions are good for you.<br /> * This game is bad because Hitler played it.<br /> * This game is for DOS computers only.<br /> * Some of the puzzles do not work correctly except on the author's computer.<br /> * Torches in Part I work correctly, while torches in Part II do not work correctly.<br /> * MagicGems are exactly like ZZT gems.<br /> * BIG_MONSTER is bad and you should kill them, please.<br /> * The award of completing this game is torture.<br /> <br /> The author would like to assure you that all of these statements are incorrect; but the administration of Digital MZX assures the readers of this page that these statements are in fact correct, and that the author of this game is either lying or making a mistake, or that we have not yet found the actual author of this game.<br /> <br /> [[Category:Games]]</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=PZX&diff=7601 2010-11-27T03:23:26Z

<p>Zzo38: </p> <hr /> <div>'''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.<br /> <br /> * Win32 binaries and source-codes is available at: http://zzo38computer.cjb.net/mzx1/mzx_extended/<br /> * Documentation is available at: http://zzo38computer.cjb.net/mzx1/mzx_extended/doc/<br /> <br /> ==Features==<br /> The biggest contribution of this particular fork is FORTH support. Other changes include the ability to use the old ALT+D function in the editor (only zzo38 seems to remember what this is or use the function to begin with), deferred expressions, extended kinds, new overlay modes and SMZX modes of dubious utility (including the one that draws overlay on the outside of the viewport instead of inside, one that draws only the overlay and not the board, an SMZX mode that uses 16 colors per character (reducing the resolution per character to 4x7), and a blinking text mode), meanings for the other bits in lava_walk, and displacement overlay modes which allow adjustment of the overlay by individual pixels.<br /> <br /> zzo38 also corrected a long standing, esoteric bug in the handling of built-in spider webs, which has been merged (with changes) into the existing codebase.<br /> <br /> To make backward compatibility, the way it works, is if the first line of the global robot is a comment with a greater than sign at beginning (optionally followed by a filename), it will activate PZX mode. If there is a filename, that is the file containing the Forth codes.<br /> <br /> ===Deferred Expressions===<br /> A deferred expression is sort of like having function calls for calling another expression. The operator &lt;tt&gt;,&lt;/tt&gt; sets the current parameter value to the left side and then evaluates the right side, the operator &lt;tt&gt;p&lt;/tt&gt; gets the current parameter, and the operator &lt;tt&gt;`&lt;/tt&gt; allows you to use a deferred expression.<br /> <br /> Because parentheses are used to evaluate expression, it uses square brackets to mean a deferred expression. It will convert &lt;tt&gt;[]&lt;/tt&gt; to &lt;tt&gt;()&lt;/tt&gt; when accessing a deferred expression.<br /> <br /> The &lt;tt&gt;`&lt;/tt&gt; operator is two of &lt;tt&gt;`&lt;/tt&gt; with the name of string in between (including the dollar sign), and it call the deferred expression. You can also use &lt;tt&gt;`&lt;/tt&gt; operator with &lt;tt&gt;*&lt;/tt&gt; followed by a Forth word instead of a string, in which case it will instead call that Forth word to determine the value of the expression.<br /> <br /> ===Extended Kinds===<br /> You can create extended kinds 0x80 to 0xFE (128 to 254) using Forth codes.<br /> <br /> In order to create a extended kind you must indicate:<br /> * The number assigned to it<br /> * The character used to represent it (255 means use the parameter, like a CustomBlock does, and negative number mean various other things)<br /> * The A_ flags associated with it<br /> * How the parameter is decided (the parameter type can come from any built-in)<br /> * The name<br /> And then you can optionally define events for it, such as what happens when it is shot, updated, touched by the player, underneath the player, and so on. Which events are used depends on the A_ flags, although it is possible to have A_ flags without the corresponding events (for example, the simplest way to prevent the player from pushing something that is normally pushable is to give the object the A_ITEM flag without a corresponding event).<br /> <br /> Some new A_ flags have been implemented:<br /> * A_BREAKABLE<br /> * A_USERFLAG<br /> * A_CRUSH<br /> * A_INVISIBLE<br /> * A_ELEMENT (3 bits, and in Forth codes you use AE_WATER and so on instead of typing A_ELEMENT)<br /> <br /> ===Overlay Modes===<br /> Mode 4 makes it draw the overlay outside of the viewport instead of on the inside of the viewport.<br /> <br /> Mode 65 and 66 makes it to not draw the board, and only draw the overlay. (This feature actually already existed in MegaZeux, but there was previously no access to it during the game.)<br /> <br /> Mode 0x7? prevents it from drawing anything at all, allowing Forth codes direct access to the text_video.<br /> <br /> There are also displacement overlay modes 0xA?, 0xB?, 0xE?, which allows pixel-accuracy for drawing characters, and also can make individual pixels transparent (so you can see the character drawn underneath).<br /> <br /> ===Graphics Modes===<br /> Modes 0 to 3 are same as normal MegaZeux. Mode 64 to 67 are the mode for 16 colors per character. Mode 141 makes blinking text.<br /> <br /> ==Use of Attribute Flags==<br /> The flags are as follows (any combination can be used, except for a few exceptions):<br /> * A_PUSHNS: Allows object to be pushed north/south<br /> * A_PUSHEW: Allows object ot be push east/west<br /> * A_PUSHABLE: Object can be pushed in any direction (Do not combine with A_PUSHNS or A_PUSHEW)<br /> * A_ITEM: Calls EV.ITEM event when player touches it. Player will not automatically push or stand on this object<br /> * A_UPDATE: EV.UPDATE event will be called every step unless freeze time is active<br /> * A_HURTS: Causes damage when player hits it<br /> * A_UNDER: Things can stand on this<br /> * A_ENTRANCE: Parameter is a board number, if the player steps here it will teleport the player to that board<br /> * A_EXPLODE: Object is explosive<br /> * A_BLOW_UP: Object can blow up<br /> * A_SHOOTABLE: Player bullets and neutral bullets can destroy this<br /> * A_BREAKABLE: Any bullets can destroy this (Do not combine with A_SHOOTABLE or A_SPEC_SHOT)<br /> * A_ENEMY: Used in various purposes by MegaZeux<br /> * A_AFFECTSTOOD: Calls EV.AFFECTSTOOD event every step if the player is standing here<br /> * A_SPEC_SHOT: Calls EV.SHOT event if hit by a bullet<br /> * A_SPEC_PUSH: Object can be pushed in any direction<br /> * A_SPEC_BOMB: Calls EV.BOMB event when explosion hits it<br /> * A_SPEC_STOOD: Player can stand here, even if other things can't<br /> * A_USERFLAG: Does nothing<br /> * A_CRUSH: Object can be crushed like in ZZT<br /> * A_INVISIBLE: Draws using under color, or draws black if this is the under object<br /> * A_SEEBLIND: Object is visible even if the player is blind<br /> <br /> There are also element flags (up to one of these flags can be used):<br /> * AE_WATER: Things that are not allowed to move onto water won't move onto here<br /> * AE_FIRE: Things that are not allowed to move onto fire won't move onto here<br /> * AE_LAVA: Things that are not allowed to move onto lava won't move onto here, also cannot be pushed or pushed onto<br /> * AE_GOOP: Things that are not allowed to move onto goop won't move onto here, also cannot be pushed or pushed onto<br /> * AE_THINWEB: Spiders that can move on thin webs are allowed to step here<br /> * AE_THICKWEB: Spiders that can move on thick webs are allowed to step here<br /> * AE_PLAYER: Cannot be pushed by things that react with the player<br /> <br /> ==Use of Events==<br /> The following events exist in game and are not corresponding to any particular object:<br /> * EV.PLAYERMOVING ( dir edge offset -- cancel ) Called to determine whether or not the player is allowed to move<br /> * EV.KEYBOARD ( key -- canceldefault ) Called when a key is pushed, can tell it to cancel the default function of that key<br /> * EV.LOADED ( category -- ) When game is started or restored<br /> * EV.ENTERED ( category -- ) When the board is switched<br /> * EV.BULLETHIT ( offset bulletoffset parameter -- category ) Indicates that a bullet is about to hit something solid<br /> * EV.GLOBAL ( slowed slowdown -- slowed ) Called on every cycle<br /> <br /> These events are corresponding to specific objects (add the extended kind number to the event code):<br /> * EV.PUSH ( offset dir category distance -- ) Called when an object is being pushed<br /> * EV.ITEM ( offset dir -- remove ) Called when the player touches an object with A_ITEM flag<br /> * EV.AFFECTSTOOD ( offset -- ) The player is stand on object with A_AFFECTSTOOD<br /> * EV.UPDATE ( offset -- ) Something with A_UPDATE is being updated<br /> * EV.SHOT ( offset bulletoffset dir bullettype -- ) Something with A_SPEC_SHOT is being hit by a bullet<br /> * EV.BOMB ( offset -- ) Something with A_SPEC_BOMB is hit by an explosion<br /> * EV.LAZER ( lazeroffset offset dir -- blocking ) Object hit by lazer beam, can block lazer or allow beam to be transmitted through<br /> * EV.ARRIVE ( offset -- ) Another object has arrived on top of this object<br /> * EV.TESTPUSH ( offset dir category distance -- cancel ) Testing whether or not an object is allowed to be pushed<br /> <br /> The following events are used in the editor:<br /> * EV.EDITORKEY ( color thing param offset key keymod -- color thing param offset canceldefault ) A key is pushed during editing<br /> * EV.BEFOREADDBOARD ( -- ? ) Before a new board is being added, the current board will be the old current board<br /> * 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<br /> <br /> ==Examples of Forth Codes==<br /> Please note that all examples are case-insensitive, just like anything else in MegaZeux.<br /> <br /> ===ZZT Keys===<br /> 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):<br /> INCLUDE megazeux.4th<br /> <br /> $80 12 A_ITEM A_PUSHABLE + 0 EXTKIND ZztKey<br /> ZztKey EV.ITEM + :EVENT<br /> DROP BOARD_COLOR + @ DUP TAKEKEY SWAP GIVEKEY DROP<br /> IF<br /> &quot;You already have the key!&quot; SETMESG 9 BISFX 0<br /> ELSE<br /> &quot;You now have the key.&quot; SETMESG 8 BISFX 1<br /> THEN<br /> ;<br /> I will explain each line and part of line one by one so that you can follow:<br /> INCLUDE megazeux.4th<br /> This loads the standard libraries of Forth codes.<br /> $80<br /> 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)<br /> 12<br /> This means it will display as character 12.<br /> A_ITEM A_PUSHABLE +<br /> 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).<br /> 0<br /> It will not ask for a parameter when placed in the editor.<br /> EXTKIND ZztKey<br /> 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.<br /> ZztKey EV.ITEM + :EVENT<br /> Adding ZztKey to EV.ITEM gets the number of the item event for the ZztKey. :EVENT tells it to start compiling an event code.<br /> DROP<br /> The top parameter passed to the EV.ITEM event is dir, which we aren't using, so we DROP it.<br /> BOARD_COLOR + @<br /> 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.<br /> DUP<br /> We are using the color twice, so we duplicate it.<br /> TAKEKEY<br /> Attempt to take away that color of key from the player, and gets a success code.<br /> SWAP<br /> We want to pass the color, not the success code to GIVEKEY, so we SWAP it.<br /> GIVEKEY DROP<br /> 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.<br /> IF<br /> 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)<br /> &quot;You already have the key!&quot; SETMESG 9 BISFX<br /> Gives the player a message and plays a sound effect.<br /> 0<br /> Zero is the value returned from the event (the &quot;remove&quot; parameter), meaning the object shouldn't be removed from the screen.<br /> ELSE &quot;You now have the key.&quot; SETMESG 8 BISFX<br /> Another message and sound effect.<br /> 1<br /> Any non-zero value means the object will be removed from the screen (because the player has just picked up the key).<br /> THEN<br /> 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 &quot;do this, and then do this...&quot; rather than &quot;if this then this...&quot;<br /> ;<br /> And this signals the end of the event code, and exits compile mode.<br /> <br /> ===ZZT Gems===<br /> INCLUDE megazeux.4th<br /> : GIVE DUP COUNTER@ ROT + SWAP COUNTER! ;<br /> <br /> 1 VARIABLE NEEDS-GEM-MESSAGE<br /> $81 4 A_ITEM A_PUSHABLE + A_CRUSH + A_SHOOTABLE + 0 EXTKIND ZztGem<br /> ZztGem EV.ITEM + :EVENT<br /> DROP DROP 1 BISFX<br /> 1 &quot;GEMS&quot; GIVE 1 &quot;HEALTH&quot; GIVE 10 &quot;SCORE&quot; GIVE<br /> NEEDS-GEM-MESSAGE @ IF<br /> &quot;Gems give you health!&quot; SETMESG<br /> 0 NEEDS-GEM-MESSAGE !<br /> THEN 1<br /> ;<br /> <br /> [[Category:MegaZeux]]</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=PZX&diff=7579 2010-11-17T05:54:35Z

<p>Zzo38: </p> <hr /> <div>'''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.<br /> <br /> * Win32 binaries and source-codes is available at: http://zzo38computer.cjb.net/mzx1/mzx_extended/<br /> * Documentation is available at: http://zzo38computer.cjb.net/mzx1/mzx_extended/doc/<br /> <br /> ==Features==<br /> The biggest contribution of this particular fork is FORTH support. Other changes include the ability to use the old ALT+D function in the editor (only zzo38 seems to remember what this is or use the function to begin with), deferred expressions, extended kinds, new overlay modes and SMZX modes of dubious utility (including the one that draws overlay on the outside of the viewport instead of inside, one that draws only the overlay and not the board, an SMZX mode that uses 16 colors per character (reducing the resolution per character to 4x7), and a blinking text mode), meanings for the other bits in lava_walk, and displacement overlay modes which allow adjustment of the overlay by individual pixels.<br /> <br /> zzo38 also corrected a long standing, esoteric bug in the handling of built-in spider webs, which has been merged (with changes) into the existing codebase.<br /> <br /> To make backward compatibility, the way it works, is if the first line of the global robot is a comment with a greater than sign at beginning (optionally followed by a filename), it will activate PZX mode. If there is a filename, that is the file containing the Forth codes.<br /> <br /> ===Deferred Expressions===<br /> A deferred expression is sort of like having function calls for calling another expression. The operator &lt;tt&gt;,&lt;/tt&gt; sets the current parameter value to the left side and then evaluates the right side, the operator &lt;tt&gt;p&lt;/tt&gt; gets the current parameter, and the operator &lt;tt&gt;`&lt;/tt&gt; allows you to use a deferred expression.<br /> <br /> Because parentheses are used to evaluate expression, it uses square brackets to mean a deferred expression. It will convert &lt;tt&gt;[]&lt;/tt&gt; to &lt;tt&gt;()&lt;/tt&gt; when accessing a deferred expression.<br /> <br /> The &lt;tt&gt;`&lt;/tt&gt; operator is two of &lt;tt&gt;`&lt;/tt&gt; with the name of string in between (including the dollar sign), and it call the deferred expression. You can also use &lt;tt&gt;`&lt;/tt&gt; operator with &lt;tt&gt;*&lt;/tt&gt; followed by a Forth word instead of a string, in which case it will instead call that Forth word to determine the value of the expression.<br /> <br /> ===Extended Kinds===<br /> You can create extended kinds 0x80 to 0xFE (128 to 254) using Forth codes.<br /> <br /> In order to create a extended kind you must indicate:<br /> * The number assigned to it<br /> * The character used to represent it (255 means use the parameter, like a CustomBlock does, and negative number mean various other things)<br /> * The A_ flags associated with it<br /> * How the parameter is decided (the parameter type can come from any built-in)<br /> * The name<br /> And then you can optionally define events for it, such as what happens when it is shot, updated, touched by the player, underneath the player, and so on. Which events are used depends on the A_ flags, although it is possible to have A_ flags without the corresponding events (for example, the simplest way to prevent the player from pushing something that is normally pushable is to give the object the A_ITEM flag without a corresponding event).<br /> <br /> Some new A_ flags have been implemented:<br /> * A_BREAKABLE<br /> * A_USERFLAG<br /> * A_CRUSH<br /> * A_INVISIBLE<br /> * A_ELEMENT (3 bits, and in Forth codes you use AE_WATER and so on instead of typing A_ELEMENT)<br /> <br /> ===Overlay Modes===<br /> Mode 4 makes it draw the overlay outside of the viewport instead of on the inside of the viewport.<br /> <br /> Mode 65 and 66 makes it to not draw the board, and only draw the overlay. (This feature actually already existed in MegaZeux, but there was previously no access to it during the game.)<br /> <br /> Mode 0x7? prevents it from drawing anything at all, allowing Forth codes direct access to the text_video.<br /> <br /> There are also displacement overlay modes 0xA?, 0xB?, 0xE?, which allows pixel-accuracy for drawing characters, and also can make individual pixels transparent (so you can see the character drawn underneath).<br /> <br /> ===Graphics Modes===<br /> Modes 0 to 3 are same as normal MegaZeux. Mode 64 to 67 are the mode for 16 colors per character. Mode 141 makes blinking text.<br /> <br /> ==Use of Attribute Flags==<br /> The flags are as follows (any combination can be used, except for a few exceptions):<br /> * A_PUSHNS: Allows object to be pushed north/south<br /> * A_PUSHEW: Allows object ot be push east/west<br /> * A_PUSHABLE: Object can be pushed in any direction (Do not combine with A_PUSHNS or A_PUSHEW)<br /> * A_ITEM: Calls EV.ITEM event when player touches it. Player will not automatically push or stand on this object<br /> * A_UPDATE: EV.UPDATE event will be called every step unless freeze time is active<br /> * A_HURTS: Causes damage when player hits it<br /> * A_UNDER: Things can stand on this<br /> * A_ENTRANCE: Parameter is a board number, if the player steps here it will teleport the player to that board<br /> * A_EXPLODE: Object is explosive<br /> * A_BLOW_UP: Object can blow up<br /> * A_SHOOTABLE: Player bullets and neutral bullets can destroy this<br /> * A_BREAKABLE: Any bullets can destroy this (Do not combine with A_SHOOTABLE or A_SPEC_SHOT)<br /> * A_ENEMY: Used in various purposes by MegaZeux<br /> * A_AFFECTSTOOD: Calls EV.AFFECTSTOOD event every step if the player is standing here<br /> * A_SPEC_SHOT: Calls EV.SHOT event if hit by a bullet<br /> * A_SPEC_PUSH: Object can be pushed in any direction<br /> * A_SPEC_BOMB: Calls EV.BOMB event when explosion hits it<br /> * A_SPEC_STOOD: Player can stand here, even if other things can't<br /> * A_USERFLAG: Does nothing<br /> * A_CRUSH: Object can be crushed like in ZZT<br /> * A_INVISIBLE: Draws using under color, or draws black if this is the under object<br /> * A_SEEBLIND: Object is visible even if the player is blind<br /> <br /> There are also element flags (up to one of these flags can be used):<br /> * AE_WATER: Things that are not allowed to move onto water won't move onto here<br /> * AE_FIRE: Things that are not allowed to move onto fire won't move onto here<br /> * AE_LAVA: Things that are not allowed to move onto lava won't move onto here, also cannot be pushed or pushed onto<br /> * AE_GOOP: Things that are not allowed to move onto goop won't move onto here, also cannot be pushed or pushed onto<br /> * AE_THINWEB: Spiders that can move on thin webs are allowed to step here<br /> * AE_THICKWEB: Spiders that can move on thick webs are allowed to step here<br /> * AE_PLAYER: Cannot be pushed by things that react with the player<br /> <br /> ==Use of Events==<br /> The following events exist in game and are not corresponding to any particular object:<br /> * EV.PLAYERMOVING ( dir edge offset -- cancel ) Called to determine whether or not the player is allowed to move<br /> * EV.KEYBOARD ( key -- canceldefault ) Called when a key is pushed, can tell it to cancel the default function of that key<br /> * EV.LOADED ( category -- ) When game is started or restored<br /> * EV.ENTERED ( category -- ) When the board is switched<br /> * EV.BULLETHIT ( offset bulletoffset parameter -- category ) Indicates that a bullet is about to hit something solid<br /> <br /> These events are corresponding to specific objects (add the extended kind number to the event code):<br /> * EV.PUSH ( offset dir category distance -- ) Called when an object is being pushed<br /> * EV.ITEM ( offset dir -- remove ) Called when the player touches an object with A_ITEM flag<br /> * EV.AFFECTSTOOD ( offset -- ) The player is stand on object with A_AFFECTSTOOD<br /> * EV.UPDATE ( offset -- ) Something with A_UPDATE is being updated<br /> * EV.SHOT ( offset bulletoffset dir bullettype -- ) Something with A_SPEC_SHOT is being hit by a bullet<br /> * EV.BOMB ( offset -- ) Something with A_SPEC_BOMB is hit by an explosion<br /> * EV.LAZER ( lazeroffset offset dir -- blocking ) Object hit by lazer beam, can block lazer or allow beam to be transmitted through<br /> * EV.ARRIVE ( offset -- ) Another object has arrived on top of this object<br /> * EV.TESTPUSH ( offset dir category distance -- cancel ) Testing whether or not an object is allowed to be pushed<br /> <br /> The following events are used in the editor:<br /> * EV.EDITORKEY ( color thing param offset key keymod -- color thing param offset canceldefault ) A key is pushed during editing<br /> * EV.BEFOREADDBOARD ( -- ? ) Before a new board is being added, the current board will be the old current board<br /> * 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<br /> <br /> ==Examples of Forth Codes==<br /> Please note that all examples are case-insensitive, just like anything else in MegaZeux.<br /> <br /> ===ZZT Keys===<br /> 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):<br /> INCLUDE megazeux.4th<br /> <br /> $80 12 A_ITEM A_PUSHABLE + 0 EXTKIND ZztKey<br /> ZztKey EV.ITEM + :EVENT<br /> DROP BOARD_COLOR + @ DUP TAKEKEY SWAP GIVEKEY DROP<br /> IF<br /> &quot;You already have the key!&quot; SETMESG 9 BISFX 0<br /> ELSE<br /> &quot;You now have the key.&quot; SETMESG 8 BISFX 1<br /> THEN<br /> ;<br /> I will explain each line and part of line one by one so that you can follow:<br /> INCLUDE megazeux.4th<br /> This loads the standard libraries of Forth codes.<br /> $80<br /> 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)<br /> 12<br /> This means it will display as character 12.<br /> A_ITEM A_PUSHABLE +<br /> 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).<br /> 0<br /> It will not ask for a parameter when placed in the editor.<br /> EXTKIND ZztKey<br /> 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.<br /> ZztKey EV.ITEM + :EVENT<br /> Adding ZztKey to EV.ITEM gets the number of the item event for the ZztKey. :EVENT tells it to start compiling an event code.<br /> DROP<br /> The top parameter passed to the EV.ITEM event is dir, which we aren't using, so we DROP it.<br /> BOARD_COLOR + @<br /> 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.<br /> DUP<br /> We are using the color twice, so we duplicate it.<br /> TAKEKEY<br /> Attempt to take away that color of key from the player, and gets a success code.<br /> SWAP<br /> We want to pass the color, not the success code to GIVEKEY, so we SWAP it.<br /> GIVEKEY DROP<br /> 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.<br /> IF<br /> 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)<br /> &quot;You already have the key!&quot; SETMESG 9 BISFX<br /> Gives the player a message and plays a sound effect.<br /> 0<br /> Zero is the value returned from the event (the &quot;remove&quot; parameter), meaning the object shouldn't be removed from the screen.<br /> ELSE &quot;You now have the key.&quot; SETMESG 8 BISFX<br /> Another message and sound effect.<br /> 1<br /> Any non-zero value means the object will be removed from the screen (because the player has just picked up the key).<br /> THEN<br /> 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 &quot;do this, and then do this...&quot; rather than &quot;if this then this...&quot;<br /> ;<br /> And this signals the end of the event code, and exits compile mode.<br /> <br /> ===ZZT Gems===<br /> INCLUDE megazeux.4th<br /> : GIVE DUP COUNTER@ ROT + SWAP COUNTER! ;<br /> <br /> 1 VARIABLE NEEDS-GEM-MESSAGE<br /> $81 4 A_ITEM A_PUSHABLE + A_CRUSH + A_SHOOTABLE + 0 EXTKIND ZztGem<br /> ZztGem EV.ITEM + :EVENT<br /> DROP DROP 1 BISFX<br /> 1 &quot;GEMS&quot; GIVE 1 &quot;HEALTH&quot; GIVE 10 &quot;SCORE&quot; GIVE<br /> NEEDS-GEM-MESSAGE @ IF<br /> &quot;Gems give you health!&quot; SETMESG<br /> 0 NEEDS-GEM-MESSAGE !<br /> THEN 1<br /> ;<br /> <br /> [[Category:MegaZeux]]</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=PZX&diff=7578 2010-11-17T05:52:22Z

<p>Zzo38: ZZT Gems</p> <hr /> <div>'''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.<br /> <br /> * Win32 binaries and source-codes is available at: http://zzo38computer.cjb.net/mzx1/mzx_extended/<br /> * Documentation is available at: http://zzo38computer.cjb.net/mzx1/mzx_extended/doc/<br /> <br /> ==Features==<br /> The biggest contribution of this particular fork is FORTH support. Other changes include the ability to use the old ALT+D function in the editor (only zzo38 seems to remember what this is or use the function to begin with), deferred expressions, extended kinds, new overlay modes and SMZX modes of dubious utility (including the one that draws overlay on the outside of the viewport instead of inside, one that draws only the overlay and not the board, an SMZX mode that uses 16 colors per character (reducing the resolution per character to 4x7), and a blinking text mode), meanings for the other bits in lava_walk, and displacement overlay modes which allow adjustment of the overlay by individual pixels.<br /> <br /> zzo38 also corrected a long standing, esoteric bug in the handling of built-in spider webs, which has been merged (with changes) into the existing codebase.<br /> <br /> To make backward compatibility, the way it works, is if the first line of the global robot is a comment with a greater than sign at beginning (optionally followed by a filename), it will activate PZX mode. If there is a filename, that is the file containing the Forth codes.<br /> <br /> ===Deferred Expressions===<br /> A deferred expression is sort of like having function calls for calling another expression. The operator &lt;tt&gt;,&lt;/tt&gt; sets the current parameter value to the left side and then evaluates the right side, the operator &lt;tt&gt;p&lt;/tt&gt; gets the current parameter, and the operator &lt;tt&gt;`&lt;/tt&gt; allows you to use a deferred expression.<br /> <br /> Because parentheses are used to evaluate expression, it uses square brackets to mean a deferred expression. It will convert &lt;tt&gt;[]&lt;/tt&gt; to &lt;tt&gt;()&lt;/tt&gt; when accessing a deferred expression.<br /> <br /> The &lt;tt&gt;`&lt;/tt&gt; operator is two of &lt;tt&gt;`&lt;/tt&gt; with the name of string in between (including the dollar sign), and it call the deferred expression. You can also use &lt;tt&gt;`&lt;/tt&gt; operator with &lt;tt&gt;*&lt;/tt&gt; followed by a Forth word instead of a string, in which case it will instead call that Forth word to determine the value of the expression.<br /> <br /> ===Extended Kinds===<br /> You can create extended kinds 0x80 to 0xFE (128 to 254) using Forth codes.<br /> <br /> In order to create a extended kind you must indicate:<br /> * The number assigned to it<br /> * The character used to represent it (255 means use the parameter, like a CustomBlock does, and negative number mean various other things)<br /> * The A_ flags associated with it<br /> * How the parameter is decided (the parameter type can come from any built-in)<br /> * The name<br /> And then you can optionally define events for it, such as what happens when it is shot, updated, touched by the player, underneath the player, and so on. Which events are used depends on the A_ flags, although it is possible to have A_ flags without the corresponding events (for example, the simplest way to prevent the player from pushing something that is normally pushable is to give the object the A_ITEM flag without a corresponding event).<br /> <br /> Some new A_ flags have been implemented:<br /> * A_BREAKABLE<br /> * A_USERFLAG<br /> * A_CRUSH<br /> * A_INVISIBLE<br /> * A_ELEMENT (3 bits, and in Forth codes you use AE_WATER and so on instead of typing A_ELEMENT)<br /> <br /> ===Overlay Modes===<br /> Mode 4 makes it draw the overlay outside of the viewport instead of on the inside of the viewport.<br /> <br /> Mode 65 and 66 makes it to not draw the board, and only draw the overlay. (This feature actually already existed in MegaZeux, but there was previously no access to it during the game.)<br /> <br /> Mode 0x7? prevents it from drawing anything at all, allowing Forth codes direct access to the text_video.<br /> <br /> There are also displacement overlay modes 0xA?, 0xB?, 0xE?, which allows pixel-accuracy for drawing characters, and also can make individual pixels transparent (so you can see the character drawn underneath).<br /> <br /> ===Graphics Modes===<br /> Modes 0 to 3 are same as normal MegaZeux. Mode 64 to 67 are the mode for 16 colors per character. Mode 141 makes blinking text.<br /> <br /> ==Use of Attribute Flags==<br /> The flags are as follows (any combination can be used, except for a few exceptions):<br /> * A_PUSHNS: Allows object to be pushed north/south<br /> * A_PUSHEW: Allows object ot be push east/west<br /> * A_PUSHABLE: Object can be pushed in any direction (Do not combine with A_PUSHNS or A_PUSHEW)<br /> * A_ITEM: Calls EV.ITEM event when player touches it. Player will not automatically push or stand on this object<br /> * A_UPDATE: EV.UPDATE event will be called every step unless freeze time is active<br /> * A_HURTS: Causes damage when player hits it<br /> * A_UNDER: Things can stand on this<br /> * A_ENTRANCE: Parameter is a board number, if the player steps here it will teleport the player to that board<br /> * A_EXPLODE: Object is explosive<br /> * A_BLOW_UP: Object can blow up<br /> * A_SHOOTABLE: Player bullets and neutral bullets can destroy this<br /> * A_BREAKABLE: Any bullets can destroy this (Do not combine with A_SHOOTABLE or A_SPEC_SHOT)<br /> * A_ENEMY: Used in various purposes by MegaZeux<br /> * A_AFFECTSTOOD: Calls EV.AFFECTSTOOD event every step if the player is standing here<br /> * A_SPEC_SHOT: Calls EV.SHOT event if hit by a bullet<br /> * A_SPEC_PUSH: Object can be pushed in any direction<br /> * A_SPEC_BOMB: Calls EV.BOMB event when explosion hits it<br /> * A_SPEC_STOOD: Player can stand here, even if other things can't<br /> * A_USERFLAG: Does nothing<br /> * A_CRUSH: Object can be crushed like in ZZT<br /> * A_INVISIBLE: Draws using under color, or draws black if this is the under object<br /> * A_SEEBLIND: Object is visible even if the player is blind<br /> <br /> There are also element flags (up to one of these flags can be used):<br /> * AE_WATER: Things that are not allowed to move onto water won't move onto here<br /> * AE_FIRE: Things that are not allowed to move onto fire won't move onto here<br /> * AE_LAVA: Things that are not allowed to move onto lava won't move onto here, also cannot be pushed or pushed onto<br /> * AE_GOOP: Things that are not allowed to move onto goop won't move onto here, also cannot be pushed or pushed onto<br /> * AE_THINWEB: Spiders that can move on thin webs are allowed to step here<br /> * AE_THICKWEB: Spiders that can move on thick webs are allowed to step here<br /> * AE_PLAYER: Cannot be pushed by things that react with the player<br /> <br /> ==Use of Events==<br /> The following events exist in game and are not corresponding to any particular object:<br /> * EV.PLAYERMOVING ( dir edge offset -- cancel ) Called to determine whether or not the player is allowed to move<br /> * EV.KEYBOARD ( key -- canceldefault ) Called when a key is pushed, can tell it to cancel the default function of that key<br /> * EV.LOADED ( category -- ) When game is started or restored<br /> * EV.ENTERED ( category -- ) When the board is switched<br /> * EV.BULLETHIT ( offset bulletoffset parameter -- category ) Indicates that a bullet is about to hit something solid<br /> <br /> These events are corresponding to specific objects (add the extended kind number to the event code):<br /> * EV.PUSH ( offset dir category distance -- ) Called when an object is being pushed<br /> * EV.ITEM ( offset dir -- remove ) Called when the player touches an object with A_ITEM flag<br /> * EV.AFFECTSTOOD ( offset -- ) The player is stand on object with A_AFFECTSTOOD<br /> * EV.UPDATE ( offset -- ) Something with A_UPDATE is being updated<br /> * EV.SHOT ( offset bulletoffset dir bullettype -- ) Something with A_SPEC_SHOT is being hit by a bullet<br /> * EV.BOMB ( offset -- ) Something with A_SPEC_BOMB is hit by an explosion<br /> * EV.LAZER ( lazeroffset offset dir -- blocking ) Object hit by lazer beam, can block lazer or allow beam to be transmitted through<br /> * EV.ARRIVE ( offset -- ) Another object has arrived on top of this object<br /> * EV.TESTPUSH ( offset dir category distance -- cancel ) Testing whether or not an object is allowed to be pushed<br /> <br /> The following events are used in the editor:<br /> * EV.EDITORKEY ( color thing param offset key keymod -- color thing param offset canceldefault ) A key is pushed during editing<br /> * EV.BEFOREADDBOARD ( -- ? ) Before a new board is being added, the current board will be the old current board<br /> * 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<br /> <br /> ==Examples of Forth Codes==<br /> Please note that all examples are case-insensitive, just like anything else in MegaZeux.<br /> <br /> ===ZZT Keys===<br /> 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):<br /> INCLUDE megazeux.4th<br /> <br /> $80 12 A_ITEM A_PUSHABLE + 0 EXTKIND ZztKey<br /> ZztKey EV.ITEM + :EVENT<br /> DROP BOARD_COLOR + @ DUP TAKEKEY SWAP GIVEKEY DROP<br /> IF<br /> &quot;You already have the key!&quot; SETMESG 9 BISFX 0<br /> ELSE<br /> &quot;You now have the key.&quot; SETMESG 8 BISFX 1<br /> THEN<br /> ;<br /> I will explain each line and part of line one by one so that you can follow:<br /> INCLUDE megazeux.4th<br /> This loads the standard libraries of Forth codes.<br /> $80<br /> 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)<br /> 12<br /> This means it will display as character 12.<br /> A_ITEM A_PUSHABLE +<br /> 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).<br /> 0<br /> It will not ask for a parameter when placed in the editor.<br /> EXTKIND ZztKey<br /> 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.<br /> ZztKey EV.ITEM + :EVENT<br /> Adding ZztKey to EV.ITEM gets the number of the item event for the ZztKey. :EVENT tells it to start compiling an event code.<br /> DROP<br /> The top parameter passed to the EV.ITEM event is dir, which we aren't using, so we DROP it.<br /> BOARD_COLOR + @<br /> 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.<br /> DUP<br /> We are using the color twice, so we duplicate it.<br /> TAKEKEY<br /> Attempt to take away that color of key from the player, and gets a success code.<br /> SWAP<br /> We want to pass the color, not the success code to GIVEKEY, so we SWAP it.<br /> GIVEKEY DROP<br /> 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.<br /> IF<br /> 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)<br /> &quot;You already have the key!&quot; SETMESG 9 BISFX<br /> Gives the player a message and plays a sound effect.<br /> 0<br /> Zero is the value returned from the event (the &quot;remove&quot; parameter), meaning the object shouldn't be removed from the screen.<br /> ELSE &quot;You now have the key.&quot; SETMESG 8 BISFX<br /> Another message and sound effect.<br /> 1<br /> Any non-zero value means the object will be removed from the screen (because the player has just picked up the key).<br /> THEN<br /> 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 &quot;do this, and then do this...&quot; rather than &quot;if this then this...&quot;<br /> ;<br /> And this signals the end of the event code, and exits compile mode.<br /> <br /> ===ZZT Gems===<br /> INCLUDE megazeux.4th<br /> : GIVE DUP COUNTER@ ROT + SWAP COUNTER! ;<br /> <br /> 1 VARIABLE NEEDS-GEM-MESSAGE<br /> $81 4 A_ITEM A_PUSHABLE + 0 EXTKIND ZztGem<br /> ZztGem EV.ITEM + :EVENT<br /> DROP DROP 1 BISFX<br /> 1 &quot;GEMS&quot; GIVE 1 &quot;HEALTH&quot; GIVE 10 &quot;SCORE&quot; GIVE<br /> NEEDS-GEM-MESSAGE @ IF<br /> &quot;Gems give you health!&quot; SETMESG<br /> 0 NEEDS-GEM-MESSAGE !<br /> THEN 1<br /> ;<br /> <br /> [[Category:MegaZeux]]</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=MZX_Clich%C3%A9_Page&diff=7577 2010-11-15T02:35:24Z

<p>Zzo38: </p> <hr /> <div>The ''MZX Cliche'' page is a list of clichés commonly found in the [[MegaZeux]] community and in its [[Category:Games|Games]]. Often these clichés have corollaries or additional similar rules attached to complete them. The file has not been updated in quite some time but still technically accepts submissions.<br /> <br /> ==External Links==<br /> * The [http://sites.google.com/site/kkairossportalthingy/mzx-cliche-page MZX Cliché Page]</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=Super_ASCII_MZX_Town&diff=7576 2010-11-15T02:28:55Z

<p>Zzo38: </p> <hr /> <div>{{Game| title = Super ASCII MZX Town<br /> |image = Ascmzxto.png<br /> |creator = [[zzo38]]<br /> |company = <br /> |released = 2009<br /> |genre = We don't use &quot;genre&quot; here.<br /> }}<br /> <br /> [[Super ASCII MZX Town]] is a pure ASCII game made by zzo38. Part I uses normal MegaZeux, but Part II (and any subsequent sequels) requires PZX features, so you have to use the same forked version of MegaZeux that zzo38 wrote. These game are not the ordinary slider puzzle. It's different. Unlike other MegaZeux games, in this game you actually have to think about it. And remember also you might try for a high score when completing the game. You can try just to complete the game, or you can try to complete the game with a higher score.<br /> <br /> == Part I ==<br /> You have to get all of the purple keys to reach the final level, where you will see BIG_MONSTER. You also need the keycards to teleport to a different place. This game also has a dark engine and a high-score system. And you get a lot of bonus points for conserved ammo/bombs/gems/health/etc. There is 91 boards in this game (including the title screen).<br /> <br /> == Part II ==<br /> This game is the sequel to Part I. This one also has some platform game levels, and a better dark engine also. This game uses many Forth codes and Robotic codes. And there is magic keycards in this game.<br /> <br /> == Criticize ==<br /> These game have many criticism:<br /> * The sliders on the title screen are not real sliders.<br /> * Most of the levels have yellow borders.<br /> * There is no URL to download this game.<br /> * The scoring system is really bad.<br /> * In one level you have to go through a corridor of lava with a windy potion.<br /> * Half of the levels in this game are impossible to complete.<br /> * You have to go through the water in the wrong direction; but this is, of course, impossible.<br /> * Killing enemies potions are good for you.<br /> * This game is bad because Hitler played it.<br /> * This game is for DOS computers only.<br /> * Some of the puzzles do not work correctly except on the author's computer.<br /> * Torches in Part I work correctly, while torches in Part II do not work correctly.<br /> * MagicGems are exactly like ZZT gems.<br /> * BIG_MONSTER is bad and you should kill them, please.<br /> * The award of completing this game is torture.<br /> <br /> The author would like to assure you that all of these statements are incorrect; but the administration of Digital MZX assures the readers of this page that these statements are in fact correct, and that the author of this game is either lying or making a mistake, or that we have not yet found the actual author of this game.<br /> <br /> [[Category:Games]]</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=MZXWiki:Community_portal&diff=7575 2010-11-15T02:14:37Z

<p>Zzo38: Created page with &quot;Welcome to the MZX Wiki Community Portal. ==Forums== * &lt;tt&gt;http://www.digitalmzx.net/forums/index.php?act=idx&lt;/tt&gt; ==DigiVault== * &lt;tt&gt;http://vault.digitalmzx.net/&lt;/tt&gt; ==Inte...&quot;</p> <hr /> <div>Welcome to the MZX Wiki Community Portal.<br /> <br /> ==Forums==<br /> * &lt;tt&gt;http://www.digitalmzx.net/forums/index.php?act=idx&lt;/tt&gt;<br /> <br /> ==DigiVault==<br /> * &lt;tt&gt;http://vault.digitalmzx.net/&lt;/tt&gt;<br /> <br /> ==Internet Relay Chat==<br /> * Host: &lt;tt&gt;irc.slashnet.org&lt;/tt&gt;<br /> * Port: &lt;tt&gt;6667&lt;/tt&gt;<br /> * Channel: &lt;tt&gt;#mzx&lt;/tt&gt;</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=Super_ASCII_MZX_Town&diff=7574 2010-11-15T01:55:11Z

<p>Zzo38: </p> <hr /> <div>{{Game| title = Super ASCII MZX Town<br /> |image = Ascmzxto.png<br /> |creator = [[zzo38]]<br /> |company = <br /> |released = 2009<br /> |genre = We don't use &quot;genre&quot; here.<br /> }}<br /> <br /> [[Super ASCII MZX Town]] is a pure ASCII game made by zzo38. Part I uses normal MegaZeux, but Part II (and any subsequent sequels) requires PZX features, so you have to use the same forked version of MegaZeux that zzo38 wrote. These game are not the ordinary slider puzzle. It's different. Unlike other MegaZeux games, in this game you actually have to think about it. And remember also you might try for a high score when completing the game. You can try just to complete the game, or you can try to complete the game with a higher score.<br /> <br /> == Part I ==<br /> You have to get all of the purple keys to reach the final level, where you will see BIG_MONSTER. You also need the keycards to teleport to a different place. This game also has a dark engine and a high-score system. And you get a lot of bonus points for conserved ammo/bombs/gems/health/etc. There is 91 boards in this game (including the title screen).<br /> <br /> == Part II ==<br /> This game is the sequel to Part I. This one also has some platform game levels, and a better dark engine also. This game uses many Forth codes and Robotic codes. And there is magic keycards in this game.<br /> <br /> == Criticize ==<br /> These game have many criticism:<br /> * The sliders on the title screen are not real sliders.<br /> * Most of the levels have yellow borders.<br /> * There is no URL to download this game.<br /> * The scoring system is really bad.<br /> * In one level you have to go through a corridor of lava with a windy potion.<br /> * Half of the levels in this game are impossible to complete.<br /> * You have to go through the water in the wrong direction; but this is, of course, impossible.<br /> * Killing enemies potions are good for you.<br /> <br /> The author would like to assure you that all of these statements are incorrect; but the administration of Digital MZX assures the readers of this page that these statements are in fact correct, and that the author of this game is either lying or making a mistake, or that we have not yet found the actual author of this game.<br /> <br /> [[Category:Games]]</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=Super_ASCII_MZX_Town&diff=7573 2010-11-15T01:01:17Z

<p>Zzo38: </p> <hr /> <div>{{Game| title = Super ASCII MZX Town<br /> |image = Ascmzxto.png<br /> |creator = [[zzo38]]<br /> |company = <br /> |released = 2009<br /> |genre = We don't use &quot;genre&quot; here.<br /> }}<br /> <br /> [[Super ASCII MZX Town]] is a pure ASCII game made by zzo38. Part I uses normal MegaZeux, but Part II (and any subsequent sequels) requires PZX features, so you have to use the same forked version of MegaZeux that zzo38 wrote. These game are not the ordinary slider puzzle. It's different. Unlike other MegaZeux games, in this game you actually have to think about it. And remember also you might try for a high score when completing the game. You can try just to complete the game, or you can try to complete the game with a higher score.<br /> <br /> == Part I ==<br /> You have to get all of the purple keys to reach the final level, where you will see BIG_MONSTER. You also need the keycards to teleport to a different place. This game also has a dark engine and a high-score system. And you get a lot of bonus points for conserved ammo/bombs/gems/health/etc. There is 91 boards in this game (including the title screen).<br /> <br /> == Part II ==<br /> This game is the sequel to Part I. This one also has some platform game levels, and a better dark engine also. This game uses many Forth codes and Robotic codes. And there is magic keycards in this game.<br /> <br /> == Criticize ==<br /> These game have many criticism:<br /> * The sliders on the title screen are not real sliders.<br /> * Most of the levels have yellow borders.<br /> * There is no URL to download this game.<br /> * The scoring system is really bad.<br /> * In one level you have to go through a corridor of lava with a windy potion.<br /> * Half of the levels in this game are impossible to complete.<br /> * You have to go through the water in the wrong direction; but this is, of course, impossible.<br /> * Killing enemies potions are good for you.<br /> <br /> The author would like to assure you that all of these statements are incorrect; but the administration of Digital MZX assures the readers of this page that these statements are in fact correct, and that the author of this game is either lying or making a mistake.<br /> <br /> [[Category:Games]]</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=Super_ASCII_MZX_Town&diff=7572 2010-11-15T01:00:35Z

<p>Zzo38: Criticize</p> <hr /> <div>{{Game| title = Super ASCII MZX Town<br /> |image = Ascmzxto.png<br /> |creator = [[zzo38]]<br /> |company = <br /> |released = 2009<br /> |genre = We don't use &quot;genre&quot; here.<br /> }}<br /> <br /> [[Super ASCII MZX Town]] is a pure ASCII game made by zzo38. Part I uses normal MegaZeux, but Part II (and any subsequent sequels) requires PZX features, so you have to use the same forked version of MegaZeux that zzo38 wrote. These game are not the ordinary slider puzzle. It's different. Unlike other MegaZeux games, in this game you actually have to think about it. And remember also you might try for a high score when completing the game. You can try just to complete the game, or you can try to complete the game with a higher score.<br /> <br /> == Part I ==<br /> You have to get all of the purple keys to reach the final level, where you will see BIG_MONSTER. You also need the keycards to teleport to a different place. This game also has a dark engine and a high-score system. And you get a lot of bonus points for conserved ammo/bombs/gems/health/etc. There is 91 boards in this game (including the title screen).<br /> <br /> == Part II ==<br /> This game is the sequel to Part I. This one also has some platform game levels, and a better dark engine also. This game uses many Forth codes and Robotic codes. And there is magic keycards in this game.<br /> <br /> == Criticize ==<br /> These game have many criticism:<br /> * The sliders on the title screen are not real sliders.<br /> * Most of the levels have yellow borders.<br /> * There is no URL to download this game.<br /> * The scoring system is really bad.<br /> * In one level you have to go through a corridor of lava with a windy potion.<br /> * Half of the levels in this game are impossible to complete.<br /> * You have to go through the water in the wrong direction.<br /> * Killing enemies potions are good for you.<br /> <br /> The author would like to assure you that all of these statements are incorrect; but the administration of Digital MZX assures the readers of this page that these statements are in fact correct, and that the author of this game is either lying or making a mistake.<br /> <br /> [[Category:Games]]</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=Zzo38&diff=7571 2010-11-15T00:42:21Z

<p>Zzo38: </p> <hr /> <div>'''zzo38''' is something of an enigma to the community. Nobody is quite sure if they are a real person or the [[Identity deception|alternative account]] of somebody else, and there doesn't seem to be any evidence pointing in either direction. Typical characteristics of &quot;classic&quot; zzo38 include horribly broken English such as &quot;Old mesiges ar being crosed out.&quot;[http://en.wikipedia.org/w/index.php?title=User_talk:Zzo38&amp;oldid=21293425] and &quot;I think I like the old un-frenly serch more beter.&quot; [http://www.digitalmzx.net/forums/index.php?s=&amp;showtopic=6023&amp;view=findpost&amp;p=77256] and a general lack of effort in things that he does, though that seems to be quite a different story when looking at his more recent activities. (There is some speculation that the &quot;classic&quot; zzo38 may be a joke, a conspiracy, or a different person. But a few of the old stuff is still on the same web-site, so we cannot be exactly sure.)<br /> <br /> zzo38 released several ZZT and MZX games, including [[Cooking Game]], and [[Super ASCII MZX Town]], and also a [[PZX|fork of MegaZeux with different features]].<br /> <br /> Recently&lt;sup&gt;[please specify]&lt;/sup&gt;, zzo has reappeared on the DigitalMZX forums with vastly improved grammar and an apparent fascination with Mahjong games and Forth codes.<br /> <br /> ==MegaZeux Games==<br /> * [[Super ASCII MZX Town]]<br /> <br /> ==External Links==<br /> *[http://zzo38computer.cjb.net/ ZZO38COMPUTER (HTTP)]<br /> *[gopher://zzo38computer.cjb.net/ ZZO38COMPUTER (Gopher)]<br /> *[http://zzo38computer.cjb.net/mzx1/ MegaZeux games]<br /> <br /> {{WeaselStub}}<br /> {{NeedsPeerReview}}</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=PZX&diff=7519 2010-06-26T11:38:02Z

<p>Zzo38: </p> <hr /> <div>'''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.<br /> <br /> * Win32 binaries and source-codes is available at: http://zzo38computer.cjb.net/mzx1/mzx_extended/<br /> * Documentation is available at: http://zzo38computer.cjb.net/mzx1/mzx_extended/doc/<br /> <br /> ==Features==<br /> The biggest contribution of this particular fork is FORTH support. Other changes include the ability to use the old ALT+D function in the editor (only zzo38 seems to remember what this is or use the function to begin with), deferred expressions, extended kinds, new overlay modes and SMZX modes of dubious utility (including the one that draws overlay on the outside of the viewport instead of inside, one that draws only the overlay and not the board, an SMZX mode that uses 16 colors per character (reducing the resolution per character to 4x7), and a blinking text mode), meanings for the other bits in lava_walk, and displacement overlay modes which allow adjustment of the overlay by individual pixels.<br /> <br /> zzo38 also corrected a long standing, esoteric bug in the handling of built-in spider webs, which has been merged (with changes) into the existing codebase.<br /> <br /> To make backward compatibility, the way it works, is if the first line of the global robot is a comment with a greater than sign at beginning (optionally followed by a filename), it will activate PZX mode. If there is a filename, that is the file containing the Forth codes.<br /> <br /> ===Deferred Expressions===<br /> A deferred expression is sort of like having function calls for calling another expression. The operator &lt;tt&gt;,&lt;/tt&gt; sets the current parameter value to the left side and then evaluates the right side, the operator &lt;tt&gt;p&lt;/tt&gt; gets the current parameter, and the operator &lt;tt&gt;`&lt;/tt&gt; allows you to use a deferred expression.<br /> <br /> Because parentheses are used to evaluate expression, it uses square brackets to mean a deferred expression. It will convert &lt;tt&gt;[]&lt;/tt&gt; to &lt;tt&gt;()&lt;/tt&gt; when accessing a deferred expression.<br /> <br /> The &lt;tt&gt;`&lt;/tt&gt; operator is two of &lt;tt&gt;`&lt;/tt&gt; with the name of string in between (including the dollar sign), and it call the deferred expression. You can also use &lt;tt&gt;`&lt;/tt&gt; operator with &lt;tt&gt;*&lt;/tt&gt; followed by a Forth word instead of a string, in which case it will instead call that Forth word to determine the value of the expression.<br /> <br /> ===Extended Kinds===<br /> You can create extended kinds 0x80 to 0xFE (128 to 254) using Forth codes.<br /> <br /> In order to create a extended kind you must indicate:<br /> * The number assigned to it<br /> * The character used to represent it (255 means use the parameter, like a CustomBlock does, and negative number mean various other things)<br /> * The A_ flags associated with it<br /> * How the parameter is decided (the parameter type can come from any built-in)<br /> * The name<br /> And then you can optionally define events for it, such as what happens when it is shot, updated, touched by the player, underneath the player, and so on. Which events are used depends on the A_ flags, although it is possible to have A_ flags without the corresponding events (for example, the simplest way to prevent the player from pushing something that is normally pushable is to give the object the A_ITEM flag without a corresponding event).<br /> <br /> Some new A_ flags have been implemented:<br /> * A_BREAKABLE<br /> * A_USERFLAG<br /> * A_CRUSH<br /> * A_INVISIBLE<br /> * A_ELEMENT (3 bits, and in Forth codes you use AE_WATER and so on instead of typing A_ELEMENT)<br /> <br /> ===Overlay Modes===<br /> Mode 4 makes it draw the overlay outside of the viewport instead of on the inside of the viewport.<br /> <br /> Mode 65 and 66 makes it to not draw the board, and only draw the overlay. (This feature actually already existed in MegaZeux, but there was previously no access to it during the game.)<br /> <br /> Mode 0x7? prevents it from drawing anything at all, allowing Forth codes direct access to the text_video.<br /> <br /> There are also displacement overlay modes 0xA?, 0xB?, 0xE?, which allows pixel-accuracy for drawing characters, and also can make individual pixels transparent (so you can see the character drawn underneath).<br /> <br /> ===Graphics Modes===<br /> Modes 0 to 3 are same as normal MegaZeux. Mode 64 to 67 are the mode for 16 colors per character. Mode 141 makes blinking text.<br /> <br /> ==Use of Attribute Flags==<br /> The flags are as follows (any combination can be used, except for a few exceptions):<br /> * A_PUSHNS: Allows object to be pushed north/south<br /> * A_PUSHEW: Allows object ot be push east/west<br /> * A_PUSHABLE: Object can be pushed in any direction (Do not combine with A_PUSHNS or A_PUSHEW)<br /> * A_ITEM: Calls EV.ITEM event when player touches it. Player will not automatically push or stand on this object<br /> * A_UPDATE: EV.UPDATE event will be called every step unless freeze time is active<br /> * A_HURTS: Causes damage when player hits it<br /> * A_UNDER: Things can stand on this<br /> * A_ENTRANCE: Parameter is a board number, if the player steps here it will teleport the player to that board<br /> * A_EXPLODE: Object is explosive<br /> * A_BLOW_UP: Object can blow up<br /> * A_SHOOTABLE: Player bullets and neutral bullets can destroy this<br /> * A_BREAKABLE: Any bullets can destroy this (Do not combine with A_SHOOTABLE or A_SPEC_SHOT)<br /> * A_ENEMY: Used in various purposes by MegaZeux<br /> * A_AFFECTSTOOD: Calls EV.AFFECTSTOOD event every step if the player is standing here<br /> * A_SPEC_SHOT: Calls EV.SHOT event if hit by a bullet<br /> * A_SPEC_PUSH: Object can be pushed in any direction<br /> * A_SPEC_BOMB: Calls EV.BOMB event when explosion hits it<br /> * A_SPEC_STOOD: Player can stand here, even if other things can't<br /> * A_USERFLAG: Does nothing<br /> * A_CRUSH: Object can be crushed like in ZZT<br /> * A_INVISIBLE: Draws using under color, or draws black if this is the under object<br /> * A_SEEBLIND: Object is visible even if the player is blind<br /> <br /> There are also element flags (up to one of these flags can be used):<br /> * AE_WATER: Things that are not allowed to move onto water won't move onto here<br /> * AE_FIRE: Things that are not allowed to move onto fire won't move onto here<br /> * AE_LAVA: Things that are not allowed to move onto lava won't move onto here, also cannot be pushed or pushed onto<br /> * AE_GOOP: Things that are not allowed to move onto goop won't move onto here, also cannot be pushed or pushed onto<br /> * AE_THINWEB: Spiders that can move on thin webs are allowed to step here<br /> * AE_THICKWEB: Spiders that can move on thick webs are allowed to step here<br /> * AE_PLAYER: Cannot be pushed by things that react with the player<br /> <br /> ==Use of Events==<br /> The following events exist in game and are not corresponding to any particular object:<br /> * EV.PLAYERMOVING ( dir edge offset -- cancel ) Called to determine whether or not the player is allowed to move<br /> * EV.KEYBOARD ( key -- canceldefault ) Called when a key is pushed, can tell it to cancel the default function of that key<br /> * EV.LOADED ( category -- ) When game is started or restored<br /> * EV.ENTERED ( category -- ) When the board is switched<br /> * EV.BULLETHIT ( offset bulletoffset parameter -- category ) Indicates that a bullet is about to hit something solid<br /> <br /> These events are corresponding to specific objects (add the extended kind number to the event code):<br /> * EV.PUSH ( offset dir category distance -- ) Called when an object is being pushed<br /> * EV.ITEM ( offset dir -- remove ) Called when the player touches an object with A_ITEM flag<br /> * EV.AFFECTSTOOD ( offset -- ) The player is stand on object with A_AFFECTSTOOD<br /> * EV.UPDATE ( offset -- ) Something with A_UPDATE is being updated<br /> * EV.SHOT ( offset bulletoffset dir bullettype -- ) Something with A_SPEC_SHOT is being hit by a bullet<br /> * EV.BOMB ( offset -- ) Something with A_SPEC_BOMB is hit by an explosion<br /> * EV.LAZER ( lazeroffset offset dir -- blocking ) Object hit by lazer beam, can block lazer or allow beam to be transmitted through<br /> * EV.ARRIVE ( offset -- ) Another object has arrived on top of this object<br /> * EV.TESTPUSH ( offset dir category distance -- cancel ) Testing whether or not an object is allowed to be pushed<br /> <br /> The following events are used in the editor:<br /> * EV.EDITORKEY ( color thing param offset key keymod -- color thing param offset canceldefault ) A key is pushed during editing<br /> * EV.BEFOREADDBOARD ( -- ? ) Before a new board is being added, the current board will be the old current board<br /> * 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<br /> <br /> ==Examples of Forth Codes==<br /> Please note that all examples are case-insensitive, just like anything else in MegaZeux.<br /> <br /> ===ZZT Keys===<br /> 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):<br /> INCLUDE megazeux.4th<br /> <br /> $80 12 A_ITEM A_PUSHABLE + 0 EXTKIND ZztKey<br /> ZztKey EV.ITEM + :EVENT<br /> DROP BOARD_COLOR + @ DUP TAKEKEY SWAP GIVEKEY DROP<br /> IF<br /> &quot;You already have the key!&quot; SETMESG 9 BISFX 0<br /> ELSE<br /> &quot;You now have the key.&quot; SETMESG 8 BISFX 1<br /> THEN<br /> ;<br /> I will explain each line and part of line one by one so that you can follow:<br /> INCLUDE megazeux.4th<br /> This loads the standard libraries of Forth codes.<br /> $80<br /> 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)<br /> 12<br /> This means it will display as character 12.<br /> A_ITEM A_PUSHABLE +<br /> 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).<br /> 0<br /> It will not ask for a parameter when placed in the editor.<br /> EXTKIND ZztKey<br /> 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.<br /> ZztKey EV.ITEM + :EVENT<br /> Adding ZztKey to EV.ITEM gets the number of the item event for the ZztKey. :EVENT tells it to start compiling an event code.<br /> DROP<br /> The top parameter passed to the EV.ITEM event is dir, which we aren't using, so we DROP it.<br /> BOARD_COLOR + @<br /> 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.<br /> DUP<br /> We are using the color twice, so we duplicate it.<br /> TAKEKEY<br /> Attempt to take away that color of key from the player, and gets a success code.<br /> SWAP<br /> We want to pass the color, not the success code to GIVEKEY, so we SWAP it.<br /> GIVEKEY DROP<br /> 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.<br /> IF<br /> 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)<br /> &quot;You already have the key!&quot; SETMESG 9 BISFX<br /> Gives the player a message and plays a sound effect.<br /> 0<br /> Zero is the value returned from the event (the &quot;remove&quot; parameter), meaning the object shouldn't be removed from the screen.<br /> ELSE &quot;You now have the key.&quot; SETMESG 8 BISFX<br /> Another message and sound effect.<br /> 1<br /> Any non-zero value means the object will be removed from the screen (because the player has just picked up the key).<br /> THEN<br /> 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 &quot;do this, and then do this...&quot; rather than &quot;if this then this...&quot;<br /> ;<br /> And this signals the end of the event code, and exits compile mode.<br /> <br /> [[Category:MegaZeux]]</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=PZX&diff=7133 2009-09-13T00:11:57Z

<p>Zzo38: documentation link</p> <hr /> <div>'''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.<br /> <br /> * Win32 binaries and source-codes is available at: http://zzo38computer.cjb.net/mzx1/mzx_extended/<br /> * Documentation is available at: http://zzo38computer.cjb.net/mzx1/mzx_extended/doc/<br /> <br /> ==Features==<br /> The biggest contribution of this particular fork is FORTH support. Other changes include the ability to use the old ALT+D function in the editor (only zzo38 seems to remember what this is or use the function to begin with), deferred expressions, extended kinds, new overlay modes and SMZX modes of dubious utility (including the one that draws overlay on the outside of the viewport instead of inside, one that draws only the overlay and not the board, an SMZX mode that uses 16 colors per character (reducing the resolution per character to 4x7), and a blinking text mode), meanings for the other bits in lava_walk, and displacement overlay modes which allow adjustment of the overlay by individual pixels.<br /> <br /> zzo38 also corrected a long standing, esoteric bug in the handling of built-in spider webs, which has been merged (with changes) into the existing codebase.<br /> <br /> To make backward compatibility, the way it works, is if the first line of the global robot is a comment with a greater than sign at beginning (optionally followed by a filename), it will activate PZX mode. If there is a filename, that is the file containing the Forth codes.<br /> <br /> ===Deferred Expressions===<br /> A deferred expression is sort of like having function calls for calling another expression. The operator &lt;tt&gt;,&lt;/tt&gt; sets the current parameter value to the left side and then evaluates the right side, the operator &lt;tt&gt;p&lt;/tt&gt; gets the current parameter, and the operator &lt;tt&gt;`&lt;/tt&gt; allows you to use a deferred expression.<br /> <br /> Because parentheses are used to evaluate expression, it uses square brackets to mean a deferred expression. It will convert &lt;tt&gt;[]&lt;/tt&gt; to &lt;tt&gt;()&lt;/tt&gt; when accessing a deferred expression.<br /> <br /> The &lt;tt&gt;`&lt;/tt&gt; operator is two of &lt;tt&gt;`&lt;/tt&gt; with the name of string in between (including the dollar sign), and it call the deferred expression. You can also use &lt;tt&gt;`&lt;/tt&gt; operator with &lt;tt&gt;*&lt;/tt&gt; followed by a Forth word instead of a string, in which case it will instead call that Forth word to determine the value of the expression.<br /> <br /> ===Extended Kinds===<br /> You can create extended kinds 0x80 to 0xFE (128 to 254) using Forth codes.<br /> <br /> In order to create a extended kind you must indicate:<br /> * The number assigned to it<br /> * The character used to represent it (255 means use the parameter, like a CustomBlock does, and negative number mean various other things)<br /> * The A_ flags associated with it<br /> * How the parameter is decided (the parameter type can come from any built-in)<br /> * The name<br /> And then you can optionally define events for it, such as what happens when it is shot, updated, touched by the player, underneath the player, and so on. Which events are used depends on the A_ flags, although it is possible to have A_ flags without the corresponding events (for example, the simplest way to prevent the player from pushing something that is normally pushable is to give the object the A_ITEM flag without a corresponding event).<br /> <br /> Some new A_ flags have been implemented:<br /> * A_BREAKABLE<br /> * A_USERFLAG<br /> * A_CRUSH<br /> * A_INVISIBLE<br /> * A_ELEMENT (3 bits, and in Forth codes you use AE_WATER and so on instead of typing A_ELEMENT)<br /> <br /> ===Overlay Modes===<br /> Mode 4 makes it draw the overlay outside of the viewport instead of on the inside of the viewport.<br /> <br /> Mode 65 and 66 makes it to not draw the board, and only draw the overlay. (This feature actually already existed in MegaZeux, but there was previously no access to it during the game.)<br /> <br /> Mode 0x7? prevents it from drawing anything at all, allowing Forth codes direct access to the text_video.<br /> <br /> There are also displacement overlay modes 0xA?, 0xB?, 0xE?, which allows pixel-accuracy for drawing characters, and also can make individual pixels transparent (so you can see the character drawn underneath).<br /> <br /> ===Graphics Modes===<br /> Modes 0 to 3 are same as normal MegaZeux. Mode 64 to 67 are the mode for 16 colors per character. Mode 141 makes blinking text.<br /> <br /> ==Use of Attribute Flags==<br /> The flags are as follows (any combination can be used, except for a few exceptions):<br /> * A_PUSHNS: Allows object to be pushed north/south<br /> * A_PUSHEW: Allows object ot be push east/west<br /> * A_PUSHABLE: Object can be pushed in any direction (Do not combine with A_PUSHNS or A_PUSHEW)<br /> * A_ITEM: Calls EV.ITEM event when player touches it. Player will not automatically push or stand on this object<br /> * A_UPDATE: EV.UPDATE event will be called every step unless freeze time is active<br /> * A_HURTS: Causes damage when player hits it<br /> * A_UNDER: Things can stand on this<br /> * A_ENTRANCE: Parameter is a board number, if the player steps here it will teleport the player to that board<br /> * A_EXPLODE: Object is explosive<br /> * A_BLOW_UP: Object can blow up<br /> * A_SHOOTABLE: Player bullets and neutral bullets can destroy this<br /> * A_BREAKABLE: Any bullets can destroy this (Do not combine with A_SHOOTABLE or A_SPEC_SHOT)<br /> * A_ENEMY: Used in various purposes by MegaZeux<br /> * A_AFFECTSTOOD: Calls EV.AFFECTSTOOD event every step if the player is standing here<br /> * A_SPEC_SHOT: Calls EV.SHOT event if hit by a bullet<br /> * A_SPEC_PUSH: Object can be pushed in any direction<br /> * A_SPEC_BOMB: Calls EV.BOMB event when explosion hits it<br /> * A_SPEC_STOOD: Player can stand here, even if other things can't<br /> * A_USERFLAG: Does nothing<br /> * A_CRUSH: Object can be crushed like in ZZT<br /> * A_INVISIBLE: Draws using under color, or draws black if this is the under object<br /> * A_SEEBLIND: Object is visible even if the player is blind<br /> <br /> There are also element flags (up to one of these flags can be used):<br /> * AE_WATER: Things that are not allowed to move onto water won't move onto here<br /> * AE_FIRE: Things that are not allowed to move onto fire won't move onto here<br /> * AE_LAVA: Things that are not allowed to move onto lava won't move onto here, also cannot be pushed or pushed onto<br /> * AE_GOOP: Things that are not allowed to move onto goop won't move onto here, also cannot be pushed or pushed onto<br /> * AE_THINWEB: Spiders that can move on thin webs are allowed to step here<br /> * AE_THICKWEB: Spiders that can move on thick webs are allowed to step here<br /> * AE_PLAYER: Cannot be pushed by things that react with the player<br /> <br /> ==Use of Events==<br /> The following events exist in game and are not corresponding to any particular object:<br /> * EV.PLAYERMOVING ( dir edge offset -- cancel ) Called to determine whether or not the player is allowed to move<br /> * EV.KEYBOARD ( key -- canceldefault ) Called when a key is pushed, can tell it to cancel the default function of that key<br /> * EV.LOADED ( category -- ) When game is started or restored<br /> * EV.ENTERED ( category -- ) When the board is switched<br /> * EV.BULLETHIT ( offset bulletoffset parameter -- category ) Indicates that a bullet is about to hit something solid<br /> <br /> These events are corresponding to specific objects (add the extended kind number to the event code):<br /> * EV.PUSH ( offset dir category distance -- ) Called when an object is being pushed<br /> * EV.ITEM ( offset dir -- remove ) Called when the player touches an object with A_ITEM flag<br /> * EV.AFFECTSTOOD ( offset -- ) The player is stand on object with A_AFFECTSTOOD<br /> * EV.UPDATE ( offset -- ) Something with A_UPDATE is being updated<br /> * EV.SHOT ( offset bulletoffset dir bullettype -- ) Something with A_SPEC_SHOT is being hit by a bullet<br /> * EV.BOMB ( offset -- ) Something with A_SPEC_BOMB is hit by an explosion<br /> * EV.LAZER ( lazeroffset offset dir -- blocking ) Object hit by lazer beam, can block lazer or allow beam to be transmitted through<br /> * EV.ARRIVE ( offset -- ) Another object has arrived on top of this object<br /> * EV.TESTPUSH ( offset dir category distance -- cancel ) Testing whether or not an object is allowed to be pushed<br /> <br /> The following events are used in the editor:<br /> * EV.EDITORKEY ( color thing param offset key keymod -- color thing param offset canceldefault ) A key is pushed during editing<br /> * EV.BEFOREADDBOARD ( -- ? ) Before a new board is being added, the current board will be the old current board<br /> * 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<br /> <br /> ==Examples of Forth Codes==<br /> Please note that all examples are case-insensitive, just like anything else in MegaZeux.<br /> <br /> ===ZZT Keys===<br /> Here is a code to implement a ZZT key:<br /> INCLUDE megazeux.4th<br /> <br /> $80 12 A_ITEM A_PUSHABLE + 0 EXTKIND ZztKey<br /> ZztKey EV.ITEM + :EVENT<br /> DROP BOARD_COLOR + @ DUP TAKEKEY SWAP GIVEKEY DROP<br /> IF<br /> &quot;You already have the key!&quot; SETMESG 9 BISFX 0<br /> ELSE<br /> &quot;You now have the key.&quot; SETMESG 8 BISFX 1<br /> THEN<br /> ;<br /> I will explain each line and part of line one by one so that you can follow:<br /> INCLUDE megazeux.4th<br /> This loads the standard libraries of Forth codes.<br /> $80<br /> 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)<br /> 12<br /> This means it will display as character 12.<br /> A_ITEM A_PUSHABLE +<br /> 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).<br /> 0<br /> It will not ask for a parameter when placed in the editor.<br /> EXTKIND ZztKey<br /> 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.<br /> ZztKey EV.ITEM + :EVENT<br /> Adding ZztKey to EV.ITEM gets the number of the item event for the ZztKey. :EVENT tells it to start compiling an event code.<br /> DROP<br /> The top parameter passed to the EV.ITEM event is dir, which we aren't using, so we DROP it.<br /> BOARD_COLOR + @<br /> 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.<br /> DUP<br /> We are using the color twice, so we duplicate it.<br /> TAKEKEY<br /> Attempt to take away that color of key from the player, and gets a success code.<br /> SWAP<br /> We want to pass the color, not the success code to GIVEKEY, so we SWAP it.<br /> GIVEKEY DROP<br /> 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.<br /> IF<br /> 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)<br /> &quot;You already have the key!&quot; SETMESG 9 BISFX<br /> Gives the player a message and plays a sound effect.<br /> 0<br /> Zero is the value returned from the event (the &quot;remove&quot; parameter), meaning the object shouldn't be removed from the screen.<br /> ELSE &quot;You now have the key.&quot; SETMESG 8 BISFX<br /> Another message and sound effect.<br /> 1<br /> Any non-zero value means the object will be removed from the screen (because the player has just picked up the key).<br /> THEN<br /> 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 &quot;do this, and then do this...&quot; rather than &quot;if this then this...&quot;<br /> ;<br /> And this signals the end of the event code, and exits compile mode.</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=Zzo38&diff=7132 2009-09-13T00:02:33Z

<p>Zzo38: </p> <hr /> <div>'''zzo38''' is something of an enigma to the community. Nobody is quite sure if they are a real person or the [[Identity deception|alternative account]] of somebody else, and there doesn't seem to be any evidence pointing in either direction. Typical characteristics of &quot;classic&quot; zzo38 include horribly broken English such as &quot;Old mesiges ar being crosed out.&quot;[http://en.wikipedia.org/w/index.php?title=User_talk:Zzo38&amp;oldid=21293425] and &quot;I think I like the old un-frenly serch more beter.&quot; [http://www.digitalmzx.net/forums/index.php?s=&amp;showtopic=6023&amp;view=findpost&amp;p=77256] and a general lack of effort in things that he does, though that seems to be quite a different story when looking at his more recent activities. (There is some speculation that the &quot;classic&quot; zzo38 may be a joke, a conspiracy, or a different person. But a few of the old stuff is still on the same web-site, so we cannot be exactly sure.)<br /> <br /> zzo38 released several ZZT and MZX games, including [[Cooking Game]], and [[Super ASCII MZX Town]], and also a [[PZX|fork of MegaZeux with different features]].<br /> <br /> Recently&lt;sup&gt;[please specify]&lt;/sup&gt;, zzo has reappeared on the DigitalMZX forums with vastly improved grammar and an apparent fascination with Mahjong games and Forth codes.<br /> <br /> ==External Links==<br /> *[http://zzo38computer.cjb.net/ ZZO38COMPUTER (HTTP)]<br /> *[gopher://zzo38computer.cjb.net/ ZZO38COMPUTER (Gopher)]<br /> *[http://zzo38computer.cjb.net/mzx1/ MegaZeux games]<br /> <br /> {{WeaselStub}}<br /> {{NeedsPeerReview}}</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=Zzo38&diff=7131 2009-09-13T00:01:43Z

<p>Zzo38: The wiki is not used, replaced external links.</p> <hr /> <div>'''zzo38''' is something of an enigma to the community. Nobody is quite sure if they are a real person or the [[Identity deception|alternative account]] of somebody else, and there doesn't seem to be any evidence pointing in either direction. Typical characteristics of &quot;classic&quot; zzo38 include horribly broken English such as &quot;Old mesiges ar being crosed out.&quot;[http://en.wikipedia.org/w/index.php?title=User_talk:Zzo38&amp;oldid=21293425] and &quot;I think I like the old un-frenly serch more beter.&quot; [http://www.digitalmzx.net/forums/index.php?s=&amp;showtopic=6023&amp;view=findpost&amp;p=77256] and a general lack of effort in things that he does, though that seems to be quite a different story when looking at his more recent activities. (There is some speculation that the &quot;classic&quot; zzo38 may be a joke, a conspiracy, or a different person. But a few of the old stuff is still on the same web-site, so we cannot be exactly sure.)<br /> <br /> zzo38 released several ZZT and MZX games, including [[Cooking Game]].<br /> <br /> Recently&lt;sup&gt;[please specify]&lt;/sup&gt;, zzo has reappeared on the DigitalMZX forums with vastly improved grammar and an apparent fascination with Mahjong games and Forth codes.<br /> <br /> ==External Links==<br /> *[http://zzo38computer.cjb.net/ ZZO38COMPUTER (HTTP)]<br /> *[gopher://zzo38computer.cjb.net/ ZZO38COMPUTER (Gopher)]<br /> *[http://zzo38computer.cjb.net/mzx1/ MegaZeux games]<br /> <br /> {{WeaselStub}}<br /> {{NeedsPeerReview}}</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=Super_ASCII_MZX_Town&diff=7130 2009-09-12T23:58:49Z

<p>Zzo38: </p> <hr /> <div>{{Game| title = Super ASCII MZX Town<br /> |image = Ascmzxto.png<br /> |creator = [[zzo38]]<br /> |company = <br /> |released = 2009<br /> |genre = We don't use &quot;genre&quot; here.<br /> }}<br /> <br /> [[Super ASCII MZX Town]] is a pure ASCII game made by zzo38. Part I uses normal MegaZeux, but Part II (and any subsequent sequels) requires PZX features, so you have to use the same forked version of MegaZeux that zzo38 wrote. These game are not the ordinary slider puzzle. It's different. Unlike other MegaZeux games, in this game you actually have to think about it. And remember also you might try for a high score when completing the game. You can try just to complete the game, or you can try to complete the game with a higher score.<br /> <br /> == Part I ==<br /> You have to get all of the purple keys to reach the final level, where you will see BIG_MONSTER. You also need the keycards to teleport to a different place. This game also has a dark engine and a high-score system. And you get a lot of bonus points for conserved ammo/bombs/gems/health/etc. There is 91 boards in this game (including the title screen).<br /> <br /> == Part II ==<br /> This game is the sequel to Part I. This one also has some platform game levels, and a better dark engine also. This game uses many Forth codes and Robotic codes. And there is magic keycards in this game.<br /> <br /> [[Category:Games]]</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=File:Ascmzxto.png&diff=7129 2009-09-12T23:57:53Z

<p>Zzo38: Super ASCII MZX Town! &lt;div class=&quot;tag&quot; style=&quot;margin:0.5em auto;width:40%;clear:both;background-color:transparent;border:2px solid #8888aa; padding:4px;font-size:85%;min-height:64px;vertical-align:center&quot; id=&quot;imageLicense&quot;&gt; &lt;div style=&quot;float:left&quot; id=&quot;i</p> <hr /> <div>Super ASCII MZX Town!<br /> <br /> &lt;div class=&quot;tag&quot; style=&quot;margin:0.5em auto;width:40%;clear:both;background-color:transparent;border:2px solid #8888aa; padding:4px;font-size:85%;min-height:64px;vertical-align:center&quot; id=&quot;imageLicense&quot;&gt;<br /> <br /> &lt;div style=&quot;float:left&quot; id=&quot;icon&quot;&gt;[[Image:NoCopyright.png|32px|No copyright]]&lt;/div&gt;<br /> <br /> &lt;div style=&quot;text-align:left;margin-left:68px&quot; id=&quot;text&quot;&gt;<br /> This is a picture from a [[MegaZeux]] game made by [[zzo38]], and is therefore public domain.<br /> &lt;/div&gt;<br /> &lt;/div&gt;</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=File:NoCopyright.png&diff=7128 2009-09-12T23:57:43Z

<p>Zzo38: public domain</p> <hr /> <div>public domain</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=Super_ASCII_MZX_Town&diff=6958 2009-07-22T20:24:40Z

<p>Zzo38: New page: {{Game| title = Super ASCII MZX Town |image = |creator = zzo38 |company = |released = 2009 |genre = }} Super ASCII MZX Town is a pure ASCII game made by zzo38. Part I uses norm...</p> <hr /> <div>{{Game| title = Super ASCII MZX Town<br /> |image = <br /> |creator = [[zzo38]]<br /> |company = <br /> |released = 2009<br /> |genre = <br /> }}<br /> <br /> [[Super ASCII MZX Town]] is a pure ASCII game made by zzo38. Part I uses normal MegaZeux, but Part II (and any subsequent sequels) requires PZX features, so you have to use the same forked version of MegaZeux that zzo38 wrote. These game are not the ordinary slider puzzle. It's different. Unlike other MegaZeux games, in this game you actually have to think about it. And remember also you might try for a high score when completing the game. You can try just to complete the game, or you can try to complete the game with a higher score.<br /> <br /> == Part I ==<br /> You have to get all of the purple keys to reach the final level, where you will see BIG_MONSTER. You also need the keycards to teleport to a different place. This game also has a dark engine and a high-score system. And you get a lot of bonus points for conserved ammo/bombs/gems/health/etc. There is 91 boards in this game (including the title screen).<br /> <br /> == Part II ==<br /> This game is the sequel to Part I. This one also has some platform game levels, and a better dark engine also. This game uses many Forth codes and Robotic codes. And there is magic keycards in this game.<br /> <br /> [[Category:Games]]</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=PZX&diff=6880 2009-06-25T19:39:12Z

<p>Zzo38: </p> <hr /> <div>'''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.<br /> <br /> ==Features==<br /> The biggest contribution of this particular fork is FORTH support. Other changes include the ability to use the old ALT+D function in the editor (only zzo38 seems to remember what this is or use the function to begin with), deferred expressions, extended kinds, new overlay modes and SMZX modes of dubious utility (including the one that draws overlay on the outside of the viewport instead of inside, one that draws only the overlay and not the board, an SMZX mode that uses 16 colors per character (reducing the resolution per character to 4x7), and a blinking text mode), meanings for the other bits in lava_walk, and displacement overlay modes which allow adjustment of the overlay by individual pixels.<br /> <br /> zzo38 also corrected a long standing, esoteric bug in the handling of built-in spider webs, which has been merged (with changes) into the existing codebase.<br /> <br /> To make backward compatibility, the way it works, is if the first line of the global robot is a comment with a greater than sign at beginning (optionally followed by a filename), it will activate PZX mode. If there is a filename, that is the file containing the Forth codes.<br /> <br /> ===Deferred Expressions===<br /> A deferred expression is sort of like having function calls for calling another expression. The operator &lt;tt&gt;,&lt;/tt&gt; sets the current parameter value to the left side and then evaluates the right side, the operator &lt;tt&gt;p&lt;/tt&gt; gets the current parameter, and the operator &lt;tt&gt;`&lt;/tt&gt; allows you to use a deferred expression.<br /> <br /> Because parentheses are used to evaluate expression, it uses square brackets to mean a deferred expression. It will convert &lt;tt&gt;[]&lt;/tt&gt; to &lt;tt&gt;()&lt;/tt&gt; when accessing a deferred expression.<br /> <br /> The &lt;tt&gt;`&lt;/tt&gt; operator is two of &lt;tt&gt;`&lt;/tt&gt; with the name of string in between (including the dollar sign), and it call the deferred expression. You can also use &lt;tt&gt;`&lt;/tt&gt; operator with &lt;tt&gt;*&lt;/tt&gt; followed by a Forth word instead of a string, in which case it will instead call that Forth word to determine the value of the expression.<br /> <br /> ===Extended Kinds===<br /> You can create extended kinds 0x80 to 0xFE (128 to 254) using Forth codes.<br /> <br /> In order to create a extended kind you must indicate:<br /> * The number assigned to it<br /> * The character used to represent it (255 means use the parameter, like a CustomBlock does, and negative number mean various other things)<br /> * The A_ flags associated with it<br /> * How the parameter is decided (the parameter type can come from any built-in)<br /> * The name<br /> And then you can optionally define events for it, such as what happens when it is shot, updated, touched by the player, underneath the player, and so on. Which events are used depends on the A_ flags, although it is possible to have A_ flags without the corresponding events (for example, the simplest way to prevent the player from pushing something that is normally pushable is to give the object the A_ITEM flag without a corresponding event).<br /> <br /> Some new A_ flags have been implemented:<br /> * A_BREAKABLE<br /> * A_USERFLAG<br /> * A_CRUSH<br /> * A_INVISIBLE<br /> * A_ELEMENT (3 bits, and in Forth codes you use AE_WATER and so on instead of typing A_ELEMENT)<br /> <br /> ===Overlay Modes===<br /> Mode 4 makes it draw the overlay outside of the viewport instead of on the inside of the viewport.<br /> <br /> Mode 65 and 66 makes it to not draw the board, and only draw the overlay. (This feature actually already existed in MegaZeux, but there was previously no access to it during the game.)<br /> <br /> Mode 0x7? prevents it from drawing anything at all, allowing Forth codes direct access to the text_video.<br /> <br /> There are also displacement overlay modes 0xA?, 0xB?, 0xE?, which allows pixel-accuracy for drawing characters, and also can make individual pixels transparent (so you can see the character drawn underneath).<br /> <br /> ===Graphics Modes===<br /> Modes 0 to 3 are same as normal MegaZeux. Mode 64 to 67 are the mode for 16 colors per character. Mode 141 makes blinking text.<br /> <br /> ==Use of Attribute Flags==<br /> The flags are as follows (any combination can be used, except for a few exceptions):<br /> * A_PUSHNS: Allows object to be pushed north/south<br /> * A_PUSHEW: Allows object ot be push east/west<br /> * A_PUSHABLE: Object can be pushed in any direction (Do not combine with A_PUSHNS or A_PUSHEW)<br /> * A_ITEM: Calls EV.ITEM event when player touches it. Player will not automatically push or stand on this object<br /> * A_UPDATE: EV.UPDATE event will be called every step unless freeze time is active<br /> * A_HURTS: Causes damage when player hits it<br /> * A_UNDER: Things can stand on this<br /> * A_ENTRANCE: Parameter is a board number, if the player steps here it will teleport the player to that board<br /> * A_EXPLODE: Object is explosive<br /> * A_BLOW_UP: Object can blow up<br /> * A_SHOOTABLE: Player bullets and neutral bullets can destroy this<br /> * A_BREAKABLE: Any bullets can destroy this (Do not combine with A_SHOOTABLE or A_SPEC_SHOT)<br /> * A_ENEMY: Used in various purposes by MegaZeux<br /> * A_AFFECTSTOOD: Calls EV.AFFECTSTOOD event every step if the player is standing here<br /> * A_SPEC_SHOT: Calls EV.SHOT event if hit by a bullet<br /> * A_SPEC_PUSH: Object can be pushed in any direction<br /> * A_SPEC_BOMB: Calls EV.BOMB event when explosion hits it<br /> * A_SPEC_STOOD: Player can stand here, even if other things can't<br /> * A_USERFLAG: Does nothing<br /> * A_CRUSH: Object can be crushed like in ZZT<br /> * A_INVISIBLE: Draws using under color, or draws black if this is the under object<br /> * A_SEEBLIND: Object is visible even if the player is blind<br /> <br /> There are also element flags (up to one of these flags can be used):<br /> * AE_WATER: Things that are not allowed to move onto water won't move onto here<br /> * AE_FIRE: Things that are not allowed to move onto fire won't move onto here<br /> * AE_LAVA: Things that are not allowed to move onto lava won't move onto here, also cannot be pushed or pushed onto<br /> * AE_GOOP: Things that are not allowed to move onto goop won't move onto here, also cannot be pushed or pushed onto<br /> * AE_THINWEB: Spiders that can move on thin webs are allowed to step here<br /> * AE_THICKWEB: Spiders that can move on thick webs are allowed to step here<br /> * AE_PLAYER: Cannot be pushed by things that react with the player<br /> <br /> ==Use of Events==<br /> The following events exist in game and are not corresponding to any particular object:<br /> * EV.PLAYERMOVING ( dir edge offset -- cancel ) Called to determine whether or not the player is allowed to move<br /> * EV.KEYBOARD ( key -- canceldefault ) Called when a key is pushed, can tell it to cancel the default function of that key<br /> * EV.LOADED ( category -- ) When game is started or restored<br /> * EV.ENTERED ( category -- ) When the board is switched<br /> * EV.BULLETHIT ( offset bulletoffset parameter -- category ) Indicates that a bullet is about to hit something solid<br /> <br /> These events are corresponding to specific objects (add the extended kind number to the event code):<br /> * EV.PUSH ( offset dir category distance -- ) Called when an object is being pushed<br /> * EV.ITEM ( offset dir -- remove ) Called when the player touches an object with A_ITEM flag<br /> * EV.AFFECTSTOOD ( offset -- ) The player is stand on object with A_AFFECTSTOOD<br /> * EV.UPDATE ( offset -- ) Something with A_UPDATE is being updated<br /> * EV.SHOT ( offset bulletoffset dir bullettype -- ) Something with A_SPEC_SHOT is being hit by a bullet<br /> * EV.BOMB ( offset -- ) Something with A_SPEC_BOMB is hit by an explosion<br /> * EV.LAZER ( lazeroffset offset dir -- blocking ) Object hit by lazer beam, can block lazer or allow beam to be transmitted through<br /> * EV.ARRIVE ( offset -- ) Another object has arrived on top of this object<br /> * EV.TESTPUSH ( offset dir category distance -- cancel ) Testing whether or not an object is allowed to be pushed<br /> <br /> The following events are used in the editor:<br /> * EV.EDITORKEY ( color thing param offset key keymod -- color thing param offset canceldefault ) A key is pushed during editing<br /> * EV.BEFOREADDBOARD ( -- ? ) Before a new board is being added, the current board will be the old current board<br /> * 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<br /> <br /> ==Examples of Forth Codes==<br /> Please note that all examples are case-insensitive, just like anything else in MegaZeux.<br /> <br /> ===ZZT Keys===<br /> Here is a code to implement a ZZT key:<br /> INCLUDE megazeux.4th<br /> <br /> $80 12 A_ITEM A_PUSHABLE + 0 EXTKIND ZztKey<br /> ZztKey EV.ITEM + :EVENT<br /> DROP BOARD_COLOR + @ DUP TAKEKEY SWAP GIVEKEY DROP<br /> IF<br /> &quot;You already have the key!&quot; SETMESG 9 BISFX 0<br /> ELSE<br /> &quot;You now have the key.&quot; SETMESG 8 BISFX 1<br /> THEN<br /> ;<br /> I will explain each line and part of line one by one so that you can follow:<br /> INCLUDE megazeux.4th<br /> This loads the standard libraries of Forth codes.<br /> $80<br /> 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)<br /> 12<br /> This means it will display as character 12.<br /> A_ITEM A_PUSHABLE +<br /> 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).<br /> 0<br /> It will not ask for a parameter when placed in the editor.<br /> EXTKIND ZztKey<br /> 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.<br /> ZztKey EV.ITEM + :EVENT<br /> Adding ZztKey to EV.ITEM gets the number of the item event for the ZztKey. :EVENT tells it to start compiling an event code.<br /> DROP<br /> The top parameter passed to the EV.ITEM event is dir, which we aren't using, so we DROP it.<br /> BOARD_COLOR + @<br /> 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.<br /> DUP<br /> We are using the color twice, so we duplicate it.<br /> TAKEKEY<br /> Attempt to take away that color of key from the player, and gets a success code.<br /> SWAP<br /> We want to pass the color, not the success code to GIVEKEY, so we SWAP it.<br /> GIVEKEY DROP<br /> 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.<br /> IF<br /> 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)<br /> &quot;You already have the key!&quot; SETMESG 9 BISFX<br /> Gives the player a message and plays a sound effect.<br /> 0<br /> Zero is the value returned from the event (the &quot;remove&quot; parameter), meaning the object shouldn't be removed from the screen.<br /> ELSE &quot;You now have the key.&quot; SETMESG 8 BISFX<br /> Another message and sound effect.<br /> 1<br /> Any non-zero value means the object will be removed from the screen (because the player has just picked up the key).<br /> THEN<br /> 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 &quot;do this, and then do this...&quot; rather than &quot;if this then this...&quot;<br /> ;<br /> And this signals the end of the event code, and exits compile mode.</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=PZX&diff=6863 2009-06-20T05:28:09Z

<p>Zzo38: </p> <hr /> <div>'''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.<br /> <br /> ==Features==<br /> The biggest contribution of this particular fork is FORTH support. Other changes include the ability to use the old ALT+D function in the editor (only zzo38 seems to remember what this is or use the function to begin with), deferred expressions, extended kinds, new overlay modes and SMZX modes of dubious utility (including the one that draws overlay on the outside of the viewport instead of inside, one that draws only the overlay and not the board, an SMZX mode that uses 16 colors per character (reducing the resolution per character to 4x7), and a blinking text mode), meanings for the other bits in lava_walk, and displacement overlay modes which allow adjustment of the overlay by individual pixels.<br /> <br /> zzo38 also corrected a long standing, esoteric bug in the handling of built-in spider webs, which has been merged (with changes) into the existing codebase.<br /> <br /> To make backward compatibility, the way it works, is if the first line of the global robot is a comment with a greater than sign at beginning (optionally followed by a filename), it will activate PZX mode. If there is a filename, that is the file containing the Forth codes.<br /> <br /> ===Deferred Expressions===<br /> A deferred expression is sort of like having function calls for calling another expression. The operator &lt;tt&gt;,&lt;/tt&gt; sets the current parameter value to the left side and then evaluates the right side, the operator &lt;tt&gt;p&lt;/tt&gt; gets the current parameter, and the operator &lt;tt&gt;`&lt;/tt&gt; allows you to use a deferred expression.<br /> <br /> Because parentheses are used to evaluate expression, it uses square brackets to mean a deferred expression. It will convert &lt;tt&gt;[]&lt;/tt&gt; to &lt;tt&gt;()&lt;/tt&gt; when accessing a deferred expression.<br /> <br /> The &lt;tt&gt;`&lt;/tt&gt; operator is two of &lt;tt&gt;`&lt;/tt&gt; with the name of string in between (including the dollar sign), and it call the deferred expression. You can also use &lt;tt&gt;`&lt;/tt&gt; operator with &lt;tt&gt;*&lt;/tt&gt; followed by a Forth word instead of a string, in which case it will instead call that Forth word to determine the value of the expression.<br /> <br /> ===Extended Kinds===<br /> You can create extended kinds 0x80 to 0xFE (128 to 254) using Forth codes.<br /> <br /> In order to create a extended kind you must indicate:<br /> * The number assigned to it<br /> * The character used to represent it (255 means use the parameter, like a CustomBlock does, and negative number mean various other things)<br /> * The A_ flags associated with it<br /> * How the parameter is decided (the parameter type can come from any built-in)<br /> * The name<br /> And then you can optionally define events for it, such as what happens when it is shot, updated, touched by the player, underneath the player, and so on. Which events are used depends on the A_ flags, although it is possible to have A_ flags without the corresponding events (for example, the simplest way to prevent the player from pushing something that is normally pushable is to give the object the A_ITEM flag without a corresponding event).<br /> <br /> Some new A_ flags have been implemented:<br /> * A_BREAKABLE<br /> * A_USERFLAG<br /> * A_CRUSH<br /> * A_INVISIBLE<br /> * A_ELEMENT (3 bits, and in Forth codes you use AE_WATER and so on instead of typing A_ELEMENT)<br /> <br /> ===Overlay Modes===<br /> Mode 4 makes it draw the overlay outside of the viewport instead of on the inside of the viewport.<br /> <br /> Mode 65 and 66 makes it to not draw the board, and only draw the overlay. (This feature actually already existed in MegaZeux, but there was previously no access to it during the game.)<br /> <br /> Mode 0x7? prevents it from drawing anything at all, allowing Forth codes direct access to the text_video.<br /> <br /> There are also displacement overlay modes 0xA?, 0xB?, 0xE?, which allows pixel-accuracy for drawing characters, and also can make individual pixels transparent (so you can see the character drawn underneath).<br /> <br /> ===Graphics Modes===<br /> Modes 0 to 3 are same as normal MegaZeux. Mode 64 to 67 are the mode for 16 colors per character. Mode 141 makes blinking text.<br /> <br /> ==Use of Attribute Flags==<br /> The flags are as follows (any combination can be used, except for a few exceptions):<br /> * A_PUSHNS: Allows object to be pushed north/south<br /> * A_PUSHEW: Allows object ot be push east/west<br /> * A_PUSHABLE: Object can be pushed in any direction (Do not combine with A_PUSHNS or A_PUSHEW)<br /> * A_ITEM: Calls EV.ITEM event when player touches it. Player will not automatically push or stand on this object<br /> * A_UPDATE: EV.UPDATE event will be called every step unless freeze time is active<br /> * A_HURTS: Causes damage when player hits it<br /> * A_UNDER: Things can stand on this<br /> * A_ENTRANCE: Parameter is a board number, if the player steps here it will teleport the player to that board<br /> * A_EXPLODE: Object is explosive<br /> * A_BLOW_UP: Object can blow up<br /> * A_SHOOTABLE: Player bullets and neutral bullets can destroy this<br /> * A_BREAKABLE: Any bullets can destroy this (Do not combine with A_SHOOTABLE or A_SPEC_SHOT)<br /> * A_ENEMY: Used in various purposes by MegaZeux<br /> * A_AFFECTSTOOD: Calls EV.AFFECTSTOOD event every step if the player is standing here<br /> * A_SPEC_SHOT: Calls EV.SHOT event if hit by a bullet<br /> * A_SPEC_PUSH: Object can be pushed in any direction<br /> * A_SPEC_BOMB: Calls EV.BOMB event when explosion hits it<br /> * A_SPEC_STOOD: Player can stand here, even if other things can't<br /> * A_USERFLAG: Does nothing<br /> * A_CRUSH: Object can be crushed like in ZZT<br /> * A_INVISIBLE: Draws using under color, or draws black if this is the under object<br /> * A_SEEBLIND: Object is visible even if the player is blind<br /> <br /> There are also element flags (up to one of these flags can be used):<br /> * AE_WATER: Things that are not allowed to move onto water won't move onto here<br /> * AE_FIRE: Things that are not allowed to move onto fire won't move onto here<br /> * AE_LAVA: Things that are not allowed to move onto lava won't move onto here, also cannot be pushed or pushed onto<br /> * AE_GOOP: Things that are not allowed to move onto goop won't move onto here, also cannot be pushed or pushed onto<br /> * AE_THINWEB: Spiders that can move on thin webs are allowed to step here<br /> * AE_THICKWEB: Spiders that can move on thick webs are allowed to step here<br /> * AE_PLAYER: Cannot be pushed by things that react with the player<br /> <br /> ==Use of Events==<br /> The following events exist in game and are not corresponding to any particular object:<br /> * EV.PLAYERMOVING ( dir edge offset -- cancel ) Called to determine whether or not the player is allowed to move<br /> * EV.KEYBOARD ( key -- canceldefault ) Called when a key is pushed, can tell it to cancel the default function of that key<br /> * EV.LOADED ( category -- ) When game is started or restored<br /> * EV.ENTERED ( category -- ) When the board is switched<br /> * EV.BULLETHIT ( offset bulletoffset parameter -- category ) Indicates that a bullet is about to hit something solid<br /> <br /> These events are corresponding to specific objects (add the extended kind number to the event code):<br /> * EV.PUSH ( offset dir category distance -- ) Called when an object is being pushed<br /> * EV.ITEM ( offset dir -- remove ) Called when the player touches an object with A_ITEM flag<br /> * EV.AFFECTSTOOD ( offset -- ) The player is stand on object with A_AFFECTSTOOD<br /> * EV.UPDATE ( offset -- ) Something with A_UPDATE is being updated<br /> * EV.SHOT ( offset bulletoffset dir bullettype -- ) Something with A_SPEC_SHOT is being hit by a bullet<br /> * EV.BOMB ( offset -- ) Something with A_SPEC_BOMB is hit by an explosion<br /> * EV.LAZER ( lazeroffset offset dir -- blocking ) Object hit by lazer beam, can block lazer or allow beam to be transmitted through<br /> * EV.ARRIVE ( offset -- ) Another object has arrived on top of this object<br /> * EV.TESTPUSH ( offset dir category distance -- cancel ) Testing whether or not an object is allowed to be pushed<br /> <br /> The following events are used in the editor:<br /> * EV.EDITORKEY ( color thing param offset key keymod -- color thing param offset canceldefault ) A key is pushed during editing<br /> * EV.BEFOREADDBOARD ( -- ? ) Before a new board is being added, the current board will be the old current board<br /> * 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<br /> <br /> ==Examples of Forth Codes==<br /> Please note that all examples are case-insensitive, just like anything else in MegaZeux.<br /> <br /> ==ZZT Keys==<br /> Here is a code to implement a ZZT key:<br /> INCLUDE megazeux.4th<br /> <br /> $80 12 A_ITEM A_PUSHABLE + 0 EXTKIND ZztKey<br /> ZztKey EV.ITEM + :EVENT<br /> DROP BOARD_COLOR + @ DUP TAKEKEY SWAP GIVEKEY DROP<br /> IF<br /> &quot;You already have the key!&quot; SETMESG 9 BISFX 0<br /> ELSE<br /> &quot;You now have the key.&quot; SETMESG 8 BISFX 1<br /> THEN<br /> ;<br /> I will explain each line and part of line one by one so that you can follow:<br /> INCLUDE megazeux.4th<br /> This loads the standard libraries of Forth codes.<br /> $80<br /> 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)<br /> 12<br /> This means it will display as character 12.<br /> A_ITEM A_PUSHABLE +<br /> 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).<br /> 0<br /> It will not ask for a parameter when placed in the editor.<br /> EXTKIND ZztKey<br /> 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.<br /> ZztKey EV.ITEM + :EVENT<br /> Adding ZztKey to EV.ITEM gets the number of the item event for the ZztKey. :EVENT tells it to start compiling an event code.<br /> DROP<br /> The top parameter passed to the EV.ITEM event is dir, which we aren't using, so we DROP it.<br /> BOARD_COLOR + @<br /> 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.<br /> DUP<br /> We are using the color twice, so we duplicate it.<br /> TAKEKEY<br /> Attempt to take away that color of key from the player, and gets a success code.<br /> SWAP<br /> We want to pass the color, not the success code to GIVEKEY, so we SWAP it.<br /> GIVEKEY DROP<br /> 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.<br /> IF<br /> 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)<br /> &quot;You already have the key!&quot; SETMESG 9 BISFX<br /> Gives the player a message and plays a sound effect.<br /> 0<br /> Zero is the value returned from the event (the &quot;remove&quot; parameter), meaning the object shouldn't be removed from the screen.<br /> ELSE &quot;You now have the key.&quot; SETMESG 8 BISFX<br /> Another message and sound effect.<br /> 1<br /> Any non-zero value means the object will be removed from the screen (because the player has just picked up the key).<br /> THEN<br /> 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 &quot;do this, and then do this...&quot; rather than &quot;if this then this...&quot;<br /> ;<br /> And this signals the end of the event code, and exits compile mode.</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=PZX&diff=6862 2009-06-20T05:24:46Z

<p>Zzo38: </p> <hr /> <div>'''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.<br /> <br /> ==Features==<br /> The biggest contribution of this particular fork is FORTH support. Other changes include the ability to use the old ALT+D function in the editor (only zzo38 seems to remember what this is or use the function to begin with), deferred expressions, extended kinds, new overlay modes and SMZX modes of dubious utility (including the one that draws overlay on the outside of the viewport instead of inside, one that draws only the overlay and not the board, an SMZX mode that uses 16 colors per character (reducing the resolution per character to 4x7), and a blinking text mode), meanings for the other bits in lava_walk, and displacement overlay modes which allow adjustment of the overlay by individual pixels.<br /> <br /> zzo38 also corrected a long standing, esoteric bug in the handling of built-in spider webs, which has been merged (with changes) into the existing codebase.<br /> <br /> To make backward compatibility, the way it works, is if the first line of the global robot is a comment with a greater than sign at beginning (optionally followed by a filename), it will activate PZX mode. If there is a filename, that is the file containing the Forth codes.<br /> <br /> ===Deferred Expressions===<br /> A deferred expression is sort of like having function calls for calling another expression. The operator &lt;tt&gt;,&lt;/tt&gt; sets the current parameter value to the left side and then evaluates the right side, the operator &lt;tt&gt;p&lt;/tt&gt; gets the current parameter, and the operator &lt;tt&gt;`&lt;/tt&gt; allows you to use a deferred expression.<br /> <br /> Because parentheses are used to evaluate expression, it uses square brackets to mean a deferred expression. It will convert &lt;tt&gt;[]&lt;/tt&gt; to &lt;tt&gt;()&lt;/tt&gt; when accessing a deferred expression.<br /> <br /> The &lt;tt&gt;`&lt;/tt&gt; operator is two of &lt;tt&gt;`&lt;/tt&gt; with the name of string in between (including the dollar sign), and it call the deferred expression. You can also use &lt;tt&gt;`&lt;/tt&gt; operator with &lt;tt&gt;*&lt;/tt&gt; followed by a Forth word instead of a string, in which case it will instead call that Forth word to determine the value of the expression.<br /> <br /> ===Extended Kinds===<br /> You can create extended kinds 0x80 to 0xFE (128 to 254) using Forth codes.<br /> <br /> In order to create a extended kind you must indicate:<br /> * The number assigned to it<br /> * The character used to represent it (255 means use the parameter, like a CustomBlock does, and negative number mean various other things)<br /> * The A_ flags associated with it<br /> * How the parameter is decided (the parameter type can come from any built-in)<br /> * The name<br /> And then you can optionally define events for it, such as what happens when it is shot, updated, touched by the player, underneath the player, and so on. Which events are used depends on the A_ flags, although it is possible to have A_ flags without the corresponding events (for example, the simplest way to prevent the player from pushing something that is normally pushable is to give the object the A_ITEM flag without a corresponding event).<br /> <br /> Some new A_ flags have been implemented:<br /> * A_BREAKABLE<br /> * A_USERFLAG<br /> * A_CRUSH<br /> * A_INVISIBLE<br /> * A_ELEMENT (3 bits, and in Forth codes you use AE_WATER and so on instead of typing A_ELEMENT)<br /> <br /> ===Overlay Modes===<br /> Mode 4 makes it draw the overlay outside of the viewport instead of on the inside of the viewport.<br /> <br /> Mode 65 and 66 makes it to not draw the board, and only draw the overlay. (This feature actually already existed in MegaZeux, but there was previously no access to it during the game.)<br /> <br /> Mode 0x7? prevents it from drawing anything at all, allowing Forth codes direct access to the text_video.<br /> <br /> There are also displacement overlay modes 0xA?, 0xB?, 0xE?, which allows pixel-accuracy for drawing characters, and also can make individual pixels transparent (so you can see the character drawn underneath).<br /> <br /> ===Graphics Modes===<br /> Modes 0 to 3 are same as normal MegaZeux. Mode 64 to 67 are the mode for 16 colors per character. Mode 141 makes blinking text.<br /> <br /> ==Use of Attribute Flags==<br /> The flags are as follows (any combination can be used, except for a few exceptions):<br /> * A_PUSHNS: Allows object to be pushed north/south<br /> * A_PUSHEW: Allows object ot be push east/west<br /> * A_PUSHABLE: Object can be pushed in any direction (Do not combine with A_PUSHNS or A_PUSHEW)<br /> * A_ITEM: Calls EV.ITEM event when player touches it. Player will not automatically push or stand on this object<br /> * A_UPDATE: EV.UPDATE event will be called every step unless freeze time is active<br /> * A_HURTS: Causes damage when player hits it<br /> * A_UNDER: Things can stand on this<br /> * A_ENTRANCE: Parameter is a board number, if the player steps here it will teleport the player to that board<br /> * A_EXPLODE: Object is explosive<br /> * A_BLOW_UP: Object can blow up<br /> * A_SHOOTABLE: Player bullets and neutral bullets can destroy this<br /> * A_BREAKABLE: Any bullets can destroy this (Do not combine with A_SHOOTABLE or A_SPEC_SHOT)<br /> * A_ENEMY: Used in various purposes by MegaZeux<br /> * A_AFFECTSTOOD: Calls EV.AFFECTSTOOD event every step if the player is standing here<br /> * A_SPEC_SHOT: Calls EV.SHOT event if hit by a bullet<br /> * A_SPEC_PUSH: Object can be pushed in any direction<br /> * A_SPEC_BOMB: Calls EV.BOMB event when explosion hits it<br /> * A_SPEC_STOOD: Player can stand here, even if other things can't<br /> * A_USERFLAG: Does nothing<br /> * A_CRUSH: Object can be crushed like in ZZT<br /> * A_INVISIBLE: Draws using under color, or draws black if this is the under object<br /> * A_SEEBLIND: Object is visible even if the player is blind<br /> <br /> There are also element flags (up to one of these flags can be used):<br /> * AE_WATER: Things that are not allowed to move onto water won't move onto here<br /> * AE_FIRE: Things that are not allowed to move onto fire won't move onto here<br /> * AE_LAVA: Things that are not allowed to move onto lava won't move onto here, also cannot be pushed or pushed onto<br /> * AE_GOOP: Things that are not allowed to move onto goop won't move onto here, also cannot be pushed or pushed onto<br /> * AE_THINWEB: Spiders that can move on thin webs are allowed to step here<br /> * AE_THICKWEB: Spiders that can move on thick webs are allowed to step here<br /> * AE_PLAYER: Cannot be pushed by things that react with the player<br /> <br /> ==Use of Events==<br /> The following events exist in game and are not corresponding to any particular object:<br /> * EV.PLAYERMOVING ( dir edge offset -- cancel ) Called to determine whether or not the player is allowed to move<br /> * EV.KEYBOARD ( key -- canceldefault ) Called when a key is pushed, can tell it to cancel the default function of that key<br /> * EV.LOADED ( category -- ) When game is started or restored<br /> * EV.ENTERED ( category -- ) When the board is switched<br /> * EV.BULLETHIT ( offset bulletoffset parameter -- category ) Indicates that a bullet is about to hit something solid<br /> <br /> These events are corresponding to specific objects (add the extended kind number to the event code):<br /> * EV.PUSH ( offset dir category distance -- ) Called when an object is being pushed<br /> * EV.ITEM ( offset dir -- remove ) Called when the player touches an object with A_ITEM flag<br /> * EV.AFFECTSTOOD ( offset -- ) The player is stand on object with A_AFFECTSTOOD<br /> * EV.UPDATE ( offset -- ) Something with A_UPDATE is being updated<br /> * EV.SHOT ( offset bulletoffset dir bullettype -- ) Something with A_SPEC_SHOT is being hit by a bullet<br /> * EV.BOMB ( offset -- ) Something with A_SPEC_BOMB is hit by an explosion<br /> * EV.LAZER ( lazeroffset offset dir -- blocking ) Object hit by lazer beam, can block lazer or allow beam to be transmitted through<br /> * EV.ARRIVE ( offset -- ) Another object has arrived on top of this object<br /> * EV.TESTPUSH ( offset dir category distance -- cancel ) Testing whether or not an object is allowed to be pushed<br /> <br /> The following events are used in the editor:<br /> * EV.EDITORKEY ( color thing param offset key keymod -- color thing param offset canceldefault ) A key is pushed during editing<br /> * EV.BEFOREADDBOARD ( -- ? ) Before a new board is being added, the current board will be the old current board<br /> * 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<br /> <br /> ==Examples of Forth Codes==<br /> Please note that all examples are case-insensitive, just like anything else in MegaZeux.<br /> <br /> ==ZZT Keys==<br /> Here is a code to implement a ZZT key:<br /> INCLUDE megazeux.4th<br /> <br /> $80 12 A_ITEM A_PUSHABLE + 0 EXTKIND ZztKey<br /> ZztKey EV.ITEM + :EVENT<br /> DROP BOARD_COLOR + @ DUP TAKEKEY SWAP GIVEKEY DROP<br /> IF<br /> &quot;You already have the key!&quot; SETMESG 9 BISFX 0<br /> ELSE<br /> &quot;You now have the key.&quot; SETMESG 8 BISFX 1<br /> THEN<br /> ;<br /> I will explain each line and part of line one by one so that you can follow:<br /> INCLUDE megazeux.4th<br /> This loads the standard libraries of Forth codes.<br /> $80<br /> 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)<br /> 12<br /> This means it will display as character 12.<br /> A_ITEM A_PUSHABLE +<br /> 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).<br /> 0<br /> It will not ask for a parameter when placed in the editor.<br /> EXTKIND ZztKey<br /> 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.<br /> ZztKey EV.ITEM + :EVENT<br /> Adding ZztKey to EV.ITEM gets the number of the item event for the ZztKey. :EVENT tells it to start compiling an event code.<br /> DROP<br /> The top parameter passed to the EV.ITEM event is dir, which we aren't using, so we DROP it.<br /> BOARD_COLOR + @<br /> 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.<br /> DUP<br /> We are using the color twice, so we duplicate it.<br /> TAKEKEY<br /> Attempt to take away that color of key from the player, and gets a success code.<br /> SWAP<br /> We want to pass the color, not the success code to GIVEKEY, so we SWAP it.<br /> GIVEKEY DROP<br /> 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.<br /> IF<br /> 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)</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=PZX&diff=6861 2009-06-20T05:07:43Z

<p>Zzo38: </p> <hr /> <div>'''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.<br /> <br /> ==Features==<br /> The biggest contribution of this particular fork is FORTH support. Other changes include the ability to use the old ALT+D function in the editor (only zzo38 seems to remember what this is or use the function to begin with), deferred expressions, extended kinds, new overlay modes and SMZX modes of dubious utility (including the one that draws overlay on the outside of the viewport instead of inside, one that draws only the overlay and not the board, an SMZX mode that uses 16 colors per character (reducing the resolution per character to 4x7), and a blinking text mode), meanings for the other bits in lava_walk, and displacement overlay modes which allow adjustment of the overlay by individual pixels.<br /> <br /> zzo38 also corrected a long standing, esoteric bug in the handling of built-in spider webs, which has been merged (with changes) into the existing codebase.<br /> <br /> To make backward compatibility, the way it works, is if the first line of the global robot is a comment with a greater than sign at beginning (optionally followed by a filename), it will activate PZX mode. If there is a filename, that is the file containing the Forth codes.<br /> <br /> ===Deferred Expressions===<br /> A deferred expression is sort of like having function calls for calling another expression. The operator &lt;tt&gt;,&lt;/tt&gt; sets the current parameter value to the left side and then evaluates the right side, the operator &lt;tt&gt;p&lt;/tt&gt; gets the current parameter, and the operator &lt;tt&gt;`&lt;/tt&gt; allows you to use a deferred expression.<br /> <br /> Because parentheses are used to evaluate expression, it uses square brackets to mean a deferred expression. It will convert &lt;tt&gt;[]&lt;/tt&gt; to &lt;tt&gt;()&lt;/tt&gt; when accessing a deferred expression.<br /> <br /> The &lt;tt&gt;`&lt;/tt&gt; operator is two of &lt;tt&gt;`&lt;/tt&gt; with the name of string in between (including the dollar sign), and it call the deferred expression. You can also use &lt;tt&gt;`&lt;/tt&gt; operator with &lt;tt&gt;*&lt;/tt&gt; followed by a Forth word instead of a string, in which case it will instead call that Forth word to determine the value of the expression.<br /> <br /> ===Extended Kinds===<br /> You can create extended kinds 0x80 to 0xFE (128 to 254) using Forth codes.<br /> <br /> In order to create a extended kind you must indicate:<br /> * The number assigned to it<br /> * The character used to represent it (255 means use the parameter, like a CustomBlock does, and negative number mean various other things)<br /> * The A_ flags associated with it<br /> * How the parameter is decided (the parameter type can come from any built-in)<br /> * The name<br /> And then you can optionally define events for it, such as what happens when it is shot, updated, touched by the player, underneath the player, and so on. Which events are used depends on the A_ flags, although it is possible to have A_ flags without the corresponding events (for example, the simplest way to prevent the player from pushing something that is normally pushable is to give the object the A_ITEM flag without a corresponding event).<br /> <br /> Some new A_ flags have been implemented:<br /> * A_BREAKABLE<br /> * A_USERFLAG<br /> * A_CRUSH<br /> * A_INVISIBLE<br /> * A_ELEMENT (3 bits, and in Forth codes you use AE_WATER and so on instead of typing A_ELEMENT)<br /> <br /> ===Overlay Modes===<br /> Mode 4 makes it draw the overlay outside of the viewport instead of on the inside of the viewport.<br /> <br /> Mode 65 and 66 makes it to not draw the board, and only draw the overlay. (This feature actually already existed in MegaZeux, but there was previously no access to it during the game.)<br /> <br /> Mode 0x7? prevents it from drawing anything at all, allowing Forth codes direct access to the text_video.<br /> <br /> There are also displacement overlay modes 0xA?, 0xB?, 0xE?, which allows pixel-accuracy for drawing characters, and also can make individual pixels transparent (so you can see the character drawn underneath).<br /> <br /> ===Graphics Modes===<br /> Modes 0 to 3 are same as normal MegaZeux. Mode 64 to 67 are the mode for 16 colors per character. Mode 141 makes blinking text.<br /> <br /> ==Use of Attribute Flags==<br /> The flags are as follows (any combination can be used, except for a few exceptions):<br /> * A_PUSHNS: Allows object to be pushed north/south<br /> * A_PUSHEW: Allows object ot be push east/west<br /> * A_PUSHABLE: Object can be pushed in any direction (Do not combine with A_PUSHNS or A_PUSHEW)<br /> * A_ITEM: Calls EV.ITEM event when player touches it. Player will not automatically push or stand on this object<br /> * A_UPDATE: EV.UPDATE event will be called every step unless freeze time is active<br /> * A_HURTS: Causes damage when player hits it<br /> * A_UNDER: Things can stand on this<br /> * A_ENTRANCE: Parameter is a board number, if the player steps here it will teleport the player to that board<br /> * A_EXPLODE: Object is explosive<br /> * A_BLOW_UP: Object can blow up<br /> * A_SHOOTABLE: Player bullets and neutral bullets can destroy this<br /> * A_BREAKABLE: Any bullets can destroy this (Do not combine with A_SHOOTABLE or A_SPEC_SHOT)<br /> * A_ENEMY: Used in various purposes by MegaZeux<br /> * A_AFFECTSTOOD: Calls EV.AFFECTSTOOD event every step if the player is standing here<br /> * A_SPEC_SHOT: Calls EV.SHOT event if hit by a bullet<br /> * A_SPEC_PUSH: Object can be pushed in any direction<br /> * A_SPEC_BOMB: Calls EV.BOMB event when explosion hits it<br /> * A_SPEC_STOOD: Player can stand here, even if other things can't<br /> * A_USERFLAG: Does nothing<br /> * A_CRUSH: Object can be crushed like in ZZT<br /> * A_INVISIBLE: Draws using under color, or draws black if this is the under object<br /> * A_SEEBLIND: Object is visible even if the player is blind<br /> <br /> There are also element flags (up to one of these flags can be used):<br /> * AE_WATER: Things that are not allowed to move onto water won't move onto here<br /> * AE_FIRE: Things that are not allowed to move onto fire won't move onto here<br /> * AE_LAVA: Things that are not allowed to move onto lava won't move onto here, also cannot be pushed or pushed onto<br /> * AE_GOOP: Things that are not allowed to move onto goop won't move onto here, also cannot be pushed or pushed onto<br /> * AE_THINWEB: Spiders that can move on thin webs are allowed to step here<br /> * AE_THICKWEB: Spiders that can move on thick webs are allowed to step here<br /> * AE_PLAYER: Cannot be pushed by things that react with the player<br /> <br /> ==Use of Events==<br /> The following events exist in game and are not corresponding to any particular object:<br /> * EV.PLAYERMOVING ( dir edge offset -- cancel ) Called to determine whether or not the player is allowed to move<br /> * EV.KEYBOARD ( key -- canceldefault ) Called when a key is pushed, can tell it to cancel the default function of that key<br /> * EV.LOADED ( category -- ) When game is started or restored<br /> * EV.ENTERED ( category -- ) When the board is switched<br /> * EV.BULLETHIT ( offset bulletoffset parameter -- category ) Indicates that a bullet is about to hit something solid<br /> <br /> These events are corresponding to specific objects (add the extended kind number to the event code):<br /> * EV.PUSH ( offset dir category distance -- ) Called when an object is being pushed<br /> * EV.ITEM ( offset dir -- remove ) Called when the player touches an object with A_ITEM flag<br /> * EV.AFFECTSTOOD ( offset -- ) The player is stand on object with A_AFFECTSTOOD<br /> * EV.UPDATE ( offset -- ) Something with A_UPDATE is being updated<br /> * EV.SHOT ( offset bulletoffset dir bullettype -- ) Something with A_SPEC_SHOT is being hit by a bullet<br /> * EV.BOMB ( offset -- ) Something with A_SPEC_BOMB is hit by an explosion<br /> * EV.LAZER ( lazeroffset offset dir -- blocking ) Object hit by lazer beam, can block lazer or allow beam to be transmitted through<br /> * EV.ARRIVE ( offset -- ) Another object has arrived on top of this object<br /> * EV.TESTPUSH ( offset dir category distance -- cancel ) Testing whether or not an object is allowed to be pushed<br /> <br /> The following events are used in the editor:<br /> * EV.EDITORKEY ( color thing param offset key keymod -- color thing param offset canceldefault ) A key is pushed during editing<br /> * EV.BEFOREADDBOARD ( -- ? ) Before a new board is being added, the current board will be the old current board<br /> * 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</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=PZX_features&diff=6841 2009-06-14T23:58:44Z

<p>Zzo38: New page: PZX features means the zzo38 fork of MegaZeux, also known as PZX or ProngZeux. It includes support for [http://en.wikipedia.org/wiki/Forth_(programming_language) Forth], the abilit...</p> <hr /> <div>PZX features means the [[zzo38]] fork of [[MegaZeux]], also known as PZX or ProngZeux. It includes support for [http://en.wikipedia.org/wiki/Forth_(programming_language) Forth], the ability to use the old ALT+D function in the editor (only zzo38 seems to remember what this is or use the function to begin with), deferred expressions, extended kinds, new overlay modes and SMZX modes of dubious utility (including the one that draws overlay on the outside of the viewport instead of inside, one that draws only the overlay and not the board, an SMZX mode that uses 16 colors per character (reducing the resolution per character to 4x7), and a blinking text mode), meanings for the other bits in lava_walk, and displacement overlay modes which allow adjustment of the overlay by individual pixels.<br /> <br /> He also corrected a long standing, esoteric bug in the handling of built-in spider webs, which has been merged (with changes) into the existing codebase.<br /> <br /> To make backward compatibility, the way it works, is if the first line of the global robot is a comment with a greater than sign at beginning (optionally followed by a filename), it will activate PZX mode. If there is a filename, that is the file containing the Forth codes.<br /> <br /> ==Deferred Expressions==<br /> A deferred expression is sort of like having function calls for calling another expression. The operator &lt;tt&gt;,&lt;/tt&gt; sets the current parameter value to the left side and then evaluates the right side, the operator &lt;tt&gt;p&lt;/tt&gt; gets the current parameter, and the operator &lt;tt&gt;`&lt;/tt&gt; allows you to use a deferred expression.<br /> <br /> Because parentheses are used to evaluate expression, it uses square brackets to mean a deferred expression. It will convert &lt;tt&gt;[]&lt;/tt&gt; to &lt;tt&gt;()&lt;/tt&gt; when accessing a deferred expression.<br /> <br /> The &lt;tt&gt;`&lt;/tt&gt; operator is two of &lt;tt&gt;`&lt;/tt&gt; with the name of string in between (including the dollar sign), and it call the deferred expression. You can also use &lt;tt&gt;`&lt;/tt&gt; operator with &lt;tt&gt;*&lt;/tt&gt; followed by a Forth word instead of a string, in which case it will instead call that Forth word to determine the value of the expression.<br /> <br /> ==Extended Kinds==<br /> You can create extended kinds 0x80 to 0xFE (128 to 254) using Forth codes.<br /> <br /> In order to create a extended kind you must indicate:<br /> * The number assigned to it<br /> * The character used to represent it (255 means use the parameter, like a CustomBlock does, and negative number mean various other things)<br /> * The A_ flags associated with it<br /> * How the parameter is decided (the parameter type can come from any built-in)<br /> * The name<br /> And then you can optionally define events for it, such as what happens when it is shot, updated, touched by the player, underneath the player, and so on. Which events are used depends on the A_ flags, although it is possible to have A_ flags without the corresponding events (for example, the simplest way to prevent the player from pushing something that is normally pushable is to give the object the A_ITEM flag without a corresponding event).<br /> <br /> Some new A_ flags have been implemented:<br /> * A_BREAKABLE<br /> * A_USERFLAG<br /> * A_CRUSH<br /> * A_INVISIBLE<br /> * A_ELEMENT (3 bits, and in Forth codes you use AE_WATER and so on instead of typing A_ELEMENT)<br /> <br /> ==Overlay Modes==<br /> Mode 4 makes it draw the overlay outside of the viewport instead of on the inside of the viewport.<br /> <br /> Mode 65 and 66 makes it to not draw the board, and only draw the overlay. (This feature actually already existed in MegaZeux, but there was previously no access to it during the game.)<br /> <br /> Mode 0x7? prevents it from drawing anything at all, allowing Forth codes direct access to the text_video.<br /> <br /> There are also displacement overlay modes 0xA?, 0xB?, 0xE?, which allows pixel-accuracy for drawing characters, and also can make individual pixels transparent (so you can see the character drawn underneath).<br /> <br /> ==Graphics Modes==<br /> Modes 0 to 3 are same as normal MegaZeux. Mode 64 to 67 are the mode for 16 colors per character. Mode 141 makes blinking text.</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=MegaZeux&diff=6840 2009-06-14T23:33:57Z

<p>Zzo38: Is it short enough now? I agree it was getting too long, so I split it into a separate page.</p> <hr /> <div>'''MegaZeux''' is a game creation system created by [[Gregory Janson]]. It was inspired by [[ZZT]], for which Greg and other members of [[Software Visions]] had created several games beforehand. The first version, [[Changelog for 1.00g|1.00g]], was uploaded to AOL on December 4, 1994.<br /> <br /> ==Features==<br /> ===Robotic===<br /> ''See also: [[Robotic]]''<br /> <br /> Robotic is MegaZeux's object-oriented programming language. Some parts of the language, as well as the concept itself, are based on [[ZZT|ZZT's]] ZZT-OOP, though Robotic is much more advanced than ZZT-OOP.<br /> <br /> ==History==<br /> History of MZX's development.<br /> ===Shareware Versions===<br /> <br /> In 1994, MegaZeux 1.00g was released on AOL. It was designed to be an improvement over [[ZZT]], and at that point featured digital sound and music that could be played over Sound Blaster-compatible cards. It featured editable [[character set|character sets]] and larger board sizes than ZZT.<br /> <br /> Some time later, MegaZeux 2.00 was released, featuring a vast interface overhaul, the ability to edit the in-game palette, and other new features.<br /> <br /> Finally, MegaZeux 2.50 was uploaded, and among other changes, included the brand new [[BWSB]] sound engine that was more compatible and more tolerant of Windows. Shortly thereafter, version 2.51 was released, with minor bug fixes and additions. This would be the last version Gregory Janson would release.<br /> <br /> ===Spider Versions===<br /> After MegaZeux was released under the terms of the GNU GPL, [[Spider124]] updated the source code with several useful new features and released his own version of MegaZeux, 2.51s1. Among the new features were a vastly expanded counters limit (1000, compared to 2.51's 50 counters), true mouse support, [[playerx and playery|playerx/playery]] counters, and many bug fixes. Three more versions were released (s2, s3, and s3.1; of which 3.1 was a bug fix release) before development of MZX grew stagnant.<br /> <br /> [[MadBrain]] took the s3.1 source, added one new feature (the [[bi_mesg]] built-in counter) and removed password protection, releasing his modifications as MZX 2.51s3.2. s3.2 was further modified with the introduction of the [[Super MZX|SMZX]] graphics mode (this version was released as SMZX 100 Alpha).<br /> <br /> ===MegaZeux 2.7 and mzxlib===<br /> MZX 2.7 was an effort spearheaded by [[JZig]] to completely rewrite MegaZeux in C++, with a new graphics engine, audio code, and support for other operating systems such as Linux. Most of the initial coding was done by [[MenTaLguY]], until JZig took over in 1999. [[piman]], while not doing much coding himself, performed most of the non-code tasks such as updating the project's SourceForge page. JZig's development on MZX 2.7 stopped around 2001, and it was not picked up afterwards.<br /> <br /> ===MZXak===<br /> [[Akwende]] released the first MZXak version, MZXak 1.0, shortly after MadBrain's SMZX alpha version. MZXak featured several additional features (some of which, like the multi-colored configuration dialogs, were determined by the community to be too useless to warrant the memory usage) including file access, robot targeting, and built-in SMZX mode. All MZXak versions included Akwende's MZX version of Tetris, which demonstrated the use of SMZX graphics.<br /> <br /> MZXak 1.0 was pulled a few months after release from [[DigitalMZX]] due to Akwende's failure to release his source code under the terms of the GNU GPL. He eventually released the source, but not until a lot of public debate and heel-dragging. Other MZXak 1.0 controversy included forward compatibility, which led to MZXak games being playable but not necessarily functioning in MZX2.51s3.1. This broke [[ajs|wizdom's]] judging results in the [[Summer Dualstream Day of Zeux 2001|2001 DsDoZ]].<br /> <br /> MZXak 2.0 was released after much waiting, though the release sparked a fair bit of dispute due to the sudden timing with [[Koji|Koji's]] 2.60 release. MZXak 2.0 is notable for being the only code fork to completely die out.<br /> <br /> ===Exophase Versions===<br /> Following the discussions about MZXak, Koji released MZX 2.60, featuring some of the same additions as MZXak. 2.61 was released shortly after, and around 2.62's release, [[Exophase]] took over development of MegaZeux. Tons of features were added in between 2.62 and 2.70 (the last version of MegaZeux in [[DOS]]) such as [[Expression|expressions]], [[Sprite|sprites]], [[String|strings]], [[Vlayer|the vlayer]], [[MZM|MZMs]], [[Super MZX|SMZX Mode 2]], and many others.<br /> <br /> ===MZX32===<br /> During Exophase's development of MZX for DOS, [[BFeely]] began development on MZX32, which was to be a full-featured port of MegaZeux for the Windows platform. Several alpha versions were released, most of which lacked the world editor (and all of which lacked the robotic code editor). MZX32 was generally regarded as unstable and buggy, and was deemed obsolete once Exophase began work on his SDL port. The last version of MZX32 released featured support for games created using MZX 2.69c.<br /> <br /> ===SDL Port===<br /> <br /> [[Exophase]] took most of the summer of 2004 to do a update/rewrite of MegaZeux into SDL, to break some DOS limitations and to solve MegaZeux's ever-increasing compatibility issues (and to eventually expand MegaZeux onto new platforms such as Linux and the Macintosh). This included re-writing the entire Robotic editor from scratch as source was no longer available for it. Many other source modules were either completely rewritten or heavily revised. After intense pre-testing, MZX 2.80 was released on Aug 9 2004, with workability only intended for Windows 32 platforms. A slew of bug reports that only arises from public testing shortly followed, and Exophase quickly updated with three incremental versions in one month which also officially added support for Linux and MacOS X. Other MegaZeuxers helped in various aspects; for example, [[ajs|ajs's]] and [[MadBrain|mad's]] GDM conversion code was a basis for SAM conversion code. Later on, ajs would write support to abstract file operations for case sensitive file systems, and additional graphical renderers were designed by [[LogiCow]] and [[Mr_Alert]].<br /> <br /> Most version upticks added some functionality (e.g. multi-char editor, code search, ogg support), and all significantly increased stability. MegaZeux is currently extending to handhelds and consoles: [[Oncer]] released a GP2X port, [[kvance]] a Nintendo DS port, Mr_Alert a Wii port, and Exophase has done preliminary PSP support.<br /> <br /> The current version is 2.82b.<br /> <br /> ===MegaZeux Forks===<br /> In early 2007, LogiCow created his own fork of the MZX source. The first version added the Draw command, allowing users to scale characters from the [[vlayer]]. It also served as an underlay (as opposed to an overlay). In more recent versions, the draw command was deleted. A select persisted in using the older versions for the draw command, much to the annoyance of those wishing to stay with Exophase's versions.<br /> <br /> A short time after the previous fork, LogiCow created another fork with an alternate renderer that scaled the graphics up to fit the screen, regardless of aspect ratio. This also allowed for seamless resizing of the MZX window when not running in full screen mode. logicow worked with ajs to merge these renderers into the mainline MZX versions, starting with 2.81e.<br /> <br /> LogiCow's final fork of MZX (based off of 2.81g) was solely to play [[Caverns of Zeux]] with enhanced graphics.<br /> <br /> LogiCow was not the only person to fork MZX; [[NihilistMatt]] created a fork called [[SquareMZX]]. SquareMZX knocked the resolution per-character to 8x8, but allowed a &quot;quadrant&quot; coloring system where each 2x2 section of any character can have its own color pair. This fork got very minor use; [[PROcrastination]] and the second [[RPG Skool Demo]] both could optionally use SquareMZX mode.<br /> <br /> [[zzo38]] is also desperately trying to make people care about his MZX fork. His version focuses on changes and &quot;improvements&quot; that are generally only of interest to him, including support for [http://en.wikipedia.org/wiki/Forth_(programming_language) Forth], [[PZX features|and various other things]]. He also corrected a long standing, esoteric bug in the handling of built-in spider webs, which has been merged (with changes) into the existing codebase. Despite the fact that zzo38 (and possibly [[smilymzx]], with his fixation on blinking text) is the only person who actually cares about any of these changes, zzo still claims to be working on it and released an initial version of it.<br /> <br /> ==External Links==<br /> *[https://sourceforge.net/projects/mzx32 MZX32 Project Page (Sourceforge)]<br /> *[http://mzx.devzero.co.uk/ The MegaZeux Developer Site]<br /> <br /> [[Category:MegaZeux]]</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=MegaZeux&diff=6834 2009-06-14T16:57:09Z

<p>Zzo38: zzo38 fork</p> <hr /> <div>'''MegaZeux''' is a game creation system created by [[Gregory Janson]]. It was inspired by [[ZZT]], for which Greg and other members of [[Software Visions]] had created several games beforehand. The first version, [[Changelog for 1.00g|1.00g]], was uploaded to AOL on December 4, 1994.<br /> <br /> ==Features==<br /> ===Robotic===<br /> ''See also: [[Robotic]]''<br /> <br /> Robotic is MegaZeux's object-oriented programming language. Some parts of the language, as well as the concept itself, are based on [[ZZT|ZZT's]] ZZT-OOP, though Robotic is much more advanced than ZZT-OOP.<br /> <br /> ==History==<br /> History of MZX's development.<br /> ===Shareware Versions===<br /> <br /> In 1994, MegaZeux 1.00g was released on AOL. It was designed to be an improvement over [[ZZT]], and at that point featured digital sound and music that could be played over Sound Blaster-compatible cards. It featured editable [[character set|character sets]] and larger board sizes than ZZT.<br /> <br /> Some time later, MegaZeux 2.00 was released, featuring a vast interface overhaul, the ability to edit the in-game palette, and other new features.<br /> <br /> Finally, MegaZeux 2.50 was uploaded, and among other changes, included the brand new [[BWSB]] sound engine that was more compatible and more tolerant of Windows. Shortly thereafter, version 2.51 was released, with minor bug fixes and additions. This would be the last version Gregory Janson would release.<br /> <br /> ===Spider Versions===<br /> After MegaZeux was released under the terms of the GNU GPL, [[Spider124]] updated the source code with several useful new features and released his own version of MegaZeux, 2.51s1. Among the new features were a vastly expanded counters limit (1000, compared to 2.51's 50 counters), true mouse support, [[playerx and playery|playerx/playery]] counters, and many bug fixes. Three more versions were released (s2, s3, and s3.1; of which 3.1 was a bug fix release) before development of MZX grew stagnant.<br /> <br /> [[MadBrain]] took the s3.1 source, added one new feature (the [[bi_mesg]] built-in counter) and removed password protection, releasing his modifications as MZX 2.51s3.2. s3.2 was further modified with the introduction of the [[Super MZX|SMZX]] graphics mode (this version was released as SMZX 100 Alpha).<br /> <br /> ===MegaZeux 2.7 and mzxlib===<br /> MZX 2.7 was an effort spearheaded by [[JZig]] to completely rewrite MegaZeux in C++, with a new graphics engine, audio code, and support for other operating systems such as Linux. Most of the initial coding was done by [[MenTaLguY]], until JZig took over in 1999. [[piman]], while not doing much coding himself, performed most of the non-code tasks such as updating the project's SourceForge page. JZig's development on MZX 2.7 stopped around 2001, and it was not picked up afterwards.<br /> <br /> ===MZXak===<br /> [[Akwende]] released the first MZXak version, MZXak 1.0, shortly after MadBrain's SMZX alpha version. MZXak featured several additional features (some of which, like the multi-colored configuration dialogs, were determined by the community to be too useless to warrant the memory usage) including file access, robot targeting, and built-in SMZX mode. All MZXak versions included Akwende's MZX version of Tetris, which demonstrated the use of SMZX graphics.<br /> <br /> MZXak 1.0 was pulled a few months after release from [[DigitalMZX]] due to Akwende's failure to release his source code under the terms of the GNU GPL. He eventually released the source, but not until a lot of public debate and heel-dragging. Other MZXak 1.0 controversy included forward compatibility, which led to MZXak games being playable but not necessarily functioning in MZX2.51s3.1. This broke [[ajs|wizdom's]] judging results in the [[Summer Dualstream Day of Zeux 2001|2001 DsDoZ]].<br /> <br /> MZXak 2.0 was released after much waiting, though the release sparked a fair bit of dispute due to the sudden timing with [[Koji|Koji's]] 2.60 release. MZXak 2.0 is notable for being the only code fork to completely die out.<br /> <br /> ===Exophase Versions===<br /> Following the discussions about MZXak, Koji released MZX 2.60, featuring some of the same additions as MZXak. 2.61 was released shortly after, and around 2.62's release, [[Exophase]] took over development of MegaZeux. Tons of features were added in between 2.62 and 2.70 (the last version of MegaZeux in [[DOS]]) such as [[Expression|expressions]], [[Sprite|sprites]], [[String|strings]], [[Vlayer|the vlayer]], [[MZM|MZMs]], [[Super MZX|SMZX Mode 2]], and many others.<br /> <br /> ===MZX32===<br /> During Exophase's development of MZX for DOS, [[BFeely]] began development on MZX32, which was to be a full-featured port of MegaZeux for the Windows platform. Several alpha versions were released, most of which lacked the world editor (and all of which lacked the robotic code editor). MZX32 was generally regarded as unstable and buggy, and was deemed obsolete once Exophase began work on his SDL port. The last version of MZX32 released featured support for games created using MZX 2.69c.<br /> <br /> ===SDL Port===<br /> <br /> [[Exophase]] took most of the summer of 2004 to do a update/rewrite of MegaZeux into SDL, to break some DOS limitations and to solve MegaZeux's ever-increasing compatibility issues (and to eventually expand MegaZeux onto new platforms such as Linux and the Macintosh). This included re-writing the entire Robotic editor from scratch as source was no longer available for it. Many other source modules were either completely rewritten or heavily revised. After intense pre-testing, MZX 2.80 was released on Aug 9 2004, with workability only intended for Windows 32 platforms. A slew of bug reports that only arises from public testing shortly followed, and Exophase quickly updated with three incremental versions in one month which also officially added support for Linux and MacOS X. Other MegaZeuxers helped in various aspects; for example, [[ajs|ajs's]] and [[MadBrain|mad's]] GDM conversion code was a basis for SAM conversion code. Later on, ajs would write support to abstract file operations for case sensitive file systems, and additional graphical renderers were designed by [[LogiCow]] and [[Mr_Alert]].<br /> <br /> Most version upticks added some functionality (e.g. multi-char editor, code search, ogg support), and all significantly increased stability. MegaZeux is currently extending to handhelds and consoles: [[Oncer]] released a GP2X port, [[kvance]] a Nintendo DS port, Mr_Alert a Wii port, and Exophase has done preliminary PSP support.<br /> <br /> The current version is 2.82b.<br /> <br /> ===MegaZeux Forks===<br /> In early 2007, LogiCow created his own fork of the MZX source. The first version added the Draw command, allowing users to scale characters from the [[vlayer]]. It also served as an underlay (as opposed to an overlay). In more recent versions, the draw command was deleted. A select persisted in using the older versions for the draw command, much to the annoyance of those wishing to stay with Exophase's versions.<br /> <br /> A short time after the previous fork, LogiCow created another fork with an alternate renderer that scaled the graphics up to fit the screen, regardless of aspect ratio. This also allowed for seamless resizing of the MZX window when not running in full screen mode. logicow worked with ajs to merge these renderers into the mainline MZX versions, starting with 2.81e.<br /> <br /> LogiCow's final fork of MZX (based off of 2.81g) was solely to play [[Caverns of Zeux]] with enhanced graphics.<br /> <br /> LogiCow was not the only person to fork MZX; [[NihilistMatt]] created a fork called [[SquareMZX]]. SquareMZX knocked the resolution per-character to 8x8, but allowed a &quot;quadrant&quot; coloring system where each 2x2 section of any character can have its own color pair. This fork got very minor use; [[PROcrastination]] and the second [[RPG Skool Demo]] both could optionally use SquareMZX mode.<br /> <br /> [[zzo38]] is also desperately trying to make people care about his MZX fork. His version focuses on changes and &quot;improvements&quot; that are generally only of interest to him, including support for Forth, the ability to use the old ALT+D function in the editor (only zzo38 seems to remember what this is or use the function to begin with), [[deferred expressions]], [[extended kinds]], new overlay modes (including the ability to draw overlays on the outside of the viewport instead of inside, and the ability to hide the board and draw only the overlay) and SMZX modes (including a 16-color per character mode and a blinking text mode), and displacement overlay modes which allow adjustment of the overlay by individual pixels. He also corrected a long standing, esoteric bug in the handling of built-in spider webs, which has been merged (with changes) into the existing codebase. Despite the fact that zzo38 is the only person who actually cares about any of these changes, and that very little actual work has been seen, zzo still claims to be working on it and released version P1 at http://zzo38computer.cjb.net/mzx1/mzx_extended/ but it has some bugs, so version P2 will fix those bugs and add more features.<br /> <br /> ==External Links==<br /> *[https://sourceforge.net/projects/mzx32 MZX32 Project Page (Sourceforge)]<br /> *[http://mzx.devzero.co.uk/ The MegaZeux Developer Site]<br /> <br /> [[Category:MegaZeux]]</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=MegaZeux&diff=6829 2009-06-12T13:49:14Z

<p>Zzo38: zzo38 is also fork MZX.</p> <hr /> <div>'''MegaZeux''' is a game creation system created by [[Gregory Janson]]. It was inspired by [[ZZT]], for which Greg and other members of [[Software Visions]] had created several games beforehand. The first version, [[Changelog for 1.00g|1.00g]], was uploaded to AOL on December 4, 1994.<br /> <br /> ==Features==<br /> ===Robotic===<br /> ''See also: [[Robotic]]''<br /> <br /> Robotic is MegaZeux's object-oriented programming language. Some parts of the language, as well as the concept itself, are based on [[ZZT|ZZT's]] ZZT-OOP, though Robotic is much more advanced than ZZT-OOP.<br /> <br /> ==History==<br /> History of MZX's development.<br /> ===Shareware Versions===<br /> <br /> In 1994, MegaZeux 1.00g was released on AOL. It was designed to be an improvement over [[ZZT]], and at that point featured digital sound and music that could be played over Sound Blaster-compatible cards. It featured editable [[character set|character sets]] and larger board sizes than ZZT.<br /> <br /> Some time later, MegaZeux 2.00 was released, featuring a vast interface overhaul, the ability to edit the in-game palette, and other new features.<br /> <br /> Finally, MegaZeux 2.50 was uploaded, and among other changes, included the brand new [[BWSB]] sound engine that was more compatible and more tolerant of Windows. Shortly thereafter, version 2.51 was released, with minor bug fixes and additions. This would be the last version Gregory Janson would release.<br /> <br /> ===Spider Versions===<br /> After MegaZeux was released under the terms of the GNU GPL, [[Spider124]] updated the source code with several useful new features and released his own version of MegaZeux, 2.51s1. Among the new features were a vastly expanded counters limit (1000, compared to 2.51's 50 counters), true mouse support, [[playerx and playery|playerx/playery]] counters, and many bug fixes. Three more versions were released (s2, s3, and s3.1; of which 3.1 was a bug fix release) before development of MZX grew stagnant.<br /> <br /> [[MadBrain]] took the s3.1 source, added one new feature (the [[bi_mesg]] built-in counter) and removed password protection, releasing his modifications as MZX 2.51s3.2. s3.2 was further modified with the introduction of the [[Super MZX|SMZX]] graphics mode (this version was released as SMZX 100 Alpha).<br /> <br /> ===MegaZeux 2.7 and mzxlib===<br /> MZX 2.7 was an effort spearheaded by [[JZig]] to completely rewrite MegaZeux in C++, with a new graphics engine, audio code, and support for other operating systems such as Linux. Most of the initial coding was done by [[MenTaLguY]], until JZig took over in 1999. [[piman]], while not doing much coding himself, performed most of the non-code tasks such as updating the project's SourceForge page. JZig's development on MZX 2.7 stopped around 2001, and it was not picked up afterwards.<br /> <br /> ===MZXak===<br /> [[Akwende]] released the first MZXak version, MZXak 1.0, shortly after MadBrain's SMZX alpha version. MZXak featured several additional features (some of which, like the multi-colored configuration dialogs, were determined by the community to be too useless to warrant the memory usage) including file access, robot targeting, and built-in SMZX mode. All MZXak versions included Akwende's MZX version of Tetris, which demonstrated the use of SMZX graphics.<br /> <br /> MZXak 1.0 was pulled a few months after release from [[DigitalMZX]] due to Akwende's failure to release his source code under the terms of the GNU GPL. He eventually released the source, but not until a lot of public debate and heel-dragging. Other MZXak 1.0 controversy included forward compatibility, which led to MZXak games being playable but not necessarily functioning in MZX2.51s3.1. This broke [[ajs|wizdom's]] judging results in the [[Summer Dualstream Day of Zeux 2001|2001 DsDoZ]].<br /> <br /> MZXak 2.0 was released after much waiting, though the release sparked a fair bit of dispute due to the sudden timing with [[Koji|Koji's]] 2.60 release. MZXak 2.0 is notable for being the only code fork to completely die out.<br /> <br /> ===Exophase Versions===<br /> Following the discussions about MZXak, Koji released MZX 2.60, featuring some of the same additions as MZXak. 2.61 was released shortly after, and around 2.62's release, [[Exophase]] took over development of MegaZeux. Tons of features were added in between 2.62 and 2.70 (the last version of MegaZeux in [[DOS]]) such as [[Expression|expressions]], [[Sprite|sprites]], [[String|strings]], [[Vlayer|the vlayer]], [[MZM|MZMs]], [[Super MZX|SMZX Mode 2]], and many others.<br /> <br /> ===MZX32===<br /> During Exophase's development of MZX for DOS, [[BFeely]] began development on MZX32, which was to be a full-featured port of MegaZeux for the Windows platform. Several alpha versions were released, most of which lacked the world editor (and all of which lacked the robotic code editor). MZX32 was generally regarded as unstable and buggy, and was deemed obsolete once Exophase began work on his SDL port. The last version of MZX32 released featured support for games created using MZX 2.69c.<br /> <br /> ===SDL Port===<br /> <br /> [[Exophase]] took most of the summer of 2004 to do a update/rewrite of MegaZeux into SDL, to break some DOS limitations and to solve MegaZeux's ever-increasing compatibility issues (and to eventually expand MegaZeux onto new platforms such as Linux and the Macintosh). This included re-writing the entire Robotic editor from scratch as source was no longer available for it. Many other source modules were either completely rewritten or heavily revised. After intense pre-testing, MZX 2.80 was released on Aug 9 2004, with workability only intended for Windows 32 platforms. A slew of bug reports that only arises from public testing shortly followed, and Exophase quickly updated with three incremental versions in one month which also officially added support for Linux and MacOS X. Other MegaZeuxers helped in various aspects; for example, [[ajs|ajs's]] and [[MadBrain|mad's]] GDM conversion code was a basis for SAM conversion code. Later on, ajs would write support to abstract file operations for case sensitive file systems, and additional graphical renderers were designed by [[LogiCow]] and [[Mr_Alert]].<br /> <br /> Most version upticks added some functionality (e.g. multi-char editor, code search, ogg support), and all significantly increased stability. MegaZeux is currently extending to handhelds and consoles: [[Oncer]] released a GP2X port, [[kvance]] a Nintendo DS port, Mr_Alert a Wii port, and Exophase has done preliminary PSP support.<br /> <br /> The current version is 2.82b.<br /> <br /> ===MegaZeux Forks===<br /> In early 2007, LogiCow created his own fork of the MZX source. The first version added the Draw command, allowing users to scale characters from the [[vlayer]]. It also served as an underlay (as opposed to an overlay). In more recent versions, the draw command was deleted. A select persisted in using the older versions for the draw command, much to the annoyance of those wishing to stay with Exophase's versions.<br /> <br /> A short time after the previous fork, LogiCow created another fork with an alternate renderer that scaled the graphics up to fit the screen, regardless of aspect ratio. This also allowed for seamless resizing of the MZX window when not running in full screen mode. logicow worked with ajs to merge these renderers into the mainline MZX versions, starting with 2.81e.<br /> <br /> LogiCow's final fork of MZX (based off of 2.81g) was solely to play [[Caverns of Zeux]] with enhanced graphics.<br /> <br /> LogiCow was not the only person to fork MZX; [[NihilistMatt]] created a fork called [[SquareMZX]]. SquareMZX knocked the resolution per-character to 8x8, but allowed a &quot;quadrant&quot; coloring system where each 2x2 section of any character can have its own color pair. This fork got very minor use; [[PROcrastination]] and the second [[RPG Skool Demo]] both could optionally use SquareMZX mode.<br /> <br /> [[zzo38]] is also fork MZX. Version number is 2.82bP1. This version includes support for Forth codes, ability to use the old ALT+D function in the editor, deferred expressions, extended kinds, new overlay modes and SMZX modes, and displacement overlay modes which allow adjustment of overlay by individual pixels. Also the spider-webs bug is fixed. This fork version has not been seen in a while, but actually it is still getting worked on.<br /> <br /> ==External Links==<br /> *[https://sourceforge.net/projects/mzx32 MZX32 Project Page (Sourceforge)]<br /> *[http://mzx.devzero.co.uk/ The MegaZeux Developer Site]<br /> <br /> [[Category:MegaZeux]]</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=Zzo38&diff=6802 2009-05-23T12:30:40Z

<p>Zzo38: </p> <hr /> <div>'''zzo38''' is something of an enigma to the community. Nobody is quite sure if they are a real person or the [[Identity deception|alternative account]] of somebody else, and there doesn't seem to be any evidence pointing in either direction. Typical characteristics of &quot;classic&quot; zzo38 include horribly broken English such as &quot;Old mesiges ar being crosed out.&quot;[http://en.wikipedia.org/wiki/User_talk:Zzo38] and &quot;I think I like the old un-frenly serch more beter.&quot; [http://www.digitalmzx.net/forums/index.php?s=&amp;showtopic=6023&amp;view=findpost&amp;p=77256] and a general lack of effort in things that he does, though that seems to be quite a different story when looking at his more recent activities. (There is some speculation that the &quot;classic&quot; zzo38 may be a joke, a conspiracy, or a different person. But a few of the old stuff is still on the same web-site, so we cannot be exactly sure.)<br /> <br /> zzo38 released several ZZT and MZX games, including [[Cooking Game]].<br /> <br /> Recently, zzo has reappeared on the DigitalMZX forums with vastly improved grammar and an apparent fascination with Mahjong games and Forth codes.<br /> <br /> ==External Links==<br /> *[http://zzo38computer.cjb.net/ ZZO38COMPUTER]<br /> *[http://zzo38computer.cjb.net/wiki/ ZZO38COMPUTER Wiki]<br /> *[http://zzo38computer.cjb.net/mzx1/ MegaZeux games]<br /> <br /> {{WeaselStub}}<br /> {{NeedsPeerReview}}</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=Zzo38&diff=6793 2009-04-27T16:44:40Z

<p>Zzo38: </p> <hr /> <div>'''zzo38''' is something of an enigma to the community. Nobody is quite sure if they are a real person or the [[Identity deception|alternative account]] of somebody else, and there doesn't seem to be any evidence pointing in either direction. Typical characteristics of &quot;classic&quot; zzo38 include horribly broken English such as &quot;Old mesiges ar being crosed out.&quot;[http://en.wikipedia.org/wiki/User_talk:Zzo38] and &quot;I think I like the old un-frenly serch more beter.&quot; [http://www.digitalmzx.net/forums/index.php?s=&amp;showtopic=6023&amp;view=findpost&amp;p=77256] and a general lack of effort in things that he does, though that seems to be quite a different story when looking at his more recent activities. (There is some speculation that the &quot;classic&quot; zzo38 may be a joke, a conspiracy, or a different person. But a few of the old stuff is still on the same web-site, so we cannot be exactly sure.)<br /> <br /> zzo38 released several ZZT and MZX games, including [[Cooking Game]].<br /> <br /> Recently, zzo has reappeared on the DigitalMZX forums with vastly improved grammar and an apparent fascination with Mahjong games.<br /> <br /> ==External Links==<br /> *[http://zzo38computer.cjb.net/ ZZO38COMPUTER]<br /> *[http://zzo38computer.cjb.net/wiki/ ZZO38COMPUTER Wiki]<br /> *[http://zzo38computer.cjb.net/mzx1/ MegaZeux games]<br /> <br /> {{WeaselStub}}<br /> {{NeedsPeerReview}}</div>

Zzo38 https://www.digitalmzx.com/wiki/index.php?title=Talk:Zzo38&diff=5882 2008-05-17T18:13:51Z

<p>Zzo38: New page: I do not remember many of the old things described there before, and even I am unsure of the validity (or alternate account). Anyways, now I am a real person for sure, and once you have mo...</p> <hr /> <div>I do not remember many of the old things described there before, and even I am unsure of the validity (or alternate account). Anyways, now I am a real person for sure, and once you have more information, you can make it into 2 sections, &quot;Old zzo38&quot; section and &quot;New zzo38&quot; section (if that is sensible). I have nothing to post here yet (at least I have nothing related to MZX at this time). I am really zzo38 for sure though, you can prove it by telling me the number and I will make a page with that number on my web-site so that you can check if it is valid or not. --[[User:Zzo38|Zzo38]] 11:13, 17 May 2008 (PDT)</div>

Zzo38