Full Games List
Featured Games
New Games
Reviews
Images
Blogs
Game Updates
Images Feedback Summary
Game Design Highlights
Tutorials
Articles
Scripts
Utilities / Plugins
Resources
Engines
Engine Bulletins
What is Makerscore?
Past Events
Achievements
Forums
Post History
Chat
New to RMN?
Full Store List
RMN Music Pack (free)
Add Review
Subscribe
Nominate
Submit Media
RSS
*Backstage II is not an RPG but a psychological-horror adventure game. Most of the gameplay is exploration and/or solving simple puzzles to advance the story.
*Combat in Backstage II is conducted through a Seamless Cinematic Combat System (SCCS) which is a fancy way to say that it's mostly automatic. Combat starts if you collide with an enemy and is over in a few seconds without any input from you.
There are NO HUDS, NUMBERS, OR HEALTH BARS ever displayed on the screen, which is why it's seamless and cinematic. The game does not pause or its perspective change for combat. Combat resolves itself automatically largely based on what weapon you have equipped (if any) and a few other factors.
*Improvements to the SCCS since Backstage:
The combat system in Backstage II has been seriously overhauled since the original, given more bells and whistles and made more interactive. The player's choices should now have a greater effect on success or failure in combat. The basic system is the came, but modifications include the following:
+Weapons can now be 'equipped' through the main menu. This way you can choose which weapons are used on which enemies, unlike in Backstage where players were all-to-often screwed out of ammo by the automatic prioritization of Guns before Defense Items. (No more will you waste a crucial bullet on a Nightgaunt and then wind up killed by a Clockwork because all you have is a Glass Shard.)
+Defense Weapons have been added to the game. Defense weapons are like defense items, only infinitely reusable. (Unlike a glass shard, a combat knife won't break if you use it to defend yourself.) Defense weapons can only be used by The Prodigal whereas The Prophet still uses Defense Items much like in the original Backstage. To compensate for their infinite uses, Defense Weapons have less-than-perfect Accuracy. Each weapon has a base accuracy represented by a percent chance to hit. Different situational factors (more below) can effect a Defense weapon's accuracy. Although generally preferable, Defense weapons are risky to use- poor acccuracy can result in multiple hits from one monster, although each successive swing increases your probability of hitting.
+Running system has been added. Press SHIFT to toggle between walking and running. (Default is walking.) The main interactive element of combat in Backstage is still trying to avoid monsters to conserve ammunition. The ability to toggle between walking and running adds another level to this mechanic. While running, obviously, you will move faster, but receive a penalty to acccuracy with Defense Weapons. It will be easier to avoid monsters, but if you do run into one, you will have a greater chance of being damaged if you're equipped with a Defense Weapon. Running while unarmed or armed with a firearm has no disadvantages, save that firearms have limited ammo and while unarmed you will be automatically damaged.
+Directional-Combat has been implemented. If you 'Attack' a monster (collide with it instead of it colliding with you) head on you will receive a bonus to accuracy when using a Defense Weapon. If a monster catches you and hits your back or sides, you won't receive this bonus.
+Major Cosmetic Improvement: 18 different fluid character poses, articulated character movement, and improved battle animations make combat in Backstage look MUCH more like combat. If you watch carefully and don't blink, for instance, you could see Raechel attempt to fire at an enemy with an unloaded pistol, have the gun click empty, be slashed by the enemy, and then pistol whip it with the empty gun to kill it. This is the major improvement from Backstage.
And that's all you really need to know. Enjoy!
*Combat in Backstage II is conducted through a Seamless Cinematic Combat System (SCCS) which is a fancy way to say that it's mostly automatic. Combat starts if you collide with an enemy and is over in a few seconds without any input from you.
There are NO HUDS, NUMBERS, OR HEALTH BARS ever displayed on the screen, which is why it's seamless and cinematic. The game does not pause or its perspective change for combat. Combat resolves itself automatically largely based on what weapon you have equipped (if any) and a few other factors.
*Improvements to the SCCS since Backstage:
The combat system in Backstage II has been seriously overhauled since the original, given more bells and whistles and made more interactive. The player's choices should now have a greater effect on success or failure in combat. The basic system is the came, but modifications include the following:
+Weapons can now be 'equipped' through the main menu. This way you can choose which weapons are used on which enemies, unlike in Backstage where players were all-to-often screwed out of ammo by the automatic prioritization of Guns before Defense Items. (No more will you waste a crucial bullet on a Nightgaunt and then wind up killed by a Clockwork because all you have is a Glass Shard.)
+Defense Weapons have been added to the game. Defense weapons are like defense items, only infinitely reusable. (Unlike a glass shard, a combat knife won't break if you use it to defend yourself.) Defense weapons can only be used by The Prodigal whereas The Prophet still uses Defense Items much like in the original Backstage. To compensate for their infinite uses, Defense Weapons have less-than-perfect Accuracy. Each weapon has a base accuracy represented by a percent chance to hit. Different situational factors (more below) can effect a Defense weapon's accuracy. Although generally preferable, Defense weapons are risky to use- poor acccuracy can result in multiple hits from one monster, although each successive swing increases your probability of hitting.
+Running system has been added. Press SHIFT to toggle between walking and running. (Default is walking.) The main interactive element of combat in Backstage is still trying to avoid monsters to conserve ammunition. The ability to toggle between walking and running adds another level to this mechanic. While running, obviously, you will move faster, but receive a penalty to acccuracy with Defense Weapons. It will be easier to avoid monsters, but if you do run into one, you will have a greater chance of being damaged if you're equipped with a Defense Weapon. Running while unarmed or armed with a firearm has no disadvantages, save that firearms have limited ammo and while unarmed you will be automatically damaged.
+Directional-Combat has been implemented. If you 'Attack' a monster (collide with it instead of it colliding with you) head on you will receive a bonus to accuracy when using a Defense Weapon. If a monster catches you and hits your back or sides, you won't receive this bonus.
+Major Cosmetic Improvement: 18 different fluid character poses, articulated character movement, and improved battle animations make combat in Backstage look MUCH more like combat. If you watch carefully and don't blink, for instance, you could see Raechel attempt to fire at an enemy with an unloaded pistol, have the gun click empty, be slashed by the enemy, and then pistol whip it with the empty gun to kill it. This is the major improvement from Backstage.
And that's all you really need to know. Enjoy!
Latest Blog
A Look Backstage Part II...Many Things
Max McGee
First off, I just added a veritable raft of new images to the Backstage 2 game page. As people assign a lot of significance to screenshots, I'd just like to make a handful of disclaimers:
a) The game is between ~60 and ~80% done, so at this point criticism on visual or aesthetic mistakes that can't be easily fixed is not desired. If I can fix it in a minute or so of clicking I want to hear about it. If not, unless it breaks the game and makes it unplayable (which of course you can't tell from a screenshot) I'd rather not know.
b) Some of these may well look better in motion than they do as still images; the same goes with the dialogue, which might work better within its greater context. Judging Backstage on images alone is a bit unfair anyway; it's the sound design more than anything that creates the atmosphere.
c) Does it look too dark on your monitor? If so tell me. I'm considering adding an 'adjust your monitor brightness so this symbol/writing is barely visible' screen at the game start. A couple of them look darker as screenshots than they really
d) If you've been following Backstage 2 since 2006, don't expect too much that's really new. Many of these screens show the same maps and scenes that you first saw 4 or 5 years ago. To most RMN users, though, this should be new to you, unless you're one of the tiny number of people who've already played the demo.
e) Finally, several of these maps SHOULD be upgraded with reasonably sexy lighting effects before the game sees final release. Consider these screens the "plain" or "naked" version.
Secondly, I'd like to talk about systematic/procedural vs. sequential or "as you go along" design methods.
It doesn't look like much compared to the other maps, with their weather, screen tone, lighting effects, and other atmosphere, but this map, labeled 'battle system test', has been the hardest part of the entire process of making Backstage 2.
How do you make your games? Do you do all of the setup stuff all at once (create all of the heroes, classes, skills, equipment, items, and monsters in the database, create all of the maps, and then begin eventing)? Or do you do "just enough" of the procedural tasks in order to be able to expand the playable part of the game a few minutes at a time? i.e., did you ever make just enough maps and items to start the intro and the first section of gameplay, and had to go back to making more maps when you realized that the teleport event on the last one you'd made had nowhere to go to? Have you ever created a chest event only to go back and create the item the chest was supposed to give in the database right and there?
I feel like on the professional side of things procedural generation is much more common. Let's nail down the battle system before we start working on maps. Let's finish all the maps before we start writing events. Etcetera. However, for most amateurs--at least I know for myself--doing things 'as you go along' is key to your sanity as you battle the tedium of game development and struggle to stay motive, using variety as another weapon in your arsenal.
However, Backstage 2 really forced me to get systematic. For some background:
Backstage has two playable characters. Each playable character has six unique weapons they can equip over the course of the game (note that Tom from the original Backstage had only 5; glass shard, revolver, automatic, molotov, and shotgun, so the number of weapons in this game has more than doubled, as has the nuance and complexity of the battle system). These six weapons only have one instance of overlapping. Additionally, enemies need to be coded in such a way that an enemy for the 'Tim' portion of the game is unusable for the 'Raechel' portion of the game, because of how they manipulate animation poses. If Tim were to be turned into a wounded Raechel graphic, for instance, that wouldn't be right. There are also seven basic types of enemies, each of which has different attributes and properties. (Cataracts are poisonous and infect you if you are hit by them or hit them in melee with anything but a Fire based weapon; Clockworks can only be damaged by High Power weapons; Gasmasks can shoot you from a distance if you're not careful to dodge their projectiles while closing. And so on.)
So basically, there is one page of event code per weapon, per enemy, per character for me to copy paste and fiddle with. This is extraordinarily tedious and of course one switch or page missed means a potentially game breaking error. So what I have been doing is only giving enemies event code for the weapons that *can be found in the game before the enemy is encountered*. For instance, early game(Raechel) Nightgaunts can only be dispatched with bare fists, a combat knife, or the automatic pistol because those are the only weapons available in the early game. The problem with this should be obvious; if you can successfully escape an early game enemy and backtrack with a more powerful weapon to take it on later, it treats you as unarmed because it doesn't have the code for, say, a Colt Single Action army because you're not *supposed* to have that weapon at that point in the game.
This forced me to get Systematic and I really did. I managed to get Backstage II's entire battle system done over several marathon sessions comprised of hour after hour of eventing. All seven enemies can now be engaged (differently) by all weapons wielded by both heroes. This required at least 112 full pages of event code lousy with nested conditionals and switch and variable manipulation. (8 Pages per enemy x 7 Enemies per PC x 2 PCs = 112). I'm very glad I got this over with, and actually, putting the enemies side by side and testing their respective danger levels (as well as the new graphics for dispatching them with the new weapons) was very exciting. I wound up rebalancing the entire battle system by slightly modifying the stats of all major enemies; where it would improve the game, I also reskinned some of them with new and hopefully more menacing graphics. The Cataract is my favorite although at least two enemies from Backstage 1 also make a return. Hopefully this time around the enemies' strengths and weaknesses and overall threat level will be more clearly defined, whiles till keeping the focus where it should be, on scaring the player and on telling a truly creepy story.
Most importantly, though, I can now just plug and play, inserting enemies into the game and the story without having to worry about coding new weapons and sequences for them. Just switch the 'death' switch, and they're ready to go.
You'll notice I haven't included any of the enemy designs, old or new, on the screenshots I uploaded today, except the one in-editor one there where you can barely see them. There were two reasons for that; one is that the worse a horror movie's special effects are, the less the monster should be seen. It worked amazing for Alien. Secondly, those screenshots are from the early game, and Backstage II has a MUCH slower based opening than the original. It will be a while before you see your first monster, this time around.
***
Last but not least, Backstage 2 was recently featured on the Sore Losers gaming blog. While of course around here we all know Fallen-Griever as our friendly neighborhood game reviewer, I thought his blog looked quite professional and I felt honored to be getting a plug there. (Hopefully the review, when it comes, will be a favorable one.)
Anyway, that's it for this edition of "A Look Backstage" and that's it for this week's update! As usual stay tuned for more updates in the future, although the next couple weeks will be pretty crazy for me, so probably not until mid-August. I am very excited to finally be on the cusp of starting to finish this project, though!
a) The game is between ~60 and ~80% done, so at this point criticism on visual or aesthetic mistakes that can't be easily fixed is not desired. If I can fix it in a minute or so of clicking I want to hear about it. If not, unless it breaks the game and makes it unplayable (which of course you can't tell from a screenshot) I'd rather not know.
b) Some of these may well look better in motion than they do as still images; the same goes with the dialogue, which might work better within its greater context. Judging Backstage on images alone is a bit unfair anyway; it's the sound design more than anything that creates the atmosphere.
c) Does it look too dark on your monitor? If so tell me. I'm considering adding an 'adjust your monitor brightness so this symbol/writing is barely visible' screen at the game start. A couple of them look darker as screenshots than they really
d) If you've been following Backstage 2 since 2006, don't expect too much that's really new. Many of these screens show the same maps and scenes that you first saw 4 or 5 years ago. To most RMN users, though, this should be new to you, unless you're one of the tiny number of people who've already played the demo.
e) Finally, several of these maps SHOULD be upgraded with reasonably sexy lighting effects before the game sees final release. Consider these screens the "plain" or "naked" version.
Secondly, I'd like to talk about systematic/procedural vs. sequential or "as you go along" design methods.
It doesn't look like much compared to the other maps, with their weather, screen tone, lighting effects, and other atmosphere, but this map, labeled 'battle system test', has been the hardest part of the entire process of making Backstage 2.
How do you make your games? Do you do all of the setup stuff all at once (create all of the heroes, classes, skills, equipment, items, and monsters in the database, create all of the maps, and then begin eventing)? Or do you do "just enough" of the procedural tasks in order to be able to expand the playable part of the game a few minutes at a time? i.e., did you ever make just enough maps and items to start the intro and the first section of gameplay, and had to go back to making more maps when you realized that the teleport event on the last one you'd made had nowhere to go to? Have you ever created a chest event only to go back and create the item the chest was supposed to give in the database right and there?
I feel like on the professional side of things procedural generation is much more common. Let's nail down the battle system before we start working on maps. Let's finish all the maps before we start writing events. Etcetera. However, for most amateurs--at least I know for myself--doing things 'as you go along' is key to your sanity as you battle the tedium of game development and struggle to stay motive, using variety as another weapon in your arsenal.
However, Backstage 2 really forced me to get systematic. For some background:
Backstage has two playable characters. Each playable character has six unique weapons they can equip over the course of the game (note that Tom from the original Backstage had only 5; glass shard, revolver, automatic, molotov, and shotgun, so the number of weapons in this game has more than doubled, as has the nuance and complexity of the battle system). These six weapons only have one instance of overlapping. Additionally, enemies need to be coded in such a way that an enemy for the 'Tim' portion of the game is unusable for the 'Raechel' portion of the game, because of how they manipulate animation poses. If Tim were to be turned into a wounded Raechel graphic, for instance, that wouldn't be right. There are also seven basic types of enemies, each of which has different attributes and properties. (Cataracts are poisonous and infect you if you are hit by them or hit them in melee with anything but a Fire based weapon; Clockworks can only be damaged by High Power weapons; Gasmasks can shoot you from a distance if you're not careful to dodge their projectiles while closing. And so on.)
So basically, there is one page of event code per weapon, per enemy, per character for me to copy paste and fiddle with. This is extraordinarily tedious and of course one switch or page missed means a potentially game breaking error. So what I have been doing is only giving enemies event code for the weapons that *can be found in the game before the enemy is encountered*. For instance, early game(Raechel) Nightgaunts can only be dispatched with bare fists, a combat knife, or the automatic pistol because those are the only weapons available in the early game. The problem with this should be obvious; if you can successfully escape an early game enemy and backtrack with a more powerful weapon to take it on later, it treats you as unarmed because it doesn't have the code for, say, a Colt Single Action army because you're not *supposed* to have that weapon at that point in the game.
This forced me to get Systematic and I really did. I managed to get Backstage II's entire battle system done over several marathon sessions comprised of hour after hour of eventing. All seven enemies can now be engaged (differently) by all weapons wielded by both heroes. This required at least 112 full pages of event code lousy with nested conditionals and switch and variable manipulation. (8 Pages per enemy x 7 Enemies per PC x 2 PCs = 112). I'm very glad I got this over with, and actually, putting the enemies side by side and testing their respective danger levels (as well as the new graphics for dispatching them with the new weapons) was very exciting. I wound up rebalancing the entire battle system by slightly modifying the stats of all major enemies; where it would improve the game, I also reskinned some of them with new and hopefully more menacing graphics. The Cataract is my favorite although at least two enemies from Backstage 1 also make a return. Hopefully this time around the enemies' strengths and weaknesses and overall threat level will be more clearly defined, whiles till keeping the focus where it should be, on scaring the player and on telling a truly creepy story.
Most importantly, though, I can now just plug and play, inserting enemies into the game and the story without having to worry about coding new weapons and sequences for them. Just switch the 'death' switch, and they're ready to go.
You'll notice I haven't included any of the enemy designs, old or new, on the screenshots I uploaded today, except the one in-editor one there where you can barely see them. There were two reasons for that; one is that the worse a horror movie's special effects are, the less the monster should be seen. It worked amazing for Alien. Secondly, those screenshots are from the early game, and Backstage II has a MUCH slower based opening than the original. It will be a while before you see your first monster, this time around.
***
Last but not least, Backstage 2 was recently featured on the Sore Losers gaming blog. While of course around here we all know Fallen-Griever as our friendly neighborhood game reviewer, I thought his blog looked quite professional and I felt honored to be getting a plug there. (Hopefully the review, when it comes, will be a favorable one.)
Anyway, that's it for this edition of "A Look Backstage" and that's it for this week's update! As usual stay tuned for more updates in the future, although the next couple weeks will be pretty crazy for me, so probably not until mid-August. I am very excited to finally be on the cusp of starting to finish this project, though!
- Cancelled
- Max McGee
- Archeia_Nessiah
NewBlack 
RPG Tsukuru 2003- Adventure
- 12/19/2008 04:04 PM
- 03/06/2023 02:26 PM
- N/A
- 126044
- 47
- 2113
Posts 
View playlists
Closethis game needs to be updated what the heck happened it hasnt been updated in 3 years what is taking it so long
kumada
3917
It's on hiatus, probably indefinitely.
It's frustrating, but it's sort of a hazard of freeware. Because there's no money involved, every freeware game that gets made is its own small victory against the forces of "I could be doing anything else right now."
It's frustrating, but it's sort of a hazard of freeware. Because there's no money involved, every freeware game that gets made is its own small victory against the forces of "I could be doing anything else right now."
i wonder why this game is taking so long to get released what is the hold up this game should have been completed a while ago
I'm sorry guys. I am really and genuinely sorry.
To quote my favorite poet: "I love your love, and I am thankful".
To quote my favorite poet: "I love your love, and I am thankful".
i dont get why he decided to cancel the game which sucks because i have been waiting for the game to be finished.
I am sorry for that slicervanguard.
I don't post here much any more. The reason why I decided to cancel this particular game is that...I don't even feel like the same person that did the bulk of the work on this game. Most of that work happened eleven or twelve years ago between '06-'07 when I was about twenty. Over that time I lost my easy working familiarity with the engine, as well as my familiarity with the sub-engine I had evented with it. And now a legal version of 2k3 with plugins has changed the entire playing field. And I'm really feeling the years between 20 and here, especially as the victim of a degenerative incurable autoimmune disease, which is by default a one-way trip to not-so-fun town.
Even if all my other priorities and responsibilities magically evaporated over night, I don't think I could finish this if I wanted to. It would be too much like trying to finish someone else's game, not knowing for sure either how to work with the code base/event base they've already built or what it was they ultimately intended. A lot can happen to a person in twelve years, enough that they no longer even recognize themselves in the mirror, even. Also nessy never followed through on the CMS she was going to make for me :P
By the way, I just want to point out that I have earned approximately $0.00 dollars for my work in RPG Maker which means I have performed literally 100s of thousands of hours of unpaid labor to give away high quality free videogames to all y'all.
Not to sound too salty, but having given away, for free, a hundred or so hours of RPG and adventure gameplay in various completed games, demos, and cancelled projects, I don't feel particularly obligated to put in more time doing unpaid labor to finish my games nor do I feel anyone is particularly entitled to my unpaid labor on behalf of gam mak. Or, more accurately, the strongest obligation I feel is to myself; it would have been cool if Backstage II has been finished, but that's not the world we live in. I know it's a disappointment, as life so often is, as I so often am.
Now, I would be happy to take on the challenge of finishing this if I was getting paid a living wage to do so, but I don't see that happening any time soon.
I don't post here much any more. The reason why I decided to cancel this particular game is that...I don't even feel like the same person that did the bulk of the work on this game. Most of that work happened eleven or twelve years ago between '06-'07 when I was about twenty. Over that time I lost my easy working familiarity with the engine, as well as my familiarity with the sub-engine I had evented with it. And now a legal version of 2k3 with plugins has changed the entire playing field. And I'm really feeling the years between 20 and here, especially as the victim of a degenerative incurable autoimmune disease, which is by default a one-way trip to not-so-fun town.
Even if all my other priorities and responsibilities magically evaporated over night, I don't think I could finish this if I wanted to. It would be too much like trying to finish someone else's game, not knowing for sure either how to work with the code base/event base they've already built or what it was they ultimately intended. A lot can happen to a person in twelve years, enough that they no longer even recognize themselves in the mirror, even. Also nessy never followed through on the CMS she was going to make for me :P
By the way, I just want to point out that I have earned approximately $0.00 dollars for my work in RPG Maker which means I have performed literally 100s of thousands of hours of unpaid labor to give away high quality free videogames to all y'all.
Not to sound too salty, but having given away, for free, a hundred or so hours of RPG and adventure gameplay in various completed games, demos, and cancelled projects, I don't feel particularly obligated to put in more time doing unpaid labor to finish my games nor do I feel anyone is particularly entitled to my unpaid labor on behalf of gam mak. Or, more accurately, the strongest obligation I feel is to myself; it would have been cool if Backstage II has been finished, but that's not the world we live in. I know it's a disappointment, as life so often is, as I so often am.
Now, I would be happy to take on the challenge of finishing this if I was getting paid a living wage to do so, but I don't see that happening any time soon.
