Megazeux Tutorial Series on Youtube I've started a tutoriual series on Youtube and I need your thumbs
#1
Posted 24 April 2013 - 06:39 AM
01 - Introduction http://youtu.be/dzAOo812cU0
02 - download http://youtu.be/xVqhHNzmbqU
03 - explore http://youtu.be/-1b3xzK_SK8
04 - configure http://youtu.be/YxK88erfP1s
05 - joystick http://youtu.be/i-Caq2fwpRY
06 - create Pt 1 http://youtu.be/fDE4LAYEI8Q
07 - create Pt 2 http://youtu.be/OTzyAjLPIns[/b][/b]
Could you all go and give the videos a 'like' when you can? Hopefully they will get some traffic.
I have many more ideas in the works and I'll continue to make more videos as often as I can.
-More advanced game creation
-highlight help file and talk about online help file
-showcase the better games out there
-the character editor
-the palette editor
-implementing sound and music
-robotic
-counters
-strings
-loops
-fixing bugs
-subroutines
-expressions
-sprites
-animation
-the overlay
-mzm's
-super mzx modes
-file access
-how to make a side scrolling game
any other ideas?
I welcome feedback or critique of the tutorial vids. These are the first I've made and I'm sure their is room for improvement.
Thanks for the help!
"Before you criticize someone, you should walk a mile in their shoes. That way, when you criticize them, you’re a mile away and you have their shoes."
-Jack Handey
#2
Posted 24 April 2013 - 04:14 PM
Though, I think I'll use this series to introduce some of my friends to Mzx since I made them quite interested in it after showing them my current project.
#3
Posted 24 April 2013 - 04:55 PM
"Before you criticize someone, you should walk a mile in their shoes. That way, when you criticize them, you’re a mile away and you have their shoes."
-Jack Handey
#4
Posted 24 April 2013 - 08:47 PM

xx̊y (OST) - HELLQUEST (OST) - Zeux I: Labyrinth of Zeux (OST) (DOS OST)
w/ Lancer-X and/or asgromo: Pandora's Gate - Thanatos Insignia - no True(n) - For Elise OST
MegaZeux: Online Help File - Keycode Guide - Joystick Guide - Official GIT Repository
#5
Posted 25 April 2013 - 04:49 AM
"Before you criticize someone, you should walk a mile in their shoes. That way, when you criticize them, you’re a mile away and you have their shoes."
-Jack Handey
#6
Posted 26 April 2013 - 01:16 AM
Megazeux, zzt, gcs, game creation system, make your own game, text mode, ascii, video game, pc game, retro, classic, unreal, engine, game, creation, system, tim, sweeney, epic, megagames, software, visions, alexis, janson, digital, mzx, shareware, games, create, make, program, Windows, Mac OS (Operating System), Maker, Intro, Computer, Tutorial, Introduction, Linux, ubuntu, caverns of zeux, zeux, Kroz, rogue, roguelike, dwarf fortress, exophase, dos, game maker
This post has been edited by Graham: 29 April 2013 - 05:48 AM
"Before you criticize someone, you should walk a mile in their shoes. That way, when you criticize them, you’re a mile away and you have their shoes."
-Jack Handey
#7
Posted 29 April 2013 - 05:46 AM
08 - create Pt3 http://youtu.be/sTHk265g08c
09 - design Pt1 http://youtu.be/32tLs-HQmLc
10 - design Pt2 http://youtu.be/1KaTQ0WvqHE
I had hoped it would be more but it's been a busy week. The next ones I'm working on will be a lot of fun for me though, so I'm looking forward to them. They are robotic, character editing & animation.
If you get the time, go 'like' them on YouTube. It'll help them get more traffic.
This post has been edited by Graham: 29 April 2013 - 06:33 AM
"Before you criticize someone, you should walk a mile in their shoes. That way, when you criticize them, you’re a mile away and you have their shoes."
-Jack Handey
#8
Posted 30 April 2013 - 12:47 AM
This post has been edited by Graham: 30 April 2013 - 12:48 AM
"Before you criticize someone, you should walk a mile in their shoes. That way, when you criticize them, you’re a mile away and you have their shoes."
-Jack Handey
#10
Posted 30 April 2013 - 02:57 AM
"Before you criticize someone, you should walk a mile in their shoes. That way, when you criticize them, you’re a mile away and you have their shoes."
-Jack Handey
#11
Posted 08 November 2013 - 08:56 PM
Thanks!
This post has been edited by Nahah: 08 November 2013 - 08:56 PM
#12
Posted 08 November 2013 - 11:38 PM
"Before you criticize someone, you should walk a mile in their shoes. That way, when you criticize them, you’re a mile away and you have their shoes."
-Jack Handey
#13
Posted 24 April 2014 - 08:52 PM
I have been thinking about another interesting idea for a tutorial. It would be about the game design process. I've got a great asset to assist me with this, zip files of my game. I've been doing them daily since the beginning and they are numbered. I could reopen them and go through them to show the early processes of creating the game, then show how progress was made to create better systems, programming, etc. It would be fun for me as well as inform the novice game creator. What do you think? Would this be a good idea?
"Before you criticize someone, you should walk a mile in their shoes. That way, when you criticize them, you’re a mile away and you have their shoes."
-Jack Handey
#14
Posted 04 October 2014 - 01:38 AM
Test:
EDIT: And so it does!
By the way I'm having several issues with subroutines. A video explaining them would be nice. I'm trying to get robots to tell other robots to do something abruptly... and then tell them to return to what they were doing when originally interrupted.
This post has been edited by T-Bone: 04 October 2014 - 01:50 AM
#15
Posted 04 October 2014 - 03:52 PM
T-Bone, on 03 October 2014 - 05:38 PM, said:
Sigh... Yeah I want to get back to making more videos soon, I found it really fun and fulfilling. I just can't seem to get my life together lately, never enough hours in the day to do half the things I want.
Anyhoo, I use subroutines quite a bit. One thing almost every robot in the game uses is this:
: "#pause" zap "#pause" 1 end : "unpause" restore "#pause" 1 goto "#return"
This is so that any robot can pause the game and continue to run its program, then un-pause the game. There is no difference between a subroutine label used internally and one used externally.
so to call this subroutine, I have the robot use:
send "all" to "#pause"
then when the game needs to be un-paused, the command
send "all" to "unpause"
is employed. I think if i'm just addressing one robot I could just use
send "pepper" to "#return"
and then the robot "pepper" whould just return to the line after the subroutine was called, but since I'm addressing all
paused robots, I use the universal label [send all "unpause"] and they return themselves to the line after the subroutine
was called. If I used
send "all" to "#return"
then all robots that are in a subroutine would abort it, not just the paused ones.
the zap command is in case #pause gets called more than once per pause session. That would cause all paused robots to permanently halt running, since the second call to pause would return to the [end] line, where they were already halted and waiting for further instructions.
So, you need to be pretty organized with how you use subroutines, you must always get out of what ever subroutine you are in using
goto "#return"
or have another robot send to #return. If you don't, your program may begin to work unexpectedly since the robot will continue to be in that subroutine until it is called out of it.
I hope this helps. If you need further help, post the code you are having trouble with and I'm sure I or one of the other community members can help with what is going on.
"Before you criticize someone, you should walk a mile in their shoes. That way, when you criticize them, you’re a mile away and you have their shoes."
-Jack Handey
#16
Posted 05 October 2014 - 09:28 PM
Quote
This explains a lot of why all my enemies just don't move. I wasn't including a zap or restore for the pausing subroutine calls. I have been stuck on this one missing component for years lol
Thanks for this and you explained the process very well!
#17
Posted 07 October 2014 - 05:44 PM
"Before you criticize someone, you should walk a mile in their shoes. That way, when you criticize them, you’re a mile away and you have their shoes."
-Jack Handey