- Add Review
- Subscribe
- Nominate
- Submit Media
- RSS
Miscellaneous
Sonar Ping
So as this is still a project, just putting a ping out to the community, seeing what kind of echoes I get back.
Is anyone playing this, is anyone enjoying it, is anyone looking forward to more of it? Has anyone been meaning to download or play it but hasn't gotten around to it?
I like the idea of finishing this game because it seems like such a manageable job to do so; just a few more battles to stat and add and test and balance, really. But I'm not sure if even that little bit of effort is worth it when practically no one noticed I released this.
Maybe I shouldn't blog when I'm depressed, lol.
Is anyone playing this, is anyone enjoying it, is anyone looking forward to more of it? Has anyone been meaning to download or play it but hasn't gotten around to it?
I like the idea of finishing this game because it seems like such a manageable job to do so; just a few more battles to stat and add and test and balance, really. But I'm not sure if even that little bit of effort is worth it when practically no one noticed I released this.
Maybe I shouldn't blog when I'm depressed, lol.
Progress Report
Mage Duel, Animated!
Sometimes, I can be extraordinarily oblivious.
For instance, I failed to notice that having every enemy battler in Mage Duel ANIMATED in the same exciting manner as the playable characters was essentially just a few clicks away, due to the majesty of YEM. While toying with preliminary battle system overhaul plans for Linus I noticed this. So I went and corrected this oversight.
All enemies in Mage Duel are now fully animated!* I don't know about you, but I'm really excited about this! So I've released a new version, with the animated battlers.
Let me know if you find any major problems with them--Drexle is a bit screwy, due to me not having an 8-Directional spriteset for him--but the rest seem to be working perfectly to me at least. I haven't tested every single battle, so if anyone finds any problems with the animation of Iyo, Cyath, or Phaene (as enemies!) I'd appreciate if you'd let me know.
The download will be linked here as soon as the submission queue approves it. (Which hopefully won't take quite as long as last time.)
*Okay, Drexle is still kind of shitty, as mentioned above. A static image might be better for him, I don't know.
For instance, I failed to notice that having every enemy battler in Mage Duel ANIMATED in the same exciting manner as the playable characters was essentially just a few clicks away, due to the majesty of YEM. While toying with preliminary battle system overhaul plans for Linus I noticed this. So I went and corrected this oversight.
All enemies in Mage Duel are now fully animated!* I don't know about you, but I'm really excited about this! So I've released a new version, with the animated battlers.
Let me know if you find any major problems with them--Drexle is a bit screwy, due to me not having an 8-Directional spriteset for him--but the rest seem to be working perfectly to me at least. I haven't tested every single battle, so if anyone finds any problems with the animation of Iyo, Cyath, or Phaene (as enemies!) I'd appreciate if you'd let me know.
The download will be linked here as soon as the submission queue approves it. (Which hopefully won't take quite as long as last time.)
*Okay, Drexle is still kind of shitty, as mentioned above. A static image might be better for him, I don't know.
Miscellaneous
Game Design
Blogamajig Arena Digest #1: Can't We Get Beyond Thunderdome?
- Max McGee
- 15 post(s)
- 12/08/2011 07:18 PM
- 4069 views
BLOGAMAJIG ARENA DIGEST #1: CAN'T WE GET BEYOND THUNDERDOME?
Hi I want to blog about the development of Mage Duel Extreme. This particular entry will be a multi-parter. Most of them won't!
First Principles
Mage Duel the first was my very first attempt at making something in RPG Maker VX back in 2008. It is the very oldest of my new games. Please note I don't say "first serious game" or "first game I was happy with". Like the very first thing I EVER did in the RMVX editor was to map the arena and underworks (which are still being used in this game).
The purpose of making the original Mage Duel was to teach myself RPG Maker VX.
Mage Duel Extreme served the same purpose for the first major RPG Maker program to come out SINCE RPG Maker VX: RPG Maker VX with Yanfly Engine Melody. I actually first attempted the MDX training project as literally just a test project, with no intention of showing it to anyone, back in 2009. I didn't get further than the animated battler config, which I couldn't figure out--YEM can be a bitch to config, and sometimes the comments raise more questions than they answer. So in the end I buried the project, a massively frustrating timesink like my first few efforts to use YEM, in a folder literally called "What were you even thinking?" where it remains to this day.
Fast forward two years to 2011, which has been a rough year for me in a lot of ways. To highlight the one most relevant to this anecdote: I went through an RPG Maker phase this January or so, working feverishly on a project codenamed CONJURER on my own laptop. This fever was fucking COOLED by the fact that my laptop (and at the time only computer) could not PLAY RPG MAKER VX games--mine or other people's--without a hellish nightmare of lag. What I could do still, however, was work on 2k3 games.
I tried, hard, to leverage this disadvantage into motivation: even though I could, barely and only by a stretch, afford a new computer (I opted for a desktop, and I still use my crappy old laptop, which has only grown crappier, for portability) I would hold out until I had finished Backstage 2. Since I could only work on 2k3, it would make it that much easier for me to focus on finishing an ancient project: VX was out of the question anyway.
I held out literally months, until the summer, without buying a new computer. Once I bought it, I told myself it changed nothing: no RPG Maker VX until I'd finished Backstage 2. I lasted a matter of days without setting up and opening the computer. I told myself I would only PLAY RMVX games, to make sure they worked. That I wouldn't open CODE NAME: CONJURER again in the editor. But little did I know that the first RMVX game in my backlog that I'd been wanting to play would make my desire to play with YEM FULLY INSURMOUNTABLE. Edifice, if nothing else, functions as an awesome advertisement for the capabilities of YEM as a toolset, although I know Craze would add that there's no shortage of his own code in there, powering the works.
Anyway, opening MDX instead of Code Name Conjurer, telling myself that this was "not a real project" and I "just wanted to play with the mechanics" and I "wouldn't abandon Backstage 2 development" was how this project was born. (Between this temptation and the long silence of Archeiah_Nessiah regarding the menu system that was one of the final puzzle pieces I needed to complete Backstage 2, the productivity of that project was halted yet again for what must be the tenth time in its sluggish, 5+ year development cycle. A bitterly ironic twist for the sequel of a game made in just one month.)
And so the saga of heaping too much onto an over-full plate continues.
CLASS PREVIEW: ELEMENTALIST
I want to use these blogs as an opportunity to talk about the battle mechanics and the underlying strategic and tactical choices apparent in Mage Duel Extreme, which are naturally the parts of this project I'm MOST psyched about. I feel like talking about one class a week kind of like I did with To Arms! would be a good way to break this development discussion into convenient bite sized chunks. Once I've done one for all of the classes, I'll add a "classes" page.
So, without further ado or preamble I give you The Elementalist.
The words "Mage Select" at the top of the screen are animated.
The Elementalist's default name is Iyo.
Mage Duel the first had some balance issues, that's to be certain. Namely, the Conjurer was a massively overpowered "easy mode", turning one-on-one duels into two-on-one massacres. The Healer, meanwhile, focused entirely too much on healing damage in a game that was about DOING damage. So I knew those two were OUT of the remake, and therefore my starting class lineup would look nothing like that of the original.
Rather than pair the two original classes that worked with two new classes, I decided to make all of the original classes (and half of the new ones) unlockable and include classes LIKE them but different in subtle but important ways as the initially available mages for selection. The Elementalist is in many ways a stand-in for the old Evoker, and the Enchanter is a reimagining of the old Illusionist. Just like the Abjurer replaces the old Healer, while the Conjurer has no direct expy. But that gets more complicated because unlike Healer and Conjurer, Evokers and Illusionists still exist in the game.
So what are the differences between Elementalists and Evokers? Well I could talk about that in terms of mechanics or in terms of fluff.
Fluff-wise, Elementalists are all about HARMONIZING with one or more of the elements (Fire, Water, Air or Earth), a life long dedication to the principles their chosen element(s) represent.
Evokers don't give a fig for water or earth, and they only care about fire because it can deal damage, like their other two favorites, ice and lightning. These aren't elemental affinities to be revered or emulated or gods forbid harmonized with. Evokers use all of thse things as a means to an end: the end of your life, that is.
The mechanical explanation of the differences follows much the same lines.
Elementalists get access to three elements that Evokers don't: Earth, Wind, and Water. These are conveniently three elements that are tougher to absorb/negate than Fire, Ice, and Lightning. Fire remains a strong choice as it has more raw damage dealing potential. In return, of course, Elementalists aren't quite as effective off the bat at raw direct damage than Evokers.
Both classes can deal lots of nasty status effects to the enemy but Elementalists get access to something Evokers don't--elementally themed buffs like Windstride and Stoneskin, which can maximize turn control or minimize incoming damage. The only status effects that Evokers deal in are crippling debuffs; they can't enhance their own power. Elementalists also get another option totally off limits to Evokers: HEALING. This makes them a much more well-rounded and less needle-focused class overall.
In review, here are the features of the Elementalist class NOT already explicitly detailed on the character select screen above:
* Unlike other classes, Elementalists have no special status or elemental weaknesses or resistances out of the starting gate. (Status ailment resistance is handled somewhat uniquely in MDX and might deserve a blog post of its own down the road.)
* Elementalists can equip Rods and Wands but not Staves or Swords.
* Elementalists can equip all Hats, Auras, Robes and Charms but not Armor or Helms.
* Elementalists and so far ONLY Elementalists can choose a "Quickened Spell" from the Magic menu. This Quickened Spell costs two spell-picks to learn and acts as a passive boost to the Elementalist's powers, while permanently "specializing" the Elementalist and imposing a weakness. The Quickening possibilities are:
1) Infernus Pact - +50% Fire Damage output, Fire Immunity, +100% Weakness to Water.
2) Be Like Water - +50% Water Damage dealt, Water Immunity, +100% Weakness to Fire.
3) Zephyr - +50% Air Damage dealt, Air Immunity, +100% Weakness to Earth.
4) Earthdawn - +50% Earth Damage dealt, Earth Immunity, +100% Weakness to Air.
An Elementalist with Infernus Pact is a Pyromancer, an Elementalist with Be Like Water is a Hydromancer, an Elementalist with Zephyr is an Aeromancer and an Elementalist with Earthdawn is a Geomancer. Once a specialization is chosen, no other Quickened Spell can be taken, so choose wisely.
* Finally, here is the complete ELEMENTALIST SPELL LIST.
# FlareS: Basic Fire damage. STARTING SPELL.
# SplashS Basic Water damage. STARTING SPELL.
# GustS: Basic Air damage.
# StoneS Basic Earth damage.
# Burn Notice Weak Fire damage plus can inflict Flammable State (100% Weakness to Fire Damage). Requires FlareS.
# Watery Grave: Weak Water damage and low chance to inflict Death. Requires SplashS. Two picks.
# Blow Down: Weak Air damage and high chance to Stun. Requires GustS. Damage partially based on Quickness, meaning it improves with Windstrider.
# Seal: Weak Earth damage and low chance to inflict Stone'D (Petrified). Requires StoneS. Two picks.
# Stoneskin: Grant one ally a massive resistance to physical damage for a time.
# Windstrider: Grant one ally an extra turn, a 33% Evasion bonus, and extra 150% Quickness for a time.
# Fire Heal: Use the power of fire to heal one ally's LP.
# Flush System: Use Water magic to cure many status maladies. InstantCast.
# Napalm: Get back in the fiery water. Lots of damage to all foes. This is three picks in the current build but will eventually be reduced to just two.
# Maelstrom: Twelve random hits of StoneS and GustS to 12 random foes. Two picks.
All in all, Elementalist is meant to be a beginner-friendly class, well-rounded, with few extreme strengths and weaknesses and clear-and-obvious internal skill synergies.
HALP WANTED!
Are you reading this page? Are you handy with CSS? Please help me spruce up the game page for Mage Duel Extreme into something more unique! I will happily trade an equal amount of any of my own writing, testing, or miscellaneous game design services in exchange. Thank you!
Release Log
I've already unleashed two super-minor updates to Mage Duel Extreme since the first download link I unveiled on Release Something! Day. Here's the full change log for the most recent available download:
# Delusions of Grandeur returned to its rightful place on the ENCHANTER Spell List.
# Delusions of Granduer nerfed while I was at it.
# Sleeping characters now take 2x damage from the attack that wakes them up.
# Mantra fixed and working properly.
# Stunning word fixed and working properly.
# One of Enchanter's dump stats moved from Strength to LP. (Overall slight increase in power.)
# Avana's Grenado and Poison Shot are now *physical attacks* as they always should have been.
# Save bug fixed! The save point following the first cutscene was bugged for some characters, but has been fixed.
# Cyath AI slightly altered.
Hi I want to blog about the development of Mage Duel Extreme. This particular entry will be a multi-parter. Most of them won't!
First Principles
Mage Duel the first was my very first attempt at making something in RPG Maker VX back in 2008. It is the very oldest of my new games. Please note I don't say "first serious game" or "first game I was happy with". Like the very first thing I EVER did in the RMVX editor was to map the arena and underworks (which are still being used in this game).
The purpose of making the original Mage Duel was to teach myself RPG Maker VX.
Mage Duel Extreme served the same purpose for the first major RPG Maker program to come out SINCE RPG Maker VX: RPG Maker VX with Yanfly Engine Melody. I actually first attempted the MDX training project as literally just a test project, with no intention of showing it to anyone, back in 2009. I didn't get further than the animated battler config, which I couldn't figure out--YEM can be a bitch to config, and sometimes the comments raise more questions than they answer. So in the end I buried the project, a massively frustrating timesink like my first few efforts to use YEM, in a folder literally called "What were you even thinking?" where it remains to this day.
Fast forward two years to 2011, which has been a rough year for me in a lot of ways. To highlight the one most relevant to this anecdote: I went through an RPG Maker phase this January or so, working feverishly on a project codenamed CONJURER on my own laptop. This fever was fucking COOLED by the fact that my laptop (and at the time only computer) could not PLAY RPG MAKER VX games--mine or other people's--without a hellish nightmare of lag. What I could do still, however, was work on 2k3 games.
I tried, hard, to leverage this disadvantage into motivation: even though I could, barely and only by a stretch, afford a new computer (I opted for a desktop, and I still use my crappy old laptop, which has only grown crappier, for portability) I would hold out until I had finished Backstage 2. Since I could only work on 2k3, it would make it that much easier for me to focus on finishing an ancient project: VX was out of the question anyway.
I held out literally months, until the summer, without buying a new computer. Once I bought it, I told myself it changed nothing: no RPG Maker VX until I'd finished Backstage 2. I lasted a matter of days without setting up and opening the computer. I told myself I would only PLAY RMVX games, to make sure they worked. That I wouldn't open CODE NAME: CONJURER again in the editor. But little did I know that the first RMVX game in my backlog that I'd been wanting to play would make my desire to play with YEM FULLY INSURMOUNTABLE. Edifice, if nothing else, functions as an awesome advertisement for the capabilities of YEM as a toolset, although I know Craze would add that there's no shortage of his own code in there, powering the works.
Anyway, opening MDX instead of Code Name Conjurer, telling myself that this was "not a real project" and I "just wanted to play with the mechanics" and I "wouldn't abandon Backstage 2 development" was how this project was born. (Between this temptation and the long silence of Archeiah_Nessiah regarding the menu system that was one of the final puzzle pieces I needed to complete Backstage 2, the productivity of that project was halted yet again for what must be the tenth time in its sluggish, 5+ year development cycle. A bitterly ironic twist for the sequel of a game made in just one month.)
And so the saga of heaping too much onto an over-full plate continues.
CLASS PREVIEW: ELEMENTALIST
I want to use these blogs as an opportunity to talk about the battle mechanics and the underlying strategic and tactical choices apparent in Mage Duel Extreme, which are naturally the parts of this project I'm MOST psyched about. I feel like talking about one class a week kind of like I did with To Arms! would be a good way to break this development discussion into convenient bite sized chunks. Once I've done one for all of the classes, I'll add a "classes" page.
So, without further ado or preamble I give you The Elementalist.
The words "Mage Select" at the top of the screen are animated.
The Elementalist's default name is Iyo.
Mage Duel the first had some balance issues, that's to be certain. Namely, the Conjurer was a massively overpowered "easy mode", turning one-on-one duels into two-on-one massacres. The Healer, meanwhile, focused entirely too much on healing damage in a game that was about DOING damage. So I knew those two were OUT of the remake, and therefore my starting class lineup would look nothing like that of the original.
Rather than pair the two original classes that worked with two new classes, I decided to make all of the original classes (and half of the new ones) unlockable and include classes LIKE them but different in subtle but important ways as the initially available mages for selection. The Elementalist is in many ways a stand-in for the old Evoker, and the Enchanter is a reimagining of the old Illusionist. Just like the Abjurer replaces the old Healer, while the Conjurer has no direct expy. But that gets more complicated because unlike Healer and Conjurer, Evokers and Illusionists still exist in the game.
So what are the differences between Elementalists and Evokers? Well I could talk about that in terms of mechanics or in terms of fluff.
Fluff-wise, Elementalists are all about HARMONIZING with one or more of the elements (Fire, Water, Air or Earth), a life long dedication to the principles their chosen element(s) represent.
Evokers don't give a fig for water or earth, and they only care about fire because it can deal damage, like their other two favorites, ice and lightning. These aren't elemental affinities to be revered or emulated or gods forbid harmonized with. Evokers use all of thse things as a means to an end: the end of your life, that is.
The mechanical explanation of the differences follows much the same lines.
Elementalists get access to three elements that Evokers don't: Earth, Wind, and Water. These are conveniently three elements that are tougher to absorb/negate than Fire, Ice, and Lightning. Fire remains a strong choice as it has more raw damage dealing potential. In return, of course, Elementalists aren't quite as effective off the bat at raw direct damage than Evokers.
Both classes can deal lots of nasty status effects to the enemy but Elementalists get access to something Evokers don't--elementally themed buffs like Windstride and Stoneskin, which can maximize turn control or minimize incoming damage. The only status effects that Evokers deal in are crippling debuffs; they can't enhance their own power. Elementalists also get another option totally off limits to Evokers: HEALING. This makes them a much more well-rounded and less needle-focused class overall.
In review, here are the features of the Elementalist class NOT already explicitly detailed on the character select screen above:
* Unlike other classes, Elementalists have no special status or elemental weaknesses or resistances out of the starting gate. (Status ailment resistance is handled somewhat uniquely in MDX and might deserve a blog post of its own down the road.)
* Elementalists can equip Rods and Wands but not Staves or Swords.
* Elementalists can equip all Hats, Auras, Robes and Charms but not Armor or Helms.
* Elementalists and so far ONLY Elementalists can choose a "Quickened Spell" from the Magic menu. This Quickened Spell costs two spell-picks to learn and acts as a passive boost to the Elementalist's powers, while permanently "specializing" the Elementalist and imposing a weakness. The Quickening possibilities are:
1) Infernus Pact - +50% Fire Damage output, Fire Immunity, +100% Weakness to Water.
2) Be Like Water - +50% Water Damage dealt, Water Immunity, +100% Weakness to Fire.
3) Zephyr - +50% Air Damage dealt, Air Immunity, +100% Weakness to Earth.
4) Earthdawn - +50% Earth Damage dealt, Earth Immunity, +100% Weakness to Air.
An Elementalist with Infernus Pact is a Pyromancer, an Elementalist with Be Like Water is a Hydromancer, an Elementalist with Zephyr is an Aeromancer and an Elementalist with Earthdawn is a Geomancer. Once a specialization is chosen, no other Quickened Spell can be taken, so choose wisely.
* Finally, here is the complete ELEMENTALIST SPELL LIST.
# FlareS: Basic Fire damage. STARTING SPELL.
# SplashS Basic Water damage. STARTING SPELL.
# GustS: Basic Air damage.
# StoneS Basic Earth damage.
# Burn Notice Weak Fire damage plus can inflict Flammable State (100% Weakness to Fire Damage). Requires FlareS.
# Watery Grave: Weak Water damage and low chance to inflict Death. Requires SplashS. Two picks.
# Blow Down: Weak Air damage and high chance to Stun. Requires GustS. Damage partially based on Quickness, meaning it improves with Windstrider.
# Seal: Weak Earth damage and low chance to inflict Stone'D (Petrified). Requires StoneS. Two picks.
# Stoneskin: Grant one ally a massive resistance to physical damage for a time.
# Windstrider: Grant one ally an extra turn, a 33% Evasion bonus, and extra 150% Quickness for a time.
# Fire Heal: Use the power of fire to heal one ally's LP.
# Flush System: Use Water magic to cure many status maladies. InstantCast.
# Napalm: Get back in the fiery water. Lots of damage to all foes. This is three picks in the current build but will eventually be reduced to just two.
# Maelstrom: Twelve random hits of StoneS and GustS to 12 random foes. Two picks.
All in all, Elementalist is meant to be a beginner-friendly class, well-rounded, with few extreme strengths and weaknesses and clear-and-obvious internal skill synergies.
***END ELEMENTALIST***
HALP WANTED!
Are you reading this page? Are you handy with CSS? Please help me spruce up the game page for Mage Duel Extreme into something more unique! I will happily trade an equal amount of any of my own writing, testing, or miscellaneous game design services in exchange. Thank you!
Release Log
I've already unleashed two super-minor updates to Mage Duel Extreme since the first download link I unveiled on Release Something! Day. Here's the full change log for the most recent available download:
# Delusions of Grandeur returned to its rightful place on the ENCHANTER Spell List.
# Delusions of Granduer nerfed while I was at it.
# Sleeping characters now take 2x damage from the attack that wakes them up.
# Mantra fixed and working properly.
# Stunning word fixed and working properly.
# One of Enchanter's dump stats moved from Strength to LP. (Overall slight increase in power.)
# Avana's Grenado and Poison Shot are now *physical attacks* as they always should have been.
# Save bug fixed! The save point following the first cutscene was bugged for some characters, but has been fixed.
# Cyath AI slightly altered.
Game Design
Scratching That Old Itch
Hi this is a blog post about "rebooting" game projects in general.
I think every game developer struggles with the urge, once they get 25% or 50% into a project, to stop, and start from scratch. Why? Not because we all hate completing things, but because just by making a game, you can learn so much about game making in general--and about making THAT game in particular--that the quality gap between the part you're working on now and the beginning that you did ages ago seems grotesquely huge. So to ensure uniform quality, you want to go back to the beginning and apply everything you've learned since then!
Rinse and repeat.
And that, my friends, is perfectionism and I abhor perfectionism. Few enough games get released as it is--due to mere exhaustion, disillusionment, or attention deficit--without this need to constantly start over from the beginning and "do it better" or "get it right". Generally speaking, I advocate game design from the brain to the screen with as few intervening revisions as possible--just as many as are absolutely necessary. I have always hated the idea of reboots--even if the beginning isn't perfect, just finish the darn game! (Important disclaimer, it is in fact the new version of Edifice that is the one I like.)
HOWEVER,
There are some times when the gap between your development skills (and the resources available to you) when starting a project and years later, looking back on it, is simply too vast to ignore. A time when merely RESUMING a project seems absurd, because you have learned SO MUCH that you must CHANGE EVERYTHING. And Mage Duel (Extreme!) is such a case for me.
See, the original Mage Duel is in many ways a "my very first gam ever" game. I made it as an exercise to re-teach myself RPG maker in general after years of not using it, and to teach myself the ropes of RPG Maker VX for the first time. It was never meant to be GOOD. It was a learning experience, and nothing more--that's probably why it was so damn silly when most of my games are kind of, you know, serious.
That it also is the most successful game I've ever made, at least by some rubrics, confounds me to this day. But I digress.
Nonetheless, it was a concept I was invested in but the developer I was at the time really wasn't doing it justice. As a developer, I think I'm at or near the height of my powers. I'm not saying I'm the greatest, but I am saying I"m probably the closest I'll be to my personal best between now and when I quit forever. Although I've said that before and been wrong, so take this with a grain of salt. Anyway, I'm a hell of a lot better than I was in 2008. So this is my attempt--against all of my general principles--to reinforce everything that made the original Mage Duel good with everything I've learned about game design in the three long years since then, and harnessing the power of the hyperbolically awesome game development tool that is Yanfly Engine Melody.
If you liked Mage Duel, I should be able to reasonably predict that you will like this much, much better. Now obviously this is a bit rough around the edges--it's an RS!D project dump, not a proper demo--but nonetheless, please do:
GET IT WHILE IT'S HOT!
EDIT:
By the way, this being an RS!D project dump, you can expect this to be a mess of bugs, and there are some important features missing from this that will be present in the full game. Most saliently:
1) The last 10 battles.
2) The finer points of game balance.
3) A playable Necromancer, Artificer, Evoker, or Illusionist.
4) Monster battles, a feature I'm not sure I'm carrying over from the original. This means there's no way to grind your way out of trouble, so save often!
Additionally, several of the skills which are included but not yet featured are untested or have known bugs.
I think every game developer struggles with the urge, once they get 25% or 50% into a project, to stop, and start from scratch. Why? Not because we all hate completing things, but because just by making a game, you can learn so much about game making in general--and about making THAT game in particular--that the quality gap between the part you're working on now and the beginning that you did ages ago seems grotesquely huge. So to ensure uniform quality, you want to go back to the beginning and apply everything you've learned since then!
Rinse and repeat.
And that, my friends, is perfectionism and I abhor perfectionism. Few enough games get released as it is--due to mere exhaustion, disillusionment, or attention deficit--without this need to constantly start over from the beginning and "do it better" or "get it right". Generally speaking, I advocate game design from the brain to the screen with as few intervening revisions as possible--just as many as are absolutely necessary. I have always hated the idea of reboots--even if the beginning isn't perfect, just finish the darn game! (Important disclaimer, it is in fact the new version of Edifice that is the one I like.)
HOWEVER,
There are some times when the gap between your development skills (and the resources available to you) when starting a project and years later, looking back on it, is simply too vast to ignore. A time when merely RESUMING a project seems absurd, because you have learned SO MUCH that you must CHANGE EVERYTHING. And Mage Duel (Extreme!) is such a case for me.
See, the original Mage Duel is in many ways a "my very first gam ever" game. I made it as an exercise to re-teach myself RPG maker in general after years of not using it, and to teach myself the ropes of RPG Maker VX for the first time. It was never meant to be GOOD. It was a learning experience, and nothing more--that's probably why it was so damn silly when most of my games are kind of, you know, serious.
That it also is the most successful game I've ever made, at least by some rubrics, confounds me to this day. But I digress.
Nonetheless, it was a concept I was invested in but the developer I was at the time really wasn't doing it justice. As a developer, I think I'm at or near the height of my powers. I'm not saying I'm the greatest, but I am saying I"m probably the closest I'll be to my personal best between now and when I quit forever. Although I've said that before and been wrong, so take this with a grain of salt. Anyway, I'm a hell of a lot better than I was in 2008. So this is my attempt--against all of my general principles--to reinforce everything that made the original Mage Duel good with everything I've learned about game design in the three long years since then, and harnessing the power of the hyperbolically awesome game development tool that is Yanfly Engine Melody.
If you liked Mage Duel, I should be able to reasonably predict that you will like this much, much better. Now obviously this is a bit rough around the edges--it's an RS!D project dump, not a proper demo--but nonetheless, please do:
GET IT WHILE IT'S HOT!
EDIT:
By the way, this being an RS!D project dump, you can expect this to be a mess of bugs, and there are some important features missing from this that will be present in the full game. Most saliently:
1) The last 10 battles.
2) The finer points of game balance.
3) A playable Necromancer, Artificer, Evoker, or Illusionist.
4) Monster battles, a feature I'm not sure I'm carrying over from the original. This means there's no way to grind your way out of trouble, so save often!
Additionally, several of the skills which are included but not yet featured are untested or have known bugs.
Pages:
1