For every general enemy type in the game I simply code up its actions, at the same time building a library of commonly used functions, for instance animation, path following, or wall collision.
Getting on to bosses though, it makes sense to expand the system a bit to allow for (slightly) more complex behaviours.
So what does a boss do in this game? Generally they all follow the same sort of pattern.. follow a sequence of mini-actions, attacking the player, moving around, becoming vulnerable or invulnerable to attack, etc.
This needs to be easily editable at a high level, too. so iterating on gameplay is efficient.
Cheese Boss
Here's the Cheese Boss, and below is his sequence in 'code'
The commands (in CAPITALS) are actually 68000 assembler macros, while the labels (BossCheeseSeq_StartScreenShake) are memory addresses, containing code or data, depending on the command.
This works essentially like Coroutines in Unity or similar. The GameObject controller schedules calling different bits of code, following the pattern in this sequence.
SEQ_IMMEDIATE means 'call this function'
SEQ_STATE means 'call this function every frame, with this parameter, until it returns a signal that the state has come to an end'
SEQ_PAUSE, SEQ_GOTO are self explanatory, and
SEQ_BULLETPATTERN sets up another sequencer / state machine specifically to control the firing of bullets etc.
BulletPatterns
Bulletpatterns are essentially the same code as sequences. They are totally separate from normal sequences, and can be used on other GameObjects which don't contain Sequencers. Here are a couple of the sequences from the Cheese boss:
EnemyBossCheese_BulletPattern1:
.1 BP_SETVEL 0,0
BP_SETANG 0
BP_BULLETTYPE GOTYPE_LARGE_BULLET,1
BP_WAIT 100
BP_FOR 8
BP_SINGLE BP_TARGET_NONE,0
BP_ADDANG 32
BP_NEXT
BP_STOP
EnemyBossCheese_BulletPattern2:
.1 BP_SETVEL 0,0
BP_SETANG 0
BP_BULLETTYPE GOTYPE_LARGE_BULLET,2
BP_FOR 5
BP_SINGLE BP_TARGET_PLAYER,0
BP_PAUSE 6
BP_NEXT
BP_WAIT 50
BP_GOTO .1
Another simple control language using macros.
The first one waits for 100 frames, then fires a burst of 8 bullets at once, looping round a circle (I use 256 'degrees' in a circle in this code)
The second one fires patterns of 5 bullets at the player, with a 6 frame gap between them, followed by a 50 frame pause, then repeat.
Here's an example of the actual code which the sequencer calls. This one scales up the cheese at the start of the level. The sequencer actually calls the sequence's Init function once, while the Init function sets up it's own Update function.
BossCheeseSeq_ScaleIn:
move.l#0,go_renderfunc(a0) ; don't use special render code
move.l#.update,go_sequencefunc(a0) ; call '.update' every frame from now on
move.l#0,go_scale(a0) ; reset scale
rts
.update:
add.l#$4000,go_scale(a0) ; add 0.25 to the scale (scale is a 32 bit value, integer in the upper 16 bits)
cmp#32,go_scale(a0) ; has it reached max
blt .no1 ; no? then render it
moveq#1,d0 ; yes? return with the zero flag cleared, telling the sequencer to move on to the next command.
rts
.no1:
bsr BossCheeseSeq_Scale_DoBlit ; actually blit the cheese, scaled
moveq#0,d0 ; clear the zero bit, telling the sequencer to carry on
Ah, the Sega Megadrive, halcyon days. I remember pre-ordering mine from Special Reserve and eagerly awaiting the launch date. They sent me a copy of Super Monaco GP and a second control pad, which I got to stare at for a week before the console itself finally arrived. It was worth the wait. I still own one today. If you're going to make graphics for a Megadrive game, then you're going to be spending a lot of time with palettes! Aside from the pixel art program Aseprite, the most useful graphics tool I have is a post-it note stuck to the monitor with the numbers 0, 52, 87, 116, 144, 172, 206, 255 written on it. I am almost exclusively using Aseprite to produce the graphics for Rocket Panda, and occasionally Cinema4D to render any 3d animated objects which then need to be processed through Aseprite. The end result is a series of sprite and tile sheets which are mapped to particular palettes. Creating these palettes is the crux of the operation and has to be nailed down fairly e...
Overview This is all about porting Gunslugs, a PC game written in Java (by OrangePixel ) to SEGA Genesis / Megadrive, written in 68000 assembler. Original Game (PC) Genesis Conversion Code Objects / Entities There are quite a lot of active objects at once in the original game- something lke 100-200 plus bullets and effects. This would not be doable on the Genesis, so instead I generate a list of spawn points for level objects. These are sorted horizontally so that I only need to check one at a time as the screen scrolls. Once a spawnpoint is determined to be just off the right edge of the screen, it is promoted to being an active GameObject, and the spawer code continues looking for the next object in the spawner list. Early on I knew there would be a problem with this, due to objects disappearing off the left of the screen. In the original these continue to be active. But at the start I didn't know enough about the game to determine what to do about it. In other games I'd uns...
Passing Breeze, An Arcade Adventure. Our entry for Retro Platform Jam #5 We normally try to make something technically impressive for these jams, but this time we just decided to do something different. We'd never made an Interactive Fiction before. Our platform of choice was again the SEGA Genesis. The Jam theme was Breezy, so as old arcade game lovers we thought of Passing Breeze, the music from SEGA's Outrun. This all fitted together nicely. We'd do an adventure game based in a 1980s(ish) arcade. PICTURES Even though it's simple, I wanted to do something a little technical, so decided to see what sort of images we could display. I started with a simple 16 color image, then tried to do 31 colors by combining the two background scroll layers, A and B. (31 because the top layer would need a transparent color to show the bottom layer through) This all comes down to the tooling. (another story, as I'm converting my game tools to WinForms at the moment). So I wrote t...
Comments
Post a Comment