Jump to content
IGNORED

Medieval Mayhem - 2600


SpiceWare

Recommended Posts

A few people have known about this from my blog but I thought it's time to share this with the Homebrew forum as well. For the past 3 weeks I've been working on an new version of Warlords for the 2600.

 

post-3056-1143521336_thumb.pngpost-3056-1143521367_thumb.png

 

You can select NTSC or PAL by selecting COLOR or BLACK & WHITE respectively. The colors and frame size will adjust. The ball speeds will adjust as well once I get that part of the game going.

 

The main menu options are controlled by paddle 1. Turn your paddle to START then hit the firebutton to go to "start" the game. You may also use RESET to "start" the game, or SELECT to return to the main menu.

 

I say "start" as the game itself just shows the castles, the kings and 3, yep 3, fireballs flying around. For the fireballs you can make some adjustments using the difficulty switches. Set LEFT=A to "flicker" the fireballs, B to not flicker. When flickering setting RIGHT=A will fast cycle(every frame) while B will slow cycle (every 4th frame). I would appreciate any feedback on the flicker effect.

 

The checkerboard pattern on the left castles was done to test out the timing of the playfield updates. The kings are now drawn using the playfield (freeing up the missiles for 2 more fireballs) and are colored by switching SCORE mode on/off/on for each scanline. (it's really just OFF/ON as the ON wraps from one scanline to the next).

 

I've increased the playing area by putting all 4 scores on 1 scanline(and even coloring them all correctly) as well as by using a 200 scanline visible area instead of 192.

 

Future updates will, of course, include the shields. I also plan to have a dragon start each round.

 

PLEASE NOTE: These are early versions of Medieval Mayhem. The most current version will be found at the end of this message.

 

Initial BIN mm.bin

 

mm20060529NTSC.bin

mm20060529PAL.bin

 

EDIT - I added the final ROMs here to make them easier to find.

mm20071129NTSC.bin

mm20071129PAL.bin


  1. Instructions to play using
Stellastart Stella
load Medieval Mayhem
hit TAB, a menu will pop up
select Game Properties
on the CARTRIDGE tab set SOUND to STEREO
select the CONTROLLER tab
change both controllers to PADDLES
hit OK
hit EXIT MENU
restart the emulator for the change to take effect. Under OS X use APPLE R, under Windows and Linux use CONTROL R. You'll get a message "New Console Created" when it restarts.

Once you've done this, Stella will remember the settings if you play the game again later.

Edited by SpiceWare
  • Like 1
Link to comment
Share on other sites

One thing this reminds me of is how the original game has an odd quirk where the lower right player seems to have a special defence to balls flung against the right wall by the upper left player (one of the most vulnerable spots)...there's something about the geometry of the game where balls tend to bounce in in in and then out of that castle without hitting the king.

Link to comment
Share on other sites

Thanks all for the interest!

 

Is this a complete homebrew, or a 'hackbrew'?

 

I was originally going to hack Warlords but decided to write it from scratch so we can have cartridges made. I forsee some Mayhem in my brother & sister's Xmas stockings :D

Link to comment
Share on other sites

Wow...looks awsome. I always thought the fire ball was too small in Warlords, and should be the size of the ball in Breakout....any thoughts as to what the final rendering of the fireballs will look like?

 

Anyway...looks great so far, keep it up.

Link to comment
Share on other sites

Wow...looks awsome. I always thought the fire ball was too small in Warlords, and should be the size of the ball in Breakout....any thoughts as to what the final rendering of the fireballs will look like?

 

Thanx!

 

The original fireballs were smaller, as you can see in this blog entry. To make them bigger required 3 additional bytes of RAM. If I double the size again it'll take another 6 bytes of RAM, and it's running pretty tight at the moment. I'll keep it in mind, but I suspect they'll stay like they currently are.

Link to comment
Share on other sites

Have the routines to display the shields in place. They currently move by themselves. The red/yellow block in the middle is where the dragon will be flying around.

 

Turning players black so dead kings don't show also means a fireball becomes invisible on 1/3 of the screen. To work around this I'm going to always fast cycle the fireballs. The left/right difficulties have been changed to simulate dead players so you can see how this will look. Worst case scenerio is 2 players dead on the same half(top/bottom) of the screen which makes all fireballs on that section of the screen visibile 33% of the time.

 

post-3056-1143954280_thumb.png

 

bin mm.bin

 

Source and more info an be found in my blog

Link to comment
Share on other sites

very nice kernal there my man, lots going on.

 

Getting the angles right might be tough...I notice at least right now you only use 3 image (face left or right, face up or down, and diaganol) for the players, but will the ball release have more angles than that?

Link to comment
Share on other sites

Turning players black so dead kings don't show also means a fireball becomes invisible on 1/3 of the screen. To work around this I'm going to always fast cycle the fireballs. The left/right difficulties have been changed to simulate dead players so you can see how this will look. Worst case scenerio is 2 players dead on the same half(top/bottom) of the screen which makes all fireballs on that section of the screen visibile 33% of the time.

 

Are you thinking about clearing the player part of the playfield in the case where both players in that row are dead? That would solve the worst-case problem, wouldn't it?

Link to comment
Share on other sites

Are you thinking about clearing the player part of the playfield in the case where both players in that row are dead? That would solve the worst-case problem, wouldn't it?

It would, but there's not enough CPU time to do so. The king graphic is currently updated once every other scanline - to clear it on one side would require it to be updated twice on every scanline, or 4 times as often. The display kernel is really busy on the scanlines with the kings because it's drawing 3 fireballs, 2 shields, castle walls as well as changing the colors of the playfield so the kings don't look like the castle walls.

 

It's not a bad problem though - the worse flicker occurs when the fireball is next to 2 dead players that share the top or bottom of the screen. The flickering stops once the fireball gets to the middle third of the screen, so it's clearly visible as it flies towards the 2 remaining players.

Link to comment
Share on other sites

It would, but there's not enough CPU time to do so. The king graphic is currently updated once every other scanline - to clear it on one side would require it to be updated twice on every scanline, or 4 times as often. The display kernel is really busy on the scanlines with the kings because it's drawing 3 fireballs, 2 shields, castle walls as well as changing the colors of the playfield so the kings don't look like the castle walls.

 

It's not a bad problem though - the worse flicker occurs when the fireball is next to 2 dead players that share the top or bottom of the screen. The flickering stops once the fireball gets to the middle third of the screen, so it's clearly visible as it flies towards the 2 remaining players.

 

I recognize a mirrored playfield when I see it. :)

 

What I meant was to alter it only after both kings in the same row are dead, which would eliminate the worst case problem, without requiring two updates per scanline. The lesser case problem would still be there, but the worst case would be eliminated.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...