MFGG phpBB Message Boards Archive :: View topic

Alright... I messed around with the codes and got rid of almost all the scripts by adding a few codes on obj_mario.
Anybody that wants to use this Engine and save space and make it easier to work with go ahead and read my crazyness.
Spoiler:

I agree that would help out a lot of rookie gml developers. Anyways I personally don't like to use this:

Syntax: [ Download ] [ Hide ]

Using gml Syntax Highlighting

if (global.state == 0)

{

    scr_mario_small();

}

if (global.state == 1)

{

    scr_mario_big();

}

///etc...

Instead using switch can not only be convenient but also teaches rookies how a switch function works.

This is just an example:

Syntax: [ Download ] [ Hide ]

Using gml Syntax Highlighting

switch (global.state)

{

    case ("small"): scr_mario_small(); break;

    case ("big"): scr_mario_big(); break;

    case ("fire"): scr_mario_fire(); break;

    case ("leaf"): scr_mario_leaf(); break;

    case ("tanooki"): scr_mario_tanooki(); break;

    ///bunch of more power up things goes here

    default: scr_mario_big(); break; //worst case scenario just make sure Mario animates for debugging

}

Author:	SuperArthurBros [ Thu Feb 19, 2015 1:32 pm ]
Post subject:	Re: Hello Mario Engine v6.1
I don't understand Switch and Break variables function.

Author:	Hello [ Thu Feb 19, 2015 2:52 pm ]
Post subject:	Re: Hello Mario Engine v6.1
EDGE wrote: Alright... I messed around with the codes and got rid of almost all the scripts by adding a few codes on obj_mario. Anybody that wants to use this Engine and save space and make it easier to work with go ahead and read my crazyness. Spoiler: First of all, I went ahead and changed all the global.state codes. Why confuse yourself with numbers, global.state=0, global.state=1,etc. I just changed them to: Code: global.state="small" global.state="big" etc On The Create Event Added: Code: sprite="walk" global.character="mario" On the Drawing Event Code: execute_string("sprite_index=spr_"+global.character+"_"+global.powerup+"_"+sprite) Changed every sprite_index=sprite_image_here to sprite="pose here". For example, instead of having this: Code: if global.state = 0 sprite_index = spr_mario_small_walk if global.state = 1 sprite_index = spr_mario_big_walk if global.state = 2 sprite_index = spr_mario_fire_walk if global.state = 3 sprite_index = spr_mario_hammer_walk if global.state = 4 sprite_index = spr_mario_leaf_walk if global.state = 5 sprite_index = spr_mario_tanooki_walk if global.state = 6 sprite_index = spr_mario_frog_walk if global.state = 7 sprite_index = spr_mario_bomb_walk if global.state = 8 sprite_index = spr_mario_ice_walk if global.state = 9 sprite_index = spr_mario_super_walk if global.state = 10 sprite_index = spr_mario_carrot_walk if global.state = 11 sprite_index = spr_mario_ninja_walk if global.state = 12 sprite_index = spr_mario_bee_walk if global.state = 13 sprite_index = spr_mario_shell_walk if global.state = 14 sprite_index = spr_mario_penguin_walk All you need is this: Code: sprite="walk" The Code on the Drawing Event will take care of everything. As long as the sprites are named like you have them: Let's say you wanna make Mario show the small walking sprite: Quote: spr_mario_small_walk All you have to do is this: Code: sprite="walk" Just the last part of the sprite's name. No need to make a code for each power up either since the are all named the same. The Drawing event draws "spr_" Plus the global.character Plus the Powerup/State he is in Plus "sprite" which is the pose, If you Add another Character like let's say, Luigi. All you have to do is rename the sprites where it says mario to luigi, ex: Quote: spr_mario_small_walk spr_luigi_small_walk And have an event/code change the global.character="mario" to global.character="luigi". You can even use that global.character to have specific features for each character in just one object(obj_mario). It's kind of basic, can be done easier but at least with just those 3 Lines of Code (2 on the create event and 1 on the drawing event) you can get rid of: Quote: scr_mariowalk scr_mariojump scr_mariorun scr_mariorunjump scr_marioclimb scr_mariohold scr_mariocarry scr_mariowap scr_mariogoal scr_marioslide And Turn: Quote: scr_smallmario scr_bigmario scr_firemario scr_hammermario scr_leafmario scr_tanookimario scr_frogmario scr_bombmario scr_icemario scr_supermario scr_carrotmario scr_ninjamario scr_beemario scr_shellmario scr_penguinmario Into just one script. PS: This will make it easier to add power ups later too, let's say you add... the squirrel power up. just name the sprites with all the poses like the ones on the engine already are: Quote: spr_mario_fire_walk Into: Quote: spr_mario_squirrel_walk And have an item that makes mario's global.state turn into: Quote: global.state"squirrel" The rest is Self-explanatory Hypernova wrote: I agree that would help out a lot of rookie gml developers. Anyways I personally don't like to use this: Syntax: [ Download ] [ Hide ] Syntax: [ Download ] [ Show ] Using gml Syntax Highlighting if (global.state == 0) { scr_mario_small(); } if (global.state == 1) { scr_mario_big(); } ///etc... Instead using switch can not only be convenient but also teaches rookies how a switch function works. This is just an example: Syntax: [ Download ] [ Hide ] Syntax: [ Download ] [ Show ] Using gml Syntax Highlighting switch (global.state) { case ("small"): scr_mario_small(); break; case ("big"): scr_mario_big(); break; case ("fire"): scr_mario_fire(); break; case ("leaf"): scr_mario_leaf(); break; case ("tanooki"): scr_mario_tanooki(); break; ///bunch of more power up things goes here default: scr_mario_big(); break; //worst case scenario just make sure Mario animates for debugging } Both of these are suggestions for super old versions of my engine, and thus, do not apply to the current version. (Also, execute_string is bad, and not supported in Studio.)

Author:	Joelishere [ Fri Feb 20, 2015 9:38 am ]
Post subject:	Re: Hello Mario Engine v6.1
This looks awesome. I am going to download when I get home ^_^

Author:	Hello [ Sat Feb 21, 2015 5:17 pm ]
Post subject:	Re: Hello Mario Engine v6.1
Due to popular demand, a new legacy version is also available for download now.

Author:	Hello [ Fri Apr 24, 2015 2:12 pm ]
Post subject:	Re: Hello Mario Engine v6.1.1
New update available: 6.1.1 Numerous fixes. Collision events with obj_solidtop removed from most objects. Also, the Hello Mario Engine is on GitHub now.

MFGG phpBB Message Boards Archive https://phpbb.mfgg.net/

Hello Mario Engine https://phpbb.mfgg.net/viewtopic.php?f=8&t=12582	Page 13 of 15

Author:	SuperArthurBros [ Fri Apr 24, 2015 11:08 pm ]
Post subject:	Re: Hello Mario Engine v6.1.1
How can an object work without collision code with obj_solidtop? Is this another feature from GM:S?

Author:	Willsaber [ Fri Apr 24, 2015 11:24 pm ]
Post subject:	Re: Hello Mario Engine v6.1.1
SuperArthurBros wrote: How can an object work without collision code with obj_solidtop? Is this another feature from GM:S? I believe Hello is referring to that it is now implemented in the Step event.

Author:	Mors [ Sat Apr 25, 2015 6:17 am ]
Post subject:	Re: Hello Mario Engine v6.1.1
Hello wrote: Collision events with obj_solidtop removed from most objects. Finally! I was waiting for that since HE5.

Author:	Hello [ Mon Jun 29, 2015 9:09 pm ]
Post subject:	Re: Hello Mario Engine v6.1.2
New update available: 6.1.2. No new features, just a bunch of fixes. (Full changelog is on GitHub) If you know of any bugs still in 6.1.2, make sure to report them all!

Author:	Hello [ Thu Oct 01, 2015 10:01 pm ]
Post subject:	Re: Hello Mario Engine v6.1.3
New update available: 6.1.3 (Full changelog on Github) You can now add new slope shapes without touching any code. All known bugs fixed.

Author:	Mario Silva [ Fri Oct 02, 2015 12:15 am ]
Post subject:	Re: Hello Mario Engine v6.1.3
Nice job!

Author:	LuNiney [ Fri Oct 02, 2015 2:49 am ]
Post subject:	Re: Hello Mario Engine v6.1.3
Hello wrote: New update available: 6.1.3 (Full changelog on Github) You can now add new slope shapes without touching any code. All known bugs fixed. does that mean I can literally just make a slope like this? or maybe this

Author:	Gatete [ Fri Oct 02, 2015 3:10 am ]
Post subject:	Re: Hello Mario Engine v6.1.3
I just checked it, IMO Mario should stop right on the little wall at the right.

Author:	Hello [ Sat Oct 03, 2015 2:10 pm ]
Post subject:	Re: Hello Mario Engine v6.1.3
Gatete wrote: I just checked it, IMO Mario should stop right on the little wall at the right. This suggestion will break jump-through slopes, so you're going to need to use obj_solid in these situations...

Page 13 of 15	All times are UTC - 5 hours [ DST ]
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group http://www.phpbb.com/

Author:	DJ Coco [ Sat Oct 03, 2015 2:15 pm ]
Post subject:	Re: Hello Mario Engine v6.1.3
Very useful. You should also add an auto-tiling algorithm.

Author:	SuperArthurBros [ Sat Oct 03, 2015 3:05 pm ]
Post subject:	Re: Hello Mario Engine v6.1.3
DJ Coco wrote: Very useful. You should also add an auto-tiling algorithm. I can't think of anything where this could be used in the engine. Having too many tile objects in the room would create a massive lag sometimes.

Author:	Mors [ Sat Oct 03, 2015 3:26 pm ]
Post subject:	Re: Hello Mario Engine v6.1.3
DJ Coco wrote: Very useful. You should also add an auto-tiling algorithm. Also add a tool that design levels automatically. no seriously this is a bad idea.

Author:	Willsaber [ Sat Oct 03, 2015 3:31 pm ]
Post subject:	Re: Hello Mario Engine v6.1.3
DJ Coco wrote: Very useful. You should also add an auto-tiling algorithm. Finding extended tiles of the tilesets he uses is very difficult. I've had to extend them myself for Fangame Maker!

Author:	TheShyGuy [ Sat Oct 03, 2015 4:16 pm ]
Post subject:	Re: Hello Mario Engine v6.1.3
Do any of you guys know what DJ Coco meant or did you just decide to assume the worst?

Author:	LuNiney [ Sat Oct 03, 2015 4:23 pm ]
Post subject:	Re: Hello Mario Engine v6.1.3
SuperArthurBros wrote: DJ Coco wrote: Very useful. You should also add an auto-tiling algorithm. I can't think of anything where this could be used in the engine. Having too many tile objects in the room would create a massive lag sometimes. yes, but you could just make an object that would be the tileset, then when the room starts, the object would destroy itself, but draw a tile on its place.