Character Maker

From The Game-Maker Archive
Revision as of 11:30, 4 May 2014 by Aderack (talk | contribs)
Jump to navigationJump to search
Character Maker
Charmaker.png

Release type: Retail (Game-Maker suite)
Release date: 1991 (original release)
Author: Recreational Software Designs
Related tools: Palette Designer, Block Designer, Monster Maker, Map Maker, Integrator, Xferplay

Produces and edits .CHR format files. Programmed by Oliver Stone.

Version history

1994 - Version 3.00

Tips

  • The first frame of the idle animation is a throwaway. Whenever a character cuts short an animation and reverts to idle, it will skip the first frame of the idle sequence -- so whatever you want to do with your idle animation, begin with frame #2.
  • If you intend a fluid repeating animation, make sure that the first frame moves as many pixels as the later frames.
  • Use the background grid to judge character movement from frame to frame. Twenty pixels equals one block.
  • You can use the plus and minus keys to change the frame delay by ten ticks at a time.
  • If you need to blank a key assignment, assign the move to a reserved key (F1, for instance).
  • If you need to blank the top block of a frame, click on the blank space to the left of the button palette.
  • Unless you click to place a block on the grid, any flipping or rotating of the block will be ignored.
  • Note that any monster birthed from a character will automatically flip or rotate to match the last direction of character movement. So if the character walks left, the monster flips left. Although this behavior is often transparent and desirable, assuring that weapons will always be oriented in a way that makes visual sense, the behavior can get in the way of more advanced techniques -- particularly melee attacks with monster animation that extends the character sprite. In such an event, walking left then attacking right might cause a character's sword arm to stretch out from her body backwards, sword tip to shoulder joint. Problem is, this behavior is very persistent. Even the child of a birthed monster retains its parent's orientation. Yet with the child of a child, the engine loses track of things, freeing the sprite for however you might want to use it. So if you want precise behavior in your birthed monsters, what you need to do is to assign that behavior to the grandchild of the birthed monster. Set the birthed monster and its child each to die after one tick, or at the end of a path that is a single dot.

Links