# Fighter Factory Studio - Reference Documentation

For problems and bug report, go to VirtuallTek Game Studio web site. For doubts related to some specific engine, go to their own web pages or community forums.

# M.U.G.E.N Emulator

The Emulator is based on MUGENext (a M.U.G.E.N compatible engine in development). It supports all debugging functionality Fighter Factory exposes, except:

- Function breakpoints;
- File name and line number breakpoints are activated only in [State] and trigger(all) lines;
- Cannot step by individual instruction, but by line instead.

For more info about debugging, see Debug.

See Emulator workspace for more details.

The options available to customize the engine's behavior while running are:

## Engine directory

The directory where the engine installation to be loaded by the Emulator is located. It's automatically detected if the current project is already inside one. If not, a custom built-in engine based on M.U.G.E.N 1.1 will be used.

## Match mode

Choose between Versus and Training (self-explanatory).

## Match enemy

Choose between Self and Random. If Random, the char will be one from the engine's directory.

## Match rounds

The number of rounds to play. 0 means the same as playing the game, from the engine's fight.def.

## Match round time

Round time, in seconds. -1 for infinite.

## Explod mode

Defines the Explod behavior.

- Engine's default: detected from mugen.cfg in the engine directory.
- M.U.G.E.N 1.0: behave like in M.U.G.E.N 1.0.
- M.U.G.E.N 1.1: behave like in M.U.G.E.N 1.1.
- MUGENext: check our YouTube channel or Patreon page for details.
- Player's version: use mugenversion from the project definitions.

## Draw debug info

Draw debug information bellow each player/helper.

## Training

Same options from M.U.G.E.N's training menu, to be used when Match mode is set to Training.

## Screen

If the current project is system.def (System Screens), you can choose which one to test.