Mugen Battle Network

Card Sagas Wars - The future of Mugen?

2008-02-15T16:50:00.000-05:00

EXCh33ky posted a link to this earlier today on IMT. Here's a list of some characters in the game:
Chun-li
Cloud
Aeris
Yuna
Ryu
Ken
Sailor Mars
Guile
Blanka
ED and AL form FMA
Sonic
Mario
Peach
Samus
Link
Megaman
Master Chief
Mewtwo
Pikachu
Kirby
Asuna from Mahou Sensei Negima!

This full game looks awesome! You can find out more about it here.

Sorry & Thanks

2008-02-11T11:18:00.000-05:00

Sorry for the lack of updates, a lot's been going on lately, so I haven't been able to post too often. I've been working on some stuff lately, and as soon as I'm able to post more you'll all be able to see everything I've been doing. I'll try to add some more tutorials as well. Thanks again to everyone who visited here & the forum, this blog has over 8,000 pageviews and growing, thanks for the support!

EA/Marvel brawler KO'd!

2008-01-29T18:23:00.000-05:00

Via GameSpot:

When EA Chicago was closed last year, one of the issues unaddressed at the time was the fate of the studio's projects, a Marvel fighting game and a second fighter based on a new intellectual property. That mystery has been cleared up a little, as Electronic Arts and Marvel have terminated both the project and their licensing agreement, according to a GameTap report.

The deal between Marvel and EA dates back to 2004, when the companies announced a multiyear agreement for fighting games featuring famous Marvel characters alongside new EA-created heroes. The first offspring of the deal was Marvel Nemesis: Rise of the Imperfects, a poorly received effort that saw its price slashed by 40 percent less than two months after its release.

Another mystery in the wake of the EA Chicago closing--the future of the studio's general manager, Kudo Tsunoda--was recently solved when Microsoft confirmed the developer's hiring. Tsunoda will now work at Microsoft Game Studios under corporate vice president Shane Kim. However, a growing tide of unconfirmed reports has Microsoft's own Marvel project--an Xbox 360 and PC massively multiplayer online role-playing game--being put on indefinite hold.

A shame really. Why not give Capcom back the license? Then we might enjoy online multiplayer on Live or PSN or even... Marvel vs Capcom 3!!

Problems Registering On MugenChina? Look No Further!

2007-12-04T20:58:00.000-05:00

I've seen a few people lately have problems registering on MugenChina, where google and babelfish fail to help so I thought I'd make it a little easier...

on the international board there is a link (!) to help register for english users... try it!

Samus's Stage Creation Tutorial

2007-10-29T10:35:00.000-04:00

This should help out many... still online here -->> http://www.geocities.com/samus1978/help/menu.html

PART 1
GETTING STARTED

Overview: Getting your pictures for your background.
The first step in creating a background is getting your image files. If you want to rip a background, you must use an 'emulator'. An emulator is basically a computer program that can play console or arcade games on your computer, there are also emulators for other computers. An emulator won't do anything on it's own, you need a ROM image of the software or game for it to work. The legality of emulators and roms are still being discussed today, but basically under copyright laws you are able to make 1 backup copy of your purchased game, book, tape, cd, movie, ect...
The emulators that I recommend are Project64 (n64), FinalBurn (CPS-2 arcade games), ZSNES (snes), GENESYST (genesis), NESTICLE (nes), and MAME (arcade). Each emulator has it's own way of deleting the layers and capturing a picture. For example, with ZSNES the 1 - 6 keys disable or enable a background or the sprites, from there you then hit the 'F1' key to bring up the pop up menu, where you can choose 'SAVE SNAPSHOT'. Depending on what color depth you have your settings on it will save as either a .pcx (8bit) or .bmp (16bit). With UltraHLE just hit the 'F10' key and it will save a snapshot in the targa format. With CALLUS, GENESYST, and NESTICLE, on the menu if you choose SETTINGS then LAYERS, you can disable whatever layer you want. Then hit 'F9' to save the .pcx. Also a good tip when you want to create multiple layers of backgrounds, try only activating one layer at a time, then take a snapshot. That way it is much easier later.
After capturing all of the needed background(s), the next step is to move them into a folder in you MUGEN directory. Elecbyte suggests a mugen\work\stages\backgroundname folder but you can use whatever your preference is. Now that you've collected all of your files that you are going to be working with, you are now ready to move on to the next step.

PART 2
GETTING YOUR IMAGES READY

Overview: Saving your images correctly.
Now that you have all of the files you need into one directory, now you must prep every single one of them!! Yes I know this may seem a little frightening at first, but this must be done. What I really recommend is a paint program, such as Paint Shop Pro or Correl Draw. If you do not have one, you can always check www.download.com for a trial program. It will be an invaluable tool once you get started. Now for my examples I will be going by the Paint Shop Pro menu, but all of the paint programs are basically the same.
Now first OPEN your file, as you can see the picture will load and the background of the picture will most likely be black. Now for beginners sake, black (or color 0-0-0) will be the 'masking' color for all of your backgrounds, the 'masking' color will be the color that is not drawn in MUGEN.
Second you are going to DECREASE THE COLOR DEPTH to a 256 color (8bit) image. Now a problem may arise where if the black background that you want to be drawn may be misunderstood as the masking color. To check to see if this will be a problem, go to EDIT PALLETTE, then choose the upper-left color, which will be black 0-0-0. Change it to a bright color, preferably light red. If that light red shows up where you don't want it to (such as part of the background you want to keep) there is a quick way to fix it.
Here's how. First either hit undo or change the light red back to black 0-0-0. Now somewhere on the palette where a color is not defined (usually by white 256-256-256 or a gray) choose that light red again. Next INCREASE THE COLOR DEPTH to 16bit, then immediately DECREASE THE COLOR DEPTH to 256 color (8bit). Change the black 0-0-0, to something very very close to it... such as 0-0-4 or 0-0-8, then change the light red to 0-0-0. Again INCREASE THE COLOR DEPTH to 16bit, then immediately DECREASE THE COLOR DEPTH to 256 color (8bit), and the problem is solved!
Finally (this next one is easy) click FILE then SAVE AS. And make sure that you are saving the image in the right directory, and saving the image as a PCX - ZSOFT Paintbrush Image Version 5. And when you've completed this with ALL of your images... you're ready to move on to the next step!

PART 3
CREATING THE SPRITE FILE

Overview: Creating a .SFF file for the background.
Now the next step to creating a background is creating the image file for MUGEN to use. This is called an SFF file. This contains all of the sprites or images that you are going to be using to create this stage. What you'll need is SPRMAKER.EXE, from the ELECBYTE homepage in the developer section. Have SPRMAKER.EXE in the same directory as MUGEN.EXE.
Now open Microsoft Notepad from your Accessories folder. What we are going to do next is create a text file for SPRMAKER, just to make life a little easier.
The first thing to do is in the text file, on the first line, write:
stages\backgroundname.sff
Where 'backgroundname' is the name of your background, and it should be no more than 8 characters. This is going to tell SPRMAKER what the name of the file is going to be. Next you will be writing down the path of your PCX files and their image groups. It should look like this: work\stages\backgroundname\image.pcx
0
0
0
0

The first line:
work\stages\backgroundname\image.pcx
This is the path of your image.
0
This is the 'group number' of the image. Used to help sort each part of the background. For example this number would be different when you want to keep all of the background images in one 'group', and all of the foreground images in one 'group', and all of the images of a background animation in one 'group'.
0
This is the 'image number' of the group. You are to assign each image a different number. If two images are assigned the same 'group' and 'image' number, the first image will be overwritten.
0
0
These are the X and Y values of the image. For all intents and purposes these can remain at 0 and 0.
So when you're finished your text file should look something like this:
stages\backgroundname.sff work\stages\backgroundname\image1.pcx
0
0
0
0
work\stages\backgroundname\image2.pcx
0
1
0
0
work\stages\backgroundname\image3.pcx
0
2
0
0
; end of file

As you notice there are no spaces in this demonstration. This is very important because as soon as SPRMAKER sees a space, it will assume that this text file is over and will quit.
When you are finished and have all of the images included that you will need for the background... save it as backgroundname.txt. Then go into your MS-DOS prompt by either clicking the 'MS-DOS' icon on your start menu or click 'Run', from the start menu, then write 'command.com' and run it. Then navigate into your MUGEN directory ('cd..' to go up a directory, 'cd foldername' to go into that directory, 'dir' to see a list of the folders.), then choose this command line:
sprmaker.exe < backgroundname.txt.
After you close your MS-DOS prompt you are ready for the next step.

PART 4
CREATING THE DEFINITION FILE

Overview: Creating a .DEF file for the background.
OK now this may be (for some) the most difficult portion of creating a background, because it includes a lot of trail-and-error. But keep at it, you'll get it eventually. Also a good template is Kung Fu Man's background DEF file. But we will go through each part of the DEF file just for good measure. Also just a quick note, if you need a remark or a statement in the DEF file that isn't recognized by MUGEN, such as a reminder note, just use a ';' and anything after the comma on that line will be disregarded. OK, let's begin.
Start off the DEF file with:

[Info]
name = "backgroundname"
This will display the name of the stage in MUGEN. Make sure that the name is enclosed in double quotes.

[Camera]
startx = 0
starty = 0
These are the starting coordinates for the stage, normally you would keep it at 0 and 0.

boundleft = -150
boundright = 150
This is the length of the stage to the left and the right. For a longer stage, these values would be a lot larger, for a smaller stage, these values would be smaller. This is where trial-and-error come into play. But to get a general idea where these numbers will be, open your floor image and find the center of the image. There should be a number coordinate of the center displayed somewhere in your program. When get the X coordinate of the center, subtract that by 160, and that should be around the number that you are looking for.

boundhigh = -20
boundlow = 0
These are the height of the stage. With boundhigh, the bigger the number the farther the camera will follow the character. And this is ALWAYS at a negative number. boundhigh is also going to be the starting Y coordinate of your farthest background. And boundlow will always stay at 0.

verticalfollow = .2
This is how much the camera will move vertically towards the highest player. Valid values are from 0 to 1. A value of 0 will mean the camera does not move up at all. A value of 1 will makes the camera follow the highest player. Typically .2 for normal-sized backgrounds. You may need to enlarge this value up for taller backgrounds.

tension = 50
This is the distance player is from edge of the screen before camera starts to move. Typically this will stay at 50.

[PlayerInfo]
p1startx = -70
p1starty = 0
p1startz = 0
p1facing = 1
p2startx = 70
p2starty = 0
p2startz = 0
p2facing = -1
p1startx is typically -70 and p2startx is 70. These are the staring position of Player 1. p1startx is typically -70 and p2startx is 70, p1starty and p1startz should be 0. p1facing and p2facing is the direction the player faces, 1 is towards the right and -1 is towards the left.

leftbound = -1000
rightbound = 1000
topbound = 0
botbound = 0

[Scaling]
topz = 0
botz = 50
topscale = 1
botscale = 1.2

[Bound]
screenleft = 15
screenright = 15
You don't need to change these values.

[StageInfo]
zoffset = 200
The Zoffset is the line where the ground is. A larger number places the ground closer to the bottom of the screen, a higher number place the ground closer the top of the screen. This could be any number from 0 to 240, although from 200 - 240 is recommended.

autoturn = 1
A value of 1 makes the players automatically face each other. A value of 0 allows the player to face any direction. Normally you would want this at 1.

resetBG = 1
A value of 1 will have the background reset to it's starting animation between rounds. A value of 0 will have the animation continue between rounds.

[Shadow]
color = 32,32,32
This is the shadow color given in Red,Green,Blue. Valid values for each range from 0 (lightest) to 255 (darkest). The default color is 92,92,92 if omitted.

yscale = -.1
This is the scale factor of the shadow. Use a big scale factor to make the shadow longer. You can use a NEGATIVE scale factor to make the shadow fall INTO the screen. Defaults to 0.4 if omitted.

reflect = 0
A value of 0 will draw a shadow. A value of 1 will draw a reflection instead of a shadow.

[Music]
bgmusic =
You can play MP3, MOD, or MIDI here for the background, or just place a comma in front of it if you don't want music. If an invalid filename is given, then no music will play.

bgvolume = 0 This adjusts the volume for MP3s or MODs only. 0 is normal, use a negative number for a softer volume, and use a positive for louder volume.

[BGdef]
spr = stages\backgroundname.sff
This is the location of the SFF file of your background that you created before in step 3. This loads the images that you will be using in the main background definition.

debugbg = 0
Set this value to 1 if you want to clear the screen to magenta before drawing the default background. This is a great way for spotting "holes" or gaps in your background.

So far your DEF file should look something like this:

[Info]
name = backgroundname

[Camera]
startx = 0
starty = 0
boundleft = -150
boundright = 150
boundhigh = -20
boundlow = 0
verticalfollow = .2
tension = 50

[PlayerInfo]
p1startx = -70
p1starty = 0
p1startz = 0
p1facing = 1
p2startx = 70
p2starty = 0
p2startz = 0
p2facing = -1
leftbound = -1000
rightbound = 1000
topbound = 0
botbound = 0

[Scaling]
topz = 0
botz = 50
topscale = 1
botscale = 1.2

[Bound]
screenleft = 15
screenright = 15

[StageInfo]
zoffset = 200
autoturn = 1
resetBG = 1

[Shadow]
color = 92,92,92
yscale = 0.4
reflect = 0

[Music]
bgmusic = sound\backgroundmusic.mid (.mp3 or .mod)
bgvolume = 0

[BGdef]
spr = stages\backgroundname.sff
debugbg = 1

And after you're finished, you're ready to move on to the next step.

PART 5
MAIN BACKGROUND DEFINITION

Overview: A library of the sprite data and how to implement it.
This is the part of the DEF file where the each background element is defined. Each element has it's own image, velocity, starting positions, etc... etc... etc... Every element must start off with, [BG x] Where 'x' is a number or word or your choice, which is only for your records to keep track of, incase there is an error in that element, MUGEN would let you know. And element consists of parameters, which I will go over in detail.

type = parameter
This parameter defines what kind of image will this element be. There are 3 different types:
normal - This is just a flat normal image.
parallax - This gives the image a 3D look by scrolling the image. Sort of like the floors in Street Fighter 2.
anim - This declares the image to be an animation.

spriteno = group no, image no
This assigns the element an image. The Vaginatax is, spriteno = group number, index number. Make sure you remember what group and index numbers you assigned each image in your SPRMAKER text file.

start = x, y
This is the starting position of the image based on the top right of the image. x is relative to the center of the stage, which would be directly in between the starting position of the characters. If you want the image to start at the leftmost portion of your stage, it must be a negative number. Or if you want the image to start to the right of the characters you must us a positive number. y is relative to the top of the screen when you start the stage. This number should be around (if not the same) number as 'boundhigh', to be sure that when a character jumps there will still be a background. So you may need to move around these numbers until you get it just right. Also this must be an integer, no decimal places.

delta x, y
The delta is how fast the background element moves, when the camera pans. This number could be a float, or can have a decimal. A value of 1, moves the background exactly 1 pixel for every 1 camera unit moved. (So if the camera moves over 1 unit the background moves over 1 pixel, get it!?) If the value is bigger than 1, the background will scroll faster, or if the value is smaller than one, the background will scroll slower. Again you must change these values until you get your desired feel for the scrolling.

trans = parameter
This is to change the transparency of the image if desired. There are 4 types of parameters, they are:
none - Does not make any kind of transparency, this is the default if 'trans' is omitted.
add - Makes the image brighter.
add1 - I suppose it makes the image brighter than 'add' but I cannot tell the difference.
sub - Makes the image darker.

mask = flag
This flag can hide the color '0' of your palette, so that you can see through the color '0'. This is why we prepped the images in step 2. For the flag, '0' turns masking off, meaning the background will look exactly like it is, this is the default if 'mask' is omitted. A '1' will turn masking on and will not draw the color '0'. This is good when you want to have multiple backgrounds.

layerno = parameter
This will determine whether the image is drawn in front of the character or in back of the character. If you the image drawn in back of the character, (which you normally do, this being a 'background' and all) use a '0', also this is the default if 'layerno' is omitted. If you want the image drawn in front of the character, you must use a '1'.

velocity = x, y
This is the speed the background moves at. The value you use is how many pixels the image moves at per game tick. This number can be a float, or can have a decimal. The default number is '0' if 'velocity' is omitted.

tile = x, y
This will continuously place the image right next to the image, therefore 'tile'ing the image. If you want to tile the image from left to right infinitely, at the x parameter use '1'. Or if you want to tile the image up and down infinitely, at the y parameter use '1'. Or if you only want to image to be tiled a certain number of times, instead of '1', just place that certain number in the parameter instead. The default is '0' if 'tile' or one of the parameters is omitted.

tilespacing = parameter
This parameter is an integer number, meaning no decimals, of how many pixels to draw between tiles. If omitted than the image tiles 'back to back'.

sin.x = length,time
This option makes the image circle back and forth on the x axis continuously, or left to right. length is the number of pixels of the radius, and time is the game ticks that it takes to complete one rotation.

sin.y = length,time
This option makes the image circle back and forth on the y axis continuously, or up and down. length is the number of pixels of the radius, and time is the game ticks that it takes to complete one rotation.

So an example of a background element would look like this:
[BG TheFloor]
type = normal
spriteno = 1,0
start = -150, 180
delta = .8, .75
mask = 1
As you see you only define what you have to. You only implement what you need to be changed from the default. Just keep in mind, for every image set that you have, you have to create a background element. And if there is an element above this one... that sprite will be drawn behind this image. And if there is an element below this one... that sprite will be drawn in front of this image. See how that works!?

After you have fiddled and toyed and have been the anal retentive perfectionist you know you are, to make sure these backgrounds look initially how you like it, you're ready to move on to more advanced background definitions.

Super Mario Galaxy Coming Soon!

2007-10-25T15:14:00.000-04:00

Via 1up:

This week, a verdict was delivered for Super Mario Galaxy in the latest issue of Famitsu, as the game scored 38/40.

Famitsu editors are touting SMG as the game anyone can play.
"The game takes place in a 3D space where you could be walking on the ground or upside down. Normally that would look like it is difficult to control, but you can play this instinctively. The balance is just perfect and it is a game anyone can really play."

"Gimmicks and actions using the game's unique gravity, and fun boss fights definitely delivers on the Mario name. It is even just fun to watch if you are not playing."

"The game's pacing is very good, you get hooked more and more. I am glad that the game is not too easy or too difficult. Collecting the star piece by pointing the Wiimote is already fun in itself."

"The excitement of Mario 64 is back! Lots of features that are perfect for the Wii, and you get addicted wanting to know what kind of obstacles await you in the next stage. Difficulty gradually increases and the map layout is great. Every game fan should play this game."

Be sure to mark your calendar; Super Mario Galaxy hits North America on November 12. Importers can check out the game 11 days earlier, as Japan receives the game on November 1.

MBN Main Page Updated

2007-10-25T13:46:00.000-04:00

I've added a new main site, and I'm now able to host for anyone who needs it. Lots of new stuff is in the works, thanks for visiting! Also, if you want to be affiliates, shoot me an email at mugenbattlenetwork@gmail.com and it'll be added by the end of the day.

Mugen Battle Network Main Site

MBN Forums are open

2007-10-24T10:26:00.001-04:00

Just as a reminder, I started a Mugen forum a few days ago, if you wanna join, click this link.

Street Fighter IV, Bionic Commando Announced!

2007-10-17T12:50:00.000-04:00

After nearly 10 years since they last hit the arcades, Capcom says its time for a new Street Fighter (and not SF2THD, which should be hitting the PSN & Xbox Live later this year)! Street Fighter IV is currently in development, and may even reach arcades by late 2008/early 2009. The first two Street Fighter III games were ported to the Sega Dreamcast as a compilation titled Double Impact. Ports of 3rd Strike were released for the Dreamcast, PlayStation 2 and Xbox.

Bionic Commando returns after 2 decades!
Though it's been nearly 20 years since the release of the original game, Capcom has revealed that a new Bionic Commando is in the works, more on this soon!

ShugenDo Beta 2.5

2007-10-15T14:34:00.000-04:00

Here's the changelog:

Changes are:

- Increased Compatibilty for mugen chars
- Initial support for Life and Power bars ( take a look at the fight_screen.xml, in the screen pack/default folder)
- Arcade mode is now playable as player1
- Vs Mode is now playable
- A stage converter is available to convert your mugen stages to ShugenDo
- Command detection code is more accurate now
- Keymap is configureable via config.xml file in the data folder( User-interface will be in Beta 3 )
- Player Shadows are visible

You can get it here. Don't forget to leave feedback and sign the petition for OpenGl support under PS3 Linux.

40GB PS3 €399, U.S, Japan Getting Same Deal Soon?

2007-10-05T17:04:00.000-04:00

Via Joystiq & PS3Fanboy:
In separate interviews today both Sony UK boss Ray Maguire and Sony Europe spokesman Nick Sharples spoke about how the 40GB PS3 lacking backwards compatibility is fine. How is it fine? Maguire tells Eurogamer that by this Christmas the PS3 will have a whopping 65 games and so they feel "there's sufficient choice in the marketplace and that we're still better off using that money that we'd put into backwards compatibility in either investing in new games or using that money to help support bringing the price down." Meanwhile, Sharples tells GameDaily, "We have made clear on many occasions that our priority is on developing innovative new features and services for PS3 and not on backwards compatibility."

We're not sure how Maguire came to this conclusion, but the PS3's backwards compatibility feature is always one that we've appreciated for a long time. With Sony's commitment to a 10-year life span of its hardware and games still being published for last generation's console, it seems like an odd choice to "cut the cord" at this point.

This from a company who introduced backwards compatibility to the masses...

EDIT:The Hollywood Reporter notes that the new PS3 model will have fewer features than the current model, with only two USB ports instead of four, and eliminating the backwards compatibility with the PS2 and PS One. Sony Japan has made the announcement that they are going to cut the price of the 60GB PS3 and also release a 40GB PlayStation 3 on November 11th in ceramic white!
The new model will retail for USD $399.99. The existing PS3 Starter Pack will be replaced by a 60GB value pack at a price of £349. Additionally, a new 40GB entry level PS3 model will be introduced at £299. Japan will also receive the 40GB version on November 11, 2007. The recommended retail price is 39,980 yen (including tax).

Last week, rumours surfaced about the new 40GB SKU, with documents from US retailer Best Buy apparently confirming the USD $399.99 price and early November release date. SCEA has yet to officially confirm the release of the new console. The new 40GB PS3 will be packaged with a matching white DualShock 3 controller as well instead of the old SIXAXIS meaning that the 40GB PS3 will be rumble-enabled out of the box.

The DualShock 3 will not hit Europe or North America until Spring 2008. North America is now awaiting an announcement as many expect Spider-Man 3 to be packed in on Blu-ray with the release of the 40GB PS3 in that part of the world. Sony Japan is giving away 200,000 copies of Spider-Man 3 on Blu-ray to new 40GB PS3 owners.

Xmugen 4.9 by r1sky

2007-10-03T09:51:00.000-04:00

There are 2 versions - e drive and f drive. i doubt i have to explain what the differences are. anyways...

they go into X:/Games/
1 gb swap file
has mfj screenpack set to doubleres4
speed tweaks
dvd loading merged (just find a tutorial/whatever to create the dvd)

For E drive

For F drive

pretty much, the whole thing is setup to work 100%. its already had lots of testing from new ppl and works great for them. this thing is all drag and drop. just upload the xmugen folder to your 'Games' folder and your good to go. just upload your characters and add them to the select.def.

i might release a screenpack addon but who knows. so here is a dvd creator addon. its my same setup from before. but you can extract this file anywhere on your hdd and copy over your xmugen setup and make a working dvd. once again, all drag and drop. just follow the readme included.

DVD Add-on

SNK Announces Two New Fighters, Overdue U.S. Release

2007-09-29T12:58:00.000-04:00

via IGN:
SNK Playmore announced it has two new titles on the way for the PlayStation 2: The King of Fighters XI and NeoGeo Battle Coliseum.

The King of Fighters XI, the latest in the long-running fighting franchise, adds Quick Shift and Saving Shift options for more control when switching out characters. A Judgement Indicator avoids draws by measuring player aggression, the number of combos racked up, and special moves performed.

NeoGeo Battle Coliseum is a two vs. two tag-team fighting game featuring characters from SNK's roster of games such as Metal Slug, World Heroes, Art of Fighting, Fatal Fury, Samurai Showdown, and Last Blade. Set in the year 2017, players will be able to switch characters during matches and team up for special attacks.

Both King of Fighters XI and NeoGeo Battle Coliseum will arrive this fall. Please note that these games have been available in Japan for a while now, and are only now being released to the U.S.

Microsoft extends sales of Windows XP till June 2008

2007-09-28T23:19:00.000-04:00

via Engadget:

Just a week ago, reports were cropping up regarding Microsoft's decision to give Vista Business / Ultimate customers a "downgrade to XP" option amidst complaints over its latest operating system. Now, the Redmond powerhouse has decided to "keep selling Windows XP until the end of June 2008, delaying a scheduled transition to its newer Windows Vista software by five months."

Originally, the planned phase out date for XP was January 30th of next year, but now the firm has decided to "extend XP sales in response to feedback from computer manufacturers who said there were customers who still wanted to buy the older operating system."

Of note, Mike Nash, a Microsoft corporate vice president, was quoted as saying that the company was "a little ambitious to think that it would need to make Windows XP available for only a year after the release of Windows Vista," referring to the fact that it typically makes its older OS available for two years after the launch of a new one.

Stage Template by Eternaga

2007-09-27T10:46:00.000-04:00

Eternaga's stage template [be sure to credit!]

Marvel vs. Capcom for digital download?

2007-09-26T17:00:00.000-04:00

In an interview with Gamasutra, Marvel's VP of interactive media Justin Lambros says he hopes to see Marvel vs. Capcom make its way to digital download, saying, "I'm a huge 2D fighting fan ... the Marvel vs. Capcom stuff has a definite close place in my heart, so we definitely wanna see that stuff live on." He says that there are no deals in place, but they may be considering it. If it's anything like Super Street Fighter II Turbo HD Remix, I'm all for it!

Hopefully if it is eventually available for download, we might get these added features like online multiplayer like the Japanese DC version, new/remixed soundtrack and maybe even a few of the secret characters/bosses from the other games (like Evil Ryu, Cyber Akuma, Shadow Lady & Norimaro), add downloadable versions for ALL next gen consoles & it'd be perfect... Capcom are you listening???

Halo 3 In Stores Now!

2007-09-25T13:12:00.000-04:00

Halo 3 is now on sale... GameSpot reported that 4.2 million units of Halo 3 were in retail outlets on September 24, 2007, a day before official release, a world record volume release.

The game features new vehicles, weapons, and gameplay features not present in the previous titles of the series. Halo 3 focuses on the interstellar war between 26th century humanity and a collection of alien races known as the Covenant, who after a decades-long war have begun the invasion of Earth. The player assumes the role of the Master Chief, a genetically enchanced cyborg supersoldier, as he wages war in defense of humanity.

Don't forget there's a $59.99 "Regular Edition", a $69.99 "Limited Edition" and a $129.99 "Legendary Edition" complete with a replica helmet worn by Master Chief (which apparently had some design flaws). Microsoft has stepped up and admitted fault on this issue on their website today. They are offering to replace the faulty disks for free, if you sign up for their disk replacement program.

A new $399.99 Special Edition Xbox 360 with a "Halo"-themed custom paint job — Halo 3 not included. Expect productivity for the next few weeks to drop (just kidding).

Game News

2007-09-24T14:40:00.000-04:00

Crysis Demo Delayed:

The single-player demo for Crysis, the upcoming first-person shooter from Crytek, has been delayed until October 26th. The game is set for release November 16th.

Additionally, Crytek has announced that the originally-teased "huge surprise" coming with the demo is the CryEngine 2 - Sandbox 2 game editor, now also due out next month.

New PS3 SKU?

According to Sky News, an electronic manufacturing news source said that Sony will employ the Taiwanese firm FoxConn, which currently produces PlayStation 2s, to manufacturer the 40GB PS3.

The report suggests that an announcement regarding the long rumored 40GB PS3 could be made this week in order to combat Microsoft’s Halo 3 juggernaut, a possibility also touted by industry analyst Michael Pachter earlier this month.

The report also speculates that the console will retail for $399 and will ship without the USB ports or backwards compatibility included in the more expensive 60GB and 80GB models.

Apollo Justice: Ace Attorney Trailer

Bleach: The Blade of Fate screencaps

2007-09-15T01:34:00.000-04:00

For more pics click here.

Capcom: "Three Huge Announcements" On Wednesday

2007-09-14T13:47:00.000-04:00

via Gameplayer:
As many of you know, next week sees the famous Tokyo Game Show take the industry’s centre stage and we can expect another big round of game announcements. Predominantly tiered towards Japanese developers, the 2007 show is set to be the biggest ever with rumours already running rampart across the Net as gamers prepare their saliva ducts for three days of non-stop drooling (and if you’ve seen how the local ladies dress up for the event you’ll know what we mean!). With this in mind we are excited to confirm that legendary industry stalwart Capcom are planning to use the event to make “three huge announcements.”

This information fell into our laps at Activate Asia 2007, which was held in Cairns earlier this week and, amongst many things, included some hands-on time with Devil May Cry 4 (pictured, but more on that later). While we are not at liberty to divulge what these announcements will be at this time, we’re busting at the seams with excitement and wishing we could let the information flood out. But we’re sworn to secrecy, so all we will say is that Capcom have some of the biggest franchises in gaming history tucked away in their stable, and not a few smaller ones that deserve more attention.

So Capcom fans have plenty to anticipate as next Wednesday, the 19th of September, approaches and they should keep their eyes fixated on our news section for that moment when we are given the green light. In the meantime, you should speculate on our forums. Let's see who can make the best guess..

Let the speculation begin!

Rules of the Mugen Community

2007-09-12T16:42:00.000-04:00

All of this post is taken from the Random Select Forum

The MUGEN Community Silent Laws
(taken from BlackJack's post on the subject with edits + new community ammendments)
-v0.2.0 _____________________________________________________________________________________

Disclaimer : This is here to help everyone better understand why some things are the way they are in the MUGEN Community. In no case these so-called laws are meant to rule the whole community, but reflects what the majority is thinking. You are then free not to follow them, but be warned that you'll suffer from the hate of a significant part of said community, and possible expulsion.
_____________________________________________________________________________________

Community Agreement 1 : you will not enforce part of the MUGEN license.

This extract from the license of MUGEN is deemed null and void :

"Agreement to this license grants you the right to use the MUGEN environment (...), until and not beyond 12:01 AM (Greenwich Mean Time) on June 1, 2002. (...) If no new license is offered, all use of the (...) beta must cease."

The reason for this is simple: Elecbyte did so to enforce that users would upgrade to a newer version (which would be released at the time of said expiration date) as a means to update the license. Mugen is henseforth covered under the protections of abandonware.

Despite this expiration, it should be noted that there is not one set on the agreements and guidelines listed here, and they have been set in stone for many years. Failure to comply to any of the agreements will usually result in swift removal from the community.
_____________________________________________________________________________________

Community Agreement 2 : Mugen creations are considered fan art.
It is legal to take material under copyright and include it without permission in MUGEN creations, as long as profit isn't being made.
We call that fan-art : the owner of the original material recognize it as harmless to him, for several reasons.
In the case of sprites/sounds/etc. taken from a game :

*He's not being deprived of something (such as money).
*He has been rewarded for his work by the company that employs him.
*Most of all, his original work is prevented from any modification (for it is under copyright, on cartdridges, CD-ROMs, etc.).
_____________________________________________________________________________________

Community Agreement 3 : you will not take fan-art (nor other derivative work not under copyright) to include it in your MUGEN creation without permission, in the case you're going to publically release it.

If you take sprites or coding you take time and dedication from the MUGEN developer. The MUGEN developers spent much time to rip sprites and learn coding, without being paid. They haven't the same protection as someone that would have his work under copyright. So when some random person edits his character/stage, or takes code/sprites without asking, then distributes it, he doesn't respect the work (which is the rip, the coding, the time spent, etc.) of the original Mugen developer.

To respect the MUGEN developer, ask for permission first, even if you're using a small part of his work save for a small chunk of code (in which case you must credit them for it in a readme or the def file).

You can release updates, patches, palettes, etc. for existing MUGEN creations, as long as you credit the original MUGEN developer, and that nothing from the original MUGEN developer's creation is included in the patch.

Basically, here's the thinking behind those rules :

*Companies ask for money, you pay for their game and you have the right to use it as you see fit for your own personal use.
*Creators only ask for a permission request, a much cheaper method of gaining the right to use their material.

Just remember one thing, when you release something:

*You show respect to the original developer by buying his game.
*You show respect to the MUGEN developer by asking his permission before releasing something where his work is involved.

Under the following circumstances however you are allowed to use or modify parts from another creator's character if:

*The creator and all his or her works have been offline for approximately a year.
*There is no contact to reach or representative for said person to reach regarding hosting of said works, and there is no previous indication of denial to use said parts or modify said character
*Said work is not private and leaked online (thus, no Blaque)
*If the creator returns and demands removal of said work, you comply immediately.
*The work is not a fully edited character (see: Rikard's work, excludes Evil Dan conversely) to the point of originality, or made of original sprites entirely (see: Borghi's work).

While you will not be penalized for using coding from another character like a few blocks of code if they're still about or don't meet the above guidelines (as long as you credit them), do not take sprites from another character as this runs risk of accidentally making use of original or edited sprites in your own work. If you need help with rips or edits, please make use of classified sections on forums to request the parts and/or assistance you need.

Something to note: Some do not respect these rules, and would gladly do their own thing with the work you've done. In doing so, they in turn damage the community.
_____________________________________________________________________________________

Community Agreement 4 : you will not host someone elses creation without their permission

Mugen code is legally copyright of the person who coded it, much like a FAQ is copyright it's original author and should not be rehosted on a site without consent. This overrides the fact that many mugen works utilize copyrighted material by the aforementioned fact that such characters, stages, etc are considered "fan art" and therefore the core of the item for mugen is the key factor here, that being the coding within. In a nutshell, hosting someone else's work on a site or free filesharing service is not only morally wrong, but very much illegal.

In the following circumstances however, you are permitted to host works if the author cannot be reached and the whole of the author's works have been offline for roughly a year:

*The creator and his or her works have been offline for approximately a year.
*There is no contact to reach or representative for said person to reach regarding hosting of said works, and there is no previous indication of denial to rehost it
*Said work is not stolen or private and leaked online (thus, no Blaque)
*If the creator returns and demands removal of said work, you comply immediately.
*Character is the most up to date version

Youtube Stuff

2007-09-09T11:58:00.000-04:00

Just added the Mugen G4 clip, you can check it out on my bare Youtube page.

Hitman - The Movie

2007-09-07T20:09:00.000-04:00

Hitman is a 2007 film adaptation of the video game series Hitman. The film is directed by Xavier Gens and stars Timothy Olyphant. The script is written by Skip Woods. Hitman is scheduled for release on November 21, 2007. Click here for the trailer.

Dreamcast & Mugen [Part 1]

2007-09-06T15:36:00.000-04:00

It looks like the Dreamcast's long, slow demise has taken another turn for the worse, as Sega announced at the beginning of this year that it'll soon stop supporting the console in Japan, with its predecessor, the Saturn, also suffering a similar fate. According to the company, the cut-off date for repairs will be September 28th of this year, after which you'll be left to fend for yourself if your console finally conks out after one too many games of Ikaruga. Given what they're selling for these days, however, simply replacing the console with another, slightly less used one is probably your best bet in any event.

The Sega Dreamcast was the first of the Sixth gen game consoles, and notably, the first with online play. Dreamcast had the GREATEST launch games in the history of consoles (go look at the lineup and compare it to the absolute crap launches of every system since), on 9.9.99. DC games are STILL being made (mostly shooters) in Japan. The last DC GD-ROM game will be made this year, then the GD-ROM factory(ies?) will be shut down for good.

There was a lot for DC to offer, including incredible graphics (use a VGA box, gorgeous 640x480), amazing arcade ports, built-in modem, and a respectable price. The VMU was also a very novel idea.

A lot of people were burned by SegaCD, 32X, and then Saturn (at least in the US, Saturn did great in Japan since so many more games came out there), so DC didn't fare well MOSTLY from that, not necessarily just because of the PS2 coming out.
I still play lots of homebrew/emulators/bootlegs on my Dreamcasts (yes, I own 2). It doesn't even seem like it's been 8 years almost to the day since it launched...

I've been looking around the net for the past couple weeks, after I heard it was possible to play Mugen on the Dreamcast by using Openmugen or Linmugen... as the Dreamcast will soon become abandonware, I'm trying to find more & more ways to get more fun out of my then $50 console...stay tuned.

Open Source: Who Is & Who Isn't

2007-09-05T14:01:00.000-04:00

With what's been going on in the community lately, I thought it wouldn't hurt to repost KFM's list. It is based on the new, modified rules of the community...

Under the following circumstances however you are allowed to use or modify parts from another creator's character if:

* The creator and all his or her works have been offline for approximately a year.
* There is no contact to reach or representative for said person to reach regarding hosting of said works, and there is no previous indication of denial to use said parts or modify said character
* Said work is not private and leaked online (thus, no Blaque)
* If the creator returns and demands removal of said work, you comply immediately.
* The work is not a fully edited character (see: Rikard's work, excludes Evil Dan conversely) to the point of originality, or made of original sprites entirely (see: Borghi's work).
-------------------------------------------------------------------------------------

All characters made by these people are known to be Open Source from info gathered (NOTE: ALWAYS GIVE CREDIT!):
Elecbyte (material packaged by them with mugen EXE only)
Abster
Alchemist (only Sakura and Cammy)
aokmaniac13
Arma X
@ndroide
Aztec Soldier
BBaga
Bia/SMEE/SMI
Cabbit007
Chrono_Strife
Cyanide (unless otherwise specified, notably sprites in Sonic Battle)
Cybaster
DavidGee/Infirmia
Di Gi Jared
DiscoInferno (Green Ranger only)
DG
DJ-Van
Don Drago
[E]dgar/MaximillianJenus
Ermac Won
Felineki (unless otherwise stated)
IronMugen (code only)
Jango
Jo (save for collaborations)
Jin/MugenJin
K.O.D/Ninja_Naruto
KoYoTae/Corntortillas (save for Silver Samurai sprites and sounds)
Laxxe23/Zeckle (only the code)
LegatoB
LimitedMoon
Loona
Majita
MamboJambo (sprites only)
Messatsu
MostMysterious
Mouser
NeoCide (Majita only)
NeoKamek/Kamek (unless otherwise stated)
Nobun
obreck2
O Ilusionista
OnslaughtX
OrochiWeapon2000 (code only, must ask regarding sprites)
P.o.t.S. (except for CvS2 FX)
RRRRRRRR
Reu (code only)
Renzo
ROQUE
Sepp
TestP
TheNone (unless otherwise stated)
TigerMask
Thomas Hsieh
Useless Chicken (only his Akuma)
VinceJ
Vyn (code only)
Warner
Warusaki3 (Note: must ask permission for CvS chars, as works include content from H")
Zeldagis296 (must include readme)

All characters made by these people are Open Sourced due to rules:
Matheus

Hosting Only Under RS's Guidelines (works are original or full edits):
E.R.
Taruse

All characters made by these people are Closed Sourced (You *CANNOT* edit and distribute these works):
ahrimanes
BadDarkness
Borghi
Byakko
Chottomaru
cmh777
Deuce
Fervicante
FlowaGirl/TheNecromancer
Fou-Lu
FreezeMan
H"
Helios
Hoshi
intense mc
Jesuszilla
JinKazama
Kamekaze
Kung Fu Man
Loganir
Lost Soldier
M@ppy
Mature4Evr
McCready
MGBenz
Moldredd
Mr. Fong
N64Mario
NeoAnkh
NeoCide
NeoGouki
Neon Tiger
Orochi Herman
OrochiKOF97
Pneophen
Rikard
Roken
Rolento
ShinRyoga
Splode
Sunboy
Supermystery (unless otherwise stated)
Third
TMasta
Vans
VisualKreations
XCalibreBlade (XCB)
XGargoyle
ZSabreUser

of course, when the lists are updated, it will be reflected in this post.

1st Look - EA's New Marvel Fighting Game

2007-09-02T10:10:00.000-04:00

Looks pretty good... hopefully the background characters won't keep running into each other when it's released sometime next year. Demo footage shown was run on the Xbox 360.

PSP Palette Tutorial by SLotman

2007-09-02T00:30:00.000-04:00

This tutorial is using Paint Shop Pro 7 as a guideline. Newer/older versions may differ a little.

It's a pretty simple and easy process, let's start opening an image:

STEP 1 - Making the Palette

If the image does not have a palette yet, we continue, if it has, you can skip to the next step.

Click on Colors->Decrease Color Depth->256 colors.

This dialog will show, with different options. Set as above (you can experiment with the others later) to optimized octree / Nearest color and click OK.

Congratulations, you just made your palette!

STEP 2 - Changing the Palette

Click on Colors->Edit Palette to show the palette window.

Now, with the window open, move your mouse over the color you want to change and click on it. The color will be selected on the window. You can also direct choose any color on the window palette by clicking on them

Now, double click the color you chose, and a standard "color picker" window will open.

On the color picker, just click the color you want to replace the old one, and click OK.

You see that the image already changed. Change as many colors as you want (you can select another one, double click it, etc), and then click on OK to finish and apply the changes.

You're done! Just remember to save the image in a format that supports palettes, like PCX (best for MUGEN), BMP, GIF (good for animations) or PNG (best to post static images online).

Also keep in mind that the color 0 (the top-left square) will be the transparent color in MUGEN - so nothing on that color will appear on screen.

Homing Projectiles by Flowagirl

2007-09-01T00:26:00.000-04:00

===================
Homing Projectiles
===================
Author: FlowaGirl
flowergirl@cutey.com
http://blargh.i-xcell.com

---------------------------------------------------------------------------
This creates a projectile that follows the opponent where ever they go.
---------------------------------------------------------------------------

To accomplish this, a Helper must be used. If you wish to add
any Projectile Effects, simply add them to this state.

[Statedef ****]
type = A
movetype = A
physics = N
anim = ****

This is needed, so that the projectile cannot be hit, and turn into a
copy of the main character. This is what I use, but alternatively, you
can put in a HitOverride, or just forget about the Clsn2 boxes. =)

[State ****: NotHitBy]
type = NotHitBy
trigger1 = 1
value = SCA

These next pieces are needed to follow the opponent, and to turn if the
opponent somehow gets behind it. The turning is not required, but it depends
on the type of anim you are using for the projectile.

All the VelSet and VelAdd values should can be changed accordingly.

The triggers "Vel X > -6", "Vel Y <> -6" are used to limit the speed of the projectile.

[State ****: Turn]
type = Turn
trigger1 = (P2Dist X < type =" VelSet" trigger1 =" (!Time)" x =" 3" type =" VelAdd" trigger1 =" (P2Dist"> -6)
x = -0.2

[State ****: VelAdd]
type = VelAdd
trigger1 = (P2Dist X > 0) && (Vel X < x =" 0.2" type =" VelAdd" trigger1 =" (EnemyNear,"> Pos Y) && (Vel Y < y =" 0.2" type =" VelAdd" trigger1 =" (EnemyNear,"> -6)
y = -0.2

Of course, a HitDef controller is needed. Everything here is up to you, but the "attr" parameter must
be set to a projectile type. Eg "S, SP"

[State ****: HitDef]
type = HitDef
trigger1 = 1
attr = S, SP
[etc...]

This last piece is used to destroy the Helper when it makes contact with the opponent, or when it has
floating around for a period of time, to reduce cheapness.

Alternatively you can put the Projectile into another state, if you want something else to occur before
it is removed.

[State ****: DestroySelf]
type = DestroySelf
trigger1 = (MoveContact) || (Time > 200)
ignorehitpause = 1

Normalize Music in M.U.G.E.N with Audacity (MP3, WAV & Ogg) by DarkValentine

2007-08-31T21:30:00.000-04:00

1] Download Audacity, install and run

2] The main screen for Audacity should look like this:

3] Load your music, or do a Drag n Drop of the music, into the window that will appear before you. Once you have done so, Press Ctrl+A to make it select the entire length of the track, and then click on Effect. as shown below.

4] Once you click on Effect, select the "normalize" option, and then simply press OK on the next small window that appears. No need to adjust it, unless you want to.

then:

5] When it is finished Normalizing the track, for clarity in your audio track to use in mugen, click on File and then select either one of the following in the picture, corresponding to what you wanted to normalize. it is self explanatory.

It should eliminate the humming noise, or other extra noises that are associated with audio tracks that are not at the proper volume levels. Providing clarity, without hassle. Based on some of the stuff i've seen and heard, some tracks could use this.

The time it takes to do all of the above, should be no more than 5 minutes or less.

Adding slow, continuous regeneration by Ragnarok, Serj Tankian & shinra358

2007-08-31T15:39:00.000-04:00

Here is a little code for the .cns file, to add a continuous regeneration to a character (such as Wolverine or the Hulk, etc.)

[Statedef -2]
type = U
movetype = U
physics = U

[State -2, regen]
type = LifeAdd
trigger1 = animelem = X
trigger1 = Life > 0
value = Y

Replace X with a frame number(something low so that all states have it; don't give it something like 32 as not all animations have 32 frames, obviously)

Replace Y with how much health you want it to regenerate each time the animelem hits X.

Also, if you want to make it so it doesn't regenerate while in a certain state, you can set another trigger1 to:

trigger1 = stateno != Z

where Z= the number of the state you want to not regenerate during(such as while lying on the ground or a state that may only have 2 frames or something).

Pretty simple but useful. Some people find regeneration like this kind of cheap, so I usually give the player who has it a good deal less health than other characters(a lot of characters have 1000 health; I give regenerating characters about 750)

;============================
; WOLVERINE X'S BASIC CODING
;============================

[Data]
life = 1000 ;Amount of life to start with
attack = 100 ;100% attack power (more is stronger)
defence = 100 ;100% defensive power (more is stronger)
fall.defence_up = 90 ;Def goes up by 50% everytime player is hit on ground
liedown.time = 20 ;Time player takes before getting up from HIT_LIEDOWN
airjuggle = 15 ;Can do 15 points of juggling
sparkno = 0 ;Default spark number
guard.sparkno = 0 ;Default guard spark number
volume = 100
IntPersistIndex=1
FloatPersistIndex=0
KO.echo = 0 ;1 to enable echo on KO
power = 3000

[Size]
xscale = 1 ;.98 ;Horizontal scaling factor.
yscale = 1 ;.98 ;Vertical scaling factor.
ground.back = 26 ;Player width (back, ground)
ground.front = 31 ;Player width (front, ground)
air.back = 22 ;Player width (back, air)
air.front = 25 ;Player width (front, air)
z.width = 3 ;Player width (into and out)
attack.width = 0 ;Default attack width: back, front
attack.dist = 160 ;Default attack distance
proj.attack.dist = 90 ;Default attack distance for projectiles
head.pos = 20, -75 ;Approximate position of head
mid.pos = 1, -48 ;Approximate position of midsection

[Velocity]
walk.fwd = 3.0625 ;Walk forward
walk.back = -3.0625 ;Walk backward
run.fwd = 10.1667 ;Run forward (x, y) - if y<0, player will hop
run.back = -9.5,0 ;Run backward (x, y) - if y=0, player will run
jump.neu = 0,-9.05 ;Neutral jumping velocity (x, y)
jump.back = -3.01, -9.05 ;Jump back Speed (x, y)
jump.fwd = 3.01,-9.05 ;Jump forward Speed (x, y)
runjump.fwd = 4.1,-9.7
airjump.neu = 0,-9.7
airjump.back = -2.55,-9.7 ;Air jump speeds (opt)
airjump.fwd = 2.5,-9.7

[Movement]
airjump.num = 0 ;Number of air jumps allowed (opt)
airjump.height = 35 ;Minimum distance from ground before you can air jump (opt)
yaccel = .46 ;Vertical acceleration
stand.friction = .83 ;Friction coefficient when standing
crouch.friction = .82 ;Friction coefficient when crouching

;====================================
;INITIALIZE
[Statedef 5900]
type = S

[State 5900, 1] ;Clear all int variables
type = VarRangeSet
trigger1 = !RoundsExisted
value = 0

[State 5900, 2] ;Clear all float variables
type = VarRangeSet
trigger1 = !RoundsExisted
fvalue = 0

[State 5900, speed]
type = Varset
trigger1 = time = 0
var(19) = 0

[State 5900, 3] ;Intro
type = ChangeState
trigger1 = roundno = 1
value = 188 ;190

[State 5900, Turns Mode Intro]
type = ChangeState
trigger1 = teammode = turns
trigger1 = roundno > 1
trigger1 = roundsexisted <= 0
trigger1 = roundstate = 0
trigger1 = prevstateno != 197
value = 188

[Statedef -2]
type = U
movetype = U
physics = U

[State -2, regen]
type = LifeAdd
trigger1 = animelem = 2
trigger1 = Life > 0
value = 5

Just open the .CNS file in Notepad and add the text that I put in yellow like in the example above.

To add it so it shows in the lifebars:

;put under statedef 0 of common1.cns or char common or both
[State 0]; power regen; state description
type = poweradd; the option to direct this coding to the power meter
trigger1 = StateNo = 0; this particular state is usually just the standing still state
trigger1 = Roundstate = 2; this means while actually fighting
value = 2; amount to recharge per tick
persistent = 10 ; (change this to however many ticks need to pass for each poweradd)

Slow Motion by FlowaGirl

2007-08-30T14:31:00.000-04:00

============
Slow Motion
============
Author: FlowaGirl
flowergirl@cutey.com
http://blargh.i-xcell.com

---------------------------------------------------------------------------
In some fighting games, slow motion effects are used, like in SF2, when a
projectile hits the opponent. The effect itself can be easily accomplished.
Triggering it can vary, but I'll leave that to you.
---------------------------------------------------------------------------

In the state that you want to create the effect, add this one piece in: The
trigger used should last for a number of ticks, such as "Time = [0,20]"

[State ****: Pause]
type = Pause
triggerall = (GameTime%3) = 0
trigger1 = [Insert trigger here.]
time = 1
movetime = 1
ignorehitpause = 1

If you want to increase the intensity of the effect, you can change the value of
the "GameTime" trigger to 2 or 1. If that's not slow enough, you can increase the
value of the "time" and "movetime" parameters until it suits your needs.

Sprite alignment tutorial by taizongames

2007-08-27T13:38:00.000-04:00

click to enlarge

Sony still strongly supporting the PS2

2007-08-26T21:08:00.000-04:00

via PSPSPS

Although most of this week’s convention was geared towards what’s next in the next-gen war, Sony took a sidestep to let the industry know that it plans to continue to support its seven year old PS2 for a while to come yet.

Over 100m PS2s have been sold since launch back in 2002, and now that its price is so damn low, consumers don’t even blink about buying one, and it also means that emerging markets are just getting used to the console and aren’t even thinking of the PS3.

With this in mind Sony plans to continue backing the console for a few years yet. "We are committing funds for PS2 ... we encourage third parties to continue development for PS2. If they bring a PS3 version out, they can bring a PS2 version out as well," David Reeves, head of Sony's European games unit said.

Reeves expects PS2 game development to continue for three to four years; for those people who aren’t ready to move onto the PS3 just yet, and publishers also think this is a wise move, as these consoles get passed onto friends and family as people upgrade etc.

"Machines in the market may be handed on - not to the younger brother, but maybe to the older sister to play a party game," said Gerhard Florin, general manager of international publishing at EA.

Indeed, he believes that these party games are the kind of thing that will breathe life into the machine for a few years yet.

"'Rock Band' or 'Smarty Pants' are not necessarily driven by processor power," he said.

Cartoons & Sound Rips

2007-08-25T12:44:00.000-04:00

I used to do sound ripping from a bunch of classic comic cartoons like Spider-Man, The X-Men, The Incredible Hulk & more until my external drive crashed a couple months ago. Luckily I still have my cartoons safe in another part of my PC so I'd just need to start over...

Marvel vs Capcom 3?

2007-08-22T05:04:00.000-04:00

This was on the old Infinity Mugen forum... I sent somebody some archive links (I think they were from Flickr) relating to them but they've been speculated to be photoshopped. I first noticed this from the MvC3 Mugenesis Project thread a while back. Wonder if they're still working on that project? Anyway, it would be cool if somebody made it, if I knew anything about making screenpacks I'd make a 900 character version... it looks pretty authentic though, I'd like to see some lifebars like that for Mugen!

Anyone Still Play The Dreamcast?

2007-08-21T17:00:00.000-04:00

I think I'm gonna dust mine off and get back to Unreal Tournament, Soul Calibur & MVC1... I also found out games are still being developed for the Dreamcast! Here's the link...

All in all, the Sega Dreamcast is still one of the most beloved pieces of abandonware ever created. Peeps have gotten Linux to run, made it a server/router, we can emulate our favorite classic games of yesteryear, and don't get me started on all the mods out there, including the portable version made from scratch!

The guy who made this, Dave, created this beauty, which features a custom designed case, 5" LCD display, and a built-in 16MB memory card. It's powered by 2 rechargeable batteries for up to 1.5 hours of playtime.

Anybody else still play this great console?

Mugen on a Game Console?

2007-08-18T20:31:00.000-04:00

XMugen - A mini linux distro reduced to it's minimum in order to launch Mugen on a modded Xbox. XMugen as it is commonly referred to is a port of LinMugen to Xbox by Alg5. LinMugen is Linux Mugen as WinMugen is the Windows mugen. Alg5 compiled a bare bones linux kernel based on XDSL. Since it is based off of LinMugen, there are some compatibility issues with WinMugen and DosMugen files running in it. So depending on your luck, you may or may not have to do a lot of configuring to get your characters/stages/screenpacks running. As XMugen is such a picky program, if there are any misconfigurations in the character select screens, character files, or stage files, it will either freeze at the versus screen (usually a memory issue but not always) or it might error out to the linux kernel that is running in the background. As with WinMugen, there is no online play.

PSP InfinityCat Mugen - The PSP port of InfinityCat allows you to play online across ports (Win32 <-> PSP)

If there are anymore ports of Mugen on the console I'll be sure to add them here.

Bases For Martial Artists?

2007-08-18T16:18:00.000-04:00

In addition to my Starman character, I'm working on a martial artist character who has the skills to take down the Batman... some peeps may already know who I'm talking about, but I just wanted to get this right - Who(m) in Mugen is a good martial artist and would work for a base? Or even who are the best Mugen martial artists?

Of course, I'm talking about the Karate Kid, from the Legion of Super-Heroes.

Karate Kid (Val Armorr) is a fictional character, a superhero in the future of the DC Comics universe, and a member of the Legion of Super-Heroes. He is a master of every form of martial arts to have been developed by the 30th century. The extent of his skill is so great that he can severely damage various types of hard material with a single blow and was briefly able to hold his own against Superboy through use of what he called "Super Karate".

Val Armorr was the son of Japan's greatest crimelord, Kirau Nezumi, also known as Black Dragon. When he was born, his mother, the American secret agent Valentina Armorr, tried to hide him from his father, but she failed and was killed for her affront. Japan's greatest hero Sensei Toshiaki (the White Crane) eventually killed Black Dragon for his crimes and adopted the infant Val. He raised Val as if he were his own son, and trained him in all manner of the martial arts. Val became the youngest warrior ever to earn the title Samurai, and he went to work for his local shogun. However, after trying his best and failing to please his supervisor, he quit and searched the galaxy for new forms of battle to master.

edit: I've gotten some responses saying I should check "Martial Masters" for some bases. If only I could find any characters from that game...

Captain America Returns To Marvel

2007-08-16T02:04:00.000-04:00

I saw this coming from a mile away, and if it keeps up there will be another comics implosion, similar to the DC Implosion of 1978 & the time right after Superman died. I was surprised back when I first saw it on the news, so the following Saturday I go to my lcs & they had 1 copy left, the only sold-out book in the store... they're just building for the movie which should be out sometime in 2009

Long jump by FlowaGirl

2007-08-15T22:48:00.000-04:00

==========
Long Jump
==========
Author: FlowaGirl
flowergirl@cutey.com
http://blargh.i-xcell.com

---------------------------------------------------------------------------
This is one way to program a long jump in Mugen. It uses your character's
normal jumping state.

Be sure to add in a command for the long jump, which is typically "$D, U"
---------------------------------------------------------------------------

In state 40, add this in:

[State 40: VarSet]
type = VarSet
trigger1 = (!Time)
var(0) = 0

[State 40: VarSet]
type = VarSet
triggerall = (Var(0) = 0)
trigger1 = ((PrevStateNo = 100) && (Command = "holdfwd")) || ((PrevStateNo = 105) && (Command = "holdback")) || (Command = "Long Jump")
var(0) = 1

And in state 50, add in these 2 states. The VelAdd is used to increase the velocities of
the normal jump state, so adjust this according to your preferences.

[State 50: VelAdd]
type = VelAdd
trigger1 = (!Time) && (Var(0) = 1)
x = IfElse((Vel X) = 0,0,IfElse((Vel X) < 0,-4,4))
y = -3

[State 50: AfterImage]
type = AfterImage
trigger1 = ((!Time) && (Var(0) = 1) && (Vel X != 0))
time = 15
timegap = 4
framegap = 1
length = 10
paladd = 0, 0, 0
palmul = .50, .50, .50
palcontrast = 110,110,110
trans = add
persistent = 0

Mike Wieringo dead at 44

2007-08-14T13:49:00.000-04:00

The comics industry lost a luminary this weekend - Mike Wieringo passed away Sunday of a sudden heart attack. Details are still sketchy as of this time, but according to close sources, the acclaimed artist had chest pains at some point during the day and called 911, but the responders did not make it in time.

Mike Wieringo was 44 years old. He was a vegetarian, and "one of the healthiest ones of us in the bunch," as his longtime friend and collaborator Todd Dezago described him.

R.I.P. to Mike & his family, he was a great inspiration to me, drew one of my favorite versions of Spidey & Flash. I still have Flash #80, which I believe was his first DC work and his style had me hooked since. He will be missed.

for more info you can check his blog where his brother now maintains.

Final Boss by MugenJF

2007-08-13T17:52:00.000-04:00

Final head:
To add to order = 10 behind char that you want that is the head
and in arcade.maxmatches (at the end of the file select.def) pon a one in the last number one.
it is more or less this line arcade.maxmatches = 6,0,0,0,0,0,0,0,0,1.

Order is as if you made a group
for example if you want that there are 6 random fighters at the outset, soon a semifinal, and finally a end
you must make three groups
to the six random ones you put to them to order =1
to that you want that it is the semifinal you put to order =2
and to the you want that it is the end you put to order = 3
and soon you add this line
arcade.maxmatches = 6,1,1,0,0,0,0,0,0,0
this line completes says to whichever fighters you want to us that they leave in your game each order
that is to say, you want that they leave 6 order 1
that it leaves one order 2 (your semininalista)
and that leaves one order 3 (your finalist finalist)
the total of fighters to beat will be 6 (to order =1) + 1 (to order =2) + 1 (to order =3).

Other normal groups, are that you always want that follows an order equal, therefore you can have up to 10 groups
of a person, serious thus
arcade.maxmatches = 1,1,1,1,1,1,1,1,1,1
and you put to each char the order in that you want that it leaves, to order =1, first and to order =10 I complete.

Voltron Movie In The Works

2007-08-11T16:06:00.000-04:00

20th Century Fox-based production company New Regency has partnered with the Mark Gordon Company to adapt Voltron: Defender of the Universe into a possible franchise.

Producer Mark Gordon has been developing the film, based on the popular 1980s Japanese animated TV series, comic books and toy line, for some time with Justin Marks writing the script.

But interest in the property hit a high after Transformers turned into a box office juggernaut, raking in nearly $300 million to date.

Marks' take is described as a post-apocalyptic tale of survival set in New York City and Mexico.

In the animated series, five Galaxy Alliance pilots control vehicles shaped like lions that combine and form the massive sword-wielding Voltron robot in order to battle an evil menace.

Gordon is producing with Lawrence Inglee and Jordan Wynn shepherding the project. Mark Costa and Ford Oelman are executive producers.

Marks is also adapting He-Man and the Masters of the Universe for Joel Silver at Warner Bros., as well as the Green Arrow pic Supermax, also at the studio. Marks also has Street Fighter in the works at Hyde Park and Fox.

Info on the new PSP SKU

2007-08-10T16:11:00.000-04:00

MTV News' Stephen Totilo managed to snag a plethora of details on the PSP 2000 (that's what they're calling it internally) from SCEA's head of marketing for the PSP division John Koller.

All future PSP titles from Sony will utilize the upgraded 333MHz clockspeed, reportedly without a hit on battery life, said Koller. A second thumbstick was considered, as was (briefly) a built-in hard drive instead of Memory Stick. Both ideas were ultimately turned down.

Sony has given the PSP-2000 a Japanese release date of Sept. 20. The handheld will release for ¥19,800 ($162) in six colors (black, white, silver and three pastels). If you'd like to know more about the gooey innards of the machine, feel free to check out the manual. PSP-2000 units will cost $199 in the US for an entertainment pack and $169 for the stand alone, they'll replace the original PSP model the same way the DS Lite replaced the phat.

Super Armor by Winane

2007-08-09T02:48:00.000-04:00

;CNS
;-----------------------------------
;
[StateDef 44304]
ctrl = 0
physics = N
velset = 0
sprpriority = -5

[State 44304, Follow]
type = BindToRoot
trigger1 = 1
time = -1
facing = 1
pos = 0,0

[State 44304, Mimic]
type = ChangeAnim
trigger1 = SelfAnimExist(Root,Anim)
value = Root,Anim
elem = Root,AnimElemNo(0)

[State 44304, STSS]
type = StateTypeSet
trigger1 = Root,StateType = S
StateType = S

[State 44304, STSC]
type = StateTypeSet
trigger1 = Root,StateType = C
StateType = C

[State 44304, STSA]
type = StateTypeSet
trigger1 = Root,StateType = A
StateType = A

[State 44304, STSL]
type = StateTypeSet
trigger1 = Root,StateType = L
StateType = L

[State 44304, MTSA]
type = StateTypeSet
trigger1 = Root,MoveType = A
MoveType = A

[State 44304, MTSI]
type = StateTypeSet
trigger1 = Root,MoveType = I
MoveType = I

[State 44304, MTSH]
type = StateTypeSet
trigger1 = Root,MoveType = H
MoveType = H

[State 44304, Hide]
type = AssertSpecial
trigger1 = 1
flag = invisible
flag2 = NoShadow

[State 44304, NHB]
type = NotHitBy
trigger1 = 1
value = , AT
time = -1

[State 44304, HO]
type = HitOverride
trigger1 = 1
attr = SCA, AA,AP,AT
time = -1
stateno = 44305

[StateDef 44305]
ctrl = 0
physics = N
velset = 0
sprpriority = -5

[State 44305, PVS]
type = ParentVarSet
trigger1 = 1
var(20) = GetHitVar(damage)

[State 44305, Revert]
type = ChangeState
trigger1 = 1
value = 44304

;====================================================================

Then, put this at the top of StateDef -1:
======================================================================

[State -1, Hide]
type = AssertSpecial
trigger1 = IsHelper(44304)
flag = invisible
flag2 = NoShadow
IgnoreHitPause = 1

[State -1, Reset]
type = SelfState
trigger1 = IsHelper(44304)
trigger1 = StateNo != [44304,44305]
value = 44304
IgnoreHitPause = 1

;And make sure none of the controllers below these two can ever be triggered for the armor helper.

;Then put these in StateDefs -3 and -2

[State -3, ArmorHelper]
type = Helper
trigger1 = !NumHelper(44304)
trigger1 = Alive
name = "Armor"
ID = 44304
StateNo = 44304
KeyCtrl = 1
PauseMoveTime = 2147483647
SuperMoveTime = 2147483647

[State -3, Ow]
type = LifeAdd
trigger1 = var(20) && StateNo != [120,155]
value = -var(20)

[State -3, Reset]
type = VarSet
trigger1 = 1
var(20) = 0

[State -2, HandsOff]
type = NotHitBy
trigger1 = 1
value = SCA
time = -1
IgnoreHitPause = 1

AI Activation - Command method by FlowaGirl

2007-08-08T13:48:00.000-04:00

==============================
AI Activation: Command method
==============================
Author: FlowaGirl
flowergirl@cutey.com
http://blargh.i-xcell.com

---------------------------------------------------------------------------
Until Elecbyte decides to add in a trigger that detects
whether the character is controlled by a player or by the
CPU, this code will be used as a workaround.

After implementing this little piece, you are free to program
your character's AI, providing that you know how it's done. Wink

This is amongst the 3 most commonly used methods of AI activation.
I'm not sure who first developed this concept, but it is a popular
belief that Visual Kreations first came up with this, showing a few
creators how it was done.
---------------------------------------------------------------------------

This method uses the CMD file to activate the AI. These commands
are impossible to execute by a player but for the CPU, it is not a
problem. However, it heavily relies that the CPU to execute this as
soon as possible, so it's not a guarantee that your character's AI
will activate immediately. (Which could mean a victory, or a lose.)

Add into your CMD file, several AI activation commands. Generally,
the more commands you put in, the odds of the AI activating more quickly
are increased. Adding in about 20-30 commands will suffice.

Here are some examples:

[Command]
name = "AI1"
command = D, D, D, D
time = 1

[Command]
name = AI2"
command = D, F, B, U
time = 1

The "time = 1" is very important, as the command must be executed in that
amount of time. This is of course, impossible for any human to do.

Next you add this in under StateDef -1. This is used to activate the AI
when the CPU executes one of the commands you've made.

[State -1: VarSet]
type = VarSet
triggerall = (Var(0) != 1)
trigger1 = (Command = "AI1") || (Command = "AI2")
var(0) = 1

Simple, no? =)

AI Activation - Helper method by FlowaGirl

2007-08-07T04:58:00.000-04:00

=============================
AI Activation: Helper method
=============================
Author: FlowaGirl
flowergirl@cutey.com
http://blargh.i-xcell.com

---------------------------------------------------------------------------
Until Elecbyte decides to add in a trigger that detects
whether the character is controlled by a player or by the
CPU, this code will be used as a workaround.

After implementing this little piece, you are free to program
your character's AI, providing that you know how it's done. Wink

This is amongst the 3 most commonly used methods of AI activation.
I'm not sure who first developed this concept, but it is a popular
belief that ANMC or Kaku Kuo first came up with this, showing a few
creators how it was done.
---------------------------------------------------------------------------

You must first create a helper. Add this code under StateDef -2.

[State -2: Helper]
type = Helper
trigger1 = (NumHelper(****) = 0) && (Var(0) = 0)
helpertype = Normal
name = "Whatever"
id = ****
pos = 0,0
postype = p1
facing = 0
stateno = ****
keyctrl = 1
ownpal = 1
supermovetime = 0
pausemovetime = 0

These next few states are used to turn the AI on and off at the
appropriate times. We wouldn't want the character to battle during
his winpose. Wink

[State -2: VarSet]
type = VarSet
trigger1 = (Var(0) = 1)
var(0) = 2

[State -2: VarSet]
type = VarSet
trigger1 = (Var(0) != 0) && (RoundState != 2)
var(0) = 0

[State -2: ChangeState]
type = ChangeState
trigger1 = (RoundState = 3) && (StateType != A) && (Ctrl)
value = 0

Next, in the Helper's state...

[Statedef ****]
type = S
movetype = I
physics = N
anim = **** ;Invisible anim

This part is used to detect whether the character is controlled by a
player, or the CPU.

[State ****: ParentVarSet]
type = ParentVarSet
triggerall = (Parent, Var(0) != 1)
trigger1 = ((Parent, Command = "x") && (Command != "x")) || ((Parent, Command = "y") && (Command != "y")) || ((Parent, Command = "z") && (Command != "z"))
trigger2 = ((Parent, Command = "a") && (Command != "a")) || ((Parent, Command = "b") && (Command != "b")) || ((Parent, Command = "c") && (Command != "c"))
trigger3 = ((Parent, Command = "holdfwd") && (Command != "holdfwd")) || ((Parent, Command = "holdback") && (Command != "holdback"))
trigger4 = ((Parent, Command = "holdup") && (Command != "holdup")) || ((Parent, Command = "holddown") && (Command != "holddown"))
var(0) = 1

[State ****: ParentVarSet]
type = ParentVarSet
triggerall = (Parent, Var(0) != -1)
trigger1 = ((Parent, Command = "x") && (Command = "x")) || ((Parent, Command = "y") && (Command = "y")) || ((Parent, Command = "z") && (Command = "z"))
trigger2 = ((Parent, Command = "a") && (Command = "a")) || ((Parent, Command = "b") && (Command = "b")) || ((Parent, Command = "c") && (Command = "c"))
trigger3 = ((Parent, Command = "holdfwd") && (Command = "holdfwd")) || ((Parent, Command = "holdback") && (Command = "holdback"))
trigger4 = ((Parent, Command = "holdup") && (Command = "holdup")) || ((Parent, Command = "holddown") && (Command = "holddown"))
var(0) = -1

This piece is used to remove the helper, once it has served it's purpose.
It prevents the AI from turning on by accident if controlled by a human,
and it frees up some memory.

[State ****: DestroySelf]
type = DestroySelf
trigger1 = (Parent, Var(0) = -1)

Madka's Frankenspriting Tutorial

2007-08-05T13:17:00.000-04:00

You can also download the video here (note the video doesn't have sound!)

Sykotik's Character Creation Tutorial

2007-08-04T17:35:00.000-04:00

Note: Done in a day, might be sloppy, e-mail me for corrections and changes, if you want something added, in the subject line, put the name of the section that you want it added to, thank you...

Note: I will also be rushing through the first 3 or 4 sections, since they have been done before, so sorry if this has caused you any inconvienence...

Note: I recommend that you use KFM's template files for the base of your first character, or at least for testing while reading this tutorial...

Introduction

Ok, this tutorial was meant for people who want their favorite character in MUGEN, the 2d fighting game engine created by Elecbyte, and have no idea whatsoever on how to start. I will go over the following things in detail and with descriptions of what they do. This is what I will be following in this version of the tutorial:

Ripping Sprites

How to make sprites acceptable in MUGEN (cleaning, cropping, making it the right file type, etc.)

How to make a palette for the character in MUGEN

How to make the SFF file (the axis of pictures, group numbers, and image numbers)

How to make the AIR file (CLSN boxes, how to make an action, etc.)

How to make a command in the CMD file (along with AI and what the different options for a State -1 are)

How to make a state in the CNS file (pretty much descriptions of what all the options are)

Examples of most of the above and how to program things that you always wanted to program (artificial intelligence, super jumps, launchers, combos, moves that hit twice, etc.)

Finally, link to other great tutorials by famous MUGEN gods

Without any further ranting, I think we can start with the tutorial now...

Ripping Sprites

Ripping the sprites of the character that you are going to make is an essential part of MUGEN, since if they weren't there, there wouldn't be any character. First of all, you must find a character that you would want to make. Also, it would be a good idea to see if he was even made, first. Now, once you've found out who you want to make, the next step is to get a rom and/or emulator with that character, so that you can begin the sprite ripping process. With some roms, like NeoRageX, sprite ripping is made incredibly easy with shot factory. Shot factory disables any unneeded layers, presumably the background and other fighter, then allows you to save the picture that you have. Plus, it allows you to play the rest of the game with those layers disabled, allowing you to take much faster and easier pictures. Some other roms, like Zsnes, Callus, and Bleem, are easy to rip from with the ability to screen capture, but they aren't as detailed as NeoRageX, and only allow you to take a picture and edit everything out later. However, Zsnes has the ability to disable layers so that only you and your opponent are left, making the cleaning process easier. Callus even has a feature so that you can slow down animation very much, which makes ripping every sprite much easier. Whichever emulator that your character is on, it shouldn't be too much of a trouble ripping them. Unfortunately, some good emulators don't even have a screen capture feature. "Then, how do I rip sprites from it", you make ask, and the answer is simple. You just have to download a screen capture program from off the internet, enlarge your emulator screen to full size, and set the screen capture program to capture the pic when you press a certain key. A few good screen capture programs happen to be Namo Capture and a program called just plain Capture. I believe that I have touched base with about everything needed in this section of the tutorial. If you would like anything else added to this section that makes sense, just e-mail me and I will probably add it.

How To Make Sprites Acceptable In MUGEN and How To Make A Palette For The Character In MUGEN

First of all, most emulators, as I have mentioned above, help out a lot in this process. Some convert the pictures to 8-bit PCX, like what MUGEN accepts, and even take out all of the unneeded layers. However, this section will deal with a picture that was screen captured, uncleaned, in some type of BMP format, and whatever else that might make the picture harder to make MUGEN acceptable. Ok, first you can download PCX Clean from Elecbyte's website and then use that to take out all unneeded objects in the picture. I have never used PCX Clean, so unfortunately, I won't be able to tell you how to use it. I figure that you are smart enough to find out how to use this. Next, we must make a palette by opening up Paint Shop Pro or Adobe Photosop, whichever you use, and converting the picture to an 8-bit PCX, so that you can make a palette for it. Then, click on save palette and save it as something that you will remember. Do the following with every other picture, but instead of saving the palette, click load palette, and load the palette that you saved earlier. This shouldn't cause too many problems, but you can e-mail me if some problems pop up, and if they are familiar to me, I will be able to help fix them. I think that I have pretty much touched base on everything here, also, so I will go on to the next section of this tutorial. However, if want anything added to this section of the tutorial, just be sure to e-mail me and I will be happy to add it, if it would fit here mind you.

Sunboy's Commentary: For creating a palette, I suggest getting all sprites with different colors and putting them into one big PCX to convert to 8-bit color and apply that palette to all the other frames.

How To Make The SFF File

Ok, first you have to go to Sés' page and download the Mugen Character Maker. Not only is this little gadget handy for making SFF files, but it is the only way to make SFF files in this day and age. Once you download Mugen Character Maker and play around with it a bit, it shouldn't be too hard to figure out how to use it. I might as well go over the basics though first. Keep in mind, when using Mugen Character Maker, it does crash quite a bit, but not nearly as much as MuGenerator does. Now, when you open up MCM (Mugen Character Maker from now on), you will notice that its pretty blank. I suggest putting MCM in the directory with your characters sprites, since that is a good place to save the SFF file and it makes it easier to add sprites. All you have to do basically is keep on adding sprites until every one of them is in the SFF. My advice, though, is to save your sprites in the order that they're animated when put in the SFF file. That way, when you go to do SFF work, like the group and image numbers, you don't have to travel all over the SFF looking for the next frame of animation or even wondering what it is, if the animation is so fluid that the frames look the same and are nowhere near each other. Anyway, once you have added every sprite you must do the axis for the sprites, which is pretty easy, and I really can't help you, since every character (well almost) has a different axis. But, I'm sure you can figure out that the horizontal line on the + in the middle of the MCM screen is the floor, which you want your characters feet to be a little below that, since floors aren't one line in MUGEN and you want them to not be at the very beginning of the wall, but in the middle of the floor. After you are done with the axis for every sprite, you must now do the group and action numbers. Both numbers mean what sprite you will use, since the following is how they are used (excerpt from an AIR file):

0,0 0,0 10

The first two 0's are its group and image number, the second two are its x,y position, and the 10, standing for amount of game ticks, is how long the animation plays. Sorry, for taking a huge bite out of the AIR file section, but I will explain stuff more detailed there. Also, keep in mind that the group number is usually the same as its action number in the AIR file and its state number in the CNS file. I believe that I have pretty much covered this section. Once again, e-mail me if you want to see anything added to this section of the tutorial and I will do so if I see it fitting.

How To Make The AIR File

This is probably one of the easiest parts of MUGEN programming, so I probably won't be spending too much time on it. Let's just start by defining for you, every part of an action so that you can see exactly what the actions in the AIR file really do. Then, I will go into CLSN boxes, which shouldn't be much of a problem if you use AirEdit like any other normal Windows program. Anyway, the following is from an upcoming characters AIR file, we will define every part of the state there, as said above, so that you can have a better understanding of the state:

;--------------------------------------------------------------------------- ;Divider (Unrequired)
; Standing Animation ;Name Of Move (Unrequired)
[Begin Action 000] ;Action Number Of Move (Required)
Clsn2Default: 2 ;Number Of CLSN2 default boxes used for all sprites below it (Required)
Clsn2[0] = -13, 0, 16,-79 ;CLSN box (Required)
Clsn2[1] = 5,-79, -7,-93 ;CLSN box (Required)
0,1, 0,0, 10 ;Group Number, Sprite Number X Axis, Y Axis Time (Game Ticks) (Required)
0,2, 0,0, 10 ;Group Number, Sprite Number X Axis, Y Axis Time (Game Ticks) (Required)
0,3, 0,0, 10 ;Group Number, Sprite Number X Axis, Y Axis Time (Game Ticks) (Required)
0,4, 0,0, 10 ;Group Number, Sprite Number X Axis, Y Axis Time (Game Ticks) (Required)
0,5, 0,0, 10 ;Group Number, Sprite Number X Axis, Y Axis Time (Game Ticks) (Required)
0,6, 0,0, 10 ;Group Number, Sprite Number X Axis, Y Axis Time (Game Ticks) (Required)
0,7, 0,0, 10 ;Group Number, Sprite Number X Axis, Y Axis Time (Game Ticks) (Required)

As you can see, the AIR file isn't really that tough at all, but if you are still skeptical, here is another excerpt from the same character, showing you that it doesn't get much tougher than the above:

;--------------------------------------------------------------------------- ;Divider (Unrequired)
; New Super ;Name Of Move (Unrequired)
[Begin Action 6050] ;Action Number Of Move (Required)
Clsn2Default: 1 ;Number Of CLSN2 default boxes used for all sprites below it (Required)
Clsn2[0] = 15, 0,-20,-91 ;CLSN box (Required)
6050,0, 0,-10, 6 ;Group Number, Sprite Number X Axis, Y Axis Time (Game Ticks) (Required)
Clsn1: 7 ;Number Of CLSN1 boxes used for all sprites below it (Required)
Clsn1[0] = 82,-110, 72,-89 ;CLSN box (Required)
Clsn1[1] = 74,-95, 63,-83 ;CLSN box (Required)
Clsn1[2] = 67,-87, 55,-80 ;CLSN box (Required)
Clsn1[3] = 12,-71, 24,-60 ;CLSN box (Required)
Clsn1[4] = 21,-73, 35,-66 ;CLSN box (Required)
Clsn1[5] = 33,-68, 47,-78 ;CLSN box (Required)
Clsn1[6] = 43,-74, 59,-84 ;CLSN box (Required)
6050,1, 0,-20, 6 ;Group Number, Sprite Number X Axis, Y Axis Time (Game Ticks) (Required)
Clsn1: 7 ;Number Of CLSN1 boxes used for all sprites below it (Required)
Clsn1[0] = 31,-130, 14,-50 ;CLSN box (Required)
Clsn1[1] = 74,-95, 63,-83 ;CLSN box (Required)
Clsn1[2] = 67,-87, 55,-80 ;CLSN box (Required)
Clsn1[3] = 12,-71, 24,-60 ;CLSN box (Required)
Clsn1[4] = 21,-73, 35,-66 ;CLSN box (Required)
Clsn1[5] = 33,-68, 47,-78 ;CLSN box (Required)
Clsn1[6] = 43,-74, 59,-84 ;CLSN box (Required)
6050,2, 0,-30, 6 ;Group Number, Sprite Number X Axis, Y Axis Time (Game Ticks) (Required)
6050,3, 0,-30, 6 ;Group Number, Sprite Number X Axis, Y Axis Time (Game Ticks) (Required)
6050,4, 0,-20, 6 ;Group Number, Sprite Number X Axis, Y Axis Time (Game Ticks) (Required)
6050,5, 0,-10, 6 ;Group Number, Sprite Number X Axis, Y Axis Time (Game Ticks) (Required)

This action number seems to be much more difficult at first, but after reading the comments, you can see that it is just like the first, just with larger group numbers for the sprites and more CLSN boxes (Heh, notice that there are even less sprites in this action number). Now, I will go into how to make a CLSN box. First of all, open AirEdit through Windows and not MSDos. Then, click open and select your characters AIR file (everything except for the CLSN boxes should be done in here at this point), then select its SFF file. Note that it might be SFF file then the AIR file. Either way, make sure that AirEdit is in your characters directory so that you can access the characters files easier. Then, once you are done with that, select (click on the boxes next to, causing an X to appear) Show CLSN1 Boxes and Show CLSN2 Boxes. Afterwards, just highlight where you want the box to be, click Save1 (or Save2 etc. if you want to add a second or more boxes to the same frame), and then go to File>Save to select which kind of CLSN box that you would like to make. In order to delete a box, without drawing a box, click Save1 (or Save2 etc. depending on which box that you want to delete), and then go to File>Save>CLSN1 so that it says something about there being no boxes highlighted and would you like to delete all boxes in this frame. However, it only illusions all boxes being deleted, and only the box that you selected will be deleted. After you do all of the CLSN boxes, click exit and they should all be automatically saved, but it is safe to keep on reopening AirEdit and checking that it saved the new boxes right, but I think what I told you might fix that problem. As always, if you want anything else added to this section, just feel free to e-mail me and I will most certainly do so as long as it fits here. Now, onto the examples of making a CNS and CMD file, which should be more detailed on how to do so, but won't explain how to do everything.

How To Make A Command In The CMD File

This shouldn't be too hard, so I'll first explain a few things before I get into the basics with a bunch of examples. The CMD file isn't all that hard at all, and you should be able to learn it quickly. The sooner the better because all AI programming is done in the CMD, pretty much. Well, actually there isn't much else to say, so let me get into a command. The following is an example one with descriptions on what each part does:

;-| Special Motions |----------------------------------------- ;Header For The Type Of Moves To Follow (Unrequired)
[Command] ;Defines that this is a command (Required)
name = "QCF_x" ;The name of the move, which you use later when you are doing the State-1's (Required)
command = ~D, DF, F, x ;The command that needs to be done in order to do the move (Required)

As you can see, the command isn't that complicated. The name can be whatever you want, and so can the command, but it is recommended that you make the command the same as it is in the game. However, if you have trouble understanding the stuff that comes after "command =", read the CMD file for Kung Fu Man, and it explains what you put in for each kind of motion that is possible in MUGEN. Now, to teach you people about the State-1's which is basically just a state that is lower in the CMD file that calls the command and tells it what state in the CNS to affect. Here is an example of the State-1 that calls the above command, so study it carefully:

[Statedef -1] ;This Does Not Come Before Every Move, But Is Rather The Header To The State-1's (Required)

;--------------------------------------------------------------------------- ;Divider (Unrequired)
;Light Kung Fu Palm ;Name Of Move (Unrequired)
;ƒJƒ“ƒt�[“Ë‚«Žè�iŽã�j ;Gibberish, but probably a description or something (Unrequired)
[State -1, Light Kung Fu Palm] ;All Moves In The Statedef-1 Start Like This, With The "Light Kung Fu Palm" Being The Name Of The Move
type = ChangeState ;Changes The State So That It Goes To The Value Below In The CNS (Required)
value = 1000 ;This Is The State Number In The CNS That The Command Activates When Move Is Performed (Required)
triggerall = command = "QCF_x" ;This Tells The State-1 To Activate When The Command To The Left Is Performed (Required)
trigger1 = statetype = S ;This Tells The Command To Only Work When The Opponent Is Standing (Unrequired)
trigger1 = ctrl ;This Tells The Command To Work Only When The Character Has Control (Unrequired)
trigger2 = (stateno = [200,299]) || (stateno = [400,499]) ;Tells Command To Occur If Character Is Between These States (Unrequired)
trigger2 = stateno != 440 ;This Tells The Command To Not Occur When In State 440, Since != Means Not
trigger2 = movecontact ;Tells The Command To Occur On Move Contact

This might confuse you, but keep in mind it is only to give you a very basic idea of the MUGEN game engine, and since this is a very early version of the tutorial, it will probably have many mistakes, and I have asked you people before to help me in correcting them. If you are talented in MUGEN and wants to continue this tutorials, please feel free to as long as credit to me is given for the first version. Also remember, I will only let you continue this tutorials if I believe that you can handle it right. And as I have said many times before, e-mail me if you believe that something is missing and/or wrong, and I will fix it immediately as I see fitting. Now, we must go on to the CNS, which will be a little less descriptive, since I can't cover anywhere near everything that is needed in order to program for MUGEN.

How To Make A State In The CNS File

Ok, this will be on of the shortest sections since I don't have much to say on this subject. CNS file programming, in my opinion, is the hardest thing about MUGEN, so I am just going to explain about a few triggers and commands and what they do. I will probably also go over a basic state header and footer, and who knows what else. After this I will get into some of the more fun stuff, like artificial intelligence, super jumping, launchers, and all sorts of combos, but we must first learn the basics. First, I will give you an example state header and a state footer and describe what it does, before I give you a few pieces of coding that you can use in the CNS. Here is the header and the footer, borrowed from an upcoming character by myself which will be released soon, so read the comments carefully and study so that you get them right.

Header

;--------------------------------------------------------------------------- ;Divider (Unrequired)
; Kung Fu Palm ;Name Of Move (Unrequired)
; CNS difficulty: medium ;Difficulty Of Programming (Unrequired)
[Statedef 6050] ;Number Of Statedef That Is Called From Command (Required)
type = S ;Tells The Type Of The Move Which Is A Standing Move
movetype= A ;A Stands For Attack Since This Move Is Actually An Attack (Required)
physics = S ;S Stands For Standing Which Is The Characters Physics At The Time Of The Move (Required)
juggle = 4 ;Tells The Game How Many Times The Characters Is Allowed To Juggle The Opponent With This Move (Unrequired)
poweradd= 110 ;This Adds The Amount Of Power Stated To The Left To The Power Bar (Unrequired)
velset = 0,0 ;Tells The Characters To Move To This Position On Screen, Here It Would Be Standing Still (Unrequired)
anim = 6050 ;Tells The Characters To Use This Animation
ctrl = 0 ;Takes Control Away From The Character

Footer

[State 1000, 7] ;Number Of The State, The Footer Is Usually The Last State (Required)
type = ChangeState ;Tells The Character To Change His State (Required)
trigger1 = AnimTime = 0 ;Tells The Character To Do So After The Number Of Seconds To The Left (Required)
value = 0 ;The Value To The Left Is The State Number Where The Characters Goes, Usually 0, The Standing Animation (Required)
ctrl = 1 ;This Gives Control back To The Character

The rest of the states that come between this explain what the move does, and that is pretty much the purpose of the CNS and its states, to tell what the move is supposed to do. Unfortunately, in return for an earlier release, I won't go much further into the CNS, but I will add the following to the next section, Cool Tricks And Tips:

Artificial Intelligence

Super Jumping

Explods

Projectiles

Teleporting

Cool Tips And Tricks

Ok, here I will explain how to do some cool stuff in the MUGEN game engine. I will start with artificial intelligence, which I am sure that a lot of you would like to learn about. First, you must make as many commands as you can with the time being one and the commands can be something like U, D, D, U. The command can be anything as long as time is small and command is impossible for a human to do in that time. The computer, however, if you have the illusion of AI (see mugen.cfg) turned on, can do these controls easily. This command will activate AI, and a good thing to do is make about 50 something of these commands. Because the more commands that you have, the better the chance that the AI will start. It's kind of like pulling a winning ticket out of a hat. The more winning tickets there are, the better the chance that you'll choose it. Anyway, I think you get the point. I am too lazy to go intro description about this so just copy what is below and learn yourself or wait for the other artificial intelligence tutorial that somebody is making:

*Just Copy This At The Top Of The CMD File, I Am Too Lazy To Explain Everything*

;-| AI Commands |----------------------------------------------------------

[Command]
name = "cpu1"
command = U, U, U, U
time = 1
[Command]
name = "cpu2"
command = U, U, U, D
time = 1
[Command]
name = "cpu3"
command = U, U, D, D
time = 1
[Command]
name = "cpu4"
command = U, D, D, D
time = 1
[Command]
name = "cpu5"
command = D, D, D, D
time = 1
[Command]
name = "cpu6"
command = D, D, D, U
time = 1
[Command]
name = "cpu7"
command = D, D, U, U
time = 1
[Command]
name = "cpu8"
command = D, U, U, U
time = 1
[Command]
name = "cpu9"
command = U, D, U, U
time = 1
[Command]
name = "cpu10"
command = U, U, D, U
time = 1
[Command]
name = "cpu11"
command = D, U, U, D
time = 1
[Command]
name = "cpu12"
command = U, D, D, U
time = 1
[Command]
name = "cpu13"
command = D, U, D, U
time = 1
[Command]
name = "cpu14"
command = U, D, U, D
time = 1
[Command]
name = "cpu15"
command = F, F, F, F
time = 1
[Command]
name = "cpu16"
command = B, B, B, B
time = 1
[Command]
name = "cpu17"
command = F, B, F, F
time = 1
[Command]
name = "cpu18"
command = F, F, B, F
time = 1
[Command]
name = "cpu19"
command = B, F, F, F
time = 1
[Command]
name = "cpu20"
command = F, F, F, B
time = 1
[Command]
name = "cpu21"
command = F, B, B, F
time = 1
[Command]
name = "cpu22"
command = B, F, F, B
time = 1
[Command]
name = "cpu23"
command = F, B, F, B
time = 1
[Command]
name = "cpu24"
command = B, F, B, F
time = 1
[Command]
name = "cpu25"
command = D, F, D, F
time = 1
[Command]
name = "cpu26"
command = D, B, D, B
time = 1
[Command]
name = "cpu27"
command = D, B, D, F
time = 1
[Command]
name = "cpu28"
command = D, F, D, B
time = 1
[Command]
name = "cpu29"
command = U, F, D, B
time = 1
[Command]
name = "cpu30"
command = U, B, D, F
time = 1
[Command]
name = "cpu31"
command = B, D, F, U
time = 1
[Command]
name = "cpu32"
command = F, D, B, U
time = 1
[Command]
name = "cpu33"
command = U, U, U, U
time = 1
[Command]
name = "cpu34"
command = U, U, U, D
time = 1
[Command]
name = "cpu35"
command = U, U, D, D
time = 1
[Command]
name = "cpu36"
command = U, D, D, D
time = 1
[Command]
name = "cpu37"
command = D, D, D, D
time = 1
[Command]
name = "cpu38"
command = D, D, D, U
time = 1
[Command]
name = "cpu39"
command = D, D, U, U
time = 1
[Command]
name = "cpu40"
command = D, U, U, U
time = 1
[Command]
name = "cpu41"
command = U, D, U, U
time = 1
[Command]
name = "cpu42"
command = U, U, D, U
time = 1
[Command]
name = "cpu43"
command = D, U, U, D
time = 1
[Command]
name = "cpu44"
command = U, D, D, U
time = 1
[Command]
name = "cpu45"
command = D, U, D, U
time = 1
[Command]
name = "cpu46"
command = U, D, U, D
time = 1
[Command]
name = "cpu47"
command = F, F, F, F
time = 1
[Command]
name = "cpu48"
command = B, B, B, B
time = 1
[Command]
name = "cpu49"
command = F, B, F, F
time = 1
[Command]
name = "cpu50"
command = F, F, B, F
time = 1
[Command]
name = "cpu51"
command = B, F, F, F
time = 1
[Command]
name = "cpu52"
command = F, F, F, B
time = 1
[Command]
name = "cpu53"
command = F, B, B, F
time = 1
[Command]
name = "cpu54"
command = B, F, F, B
time = 1
[Command]
name = "cpu55"
command = F, B, F, B
time = 1
[Command]
name = "cpu56"
command = B, F, B, F
time = 1
[Command]
name = "cpu57"
command = D, F, D, F
time = 1
[Command]
name = "cpu58"
command = D, B, D, B
time = 1
[Command]
name = "cpu59"
command = D, B, D, F
time = 1
[Command]
name = "cpu60"
command = D, F, D, B
time = 1
[Command]
name = "cpu61"
command = U, F, D, B
time = 1
[Command]
name = "cpu62"
command = U, B, D, F
time = 1
[Command]
name = "cpu63"
command = B, D, F, U
time = 1
[Command]
name = "cpu64"
command = F, D, B, U
time = 1

*Just Copy This Under The Statedef -1, I Am Too Lazy To Explain Everything*

;-|AI Routine|----------------------------------------------------------------------------

;-|Signal AI Routines|--------------------------------------------------------------------
[State -1]
type = VarSet
v = 7
value = 1
triggerall = RoundState = 1 || RoundState = 2 || RoundState = 3 || RoundState = 4
triggerall = ctrl = 0 || ctrl = 1
trigger1 = command = "cpu1"
trigger2 = command = "cpu2"
trigger3 = command = "cpu3"
trigger4 = command = "cpu4"
trigger5 = command = "cpu5"
trigger6 = command = "cpu6"
trigger7 = command = "cpu7"
trigger8 = command = "cpu8"
trigger9 = command = "cpu9"
trigger10 = command = "cpu10"
trigger11 = command = "cpu11"
trigger12 = command = "cpu12"
trigger13 = command = "cpu13"
trigger14 = command = "cpu14"
trigger15 = command = "cpu15"
trigger16 = command = "cpu16"
trigger17 = command = "cpu17"
trigger18 = command = "cpu18"
trigger19 = command = "cpu19"
trigger20 = command = "cpu20"
trigger21 = command = "cpu21"
trigger22 = command = "cpu22"
trigger23 = command = "cpu23"
trigger24 = command = "cpu24"
trigger25 = command = "cpu25"
trigger26 = command = "cpu26"
trigger27 = command = "cpu27"
trigger28 = command = "cpu28"
trigger29 = command = "cpu29"
trigger30 = command = "cpu30"
trigger31 = command = "cpu31"
trigger32 = command = "cpu32"
trigger33 = command = "cpu33"
trigger34 = command = "cpu34"
trigger35 = command = "cpu35"
trigger36 = command = "cpu36"
trigger37 = command = "cpu37"
trigger38 = command = "cpu38"
trigger39 = command = "cpu39"
trigger40 = command = "cpu40"
trigger41 = command = "cpu41"
trigger42 = command = "cpu42"
trigger43 = command = "cpu43"
trigger44 = command = "cpu44"
trigger45 = command = "cpu45"
trigger46 = command = "cpu46"
trigger47 = command = "cpu47"
trigger48 = command = "cpu48"
trigger49 = command = "cpu49"
trigger50 = command = "cpu50"
trigger51 = command = "cpu51"
trigger52 = command = "cpu52"
trigger53 = command = "cpu53"
trigger54 = command = "cpu54"
trigger55 = command = "cpu55"
trigger56 = command = "cpu56"
trigger57 = command = "cpu57"
trigger58 = command = "cpu58"
trigger59 = command = "cpu59"
trigger60 = command = "cpu60"
trigger61 = command = "cpu61"
trigger62 = command = "cpu62"
trigger63 = command = "cpu63"
trigger64 = command = "cpu64"

Ok, now that you have done that, look at all of the moves that your character has and copy and paste them all under what it says above and you can put a label that says "AI Moves" or something if you want. I will now tell you how to alter the move so that the AI can use them. Here is an example move explaining the AI only commands and you can edit them to your own tastes. Please study this and add the AI only command to all of the moves that you have copied and pasted under the above code. AI only commands will be marked by an asterisk (*) next to them:

[State -1, Triple Kung Fu Palm]
type = ChangeState
value = 3000
*triggerall = var(7) = 1
triggerall = power >= 1000
trigger1 = statetype = S
trigger1 = ctrl
*trigger1 = statetype != A ;Tells the AI not to do the move in the air, add this to the move and feel free to change != A to anything that you want
*trigger1 = p2bodydist X <= 50 ;Tells the AI to do this move only when it is less than 50 pixels away from the opponent, add this to the move and feel free to change <= 50 to whatever you want
*trigger1 = p2movetype != A ;Tells the AI not to do this move then opponent is doing an air move, add this to the move and feel free to change != A to whatever you want
*trigger1 = random < 599 ;Tells the AI to do this move when a number of less than 599 out of 999 is randomly chosen, add this to the move and feel free to change < 599 to whatever you want
trigger2 = hitdefattr = SC, NA, SA
trigger2 = movecontact

If you copy and pasted what I told you to do and added those triggers to each move that you copied for the AI, you will have artificial intelligence. Remember, that you must keep on trying your AI until you find something that is very good and works. I'm sorry I couldn't go into much detail on this move, but as long as you have a basic understanding (hopefully), then I believe that I have accomplished what I wanted to accomplish from the beginning.

Conclusion

Because of time and boredom, I have decided to stop the tutorial here. I know that this isn't much of anything and is a large disappointment to many who wants to make a character. I close now with coding to a very basic Explod and Projectile. Add these to the state of the move where you want them, and they should work after they have been edited a bit. If you crave for more information visit FallenAngel's or [E]Magius's sites. Thank you for your time and concern.

Explod

[State 1000, 8]
type = Explod ;the type is an explod
trigger1 = AnimElem = 1 ;triggered on the first sprite
anim = 6070 ;this is the animation of the explod
postype = p1 ;this is where the explod will appear...choices of p1, p2, front, back, left, or right
pos = 0,0 ;position of the epxlod on the screen...in this case right where specified above...p1 (player 1)
bindtime = 100 ;how long the explod will stay where it was specified...in this case the whole move until animation is done

Projectile

------------------------------------------------------------

Projectile ;I figure if nobody reads the docs, maybe they'll read this...

------------------------------------------------------------

Creates a projectile for the player. The Projectile controller takes

all the parameters of the HitDef controller, which control the HitDef

for the projectile. In addition, Projectile has the following additional parameters:

Required parameters:

none

Optional parameters:

ProjID = id_no (int)

Specifies an ID number to refer to this projectile by. Should be

positive, if specified.

projanim = anim_no (int)

Specifies the animation action number to use for the projectile's

animation. Defaults to 0 if omitted.

projhitanim = anim_no (int)

Specifies the animation action number to play when the projectile

hits the opponent. Defaults to -1 (no change in animation) if

omitted.

projremanim = anim_no (int)

Specifies the animation action number to play when the projectile

is removed (due to its time expiring or hitting the its removal

boundaries, etc.) If omitted, projhitanim is used instead.

projcancelanim = anim_no (int)

Specifies the animation action number to play when the projectile

is cancelled by hitting another projectile. If omitted,

projremanim is used instead.

projremove = remove_flag (int)

Set to a nonzero value to have the projectile be removed after it

hits, or to 0 to disable this behavior. Defaults to 1.

projremovetime = remove_time (int)

Specifies the number of ticks after which the projectile should be

removed from the screen. Defaults to -1 (never time out).

velocity = x_vel, y_vel (float)

Specifies the initial x and y velocities for the projectile to

travel at. Defaults to 0,0 if omitted.

remvelocity = x_vel, y_vel (float)

Specifies the x and y velocities at which the projectile should

travel while being removed. Defaults to 0,0 if omitted.

accel = x_accel, y_accel (float)

Specifies the acceleration to apply to the projectile in the x and

y directions. Defaults to 0,0 if omitted.

velmul = x_mul, y_mul (float)

Specifies x and y velocity multipliers. The projectile's velocity

is multiplied by these multipliers on every tick. The multipliers

default to 1 if omitted.

projhits = num_hits (int)

Specifies the number of hits that this projectile should be able

to do before being removed. Defaults to 1.

projmisstime = miss_time (int)

If the projectile does multiple hits, specifies the least number

of ticks that must elapse between hits. Defaults to 0, but you

will most likely need a nonzero value.

projpriority = proj_priority (int)

Specifies the projectile priority. If the projectile collides with

another projectile of equal priority, they will cancel. If it

collides with another of lower priority, it will cancel the lower-

priority projectile, and the higher-priority one will have its

priority decreased by 1.

Defaults to 1.

projsprpriority = priority (int)

Specifies the sprite priority of the projectile. Higher-priority

sprites are drawn on top of lower-priority sprites. Defaults to 3.

projedgebound = value (int)

This is the distance (in pixels) off the edge of the screen before

the projectile is deleted. Defaults to 40.

projstagebound = value (int)

Specifies the greatest distance the projectile can travel off the

edge of the stage (not screen) before being deleted. Defaults to

40.

projheightbound = lowbound, highbound (int)

Specifies the least and greatest y values the projectile is

allowed to reach. If the projectile leaves these boundaries, it is

removed. Note: since y values decrease with increasing height on

the screen, lowbound actually specifies the greatest height the

projectile can attain. These parameters default to -240,1 if

omitted.

offset = off_x, off_y (int)

Specifies the x and y offsets at which the projectile should be

created. Both parameters default to 0 if omitted. The exact

behavior of the offset parameters is dependent on the postype.

postype = type_string

type_string specifies the postype -- how to interpret the pos

parameters.

In all cases, a positive y offset means a downward displacement.

Valid values for postype are the following:

- p1

Interprets pos relative to p1's axis. A positive x offset is

toward the front of p1. This is the default value for postype.

- p2

Interprets pos relative to p2's axis. A positive x offset is

toward the front of p2.

- front

Interprets xpos relative to the edge of the screen that p1 is

facing toward, and ypos relative to p1's y axis. A positive x

offset is away from the center of the screen, whereas a

negative x offset is toward the center.

- back

Interprets xpos relative to the edge of the screen that p1 is

facing away from, and ypos relative to p1's y axis. A positive

x offset is toward the center of the screen, whereas a

negative x offset is away from the center.

- left

Interprets xpos and ypos relative to the upper-left corner of

the screen. A positive x offset is toward the right of the

screen.

- right

Interprets xpos and ypos relative to the upper-right corner of

the screen. A positive x offset is toward the right of the

screen.

projshadow = shad_r, shad_g, shad_b (int)

Specifies the R, G, and B components of the projectile's shadow.

These components should be integers between 0 and 255,

inclusive. If shad_r evaluates to -1, then the stage's shadow

color will be used. The higher a component value, the less of

that color is displayed in the shadow. So a perfectly black shadow

is 255,255,255. Defaults to 0,0,0 (no shadow).

supermovetime = move_time (int)

Determines the number of ticks that the projectile should be

"unfrozen" during a SuperPause. Defaults to 0.

pausemovetime = move_time (int)

Determines the number of ticks that the projectile should be

"unfrozen" during a Pause. Defaults to 0.

Teleportation by The Necromancer

2007-08-03T00:46:00.000-04:00

=============
Teleportation
=============
Created by The Necromancer

;---------------------------------------------------------------------------
Teleportation -- The ability to move from one place to another without
physical movement.

There are two types of teleportation: Teleportation that works at a fixed
position, and teleportation that works according to a particular situation.
(eg. opponent's position)
;---------------------------------------------------------------------------

1.) Fixed Teleportation

This particular code can be controlled with the directional keys.

[Statedef 9000]

[State 9000, PlaySnd]
type = PlaySnd
trigger1 = (whatever)
value = *,*

[State 9000, PosSet]
type = PosSet
trigger1 = Pos Y > 0
y = 0

[State 9000, PosAddFwd]
type = PosAdd
triggerall = Time = *** ;Time to teleport.
trigger1 = ((command = "holdfwd") || (command != "holdfwd")) && (command != "holdback") && (command != "holdup") && (command != "holddown")
x = * ;Must be a positive value.
y = 0

[State 9000, PosAddBack]
type = PosAdd
triggerall = Time = *** ;Time to teleport.
trigger1 = (command = "holdback") && (command != "holdfwd") && (command != "holdup") && (command != "holddown")
x = * ;Must be a negative value.
y = 0

[State 9000, PosAddUp]
type = PosAdd
triggerall = Time = *** ;Time to teleport.
trigger1 = (command = "holdup") && (command != "holdfwd") && (command != "holdback") && (command != "holddown")
x = 0
y = * ;Must be a negative value.

[State 9000, PosAddDown]
type = PosAdd
triggerall = Time = *** ;Time to teleport.
trigger1 = (command = "holddown") && (command != "holdfwd") && (command != "holdback") && (command != "holdup")
x = 0
y = * ;Must be a positive value.

[State 9000, PosAddFwdUp]
type = PosAdd
triggerall = Time = *** ;Time to teleport.
trigger1 = (command = "holdfwd") && (command = "holdup") && (command != "holdback") && (command != "holddown")
x = * ;Must be a positive value.
y = * ;Must be a negative value.

[State 9000, PosAddFwdDown]
type = PosAdd
triggerall = Time = *** ;Time to teleport.
trigger1 = (command = "holdfwd") && (command = "holddown") && (command != "holdback") && (command != "holdup")
x = * ;Must be a positive value.
y = * ;Must be a positive value.

[State 9000, PosAddBackUp]
type = PosAdd
triggerall = Time = *** ;Time to teleport.
trigger1 = (command = "holdback") && (command = "holdup") && (command = "holdfwd") && (command = "holddown")
x = * ;Must be a negative value.
y = * ;Must be a negative value.

[State 9000, PosAddBackDown]
type = PosAdd
triggerall = Time = *** ;Time to teleport.
trigger1 = (command = "holdback") && (command = "holddown") && (command != "holdfwd") && (command != "holdup")
x = * ;Must be a negative value.
y = * ;Must be a positive value.

[State 9000, End]
type = ChangeState
trigger1 = AnimTime = 0
value = 0
ctrl = 1

2.) Non-Fixed Teleportation: Teleportation is determined by the opponent's position.
(as an example...)

[Statedef 9000]

[State 9000, PlaySnd]
type = PlaySnd
trigger1 = (whatever)
value = *,*

[State 9000, PosAdd]
type = PosAdd
trigger1 = (whatever)
x = (P2Dist X) + *
y = (P2dist Y) + *

[State 9000, End]
type = ChangeState
trigger1 = AnimTime = 0
value = 0
ctrl = 1

The "+ *" is used, so that your character is given some room away from the opponent, rather
than teleporting at the exact point of where he/she is.

AI Programming Tutorial by FlowaGirl

2007-08-02T14:47:00.000-04:00

========================
AI Programming Tutorial
========================
Author: FlowaGirl
flowergirl@cutey.com
http://blargh.i-xcell.com

---------------------------------------------------------------------------
Programming a character's custom AI is something extra; It's not needed in any
character, but most people seem to want to do it anyway, whether it is to kick
another character's arse, increase the gameplay of the character, or just for
watch mode.
---------------------------------------------------------------------------

When programming an AI, it is recommended that you have completed most of
the character. It will makes things easier, so you won't have to go back and change
anything in the script if you decide to add in more stuff.

Think about the moves for your character; How you want it to use a projectile,
when to guard, and when to attempt to throw the opponent? It's up to you. A well
planned AI is important, as poorly made AI's can end up extremely glitchy.

This example shows how your character will attempt to throw the opponent, only
when it is close to the opponent, and when the opponent is on the floor. I choose
to do the AI programming under StateDef -3, but this can be done under StateDef -2, or
even StateDef -1 of the CMD file.

[State -3: ChangeState]
type = ChangeState
trigger1 = (Var(0) > 0)
trigger1 = (Random <= 499) trigger1 = (StateType != A) && (Ctrl) trigger1 = (P2BodyDist X <= 40) && (P2StateType = S) value = **** The 1st trigger, "(Var(0) > 0)" means that the move can only be read by the AI.
Remember, the AI Activation sets the value of Var(0) to 1.

2nd trigger, "(Random <= 499)" means that the AI will make an attempt to throw the
opponent, but only half the time. This should be used, so your character
is not too predictable.

3rd trigger, is simply used, so that the character can only make the throw attempt
when he is on the ground, (StateType != A) and is able to do so. (Ctrl)

Finally, the 4th trigger, "(P2BodyDist X <= 40) && (P2StateType = S)" means that
the character will throw the opponent, only when the opponent is close, (P2BodyDist X <= 40)
and when the opponent is on the ground as well. (P2StateType = S)

Flying code by Flowagirl

2007-08-01T00:19:00.000-04:00

================================
Flying: Idainaru Densetsu Style
================================
Author: FlowaGirl
flowergirl@cutey.com
http://blargh.i-xcell.com

---------------------------------------------------------------------------
The way flying works in Idainaru Densetsu is very simple; Pressing backward
or downwards on the directional keys move your character away from the
opponent, and forward or up to move towards. Your character will move in a
straight path.
---------------------------------------------------------------------------

The startup state.

[Statedef ****]
type = A
movetype = I
physics = N
anim = ****

[State ****: VarSet]
type = VarSet
trigger1 = (!Time)
var(0) = 1

[State ****: VelSet]
type = VelSet
trigger1 = (Time > 10)
y = -6

[State ****: VelAdd]
type = VelAdd
trigger1 = (Time > 10) && (Time, < y =" 0.40" type =" ChangeState" trigger1 =" (Time"> 30)
value = ***1

The flying state, when character is idle.

[Statedef ***1]
type = A
movetype = I
physics = N
anim = ***1
velset = 0,0
ctrl = 1

[State ***1: Turn]
type = Turn
trigger1 = (P2Dist X < -1)

This NULL is actually used to set a few variables at once, without actually having to use
that many VarSet's.
(Read Elecbyte's documentation on expressions.)

Var(0): The "You're flying" variable. You can use this to call upon when needed, such as
for the CMD file.

Var(1) and Var(2): Used for the floating effect.

[State ***1: Null]
type = Null
trigger1 = (!Time)
trigger1 = (Var(1) := 0) && (Var(0) := 1)
trigger2 = (Var(1) = -10) || (Var(1) = 10)
trigger2 = (Var(2) := IfElse(Var(1) = -10,0,1))

[State ***1: VarAdd]
type = VarAdd
trigger1 = 1
var(1) = IfElse(Var(2) = 0,1,-1)

[State ***1: VelAdd]
type = VelAdd
trigger1 = 1
y = IfElse(Var(2) = 1,0.05,-0.05)

***2 is the moving towards state, and ***3 for away.

[State ***1: ChangeState]
type = ChangeState
trigger1 = (Command = "holdup") || (Command = "holdfwd")
value = ***2

[State ***1: ChangeState]
type = ChangeState
trigger1 = (Command = "holddown") || (Command = "holdback")
value = ***3

Flying towards state.

[Statedef ***2]
type = A
movetype = I
physics = N
anim = ***2
ctrl = 1

This is used to check the position of the enemy, and sets the appropriate values to
move towards him/her.

FVar(0): X velocity
FVar(1): Y velocity

[State ***2: Null]
type = Null
trigger1 = (!Time)
trigger1 = (FVar(0) := (P2Dist X * 8) / (Exp(0.5*ln((P2Dist X * P2Dist X) + (P2Dist Y * P2Dist Y)))))
trigger1 = (FVar(1) := (P2Dist Y * 8) / (Exp(0.5*ln((P2Dist X * P2Dist X) + (P2Dist Y * P2Dist Y)))))

Moves the character, using the variables as reference. You cannot use those expressions
as shown above and put it directly into the VelSet. MUGEN will lock up after this is used
a number of times.

[State ***2: VelSet]
type = VelSet
trigger1 = (Whatever)
x = FVar(0)
y = FVar(1)

Go back to the idle state when commands are released.

[State ***2: ChangeState]
type = ChangeState
trigger1 = (Command != "holdfwd") && (Command != "holdup")
value = ***1

Flying away state.

[Statedef ***3]
type = A
movetype = I
physics = N
anim = ***3
ctrl = 1

Disables air guarding. If you wish to add in air guarding while flying, you can
remove this, then edit the guarding states accordingly, using Var(0) as reference.

[State ***3: AssertSpecial]
type = AssertSpecial
trigger1 = 1
flag = NoAirGuard
ignorehitpause = 1

[State ***3: Null]
type = Null
trigger1 = (!Time)
trigger1 = (FVar(0) := (P2Dist X * 8) / (Exp(0.5*ln((P2Dist X * P2Dist X) + (P2Dist Y * P2Dist Y)))))
trigger1 = (FVar(1) := (P2Dist Y * 8) / (Exp(0.5*ln((P2Dist X * P2Dist X) + (P2Dist Y * P2Dist Y)))))

[State ***3: VelSet]
type = VelSet
trigger1 = (Whatever)
x = (FVar(0)*(-1))
y = (FVar(1)*(-1))

[State ***3: ChangeState]
type = ChangeState
trigger1 = (Command != "holdback") && (Command != "holddown")
value = ***1

Sprite Tutorial by Elecbyte

2007-07-31T12:39:00.000-04:00

The sprite standard
===================
M.U.G.E.N, (c) Elecbyte 2002
Documentation for version 2002.04.14

Updated 26 June 2000

====================================================================
0. Contents
====================================================================

I. Required Sprites
II. Recommended group numbers

====================================================================
I. Required Sprites
====================================================================

Every character must have what is called "required sprites". These are
sprites that you may not necessarily be using for your animations, but
must always be included in the character's SFF. These sprites are
necessary for your character to appear correctly when thrown.

- Use only these standard frames when making a action in the .air file
that characters beside yourself will execute. For example, getting
thrown animation.
- The horizontal component of "Axis" means around the center of the
character, unless specified otherwise

Standard getting hit
--------------------
- You MUST follow the numbers exactly.
- Axes labelled "where feet would be" should have the axis approximately
between where both feet would be, if the character was made to stand
with his center of gravity fixed in the same position as that required
frame
- Axes labelled "midsection" should have the axis around the waist area
- Axes labelled "head" should have the axis in the middle of the
character's head
- Some numbers, such as 5000,1 to 5000,9 are for you to add intermediate
frames if you choose to do so.
- See spr.gif for an example of how the sprites should approximately look
and where the axes should be placed.
- Sprites labeled with an asterisk (*) are the new required sprites that
were added since MUGEN version 2000.06.27.

Frame Description Axis
------- ------------ ----
5000,0 Hit high while standing, head back slightly Feet
5000,10 Hit high while standing, head back more Feet
5000,20 Hit high while standing, head back far Feet
5001,0 Frame 5000,0 Midsection
5001,10 Frame 5000,10 Midsection
5001,20 Frame 5000,20 Midsection
5002,0 Frame 5000,0 Head
5002,10 Frame 5000,10 Head
5002,20 Frame 5000,20 Head
5010,0 Hit low while standing, bent over slightly Feet
5010,10 Hit low while standing, bent over more Feet
5010,20 Hit low while standing, bent over far Feet
5011,0 Frame 5010,0 Midsection
5011,10 Frame 5010,10 Midsection
5011,20 Frame 5010,20 Midsection
5012,0 Frame 5010,0 Head
5012,10 Frame 5010,10 Head
5012,20 Frame 5010,20 Head
5020,0 Hit while crouching, head back slightly Feet
5020,10 Hit while crouching, head back more Feet
5020,20 Hit while crouching, head back far Feet
5030,0 Hit back, head back slightly Where feet would be if standing
5030,10 Hit back, head back far Where feet would be
5030,20 * Hit in stomach with body horizontal Where feet would be
5030,30 * Hit back, body horizontal Where feet would be
5030,40 * Falling, head down slightly Where feet would be
5030,50 * Falling, head down far Where feet would be
5031,0 Frame 5030,0 Midsection
5031,10 Frame 5030,10 Midsection
5031,20 * Frame 5030,20 Midsection
5031,30 * Frame 5030,30 Midsection
5031,40 * Frame 5030,40 Midsection
5031,50 * Frame 5030,50 Midsection
5032,0 Frame 5030,0 Head
5032,10 Frame 5030,10 Head
5032,20 * Frame 5030,20 Head
5032,30 * Frame 5030,30 Head
5032,40 * Frame 5030,40 Head
5032,50 * Frame 5030,50 Head
5040,0 Fall and hitting ground Ground-level (eg. back)
5040,10 Lying down on ground Ground-level
5040,20 * Hit while lying on ground Ground-level
5041,0 Frame 5040,0 Middle of body
5041,10 Frame 5040,10 Middle of body
5041,20 * Frame 5040,20 Middle of body
5042,0 Frame 5040,0 Head
5042,10 Frame 5040,10 Head
5042,20 * Frame 5040,20 Head
5060,0 * Hit up, head pointed up, body vertical Where feet would be if standing
5060,10 * Head pointed down, body vertical Where feet would be
5061,0 * Frame 5060,0 Midsection
5061,10 * Frame 5060,10 Midsection
5062,0 * Frame 5060,0 Head
5062,10 * Frame 5060,10 Head
5070,0 * Thrown, body tiled forwards slightly Where feet would be if standing
5070,10 * Thrown, body tiled forwards far Where feet would be
5070,20 * Thrown, body horizontal, head in front Where feet would be
5071,0 * Frame 5070,0 Midsection
5071,10 * Frame 5070,10 Midsection
5071,20 * Frame 5070,20 Midsection
5072,0 * Frame 5070,0 Head
5072,10 * Frame 5070,10 Head
5072,20 * Frame 5070,20 Head

====================================================================
II. Recommended group numbers
====================================================================

Group Description Comments
------- ------------ --------
0 Standing
5 Turning
10 Stand to crouch
11 Crouching
12 Stand to crouch
20 Walking forwards
21 Walking backwards
40 Jump start (on ground)
41 Jump neutral (upwards)
42 Jump forwards (upwards)
43 Jump back (upwards)
44 Jump neutral (downwards)
45 Jump fwd (downwards)
46 Jump back (downwards)
47 Jump landing
100 Run fwd
105 Hop back
110 Dodge up
115 Dodge down
120 Start guarding (stand)
121 Start guarding (crouch)
122 Start guarding (air)
130 Guard (stand)
131 Guard (crouch)
132 Guard (air)
140 Stop guarding (stand)
141 Stop guarding (crouch)
142 Stop guarding (air)
150 Guarding a hit (stand)
151 Guarding a hit (crouch)
152 Guarding a hit (air)

DBZ: Budokai Tenkaichi 3 for the Wii

2007-07-28T22:06:00.000-04:00

"Go Super Saiyan with the latest DBZ title hitting the Wii and PS2 this November. 150 characters from the DBZ universe are set to square off against each other in battle."

Time Running Out Music Activator by shinra358

2007-07-26T15:52:00.000-04:00

;Of course switch statedef's and music placement numbers where needed although you may not need to-

+current bugs (fix in progress):
-doubled sound on simul mode

+things in question:
-used to not stop specifically on the right time for the activation....roundstate=2 shouldve fixed it so the countdown will go only when fighttime starts
-superpause from hypers should not mess the timing up--really havent noticed yet but may exist *DOES STILL EXIST

the code:

;positive states
[Statedef 3337];time running out
type = s
movetype = i
physics = n

[State 0, ]
type = AssertSpecial
trigger1 = 1
flag = noshadow
flag2 = nomusic
flag3 = invisible

[State 0]
type = NotHitBy
trigger1 = 1
value = SCA

[State 0]
type = PlayerPush
trigger1 = 1
value = 1

[State 0, ]
type = Playsnd
trigger1 = RoundState = 2
trigger1 = Ishometeam
trigger1 = time = 0
value = F333,4; song in common.snd mugen data file
volume = 500
pan = 50
loop = 1
persistent = 0

[State 0, ]
type = Destroyself
trigger1= !alive

[State 0, ];add if using cvspro knockout music code
type = StopSnd
triggerall = (WinKo) && MatchOver = 1
triggerall = Win
triggerall = IsHomeTeam
trigger1 = StateNo = 3337
channel = 21
value = F333,2
persistent = 0

[State 0, ]
type = StopSnd
triggerall = (WinKo) && MatchOver = 1
triggerall = Win
triggerall = IsHomeTeam
trigger1 = StateNo = 3337
channel = 21
value = F333,3
persistent = 0

[state 0, ]
type = changestate
triggerall = (WinKo)
triggerall = Time = 0
trigger1 = stateno = 3337 && !numhelper(3337)
value = 3336
ctrl = 0;end

;==============================================

;****** = Music starts with 160 time left on clock if based on 999 time setting and framespercount 8 setting in fight.def file
;negative states
[State -2];time running out music
type = helper
trigger1 = Time > 110 * TicksPerSecond && !numhelper(3337);*****
;trigger1 = (GameTime%7150)=0 && !numhelper(3337)
helpertype = Normal
name = "time running out"
id = 3337
pos = 0,9000
stateno = 3337
supermovetime = 99999
pausemovetime = 99999

WinKO Effects by Flowagirl

2007-07-25T10:07:00.000-04:00

===============
WinKO Effects
===============
Author: FlowaGirl
flowergirl@cutey.com
http://blargh.i-xcell.com

---------------------------------------------------------------------------
In many games now, there is usually a special effect that occurs when you
have knocked out the opponent, eg. a special background effect if you have
finished the opponent with a hyper move.
---------------------------------------------------------------------------

Now, we're going to use a helper to create the WinKO effect. With a helper,
you can neatly program everything in that state, and prevents any bugs such
as repeated effects.

Insert this under StateDef -2/-3. If you want this to trigger only when you have knocked
out the opponent with a special/hyper move, you can add in the appropriate triggers to
do so, such as, "StateNo = 3000"

[State -2: Helper]
type = Helper
trigger1 = (WinKO) && (NumHelper(****) = 0)
helpertype = Normal
name = "WinKO"
id = ****
pos = 0,0
postype = p1
facing = 0
stateno = ****
keyctrl = 0
ownpal = 1
supermovetime = 1000
pausemovetime = 1000
ignorehitpause = 1

Next, the helper's state:

[Statedef ****]
type = S
movetype = I
physics = N
anim = **** ;Invisible anim.

This is where you may add in flashy effects, explods, or sounds. This particular example is
a simple black out effect, that gradually fades the screen back to normal.

This pauses the effect for a moment.

[State ****: Pause]
type = Pause
trigger1 = (!Time)
time = 12
movetime = 12

This darkens the background for 12 ticks. It gradually goes bright during the time.

[State ****: EnvColor]
type = EnvColor
trigger1 = (Time < 12)
value = (Time*4),(Time*4),(Time*4)
time = 1
under = 1

This causes the screen to shake a bit.

[State ****: EnvShake]
type = EnvShake
trigger1 = (!Time)
time = 12
freq = 120
ampl = -3
phase = 90

And this is causes the characters and the stage to lose their colour, only to be gradually
brought back as the black out ends.

[State ****: AllPalFX]
type = AllPalFX
trigger1 = (Time < 50)
time = 1
add = 0,0,0
mul = 256,256,256
sinadd = 0,0,0,1
invertall = 0
color = (Time*5)

You don't need a DestroySelf in this code, as the helper is removed when the round ends, so I'll leave it
out.

Smallville's Supergirl!

2007-07-23T16:25:00.000-04:00

There's gonna be a lot more progression in the series, as I believe the show only has about 2 more seasons in it... but next season, we will see Supergirl as well as more of the Justice League. Kara will be played by Canadian Laura Vandervoort. What do you think?

Wall Jump by Flowagirl

2007-07-14T04:47:00.000-04:00

==========
Wall Jump
==========
Author: FlowaGirl
flowergirl@cutey.com
http://blargh.i-xcell.com

---------------------------------------------------------------------------
Certain characters have this unique ability, to jump off the
sides of the screen. Some creators use special states to
accomplish this. I just use the regular jump. =P
---------------------------------------------------------------------------

All you need is 2 things. First, the command to jump off the wall. Insert this
in your character's CMD file:

[State -1: ChangeState]
type = ChangeState
value = 40
triggerall = (StateType = A) && (Ctrl) && (Pos Y < -30) trigger1 = ((command = "holdup") && (command = "holdfwd") && (Vel X <= 0) && (backedgebodydist <= 10) && (backedgebodydist > -10))
trigger2 = ((command = "holdup") && (command = "holdback") && (Vel X >= 0) && (frontedgebodydist <= 10) && (frontedgebodydist > -10))
persistent = 0

The 2nd thing to add is a controller, to tell Mugen that your character is in the air
during the jump start, to prevent a float bug if hit.

[State -1: StateTypeSet]
type = StateTypeSet
trigger1 = (StateNo = 40) && (Pos Y < 0)
statetype = A

If you want to use a custom anim to jump off the wall, you can add this as well.

[State -1: ChangeAnim]
type = ChangeAnim
trigger1 = (StateNo = 40) && (Pos Y < 0) && (!Time)
value = ****

Kof evade system by Flowagirl

2007-07-12T00:38:00.000-04:00

======
Evade
======
Author: FlowaGirl
flowergirl@cutey.com
http://blargh.i-xcell.com

---------------------------------------------------------------------------
This is KOF's evade system, where your character roll/slides forward,
dodging most attacks. You can also use this ability to go behind your opponent
if he/she is close enough to you.

The speed and duration of this move varies from character, so it's recommended
that you adjust those 2 attributes.
---------------------------------------------------------------------------

This is a generic evade state for moving forward, but you can also create
another state for moving back if you want.

[Statedef ****]
type = S
movetype = I
physics = N
anim = ****
velset = 0,0
ctrl = 0
poweradd = 0
juggle = 0
facep2 = 0
hitdefpersist = 0
movehitpersist = 0
hitcountpersist = 0
sprpriority = 0

If you want the character to go behind the opponent as he/she moves passes it,
add in this piece.

[State ****: SprPriority]
type = SprPriority
trigger1 = (Vel X != 0)
value = -2

This is used for the temporary invulnerability during this move. The character
can only be hit by throws. This invulnerability varies from character to character.

[State ****: NotHitBy]
type = NotHitBy
trigger1 = (Time < value =" ," time =" 5" type =" VelSet" trigger1 =" (Time" x =" *" type =" VelSet" trigger1 =" (Time" x =" 0" type =" PlayerPush" trigger1 =" (Vel" value =" 0" type =" AfterImage" trigger1 =" (Vel" time =" 25" timegap =" 2" framegap =" 4" length =" 15" paladd =" 0," palmul =" .50," palcontrast =" 100,100,100" trans =" add" persistent =" 0" type =" SuperPause" triggerall =" (!Time)" trigger1 =" (PrevStateNo" prevstateno =" 152)" time =" 10" anim =" ****" pos =" *,*" movetime =" 0" darken =" 1" poweradd =" -1000" unhittable =" 1" type =" EnvColor" triggerall =" (!Time)" trigger1 =" (PrevStateNo" prevstateno =" 152)" value =" 255,255,255" time =" 2" under =" 1" type =" ChangeState" value =" ****" triggerall =" (Command" trigger1 =" (StateType" trigger2 =" ((StateNo" stateno =" 152))">= 1000) ;Add this new trigger!

And in the CNS file... the move has ended.

[State ****: ChangeState]
type = ChangeState
trigger1 = (AnimTime = 0)
value = 0
ctrl = 1

Marvel Vs Capcom for MAME on PS3 linux

2007-06-24T23:08:00.000-04:00

...

Captain America Movie After Next Hulk Movie

2007-06-16T17:44:00.000-04:00

From Marvel's President of Production, Kevin Feige... after The Incredible Hulk, the next Marvel film will be Captain America! “Well I think we'll certainly have to play with that and play with Captain America being this patriotic propaganda machine on one hand but also being a very human Steve Rogers – interesting, fascinating hero in his own...

Fatality Tutorial by Equinócio [part 2]

2007-06-14T16:31:00.000-04:00

==========================================================

2Âº Example: Brutality
---------------------

We will now see a model of Brutality or any another sequence of blows.
As in the first example, you it will not need to around place boxes of collision
of the personage. The only difference is that the blow will be divided in two parts.
The first one is when char runs or walks in direction to the opponent to execute
the blow and the second part is when a series of blows occurs.

If to want, can place some animation that will appear in the place of P2
when it to die. This animation can be a Helper. In our example, we will place
a blood burst to substitute the figure of P2 in the game.

To make the first part, it is enough that you it copies animation 20 or 100 that
he is in the archive "common1.cns", located in the folder "data" of the MUGEN.
Later it places it in a different State.

It observes the example:

==============================
Brutality - part 1

The personage runs in direction to the opponent.
-> 3199 are an imaginary number that does not exist in the AIR.
[Statedef 3199]
type = S
movetype= A
physics = S
juggle = 1
anim = 100
velset = 0,0
ctrl = 0

;Constant speed.
[State 3199, 1]
type = VelSet
trigger1 = 1
x = const(velocity.run.fwd.x)

;It will not be interrupted by the walked one, in case that it is running.
[State 3199, 2]
type = AssertSpecial
trigger1 = 1
flag = NoWalk

;One does not turn over during the race.
[State 3199, 3]
type = AssertSpecial
trigger1 = 1
flag = NoAutoTurn

;Sound touched at the moment(optional).
[State 3199, 4]
type = PlaySnd
trigger1 = time = 1
value = 1,4

;When the personage is to less than 15 pixels of the opponent,
;it modifies of state and starts the session of blows.
[State 3199, 5]
type = ChangeState
trigger1 = P2BodyDist X <= 15
value = 3200
ctrl = 0

In the second part you it will have to create a great animation that contains
all the movements of char, but does not place no box of colisÃ£o(Clsn1 or Clsn2)
in sprites. Exactly that she is enormous and stranger, leaves as is.
This is only one technique. It has another one that consists of placing each
sprite in a different animation, but already is more laborious there and what
we want it is to simplify.

==============================
Brutality - part 2

The personage executes the sequence of blows.
-> 3200 are the animation where char it executes the blows.
[Statedef 3200]
type = S
movetype= A
physics = S
juggle = 1
anim = 3200
velset = 0,0
ctrl = 0

;Burst of blood that appears in the place of P2 in one determined time.
[State 3200, 1]
type = Helper
trigger1 = AnimElem = 63
trigger1 = NumHelper(3210) = 0 ;It cannot have Helper as this in the screen.
ID = 3210
pos = 0,0
postype = P2
facing = 1
stateno = 3210
helpertype = normal
name = "Burst"
keyctrl = 0
sprpriority >= -2

;Screen becomes gloomy(optional).
[State 3200, 2]
type = BGPalFX
trigger1 = AnimElem = 10
time = 99999
add = 0,0,0
mul = 0,0,0

If to want, places a PlaySnd.
The sound will be touched always that its to char to make a movement that
supposedly the opponent hits in case that he had Clsn1 in the animation.
In case that you it makes the screen to tremble(EnvShake) or uses animaÃ§Ãµes
of blood(VarRandom), the procedure is the same.

[State 3200, 3]
type = PlaySnd
triggerall = p2bodydist X <= 16
trigger1 = AnimElem = 2
trigger2 = AnimElem = 4
trigger3 = AnimElem = 7
trigger4 = AnimElem = 12
trigger5 = AnimElem = 16
trigger6 = AnimElem = 21
trigger7 = AnimElem = 23
trigger8 = AnimElem = 25
value = 0,6

;Stand comes back.
[State 3200, 4]
type = ChangeState
trigger1 = AnimTime = 0
value = 0
ctrl = 1

-----------------------------------
;Helper that substitutes P2 in the end of the Brutality.
[Statedef 3210]
type = S
movetype= A
physics = S
juggle = 1
velset = 0,0
anim = 3210
ctrl = 0

[State 3210, 1]
type = Helper
trigger1 = NumHelper(3210) = 0
ID = 3210
pos = 0,0
postype = P2
stateno = 3210
helpertype = normal
name = "Burst"
keyctrl = 0
sprpriority >= -2

[State 3210, 2]
type = Destroyself
trigger1 = AnimTime = 0

----------------------------------------------------------------------
;Custom State for where P2 is sent.
[Statedef 52000]
type = S
movetype= H
physics = S
juggle = 1
velset = 0,0
ctrl = 0

A drawing between animation 5000 and 5001 will occur.
The drawing will be made to each 10 ticks not to be very fast
while P2 is being hit.

[State 52000, 1]
type = VarRandom
trigger1 = (GameTime%10) = 0
trigger1 = Time >= 3
v = 10
range = 1,2

;Being hit
[State 52000, 2]
type = ChangeAnim
trigger1 = var(10) = 1
trigger1 = Time >= 3
value = 5000

;Being hit - 2
[State 52000, 3]
type = ChangeAnim
trigger1 = var(10) = 2
trigger1 = Time >= 3
value = 5001

;Life goes the 0(zero) when to arrive at one definitive time.
[State 52000, 4]
type = LifeSet
trigger1 = Time >= 298
value = 0

;Change of position and one another animation can appear in the place.
;That one shown above and that it will substitute P2.
[State 52000, 5]
type = PosSet
trigger1 = Time >= 298 ;Helper will appear at the same moment.
y = 1500

;It does not cry out in the end(optional). You do not go to want the opponent
;crying out at the same time that she blows up.
[State 52000, 6]
type = AssertSpecial
trigger1 = 1
flag = nokosnd

;He comes back to its proper CNS.
[State 52000, 7]
type = SelfState
trigger1 = Time >= 300 ;P2 will come back to its proper CNS, but already died.
value = 5150

To finish the code, it opens the CMD and it types the command referring
the execution of the Brutality. It follows the model that was placed more above.

-> You must place the regarding command the first part of the Brutality.
The blow was divided in two parts - 3199 and 3200. It places the command
only for first part - 3199. Thus, the personage will go to run and to
start the sequence.

-> In state where P2 is dizzy with chronometer(State 49999), adds a
ChangeState(that already it was commented before). Trigger must be in relation
the second part of the Brutality. "trigger1 = P2StateNo = 3200".

======================================================================

3Âº Example: Pit-Fatality
------------------------

You must catch or create a great screen with the dimensions
standards of MUGEN - 320 x 240. It is not norm, but the objective is to cover
all the screen.

You can use the same animation of the Uppercut(Hook) of its char to make the blow.
The opponent will be sent the Custom State at the same moment of the blow and will
suffer a vertical acceleration until disappearing of the screen.
When it to come back to appear, the screen of the Pit-Fatality already will
have to be present. Places it as Helper.

It observes the example:

;This is the animation where the personage executes the "hook".
[Statedef 3300]
type = C
movetype= A
physics = C
juggle = 1
ctrl = 0
anim = 3300
velset = 0,0

In one determined moment, when P2 leaves the scene, its personage disappears and
goes for a distant position. A bit before the screen of the Pit-Fatality appearing.
Compares the times.

[State 3300, 1]
type = PosSet
trigger1 = Time = 53
y = 1000

;P1 does not have shade.
[state 3300, 2]
type = AssertSpecial
trigger1 = Time >= 53
flag = noshadow

;Screen of the Pit-Fatality.
[State 3300, 3]
type = Helper
trigger1 = NumHelper(3310) = 0 ;It cannot have Helper as this in the screen.
trigger1 = Time >= 55
ID = 3310
pos = 160,-120
postype = left
stateno = 3310
helpertype = normal
name = "Screen"
keyctrl = 0
sprpriority >= -2

;Its personage will be in the same pose of "hook" until P2 to die.
[State 3300, 4]
type = ChangeState
trigger1 = P2Life = 0
value = 0
ctrl = 1

-----------------------------------
;Helper: Screen
[Statedef 3310]
type = S
movetype= A
physics = S
juggle = 1
velset = 0,0
anim = 3310
ctrl = 0

[State 3310, 1]
type = Helper
trigger1 = NumHelper(3310) = 0
ID = 3310
pos = 160,-120
postype = left
stateno = 3310
helpertype = normal
name = "Screen"
keyctrl = 0
sprpriority >= -2

[State 3310, 2]
type = Destroyself
trigger1 = AnimTime = 0

-------------------------------------
-> Custom State for where P2 is sent. When the life of P2 will be 0 (zero),
at the same time where it goes for a distant position and it is invisible, perhaps,
as suggestion, it it blows up in many pieces, as well as in the Brutality.
To if shocking with many metal thorns. The reasoning in the Custom State will be this.
If it only wants that it is stuck in the thorns and dies, obviously does not need
to make it to be invisible and to order it it a distant position.

[Statedef 53000]
type = S
movetype= H
physics = S
juggle = 1
velset = 0,0
ctrl = 0

;Without shade.
[state 53000, 1]
type = AssertSpecial
trigger1 = 1
flag = noshadow

;Camera does not follow P2 leaving the screen.
[State 53000, 2]
type = ScreenBound
trigger1 = 1
value = 0
movecamera = 0

;Taking Collision - animation of P2 to the hit being.
[State 53000, 3]
type = ChangeAnim
trigger1 = 1
value = 5030

;Speed - when P2 is leaving the screen.
;If to want to place VelSet, the choice is its.
[State 53000, 4]
type = VelAdd
trigger1 = time = [9,40]
y = -0.3

;Speed - P2 appears again in the screen.
[State 53000, 5]
type = VelAdd
trigger1 = time >= 40
y = 0.3

;Life goes 0(zero) at one definitive moment of the fall.
[State 53000, 6]
type = LifeSet
trigger1 = time = 115
value = 0

;Change of position when Life = 0
[State 53000, 7]
type = PosSet
trigger1 = Time = 115
y = 1500

;Opponent is invisible when Life = 0.
[State 53000, 8]
type = AssertSpecial
trigger1 = Life = 0
flag = invisible

;He does not cry out in final(optional).
[State 53000, 9]
type = AssertSpecial
trigger1 = 1
flag = nokosnd

;Come back to its proper CNS when Pos Y = 1000
[State 53000, 10]
type = SelfState
trigger1 = Pos Y = 1000
value = 5150

-> In state where P2 is dizzy with chronometer(State 49999),
adds a ChangeState(that already it was commented before).

It tries to make the everything most accurate possible in the Pit-Fatality.
In rare cases, part of stage appears. To diminish this bug, I suggest that
it modifies the resolution of the screen (Helper) of 320 x 240 for 350 x 260,
for example, and add this in State -2.

[State -2, Deep It Disappears]
type = BGPalFX
trigger1 = NumHelper(3310) = 1
time = 99999
add = 0,0,0
mul = 0,0,0

When the screen of the Pit-Fatality to appear, the scene will be dark.
Thus, stage will not appear.

======================================================================

;Messages after "fatality":
;--------------------------

Case you wants to place a final message(Fatality, Brutality...) after the blow,
is only enough to make a Helper. This code can be placed in our "Fatality.cns",
but I suggest that it places the Helper in state of the victory pose.
The voice of Shao Kahn can be placed in any one of states. Here or there.
The counting of the time alone depends on state.

;"FATALITY" - MSG
[Statedef 7100]
type = S
movetype= I
physics = S
juggle = 1
velset = 0,0
anim = 7100
ctrl = 0

;"FATALITY" will not have shade while it will be in the screen.
[state 7100, 1]
type = AssertSpecial
trigger1 = 1
flag = noshadow

;The message must appear above of everything in the scene, even though of
;its personage in victory pose(in accordance with the norms in MK).
[State 7100, 2]
type = SprPriority
trigger1 = 1
value = 5

;Helper of the "FATALITY" - MSG
[State 7100, 3]
type = Helper
trigger1 = NumHelper(7100) = 0 ;It cannot have message "FATALITY" in the screen.
ID = 7100
stateno = 7100
pos = 160,-110
postype = left
helpertype = normal
name = "FATALITY"
keyctrl = 0
sprpriority >= -2

Analyzing trigger of the Helper, you it will perceive that it cannot be destroyed.
For this, in the animation of the AIR, it places a line with infinite time.
As well as it was made for message "FINISH HIM".

-----------------------------------------------------------------------------------------------
Gratefulness:

- God: for giving the chance to me to learn on MUGEN and fatalities.

- Chon Wang: for teaching to the beddings and techniques to me on fatalities.
Many codes of this tutorial originally had been made by it.

- To the many creators whose works in MK I consulted to make the tutorial
and to mount the examples seen here.

-----------------------------------------------------------------------------------------------

I wait that the rial o assists during the creation of fatalities.

If it will have some doubt, informs for email.

Good Luck,

Equinócio.

Fatality Tutorial by Equinócio [part 1]

2007-06-13T16:29:00.000-04:00

=================================
= --------------------------------------- =
= Fatality Tutorial =
= by: Equinócio - 07/13/2004 =
= Modified in - 10/29/2005 =
= --------------------------------------- =
= site: http://2dgraphic.tripod.com =
= e-mail: igyur@yahoo.com =
= --------------------------------------- =
=================================

WARNING:
-----------------------------------------------------------------------------------------------
- This tutorial aims at the aid to create terminating blows in MUGEN,
between them fatalities, brutalities, pit-fatalities...

- If this tutorial the assistant in some way, I ask for that it does not place my
name in place some form of gratefulness.

- If you to want can place this tutorial in its site. It does not need to ask for to me.

- I made small modifications in tutorial in 10/29/2005. I added some Sctrls and I more
clearly tried to be in the explanations.

- This tutorial is recommendable for people who already dominate the MUGEN,
its language, Sctrls, Triggers, archives(CNS, CMD, AIR...).

-----------------------------------------------------------------------------------------------

Introduction:
-------------

When if it speaks in fatalities, the first thing that comes the head is MK(Mortal Kombat).
What you it will learn is valid any to char, independent of which game is. However,
during elapsing of tutorial, MK more will be focused to facilitate the understanding.
Let us make everything step by step to understand the mechanism of fatalities.

======================================================================================
Mounting the codes:
-------------------

AIR:

Let us start speaking of "FINISH HIM!"

First you must create an invisible animation, in the AIR,
that encloses all the screen of the game, with Clsn1. Our Helper future.

; "FINISH HIM!" - Invisible Helper
[Begin Action 7000]
Clsn1: 1
Clsn1[0] = -320,480,320,-480
-1, 0, 0, 0, -1

After this, to obtain the sprites of message "FINISH HIM" e places them in the SFF.
After that, to make its animation in the AIR. If you do not possess no message
to place at the moment of "fatality", you can jump this part.
The animation must be thus.

; "FINISH HIM!" - MSG
[Begin Action 7010]
7010, 0, 0, 0, 4,
7010, 1, 0, 0, 4,
7010, 2, 0, 0, 4,
7010, 3, 0, 0, 65,
.
.
.
-1, 0, 0, 0, -1,

-> Later I explain the reason of the line with infinite time.

======================================================================================
CNS:

1Âº step:
--------

Important states will be placed in the CNS.
For the good functioning of fatalities.

I advise, for an organization question, to type this in one another
archive CNS with name "Fatality", for example. Everything what will be said
on CNS will be interpreted as if was being placed in the archive "Fatality.cns".
It will be informed when it will be for working in the main CNS.

One remembers that invisible animation that you made in the AIR and that it
affects all the screen? You state for it will make one now.
It observes what it follows ahead.

Invisible Helper that will appear when to arrive close to the end of the fight:

Its personage calls the Helper in this instant.
;-> 10000 are an imaginary number that does not exist in the AIR.
[StateDef 10000]
type = S
movetype= I
physics = S
juggle = 1
velset = 0,0
ctrl = 1

;Invisible Helper that will make P2(opponent) is dizzy.
[State 10000, 1]
type = Helper
trigger1 = 1
trigger1 = NumHelper(7000) = 0 ;another Helper cannot exist as this in the screen.
ID = 7000
stateno = 7000
pos = 160, -140
postype = left
helpertype = normal
name = "FINISH HIM!"
keyctrl = 0
ownpal = 1

[State 10000, 2]
type = ChangeState
trigger1 = AnimTime = 0
value = 0
ctrl = 1

-------------------------------------
This is the HitDef for the Helper bred above.

[StateDef 7000]
type = S
movetype = A
physics = S
anim = 7000
velset = 0,0
ctrl = 1

;Affecting all the screen.
[State 7000, 1]
type = HitDef
trigger1 = AnimElem = 1
trigger1 = P2StateType != A
attr = S, SA
damage = 0,0
animtype = Heavy
hitflag = MF
guardflag = A
priority = 7
pausetime = 0,3
sparkxy = 0,0
sparkno = -1
gurad.sparkno = -1
hitsound = -1
guardsound = -1
ground.type = High
ground.slidetime = 0
ground.hittime = 0
ground.velocity = 0
air.velocity = 0
air.fall = 1
fall = 0
numhits = 0
p2stateno = 49999 ;P2 will go for this state after to be affected by the Helper.

-> This Helper cannot be destroyed.

-------------------------------------
This is the Helper of the animation of "FINISH HIM!"(message) that you made.
It will appear when P2 is dizzy. If you do not possess no message to place at
the moment of "fatality", you can jump this part.

He places it in [StateDef 10000], more above. Together with the invisible Helper.

;"FINISH HIM!" - MSG
[Statedef 7010]
type = S
movetype= I
physics = S
juggle = 1
velset = 0,0
anim = 7010
ctrl = 0

;Voice of Shao Kahn(optional).
[State 7010, 1]
type = PlaySnd
trigger1 = Time = 1
value = 3,3

;"FINISH HIM!" it will not have shadow while it will be in the screen.
[state 7010, 2]
type = AssertSpecial
trigger1 = 1
flag = noshadow

;The message will appear above of all the elements of the screen(scene, lifebars, chars...)
[State 7010, 3]
type = SprPriority
trigger1 = 1
value = 5

;Helper do "FINISH HIM!" - MSG
[state 7010, 4]
type = Helper
trigger1 = NumHelper(7000) = 1 ;It must have a Helper that makes P2 is dizzy in the screen.
trigger1 = NumHelper(7010) = 0 ;It cannot have message "FINISH HIM!" in the screen.
trigger1 = P2StateNo = 49999 ;P2 must be in this state it message to appear.
id = 7010
stateno = 7010
pos = 160, -140
postype = left
helpertype = normal
name = "FINISH HIM! - MSG"
keyctrl = 0

-> Analyzing triggers of the Helper, you it will perceive that it cannot be destroyed.
It was therefore that more above(animation in the AIR) a line with infinite time was placed.

-------------------------------------
2Â° step:
--------

Now you it will place a Custom State for where P2 will be sent the Helper after to appear.
It observes that the number of this state the same is placed in the HitDef of the
invisible Helper(7000: P2StateNo = 49999).

;Dizzy(before one fatality, with chronometer).
[Statedef 49999]
type = S
movetype= H
physics = S
juggle = 1
ctrl = 0
velset = 0,0

;Enemy will be with life equal the 1.
[State 49999, 1]
type = LifeSet
trigger1 = 1
value = 1

;Its personage gains a little more than energy to prevent an equal result.
[State 49999, 2]
type = TargetLifeAdd
trigger1 = P2life <= 1
value = 1

;After 480 ticks without having fatality, P2 falls.
[State 49999, 3]
type = SelfState
trigger1 = Time = 480
trigger1 = P2StateNo != [3000,3200] ;It places here the numbers of states of fatalities.
value = 5050
ctrl = 0

;After 480 ticks without having fatality, P2 is died.
[State 49999, 4]
type = LifeSet
trigger1 = Time = 480
trigger1 = P2StateNo != [3000,3200]
value = 0

;Enemy is dizzy.
[State 49999, 5]
type = ChangeAnim
trigger1 = AnimExist(5300)
trigger1 = Anim != 5300
value = 5300

-------------------------------------
3Â° step:
--------

Now, it opens the main CNS. You it will place important "States -2" in it.

To make them, you it will have to place a Var of high value,
so that it is not extinguished between rounds. Let us catch as example Var(58).
It changes the value of the IntPersistIndex parameter of the CNS.
If in the example to var he is 58, moves for 57.
Making this it will not extinguished between rounds.

[Statedef -2]

;This VAR will be set in motion when one round previous will be gained.
[State -2, 1]
type = varset
trigger1 = Win = 1
trigger1 = NumHelper(7000) = 0 ;Invisible Helper that makes the opponent is dizzy.
v = 58
value = 1

;When the enemy is deceased, it erases.
[State -2, 2]
type = varset
trigger1 = Win = 1
trigger1 = NumHelper(7000) = 1
trigger1 = p2life != 0
v = 58
value = 0

;When P2 will be with 1 of energy, it is died with any blow.
[State -2, 3]
type = AttackMulSet
triggerall = !Var(58)
triggerall = p2Life <= 1
trigger1 = Win = 0
trigger1 = RoundNo != 1
trigger2 = P2StateNo = 49999
value = 9999

;This state is optional, but I suggest that it places it to have a notion of the
;distance between P1 and P2. It will appear in debug during the game.
[State -2, 4]
type = DisplayToClipBoard
trigger1 = 1
text = "P2BodyDist X %f, P2BodyDist Y %f, Var(58) = %d"
params = P2BodyDist x, P2BodyDist y, Var(58)

-------------------------------------
It adds this code in the HitDefs and Projectiles of the personage,
with exception of the Fatalities:

kill = !var(58) || 1*p2stateno = 49999

What it will occur when life of the opponent the 1 is equal:

- Opponent will die if you did not win one round before or if it will be is dizzy.
- It prevents that the adversary is died before FINISH HIM.

======================================================================================

CMD

1Âº step:
--------

Now it comes the part of the CMD. In it you it will place the necessary commands for the execution of fatalities.

This command will call the invisible Helper when P2 will be with equal life the 1.
Everything is automatic. You do not need to type command.

[State -1]
type = Changestate
trigger1 = Ctrl ;It must have the control.
trigger1 = P2Life <= 1 ;Life of P2 must be equal the 1.
trigger1 = NumHelper(7000) = 0 ;It cannot have another Helper as this in the screen.
trigger1 = P2StateNo != 49999 ;Opponent cannot be in Custom State.
trigger1 = RoundNo != 1 ;Round cannot be the first one.
trigger1 = var(58) >= 1 ;You must be to win one round before.
trigger1 = statetype != A ;P1 cannot be in air.
trigger1 = p2statetype != A ;P2 also not.
value = 10000

This must be placed before any routine of the personage.
In the top, below of [Statedef -1].
If you it made Artificial Intelligence to char, places this ChangeState
above of the routines of it. This procedure is not norm,
but it increases the probability of the Helper to be called in the end of the fight.

EX.: Artificial Intelligence

trigger46 = command = "cpu_46"
trigger47 = command = "cpu_47"
trigger48 = command = "cpu_48"
trigger49 = command = "cpu_49"
trigger50 = command = "cpu_50"
v = 59
value = 1

(It places here the command that will call the invisible Helper)

------------------------------

2Â° step:
--------

Fatality to be executed must have parameters as the shown ones below, in the CMD.

[State -1, Fatality]
type = Changestate
trigger1 = Ctrl ;It must have the control.
trigger1 = P2Life = 1 ;Life of the opponent must be equal the 1.
trigger1 = NumHelper(7000) = 1 ;It must have at least 1 invisible Helper in the screen.
trigger1 = P2StateNo = 49999 ;Opponent must be in this state.
trigger1 = RoundNo != 1 ;Round cannot be the first one.
trigger1 = var(58) >= 1 ;You must be to win one round before.
trigger1 = command = "FATALITY" ;It places the command to execute fatality.
trigger1 = statetype != A ;P1 cannot be in air.
trigger1 = p2statetype != A ;P2 also not.
value = 3000

-> If you to want, uses another parameter as "P2BodyDist X <= 50", for example.
You can use the language of "&&" not having that to type as much "trigger1".

===============================================================================================

Making Fatalities:
------------------

-> We go to come back to work with the archive "Fatality.cns".

Basic types of fatalities exist that we can use as example:

1Âº Example:
-----------

The first example that we will analyze will be fatality where a Helper appears in
the place of P2. This method consists of ordering the opponent the Custom State.
It will be in it where P2 will lose the life. In this example it does not have
necessity of boxes of collision(Clsn1 or Clsn2) for its personage, nor for the Helper.
This model will serve for Fatality, Babality, Animality or any another finishing
where he appears something or somebody in the place it its personage or opponent it.

======================================================================
Here you it will place the animation where char it makes the movement to give fatality,
but in it it will only be the Helper.

[Statedef 3000]
type = S
movetype= A
physics = S
juggle = 1
velset = 0,0
anim = 3000 ;-> The personage makes the movement to give fatality.
ctrl = 0

;This is the Helper that will appear in the place of P2.
[State 3000, 1]
type = Helper
trigger1 = Time = 49
trigger1 = NumHelper(3010) = 0 ;It cannot have Helper as this in the screen.
ID = 3010
stateno = 3010
pos = 0,0
postype = P2
helpertype = normal
name = "Helper"
keyctrl = 0
sprpriority >= -2

;Screen is dark(optional).
[State 3000, 2]
type = BGPalFX
trigger1 = Time >= 63
time = 99999
add = 0,0,0
mul = 0,0,0

;Sound touched at the moment(optional).
[State 3000, 3]
type = PlaySnd
trigger1 = time = 1
value = 3,4

;Stand comes back.
[State 3000, 4]
type = ChangeState
trigger1 = AnimTime = 0
value = 0
ctrl = 1

-----------------------------------
;This is the Helper that will be called and that it was placed in state above.
[Statedef 3010]
type = S
movetype= A
physics = S
juggle = 1
velset = 0,0
anim = 3010
ctrl = 0

[State 3010, 1]
type = Helper
trigger1 = NumHelper(3010) = 0
ID = 3010
pos = 0,0
postype = P2
stateno = 3010
helpertype = normal
name = "Helper"
keyctrl = 0
sprpriority >= -2

[State 3010, 2]
type = Destroyself
trigger1 = AnimTime = 0

-----------------------------------
;Custom State for where P2 is sent.
[Statedef 51000]
type = S
movetype= H
physics = S
juggle = 1
velset = 0,0
ctrl = 0

;Enemy exchange of position and "disappears" of the screen.
[State 51000, 1]
type = PosSet
trigger1 = time > 62
y = 1000

;Opponent does not have shadow.
[state 51000, 2]
type = AssertSpecial
trigger1 = 1
flag = noshadow

;Life goes the zero.
[State 51000, 3]
type = LifeSet
trigger1 = time >= 63
value = 0

;Enemy it comes back to its proper CNS, however it continues in the position Y = 1000.
[State 51000, 4]
type = SelfState
trigger1 = life = 0
value = 5150

-----------------------------------
Two Sctrls important:

-> It adds this Sctrl in state where P2 is dizzy with chronometer.
Custom State for where P2 is sent the Helper after to appear.
In our tutorial one it is the State of number 49999.

[State 49999, Change]
type = ChangeState
trigger1 = P2StateNo = 3000 ;-> State of fatality.
value = 51000 ;-> Custom State for where P2 is sent.
ctrl = 0

When executing the command of fatality, its char(P1) will go for the State of fatality.
When this to happen, P2 will go immediately to the Custom State of fatality that
he is being executed. There it will lose the life, will disappear of the screen...

-> If you it will be playing in the Team way, it can happen of its partner or
the partner of its opponent to interrupt fatality.
To prevent this problem, It uses NotHitBy in the Custom States of fatalities.
This does not finish for complete with the problem, but aid very.

[State 51000, NotHitBy]
type = NotHitBy
trigger1 = 1
value = SCA

-> It places this Sctrls in all the terminating blows.

The example above also can be applied to the blows below.

Babality:
---------
You it will have that to create or to catch a figure standard of a child and
places it as Helper. The Custom State for where P2 will be sent is seemed.
When it to disappear of the screen and to lose the life, child(Helper)
appears in the place.

Opponent it not to cry out in the end, at the same time where I cry it of the child appears,
he adds this in the Custom State de P2.

[State 51000, Without crying out]
type = AssertSpecial
trigger1 = 1
flag = nokosnd

Animality:
----------
It follows project the same, but the difference is that, as its personage if transforms
into an animal, it also it will have to disappear of the screen during the
transformation and the blow. It tries to use it its to char the Sctrl PosSet,
as well as you used in the Custom of the opponent. Example of Custom State can be
used the same above. The animal could be a Helper. When the blow to finish,
its personage will come back to the same place of before. But it takes care with the
gone time of and coming for its personage.

FriendShip:
-----------
The Custom State sends P2 and, in this Custom, it makes the life of the
opponent to go the zero(Sctrl LifeSet). In SelfState it places animation
0(stand) or 5300(dizzy). The result of this is that P2 will be in same foot
later that its life will be zero. The inconvenience is that the MUGEN will
delay a little to finish the fight and to close the scene.

"Blades": One fatality where the enemy is cut in some parts.
------------------------------------------------------------
For this you can create one box black(Helper) that she appears in the place of
P2 and the parts where it is cut.

It makes its Helper to have maximum priority on P2, being used this Sctrl.

[State 3400]
type = SprPriority
trigger1 = 1
value = 5

If to want that the parts of the body of P2 are plays in the soil, then will have
that to create or to catch a body of a man used standard to be as substitute.
I suggest that this model is a half-naked man, not to have contrast of clothes with
other personages. Here, more of the one than in the other blows, I advise to use
the Sctrl BGPalFX to darken the scene. I say this so that it does not appear
one box black and rectangular in full scene. He would be very strange.

Making characters chibi sized by †Rain†

2007-06-12T16:00:00.000-04:00

If you want your big ol char to be a bit smaller just go into the cns and change the size of the x and y scale and it would normally say 1.0 if you want them bigger add more points to it like 1.1, 1.2, 1.8.... 2.0... and if you wanna make them smaller just do the opposite like 0.9, 0.8, ....0.1...

(Example)

[Size] (to make smaller)
xscale = 0.8
yscale = 0.8

or

[Size] (to make bigger)
xscale = 1.8
yscale = 1.8

Helpers combo tutorial by Okami

2007-06-11T15:57:00.000-04:00

[statedef ****]
type = S
movetype= A
physics = S
velset = 0,0
ctrl = 0
anim = **** (depends on the number of the animation in the ssf file)
sprpriority = 2(i set it to two always...)

that basically is what are you going to use to launch the helper, but! you'll need to add few more things under the same statedef to launch a helper like so:
Quote
[State ****, *]
type = Helper
trigger1 = time = 0 ,( or whatever suits you)
helpertype = normal
name = "XXXX" (depends but don't forget to put the quote)
ID = **** (here's the ID of the helper state, like a hitdef)
stateno = ****( this here defines the number of the helper state def in other meanings, the state def that will launch the helper)
pos = 0,0 (keep this as it is...)
postype = p1 ;p2,front,back,left,right
facing = 0 (set it to one for better performance)
keyctrl = 0 (keep it as it easy)
ownpal = 1 (keep as it is)
supermovetime = 0 (you'll need to keep it at zero here , you'll change it later)
pausemovetime = 0 (you'll need to keep it at zero here , you'll change it later)
size.xscale = 1 ( just for scaling, adjust it to the size you want)
size.yscale = 1( just for scaling, adjust it to the size you want)

now note, that you can add another helper state under the same state def, to have 2 helpers at the same time to enchance effects, it depends on you how many helper you wanna call...make it flashy
now you've coded the way you want your character too look like when he summons the helper next step is the helper itself, here:
Quote
[statedef ****] (this must be the same number you set as stateno in the helper state above)
type = S
movetype= A
physics = N
ctrl = 0
velset = 0,0
anim = **** ( this defines the animations used for you helper..)
sprpriority = *(set from 1 to 3)

if you want it to play sound add somethign like this:
Quote
[State ***, *]
type = PlaySnd
trigger1 = Time = 0
value = (this is the number that defines the sound meh, you choose)
now you can add alot of various states that differ depending on how you intend to make your helper look,
now most importantly to make it hit:
Quote
[State ****, *]
type = HitDef
trigger1 = time = 0
attr = S, HA
animtype = Diagup (comes from above)
damage = (set as you want...)
guardflag = none ( can't be blocked, set it to ma or ha, move attack, or helper attack to be guarded)
hitflag = MALFD (everything)
pausetime = 0,0
hitsound = s(you choose)
guardsound = 6,0
ground.type = High (low to hit as low type attack)
ground.slidetime = 30
ground.hittime = 30
ground.velocity = 0,-5
air.velocity = 0,-5
fall = 1
sparkno = (meh, i set is to s2080)
sparkxy = -10,-20(flashy)

Graphical Meter = Bar type by Flowagirl

2007-06-10T11:12:00.000-04:00

==========================
Graphical Meter: Bar type
==========================
Author: FlowaGirl
flowergirl@cutey.com
http://blargh.i-xcell.com

---------------------------------------------------------------------------
In many games, any special effects that the character
currently has, is displayed by either graphical bars, or
numerical values.

You can implement this code into another feature,
such as Ragnarok's Stun meter, or in a Timer, which
can be easily done.

This tutorial shows how a graphical bar is done.
---------------------------------------------------------------------------

In your -2/-3 states, insert this code.

Var(0) is the meter variable. If, for example, you want to implement
this into Ragnarok's Stun meter, then that variable should be used.

You must adjust the "pos" values accordingly, where:

a. TeamSide = 1; Leave unchanged
b. 1; This is the X position of the Explod if the character is on the P1 side. (Against the left wall.)
c. 319; This is the position of the Explod if the character is on the P2 side. (Against the right wall.)
d. 65; This is the Y position of both sides.

Removetime should usually be set to 1, but if your meter has flashy graphics to it, then this value should be the
same as the number of ticks in the animation used in the AIR file.

**** is the animation to be used for the bar, which will be explained later.

[State -2: Explod]
type = Explod
trigger1 = (Var(0) > 0) && (NumExplod(9000) = 0)
anim = ****+Var(0)
id = 9000
pos = IfElse(TeamSide = 1,1,319),65
postype = left
bindtime = -1
removetime = 1
ontop = 1
shadow = 0,0,0
ownpal = 1
ignorehitpause = 1

Now, after inserting this piece in, you can add the animations in the AIR file. The first animation of this
bar should be the same value as ****, while all other anims of the bar after it are done in sequence. Eg.

Anim 9000 in this example is where you put in anim ****.

[Begin Action ****]
9000,0, 0,0, -1,,A

All anims after **** should be organized like this.

[Begin Action 9001]
9001,0, 0,0, -1,,A

[Begin Action 9002]
9002,0, 0,0, -1,,A

[Begin Action 9003]
9003,0, 0,0, -1,,A

[Begin Action 9004]
9004,0, 0,0, -1,,A

[Begin Action 9005]
9005,0, 0,0, -1,,A

Etc...

The other other thing that you need to do now, is to put in your bar animations. You can use the
same concept for numerical values, but only recommended for use if values aren't very high.

Perse Effects by Flowagirl

2007-06-09T17:05:00.000-04:00

==============
Perse Effects
==============
Author: FlowaGirl
flowergirl@cutey.com
http://blargh.i-xcell.com

---------------------------------------------------------------------------
This creates an effect of particles gathering to one point from random areas
of a given radius. It is the opposite to Disperse Effects.
---------------------------------------------------------------------------

In the state where you want to accomplish the effect, create a helper like so:

[State 9000: Helper]
type = Helper
trigger1 = [Insert trigger here.]
helpertype = Normal
name = "PerseEffect"
id = 9001
pos = *,*
postype = p1
facing = 1
stateno = 9001
keyctrl = 0
ownpal = 1
supermovetime = 0
pausemovetime = 0

[Statedef 9001]
type = A
movetype = I
physics = N
anim = **** ;Invisible anim

You will need 2 variables for this effect. Don't worry about assigning new variables for the helper; They
use their own set of variables, so you can leave it at the current values.

These next 2 pieces are used for the radius of the effect. Adjust these to your preference.

[State 9001: VarRandom]
type = VarRandom
trigger1 = 1
v = 0
range = -120,120

[State 9001: VarRandom]
type = VarRandom
trigger1 = 1
v = 1
range = -120,120

This is used to create the particles themselves. You can change the trigger if you'd like.

[State 9001: Helper]
type = Helper
trigger1 = ((GameTime%8) = 0)
helpertype = Normal
name = "PerseEffect"
id = 9002
pos = var(0),var(1)
postype = p1
facing = 1
stateno = 9002
keyctrl = 0
ownpal = 1
supermovetime = 0
pausemovetime = 0
ignorehitpause = 1

This used to destroy the helper. As for when it is destroyed, is up to you. The effect will
continue to happen as long as the helper is around.

[State 9001: DestroySelf]
type = DestroySelf
trigger1 = [Insert trigger here.]

This is the state of the particles themselves. Be sure to give the proper anim for 9002.

[Statedef 9002]
type = A
movetype = I
physics = N
anim = 9002
sprpriority = 3

This is used to move the particles toward the center of effect.

[State 9002: PosAdd]
type = PosAdd
trigger1 = 1
x = IfElse(ParentDist X <= 0,-5,5) y = IfElse(ParentDist Y <= 0,-5,5) This detroys the particle when it comes in range of the center of the effect. If it is already in range when it was created, it will be detroyed after 10 game ticks. [State 9002: DestroySelf] type = DestroySelf trigger1 = (ParentDist X <= 5) && (ParentDist Y <= 5) && (Time > 10)

Spidey's Amalgam Hyper (Spider-Boy) by Radical Rex

2007-06-06T13:18:00.000-04:00

This applies to Seth Zankuten's Spider-Man:

1. open cmd and Find
[State -1, ]
type = Null
value = 15000

2. Just chang Null with this
[State -1, ]
type = ChangeState
value = 15000

3. Watch and be Amaze your With your Super Amazing Spider-Boy!

just know, the move isn't completed yet...

Just defend by Flowagirl

2007-06-05T13:10:00.000-04:00

============
Just Defend
============
Author: FlowaGirl
flowergirl@cutey.com
http://blargh.i-xcell.com

---------------------------------------------------------------------------
This feature was originally from Garou: Mark of the Wolves, and it occurs
when you block an attack right at the last moment before it hits. When
successful, you gain these benefits:

1. Recover a small amount of life.
2. Gain some power.
3. Your character's block is different; It is shorter than normal, will
not cause your character to be pushed back, and you do not suffer any guard
damage.

This is the CvS2 version and it is only available in K-Groove. It may or
may not be exactly the same as the one in MOTW.
---------------------------------------------------------------------------

Put these states under StateDef -2/-3. Var(0) is used to detect when the
backwards command is performed, Var(1) is used to detect if you've
successfully Just Defended, and Var(2) is used to remove any guard damage.

[State -2: VarAdd]
type = VarAdd
trigger1 = (Ctrl) && (Command = "holdback") && (StateNo != [120,155])
var(0) = 1

[State -2: Null]
type = Null
trigger1 = (Command != "holdback")
trigger1 = (Var(0) := 0) && (Var(1) := 0)
trigger2 = ((StateNo = 150) || (StateNo = 152) || (StateNo = 154)) && (!Time)
trigger2 = (Var(1) := IfElse(Var(0) < type =" AssertSpecial" trigger1 =" 1" flag =" NoAirGuard" ignorehitpause =" 1" type =" PowerAdd" trigger1 =" ((StateNo" stateno =" 152)" stateno =" 154))" value =" 250" type =" ChangeAnim" trigger1 =" 1" value =" 150" type =" ChangeAnim" trigger1 =" 1" value =" IfElse(Var(1)" type =" LifeAdd" trigger1 =" (Var(1)" value =" (Var(2)+8)" type =" HitVelSet" trigger1 =" (!Time)" x =" 1" type =" HitVelSet" trigger1 =" (!Time)" x =" 1" type =" ChangeState" trigger1 =" (Time">= GetHitVar(HitTime))
value = 130
ctrl = 1

Replace this with:

[State 151: ChangeState]
type = ChangeState
trigger1 = (Time >= GetHitVar(HitTime))
value = IfElse(Var(1) = 1,0,130)
ctrl = 1

The same changes are made for the crouch guard:

State 152...

[State 152: ChangeAnim]
type = ChangeAnim
trigger1 = 1
value = IfElse(Var(1) = 0,152,****)

[State 152: LifeAdd]
type = LifeAdd
trigger1 = (Var(1) = 1) && (!Time)
value = (Var(2)+8)

[PlaySnd] <--- Just Defend sound effect. [Explod] <--- Just Defend guard spark. [Add anything else you want to include.] State 153... [State 153: HitVelSet] type = HitVelSet trigger1 = (!Time) && (Var(1) = 1) x = 1 [State 153: ChangeState] type = ChangeState trigger1 = (Time >= GetHitVar(HitTime))
value = IfElse(Var(1) = 1,0,131)
ctrl = 1

The same changes are made for the air guard:

State 154...

[State 154: ChangeAnim]
type = ChangeAnim
trigger1 = 1
value = IfElse(Var(1) = 0,154,****)

[State 154: LifeAdd]
type = LifeAdd
trigger1 = (Var(1) = 1) && (!Time)
value = (Var(2)+8)

[PlaySnd] <--- Just Defend sound effect.
[Explod] <--- Just Defend guard spark.
[Add anything else you want to include.]

State 155 is not overridden, because your character is pushed
back as he/she would if he/she was air guarding normally.

Parrying by FlowaGirl

2007-06-04T22:59:00.000-04:00

=========
Parrying
=========
Author: FlowaGirl
flowergirl@cutey.com
http://blargh.i-xcell.com

---------------------------------------------------------------------------
This feature is was originally from SF3, and it is the ability to block an
attack and immediately be given the chance to retaliate.

To perform a parry, you must press forward the moment the attack is about
to hit you. Press down for low attacks.

This version is based on CvS2's version, so it does not include the
additional features that were in SF3; Guard Parry, and Lower Aerial Parry.
---------------------------------------------------------------------------

Put these states under StateDef -2/-3. Var(0) is used for the time the parry
is active, and Var(1) is used to detect the moment when you first tap the
forward/down directional key to perform it.

[State -2: Null]
type = Null
trigger1 = (!Time) && (Var(1) = 0)
trigger1 = ((Command = "holdfwd") && (StateNo = 20)) ^^ ((Command = "holddown") && (StateNo = [10,11]))
trigger1 = (Var(0) := 8)
trigger2 = (Command != "holdfwd") && (Command != "holddown") && (Var(1) = 1)
trigger2 = (Var(1) := 0)
ignorehitpause = 1

[State -2: VarAdd]
type = VarAdd
trigger1 = (Var(0) > 0)
var(0) = -1
ignorehitpause = 1

This is used for parrying in the air, while jumping and during the aerial parry.
Note: ***1 is the ground parry state, ***2 is the air parry state, ***3 is the
helper for air parrying, and ***4 is the parry spark.

[State -2: Helper]
type = Helper
trigger1 = ((StateNo = 50) || (StateNo = ***2)) && (Command = "holdfwd") && (NumHelper(***3) = 0)
helpertype = Normal
name = "Air Parry"
id = ***3
pos = 0,0
postype = p1
facing = 0
stateno = ***3
keyctrl = 0
ownpal = 1
supermovetime = 0
pausemovetime = 0
ignorehitpause = 1

The standing parry state.

[State -2: HitOverride]
type = HitOverride
triggerall = (StateType != A) && (Ctrl) && (Var(0) > 0)
trigger1 = (Command != "holddown") && (Command != "holdback")
attr = SA, AA, AP
slot = 0
stateno = ***1
ignorehitpause = 1

The crouching parry state, for low attacks.

[State -2: HitOverride]
type = HitOverride
triggerall = (StateType != A) && (Ctrl) && (Var(0) > 0)
trigger1 = (Command != "holdfwd") && (Command != "holdback")
attr = C, AA, AP
slot = 0
stateno = ***1
ignorehitpause = 1

The aerial parry state.

[State -2: HitOverride]
type = HitOverride
triggerall = ((StateNo = 50) || (StateNo = ***2)) && (Var(0) > 0)
trigger1 = (Command != "holddown") && (Command != "holdback")
attr = SCA, AA, AP
slot = 0
stateno = ***2
ignorehitpause = 1

And now, the parry states.

[Statedef ***1]
type = U
movetype = I
physics = U
anim = IfElse(StateType = S,****,****) <--- The first value should be the standing parry anim, 2nd being the crouching parry anim. velset = 0,0 ctrl = 0 poweradd = 0 juggle = 0 facep2 = 1 hitdefpersist = 0 movehitpersist = 0 hitcountpersist = 0 sprpriority = 2 The required stuff. [State ***1: AssertSpecial] type = AssertSpecial trigger1 = 1 flag = NoWalk [State ***1: CtrlSet] type = CtrlSet trigger1 = (Time > 4) && (StateType = S)
value = 1

[State ***1: NotHitBy]
type = NotHitBy
trigger1 = 1
value = SCA

[State ***1: Pause]
type = Pause
trigger1 = (!Time)
time = 14
movetime = 14

[State ***1: VarSet]
type = VarSet
trigger1 = (!Time)
var(1) = 1

Miscellaneous special effects.

[State ***1: PalFX]
type = PalFX
trigger1 = (!Time)
time = 8
add = 0,0,0
mul = 256,256,256
sinadd = 75,100,255,8
invertall = 0
color = 256

[State ***1: EnvColor]
type = EnvColor
trigger1 = (!Time)
value = 255,255,255
time = 4

[State ***1: EnvShake]
type = EnvShake
trigger1 = (!Time)
time = 8
freq = 60
ampl = -2
phase = 90

Sound effects if needed. One for the character's voice, and another for the parry spark sound effect.

[State ***1: PlaySnd]
type = PlaySnd
trigger1 = (!Time)
value = S*,*

[State ***1: PlaySnd]
type = PlaySnd
trigger1 = (!Time)
value = S*,*

This is the parry spark.

[State ***1: Explod]
type = Explod
trigger1 = (!Time)
anim = ****
id = ****
pos = (IfElse(StateType = S,*,*)),(IfElse(StateType = S,*,*)) <--- First set of co-ordinates are used for the position of the standing parry spark, with 2nd set for the crouching. postype = p1 facing = 1 vfacing = 1 bindtime = 1 vel = 0,0 accel = 0,0 random = 0,0 removetime = -2 supermove = 0 supermovetime = 0 pausemovetime = 12 scale = 1,1 sprpriority = 3 ontop = 0 shadow = 0,0,0 ownpal = 1 removeongethit = 1 And this ends the ground parry state. [State ***1: ChangeState] type = ChangeState trigger1 = (!AnimTime) value = IfElse(StateType = S,0,11) This is the aerial parry state. [Statedef ***2] type = A movetype = I physics = N anim = ***2 ctrl = 0 poweradd = 0 juggle = 0 facep2 = 0 hitdefpersist = 0 movehitpersist = 0 hitcountpersist = 0 sprpriority = 2 [State ***2: CtrlSet] type = CtrlSet trigger1 = (Time > 4)
value = 1

[State ***2: NotHitBy]
type = NotHitBy
trigger1 = (Time < value =" SCA" type =" Pause" trigger1 =" (!Time)" time =" 14" movetime =" 14" type =" VarSet" trigger1 =" (!Time)" type =" Null" trigger1 =" (!Time)" trigger1 =" (FVar(0)" type =" VelSet" trigger1 =" (Time)" x =" 0" y =" 0" persistent =" 0" type =" VelSet" trigger1 =" (Time"> 14)
x = FVar(0)
y = FVar(1)
persistent = 0

[State ***2: VelAdd]
type = VelAdd
trigger1 = (Time > 14)
y = 0.45

Parry spark can be added here.
[Explod]

And this ends the aerial parry state when the character lands.

[State ***2: ChangeState]
type = ChangeState
trigger1 = (Pos Y >= 0) && (Vel Y > 0)
value = 52

This is the aerial parry state helper. It should use an invisible anim, with no Clsns.

[Statedef ***3]
type = A
movetype = I
physics = N
anim = ***3
poweradd = 0
juggle = 0
facep2 = 0
hitdefpersist = 0
movehitpersist = 0
hitcountpersist = 0
sprpriority = 2

[State ***3: ParentVarSet]
type = ParentVarSet
trigger1 = (!Time)
var(0) = 8
ignorehitpause = 1

[State ***3: DestroySelf]
type = DestroySelf
trigger1 = (Parent, Command != "holdfwd")

Unblockable Attacks by Scorpion

2007-06-03T23:36:00.000-04:00

all you have to do is go into one the .CNS files of your char and find "guardflag" under"hitdef"
hit "Ctrl F" if to open the word search if you have trouble.

next,
change this
guardflag = MA (or whatever you see here)
to this
guardflag = (just leave it blank)

The attack is now unblockable!! Now go forth and kick ass!

Identifing the hitdef:

[State 200, 1]
type = HitDef
trigger1 = AnimElem = 3
attr = S, NA
damage = 23, 0
animtype = Light
guardflag = MA ;Erase the MA, to enable unblockable attacks.
hitflag = MAF
priority = 3, Hit
pausetime = 4, 8
sparkno = S9008
sparkxy = -10,-80
hitsound = S5, 2
guardsound = 6, 0
ground.type = High
ground.slidetime = 5
ground.hittime = 10
ground.velocity = -1
airguard.velocity = -1.9,-.8
air.type = Highground.type)
air.velocity = -1.4,-3
air.hittime = 12

Morphing Tutorial by Chocobo

2007-06-02T15:00:00.000-04:00

==================
Morphing Tutorial
==================
Author: Chocobo
[E-mail not available.]

---------------------------------------------------------------------------
Morphing/Transform/Mode Change, or whatever you call it: It is the ability
used in some characters, such as Gen of SFA3, where he can change from one
mode to another, or in a character such as Shang Tsung of MK, who can change
to another character altogether.
---------------------------------------------------------------------------

You have to decide on what this effect is going to do to your character.
We'll assume that you want your character to change simply his/her fighting style.

Create the state that your character will go into. This is where your character
changes his/her form and/or increase any stats:

[Statedef ****]
type = S
movetype= A
physics = S
anim = ****
ctrl = 0

Next, you will need to decide how long the effect will last. If you want it to last
for 1000 ticks for example, you give var(0) a value of 1000. But, if you want this
effect to last indefinitely, simply set it to 1, to make things simple.

In any case, this variable is used to set the effect on.

[State ****: VarSet]
type = VarSet
trigger1 = [Insert trigger here.]
var(0) = 1000

This is used to end the move.

[State ****: ChangeState]
type = ChangeState
trigger1 = (AnimTime = 0)
value = 0
ctrl = 1

If you decide that the effect will last for a certain number of ticks, add this next piece under
StateDef -2. Otherwise, just skip this part.

[State -2: VarAdd]
type = VarAdd
trigger1 = (Var(0) > 0)
var(0) = -1
ignorehitpause = 1

Now, you probably want to add in the special effects as a result of the move. This tutorial shows 3
examples of an effect being added.

----

1. If you want your character's standing anim to change, you can override the common1.cns file,
under StateDef 0. Look for this code:

[State 0, 1]
type = ChangeAnim
trigger1 = Anim != 0 && Anim != 5
trigger2 = Anim = 5 && AnimTime = 0 ;Turn anim over
value = 0

Remove the code as shown above entirely, and replace it with:

[State 0, 1]
type = ChangeAnim
triggerall = (Var(0) <= 0)
trigger1 = Anim != 0 && Anim != 5
trigger2 = Anim = 5 && AnimTime = 0 ;Turn anim over
value = 0

[State 0, 1]
type = ChangeAnim
triggerall = (Var(0) > 0)
trigger1 = Anim != 0 && Anim != 5
trigger2 = Anim = 5 && AnimTime = 0 ;Turn anim over
value = ****

Where **** is the new standing anim. You use the same concept for the entire common1.cns. Although
most creators use a much more efficient method of accomplishing this with the use of expressions, this
will do the job just fine.

----

2. If you want to enable any new moves while your character is in this form, but only in this form, you
simpy create the move just like any other move, with one exception; The CMD file.

This is just like any other command entry, with (Var(0) > 0) being the only new trigger added.

[State -1: ChangeState]
type = ChangeState
value = **** ;State of new move.
triggerall = (Command = "whatever") && (Var(0) > 0)
trigger1 = (StateType = A) && (Ctrl)

----

3. If you just want to increase the character's strength, go back to the morphing state, and add this in:

[State ****: AttackMulSet]
type = AttackMulSet
trigger1 = (!Time)
value = 1.5 ;50% increase to attack.

Be sure to insert this under StateDef -2. This is used to reset the character's strength back to normal when
he/she is no longer in the mode.

[State -2: AttackMulSet]
type = AttackMulSet
trigger1 = (Var(0) <= 0)
value = 1
ignorehitpause = 1

AI Activation - Command method by FlowaGirl

2007-06-01T23:14:00.000-04:00

1st Look at Speed Racer's Mach 5

2007-06-01T16:27:00.000-04:00

In a summer of sequels (and you know next year will be as well) , beloved anime's will become live action films... but will they be fan-pleasing?

Lifebar Tutorial by cabbit007

2007-05-31T11:50:00.000-04:00

Cabbit007's Lifebar Tutorial

If you find any problems or have any suggestions, e-mail me at cabbit007@hotmail.com

Note: This tutorial was written for MUGEN version 4.14

This tutorial was last updated on 12/09/2001

DISCLAIMER

The tutorial is NOT for redistribution or direct linking unless permission is given. Please respect my wishes regarding this subject since I try to update this tutorial every now and then. I don't want to be pestered with someone asking me why some outdated coding does not work because they got an older version of this tutorial from somewhere else.

For everyone's convenience, I've split up the lifebar file into its respective sections for quick referencing. This tutorial is written with the thought that the reader has at least attempted to read the documentation in the mugen/docs folder. If you have not read it, it is strongly suggested that you do so or you may not be able to understand all of the following information. Also, it might help if you read Section 20 first.

Webmaster's note: this was recovered from the MugenSex website with Sho's permission. Cabbit007 has actually been out of the community for quite some time at this point, so there wouldn't be much reason to email him with questions or comments. If you do have any questions, direct them to the RS forums and we'll try and help you from there -KFM
< sff =" fight.sff" snd =" vssnd.snd" font1 =" font/jg.fnt" font2 =" font/num1.fnt" font3 =" font/name1.fnt" font4 =" font/kof99.fnt" font5 =" font/vslev.fnt" font6 =" font/vstime.fnt" font7 =" font/vshitfnt.fnt" sff =" fightfx.sff" air =" fightfx.air" snd =" common.snd" pos =" 159,117" spr =" 11,0" layerno =" 1" spr =" 12,0" spr =" 13,0" layerno =" 1" x =" -26,-140" pos =" 159,117" spr =" 11,0" facing =" -1" layerno =" 1" spr =" 12,0" facing =" -1" spr =" 13,0" facing =" -1" layerno =" 1" x =" 26,140" pos =" 159,117" spr =" 14," layerno =" 1" spr =" 12,0" spr =" 13,0" layerno =" 1" x =" -26,-140" pos =" 159,117" spr =" 14," facing =" -1" layerno =" 1" spr =" 12,0" facing =" -1" spr =" 13,0" facing =" -1" layerno =" 1" x =" 26,140" pos =" 159,117" spr =" 12,1" spr =" 13,1" layerno =" 1" x =" -40,-134" pos =" 159,117" spr =" 12,1" facing =" -1" spr =" 13,1" facing =" -1" layerno =" 1" x =" 40,134" pos =" 160,120" spr =" 11,0" layerno =" 1" spr =" 12,0" spr =" 13,0" layerno =" 1" x =" -27,-124" pos =" 160,120" spr =" 11,1" layerno =" 1" spr =" 12,1" spr =" 13,1" layerno =" 1" x =" 26,123" pos =" 156,125" spr =" 21,0" layerno =" 1" anim =" 23" layerno =" 1" spr =" 22,0" x =" -10,-124" offset =" -135,101" font =" 5,0,0" layerno =" 1" pos =" 156,125" spr =" 21,1" layerno =" 1" anim =" 24" layerno =" 1" spr =" 22,1" x =" 16,130" offset =" 141,101" font =" 5,0,0" layerno =" 1" snd =" 0,2" snd =" 0,3" snd =" 0,4" x =" 0," y =" 0" pos =" 120," spr =" 9000,0" layerno =" 0" facing =" 1" offset =" 0,0" scale =" .6,.6" pos=" 197," spr =" 9000,0" layerno =" 0" facing =" -1" offset =" 0,0" scale =" .6,.6" pos =" 120," spr =" 9000,0" layerno =" 0" facing =" 1" scale =" 0.6,0.6" pos =" 197," spr =" 9000,0" layerno =" 0" facing =" -1" scale =" 0.6,0.6" pos =" 112,38" spr =" 9000,0" layerno =" 0" scale =" 0.45,0.45" facing =" 1" pos =" 205,38" facing =" -1" spr =" 9000,0" layerno =" 0" scale =" 0.45,0.45" facing =" -1" pos =" 10," spr =" 9000,0" layerno =" 2" facing =" 1" offset =" 0,0" scale =" .6,.6" pos =" 10,37" spacing =" 13,0" spr =" 10,0" spr =" 9000,0" scale =" .5,.5" facing =" 1" offset =" 1,0" p2pos=" 309," spr =" 9000,0" layerno =" 2" facing =" -1" offset =" 0,0" scale =" .6,.6" pos =" 310,37" spacing =" -13,0" spr =" 10,0" facing =" -1" spr =" 9000,0" scale =" 0.5,0.5" facing =" -1" offset =" -1,0" pos =" 69,36" font =" 3,0,0" layerno =" 1" pos =" 254,36" font =" 3,0,0" layerno =" 1" pos =" 69,45" font =" 3,0,0" layerno =" 1" pos =" 254,45" font =" 3,0,0" layerno =" 1" pos =" 69,52" font =" 3,0,0" layerno =" 1" pos =" 254,52" font =" 3,0,0" layerno =" 1" pos =" 69,36" font =" 3,0,0" layerno =" 1" pos =" 254,36" font =" 3,0,0" layerno =" 1" pos =" 156,41" font =" 6,0" layerno =" 1" offset =" 4," framespercount =" 60" pos =" 10,80" x =" -40" font =" 7,0" shake =" 1" text =" %iHIT" font =" 7,0" offset =" 3,0" displaytime =" 90" wins =" 2" waittime =" 0" time =" 105" time ="60" offset =" 160," text =" Round" displaytime =" 60" layerno =" 2" offset =" 160,120" anim =" 2001" snd =" 0,0" snd =" 0,0" snd =" 0,0" sndtime ="30" time ="50" offset =" 160," text =" Fight!" displaytime =" 100" snd =" 0,1" sndtime ="60" time ="0" offset =" 160," text =" KO!" displaytime =" 90" snd =" 0,5" time ="0" text =" Double" offset =" 160," displaytime =" 60" snd =" 0,6" time ="0" offset =" 160," text =" Time" displaytime =" 60" snd =" 0,7" sndtime ="0" time =" 60" waittime =" 45" hittime =" 10">:D
over.wintime = 45 Delay time before win pose is shown.
over.time = 210 Time before entire round is over.
win.time = 60 Delay time before win/draw message is shown.
win.offset = 160, 90
win.text = %s WINS! %s deplays the winner's name
win.displaytime = 540
win2.text = %s AND %s WINS!
win.displaytime = 540
draw.text = Draw!
win.displaytime = 540
win.font = 4,0
win2.font = 4,0

Section 19. [WinIcon]

For the win icons, they don't all have to be different but it does make it look better.

p1.pos = 12,5
p2.pos = 308,5

p1.iconoffset = 24,0
How much space for each of player 1's icon will take up. Note this is positive so the next one will be placed to the left of the previous.

p2.iconoffset = -24,0
How much space for each of player 2's icon will take up. Note this is positive so the next one will be placed to the right of the previous.
p2.counter.offset = 78,0
p2.counter.offset = -78,0
p1.counter.font = 2,1
p2.counter.font = 2,1
p1.n.spr = 100,0 Win by normal
p2.n.spr = 100,0
p1.s.spr = 101,0 Win by special
p2.s.spr = 101,0
p1.h.spr = 102,0 Win by hyper (super)
p2.h.spr = 102,0
p1.throw.spr = 103,0 Win by normal throw
p2.throw.spr = 103,0
p1.c.spr = 104,0 Win by cheese
p2.c.spr = 104,0
p1.t.spr = 105,0 Win by time over
p2.t.spr = 105,0
p1.suicide.spr = 100,0 Win by suicide
p2.suicide.spr = 100,0
p1.teammate.spr = 107,0 Opponent beaten by his own teammate
p2.teammate.spr = 107,0

p1.perfect.spr = 110,0
Win by perfect (overlay icon). This icon is put on top of the whatever type of win you have.
p2.perfect.spr = 110,0
useiconupto = 2 Use icons up until this number of wins

Section 20. Reference.

The following is taken from the lifebar definition file from the original MUGEN lifebars. If yu understand everything in this section, you should be able to make a of lifebars with no trouble.

;-----------------------------------------------------------
; How to customize
;-----------------------------------------------------------
; First of all, set filenames under [Files].
;
; Next, you can customize each component of the fight screen.
; A component can be anything from a piece of the lifebar,
; to the text that signals a K.O.
;
; Each component starts with its name, followed by a period,
; and then the names of its elements. For example, a
; component named "bg" with an element of "anim" looks
; like "bg.anim".
;
; There are several main element types:
; 1. anim (animation)
; 2. spr (sprite)
; 3. font (text)
; 4. snd (sound)
;
; 1. anim
; Format: anim = actionno
; actionno is the number of the action to use. You must
; specify a valid action that is defined within this file.
; The sprites for the animation come from the file given
; for the "sff" parameter in the [Files] group below.
; You can define your animation actions anywhere in this
; file, as long as it does not come in the middle of a
; group (an example of a group is the block of text
; starting with [Files], and ending on the next group
; [Lifebar]).
; For example, to use action 5 for the p1.bg0 component:
; p1.bg0.anim = 5
;
; 2. spr
; Format: spr = spritegrp, spriteno
; This is the identifier pair for the sprite you to
; display.
; For example, to show sprite 103,0 for a component named
; p1.throw:
; p1.throw.spr = 103,0
;
; 3. font
; Format: font = fontno, fontbank, alignmt
; text = text
; This lets you set the font (and optionally the content
; text). fontno is the number of the font defined under
; [Files]. For instance, for the line "font2 = font/num1.fnt",
; the fontno is 2.
; fontbank is the color bank of the font to use. Refer to
; the font for what color banks it has.
; alignmt is a number representing the text alignment.
; 1 is left, 0 means center, and -1 is for right-alignment.
; The "text" element should accompany the "font" element
; wherever necessary. The following example will display
; "FIGHT!" using font 1, bank 1, with center-alignment.
; fight.font = 1,1, 0
; fight.text = FIGHT!
;
; 4. snd
; Format: snd = sndgrp, sndno
; This is the identifier pair for the sound effect to
; play. The .snd file that the sound is played from
; is given in the "snd" parameter in the [Files] group.
; This plays sound 21,0 for the "level1" component.
; level1.snd = 21,0
;
; Take note that the anim, spr and font element types are
; mutually exclusive; you can only use one of them per
; component.
;
; The types of elements supported vary with the component.
; Usually the anim, spr and font elements are interchangeable
; for a component. However, in some cases only one element
; type may be used. An example of this is found under [Combo]:
; counter.font = 2,4 ;Font for combo counter
; You cannot use an animation or a sprite to represent a
; numeric counter, so it only makes sense to define a font
; for use.
;
; There are other element types that do nothing on their
; own. They can be used with display element types
; (spr, anim and font) to gain more control. These
; have no meaning when used with the snd element.
; 5. offset
; 6. displaytime
; 7. facing
; 8. vfacing
; 9. layerno
; 10. scale
;
; 5. offset
; Format: offset = x, y
; Displaces the display element horizontally by x pixels,
; and vertically by y pixels.
; If this element is omitted, the offset is assumed to
; be 0,0.
;
; 6. displaytime
; Format: displaytime = time_in_ticks
; This elemet defines the time to display the component.
; If omitted, the default display time varies with element
; type. For spr and font elements, the default displaytime
; is 1. For anim, it is the looptime of the animation.
; This example displays the text "FIGHT!" for 45 game
; ticks:
; fight.font = 1,1, 0
; fight.text = FIGHT!
; fight.displaytime = 45
;
; 7. facing
; Format: facing = dir
; Sets the horizontal flipping of the display element.
; 1 means no flipping, and -1 means flip horizontally.
; Does not affect "font" elements. Defaults to 1 if
; omitted.
;
; 8. vfacing
; Format: vfacing = dir
; Sets the vertical flipping of the display element.
; 1 means no flipping, and -1 means flip vertically.
; Does not affect "font" elements. Defaults to 1 if
; omitted.
;
; 9. layerno
; Format: layerno = no
; This element lets you set the layer to which the
; display element will be drawn on. 0 is in front of
; the background, but behind the players. 1 is in
; front of the players, but behind the foreground.
; 2 is in front of the foreground. The default is 0
; in most cases.
; An example of where this might be useful is when
; you want to have the life or power bars appear
; on top. In that case, set all the components to
; have layerno = 2.
;
; 10. scale
; Format: scale = xscale, yscale
; Scales the display element by a horizontal scale
; factor of xscale, and vertically by a factor of
; yscale. Defaults to 1,1 if omitted.
; Currently does not affect "font" elements.
;
; Some components have additional elements specific
; to themselves.

Section 21. Questions

Before you start harassing me/others with pointless questions, do read through these and see if they answer it.

Q: I want to display a sprite/animation instead of those stupid text. How do I do this?
A: You can replace any .text with either a .spr or an .anim. The reverse applies as well. A spr is a sprite and an anim is an animation.

Q: My life doesn't fill all the way up/my life doesn't go all the way down. What do I do?
A: Check the size or your life sprites. Check the position of your life sprites. Check the range of your life sprites.

Q: My powerbar's power sprite is too small even though the sprite size is perfect. What do I do?
A: You need to check to make sure that your power holder is present and if so, the right size.

Q: The other player's life is all gone and he still won't die until after I hit him some more. What do I do?
A: Check the range of your life sprites.

Q: I've read the entire tutorial and still have no idea how to make lifebars. Are there any others?
A: To my knowledge, I've never seen any others so you're out of luck. I learned by opening up KGenjuro's Gundam Wing Endless Duel lifebars and updated it. All you really need is to read the Reference section and experiment around and you'll get it easily.

Q: Is there an easier way to do the positioning of the sprites?
A: There isn't a perfect way to position the sprites so you'll have to do it by trial and error. Just remember that the MUGEN screensize is 320 by 240 pixels and place them accordingly. You can make a 320x240 sprite, create a new layer, place your sprites in, and then take note of the position through there. This may be more convenient (thanks to Mattasaur for that one) but once you've gained more experience, it's often much faster with guess and check through MCM.

Q: Your tutorial is too long and I don't have the time to read through it.
A: If you don't have time to read this then you probably don't have time to make lifebars so you don't have to worry about it.

Q: I've got this great idea about a set of lifebars that I want to see made. Can you make them for me?
A: And why did you download this tutorial again?

Q: Can I send you wht I have so you can correct it for me?
A: No. If you have any questions go to http://randomselect.i-xcell.com/forum/ and post in the Help Section.

Q: My lifebars screwed up my characters!
A: Lifebars do not affect the characters in any way except display their current amount of life and power.

Q: After I downloaded a set of lifebars and got some new characters, their moves won't work right!
A: Read previous answer.

Section 22. Credits

Many thanks to the following in no particular order:

Elecbyte for making MUGEN and commenting so well in its lifebars

SES for making MCM. Without it, I'd never have attempted to make anything

Kitsune Sniper for making a background tutorial. You were part of my inspiration to write this

Fallenangel for his character making tutorial. It's very well written and if you haven't read it, I suggest you do so.

KGenjuro for making the GWED lifebars since that's where I started out

NodeX for having the win icon animation bug and making me aware of it in MUGEN version 7.31. Also, thanks for proofreading this tutorial for me. Now hurry up and make Sandrock's AI harder :D

Mattasaur for proofing my tutorial and giving me suggestions as well ^_^ Thanks you great big dinosaur!

StriderX for being a great friend. Hope you get your computer fixed soon

K3nShiN for many programming tips. Now finish that Battousai and K3nShiN's Dirty Little Secret will be update more often ^_-

Mizuki for being such a great help in the Help forum on Mugen Dev and seducing people with her sweaty clothes XD~~

Ragnarok Nemo for making the fun Puyo Puyo clone (even though I still think it's too easy). Need to take you on in it if you ever get the multiplayer thing implemented. Either that or Zsnes time. Kirby's Avalanche anyone? ^_^

Ken MastersX for having the worst internet connection ever. The contest is still on and the contestants are still at the same place they were 2 months ago. >_<; Does lifebars/tutorials count?

Lord Nite for creating a haven for DBZ people. We've seen what it's like without Nitek (shudders). Let's go Alice!

The petshop guy in UHF for teaching poodles how to fly :P Go watch it if you haven't seen it!

Anyone who's ever downloaded one of my lifebars and kept it for more than 3 days.

And whoever actually read all of the above.

Supergirl W.I.P.

2007-05-14T16:57:00.000-04:00

Just in the early stages of everything, but I plan to make the current Kara Zor-El... we need a Supergirl for Mugen! I plan to mix the pre-crisis, post crisis versions with some secret extras!

For Anyone Who Likes Superheroes In Mugen...

2007-05-14T11:03:00.000-04:00

I've been into Mugen for the last few months and joined this community for all the people that helped newcomers out, cuz thats the kind of person I am. I have seen many go and I'd like to give back in a big way. I know theres a lot of peeps out who like super-heroes... there are many who arent made yet, so... I was wondering if anyone wanted to join me in creating some new chars for mugen? There are so many resources, so many creators still to learn from, so why not start something new? I've got a few projects going on right now, including The Legion of Super-Heroes - The Great Darkness Saga for mugen... if anybody wants to collaborate on some stuff holla at me.

Mugen On G4

2007-05-08T08:02:00.000-04:00

Peter Griffin MVC by Warner & JudgeSpear
Sakura by P.O.T.S.

you can watch the original video featured in the clip here in its entirety

Kevin & Olivia showed this video yesterday, stating it was "a hack of Marvel vs Capcom 2. They showed Peter Griffin fighting Sakura and thought that it was "ripped from a DVD." After hearing that, I LOL and just said to myself... Mugen has just been shown in 30 million
homes around the world... That was not a hack on Marvel Vs. Capcom. Not a modded rom. No, it's Mugen, and it rocks!

Mirror Warp by FlowaGirl

2007-05-03T23:28:00.000-04:00

============
Mirror Warp
============
Author: FlowaGirl
flowergirl@cutey.com
http://blargh.i-xcell.com

---------------------------------------------------------------------------
This feature was originally shown in Pac Man. When you go to one end of
the screen, to see yourself moving into the opposite side.
---------------------------------------------------------------------------

This is all you need. Insert this under StateDef -2/-3:

[State -2: ScreenBound]
type = ScreenBound
triggerall = (StateNo != [0,12]) && (MoveType != H) && (StateNo != [120,152])
trigger1 = (BackEdgeBodyDist <= 0) || (FrontEdgeBodyDist <= 0)
movecamera = 0,1
value = 0

[State -2: PosSet]
type = PosSet
triggerall = (StateNo != [0,12]) && (MoveType != H) && (StateNo != [120,152])
trigger1 = (BackEdgeBodyDist <= -10) || (FrontEdgeBodyDist <= -10)
x = IfElse(BackEdgeBodyDist <= -10,150,-150)*(Facing)
y = Pos Y

[State -2: VelSet]
type = VelSet
triggerall = (StateNo != [0,12]) && (MoveType != H) && (StateNo != [120,152])
trigger1 = (BackEdgeBodyDist <= -10) || (FrontEdgeBodyDist <= -10)
x = Vel X
y = Vel Y

How To Extract .dgc Files

2007-05-02T16:21:00.000-04:00

Go to this site and click DGCA Version 1.10公開( 2006/8/8 ) Continue to the download page and click english near the top. Then download the installation file according to what system you're using (for Windows95/98/Me/NT/2000/XP Win32 click the first one)

Now click the installation file and follow the steps UNTIL you get to the part where you choose where to install it. Next, take all of those files that are now on your desktop and put them in a folder with whatever name you want. Click the dgca shortcut(it may take some time) select the file, extract the dgc file and in the new window be sure to check the box that says (create folder from archive name and extract into the folder) then just click ok

you should now have a folder with the files inside....

Cyanide & Winane's Mugen Tutorials

2007-05-01T14:53:00.000-04:00

Cyanide has one of the best Mugen creation tutorials on the net...

"I originally wrote them for a naruto forum, as such the character used as an
example is naruto and he also spawns the name of "narutorial".

If you use these, please make a point of following them in sequence if it's your
first character.

Narutorial 1: How to pallete your sprites ready for use in Fighter Factory.
Narutorial 2: Adding standing sprites to an SFF with Fighter Factory.
Narutorial 3: Coding a basic punch using Fighter Factory.
Projectiles, incomplete
Combo Moves: Seperate from the series, basic intro into making moves combo.

Things like naruto's sprites are provided if you want to follow along with them.
Narutorial 2 comes packaged with the files blank.def, blank.air, blank.cns and
blank.cmd. These are stripped down Kung fu man files which you may find useful.
Some things like hitdefs have been left in there however as you go on you'll add
chop and change so you'll still be learning.

These are going up cos they seem to have been rather well recieved. I don't quite
know why though =P

Anyway, hope this helps any budding creators out there

Cyanide."

Thanks again Cyanide, for great tutorials to begin creating! Winane also has a page of tutorials including tips on A.I. & help with M.C.M.

Gotham Knights Cancelled!

2007-04-30T05:38:00.000-04:00

Apparently Nightwing has joined Batman among leaks from Magus' Gotham Knights Project, so Magus has scrapped the project indefinitely. Maybe after time it may come back, but since Nightwing has been added to the downloads on the Scruffy Dragon site as an incomplete beta.

Free Comic Book Day 2007

2007-04-21T10:25:00.000-04:00

I was checking out one of my friend's blogs... FCBD 2007 is 1 week from today! Is anybody gonna check it out, or has anyone gone before?

Gaming legend Bill Cravens passes away

2007-04-19T13:46:00.000-04:00

Bill Cravens was responsible for bringing Street Fighter, Mr. Do, Super Punch Out, Final Fight, Street Fighter and Golden Tee 3D to the masses. He will be missed. R.I.P. Bill.

For more on this check this link.

Sega Hulk-ing up on Marvel licenses

2007-04-18T13:33:00.000-04:00

via Gamespot:
Last November, Sega announced that it had taken over the game license for the Marvel Comics hero Iron Man from Activision. Today, the Japan-based company announced it has acquired three more game licenses from the venerable comic book publisher turned media powerhouse.

Evildoers, beware!.

Foremost among the new acquisitions is The Incredible Hulk, who is currently appearing in the role-playing game Marvel: Ultimate Alliance. Previously, Vivendi Games held the game rights to the brawny superhero, releasing 2005's critically acclaimed The Incredible Hulk: Ultimate Destruction (PS2, Xbox, GameCube) and 2003's less praised The Hulk (PC, PS2, Xbox, GameCube). Under the new deal, Sega will also be developing games based on the forthcoming movie The Incredible Hulk, which stars Edward Norton as the Hulk's less angry alter ego, Bruce Banner. The game will be released alongside the film next summer.

Though he may have died in comic books, Captain America will live on in game form. Sega is planning a game based on the forthcoming Captain America film, which is still in development. The last game that centered on the shield-wielding hero was Captain America and the Avengers (Game Boy, 1994), although he currently also appears in Marvel: Ultimate Alliance.

Last--but in the minds of would-be Vikings everywhere, not least--Sega has landed the license for The Mighty Thor. Like Captain America, the comic centering on the earthly adventures of the Norse god is being turned into a film with a tentative post-2008 release date. The Mighty Thor game--the first based solely on the character--will be released alongside said movie on undisclosed consoles. (Thor is also a featured hero in Marvel: Ultimate Alliance.)

Today's deal is a "multi-year global licensing agreement" that gives Sega exclusive rights to make Thor, Hulk, and Captain America games for consoles, handhelds, and the PC. In a statement, Simon Jeffery, Sega of America's president and COO, said, "As Sega continues to create games that are built from the ground up to appeal to Western audiences it makes perfect sense to work with a powerhouse like Marvel."

How to set orders in Mugen

2007-04-17T12:05:00.000-04:00

[Characters]

- order
; Set the paramvalue to the ordering priority to give the
; character. Valid values are from 1 to 10. A smaller value
; means you will fight the character sooner. You will never
; fight an order 2 character before an order 1 character,
; and never an order 3 character before an order 2 one.
; For example, you might want to set your boss character
; to have order=3. The default order value is 1 if you omit
; this param. See *.maxmatches under [Options] for how to
; limit the number of matches per order priority.

e.g kfm, stages/mybg.def, order=3

and scroll down to [options]

[Options]
;Here you set the maximum number of matches to fight before game ends
;in Arcade Mode. The first number is the number of matches against
;characters with order=1, followed by order=2 and order=3 respectively.
;For example, for 4,3,1 you will fight up to 4 randomly-picked
;characters who have order=1, followed by 3 with order=2 and 1 with
;order=3.
arcade.maxmatches = 6,1,1,0,0,0,0,0,0,0

How to keep selectable characters as Zipped files

2007-04-16T13:04:00.000-04:00

How to keep selectable characters as Zipped files

This file allows you to keep your characters Zipped while in the character folder, so you don't have to unzip every character you download.
All you have to do is overwrite the zlib.dll file that is in the main folder (with the mugen.exe) with this one.
This should save you loads of HDD space on your computer.

1]When you add your character in the select.def, make sure you also add a ".zip" at the end of the character's name.
ex：　　[Characters]
　　　　kfm.zip, stages/kfm.def

2]Do NOT leave the character inside a folder when you zip it.
（If the character has sub-folders such as "states" etc, these sub-folders can be left alone.）

3]If the character is still not recognized, it is because the last line in it's CNS file does not have a brake line.
Just open the character's CNS file with Notepad, and go to the very bottom-end and press enter, then save it.

You can find the file on Choujin's site.

How to add songs in Mugen

2007-03-25T12:00:00.000-04:00

To put a song on a stage open the Def file and look 4

Write the sound/name of your song in bgmusic and 0 in bgvolume
example

[Music]

bgmusic = sound/15_stage_of_gouki_-_worth_of_my_fist.mp3

bgvolume = 600

To put music in the menu open the system.def in your data folder look 4
[Music]
title.bgm =
title.bgm.loop =

select.bgm =
select.bgm.loop =

vs.bgm =
vs.bgm.loop =

add your music and loop

Installing the Virtua Fighter 5 Lifebars

2007-03-17T12:13:00.000-04:00

Place the vf5lb folder in your data folder, then go to system.def

Next, Create two sub-directories inside your data folder. One is for your fightfx.sff and the other is for your common.snd.

Name those new folders, sff and snd.

Now, cut the fightfx.sff file inside your data folder and paste it inside your newly made sff directory, do the same with the common.snd file, cut/paste inside the snd folder, both in your data directory.

Go back to your VF5LF directory and only COPY (DO NOT cut/paste) the following:

Fight.def

Fight.sff

Fight.snd

Place those inside your data directory, if it ask you to overwrite the original ones, just click "ok":

That will leave you with three of the same files in both your data and VF5LB folders.

The open the system.def file in the data folder, and go to where it says file ,then put the name of the lifebars folder where it says

fight = fight.def

change it to look like this
fight= VF5LB/fight.def

now restart your Mugen and the lifebars should be installed!

Mugen - What You Need To Know

2007-03-01T05:08:00.000-05:00

the video that got me into Mugen

M.U.G.E.N is a freeware 2D fighting game engine designed by Elecbyte, written in C with the Allegro library. The engine was originally released in July 17, 1999. Beta versions of it were made to work on DOS, Linux and Windows platforms, distributed through their website or to donators via email. With the release of the Linux version, support for DOS ceased.

The engine allows anyone to create characters, background stages and other game objects through interpreted text files, graphics, and sound compilations. It supports various types of audio formats such as MP3, ADX, OGG and MIDI as background music during gameplay or at other points such as an introduction or the select screen. The engine allows for most of the same type of functionality found in most any commercial 2D fighting game, up to and including close recreation of those games' characters and gameplay. While the engine is set up primarily for fighting game development, several other game types have been developed using it, including shooter and platformer style games.

Mugen is a word of Japanese origin, meaning dream, fantasy or infinite. To get started, click here. As time goes on I'll post some tutorials on how to get Mugen up & running, what to do if you have a problem and more.

Also, be sure to look around Random Select, it's a Mugen creator's toolkit!