Reaverbot Design and Concept(s) Discussion

General Specific wrote:The Reaverbots are looking good, Joe.

I'm certain that you've taken inspiration from the Habarool from MoTB and made it more like the cactus critters from Mario games. So, of course, one attack the newly-elongated-and-stilted Habarool can do is simply flatten itself against the ground, at the same time producing a minor shockwave around the head area and scything at the player with that L2-stlye horn. When working in a pair or a group of three, they could surround you as a triforce and try this attack out.

That spinning top bot looks great too, and could work in a small group as I mentioned just previously. And the rest—well, nothing too special about them. I think you're improving a lot, man!

Virus111 wrote:I'm not at all an artistic person, more of a concept dude. XD But I agree with Edich when he said that we should focus on Bosses and Mini-bosses first. I also think that we should have the ruin concepts there first, so we know what kind of reaverbots to have in each one. I'm not saying that we shouldn't be drawing reaverbots yet, because I LOVE the designs we have so far. I also think that ruin design will give the designers a more focus direction to be heading. On the other side, the reaverbots people design could influence entire ruins. XD Anyway! I think what we have so far is pretty good! So, I suppose I could pitch a reaverbot here to not make this a useless post. XD

I'd rather get ruin concepts down first, then making context-specific Reaverbot designs based on said concepts. Generally, though, we need mission context and ruin context to get started on Reaverbots and non-Reaverbot enemies—that should be the first goal outside of actually nailing the physics and playability for the player character.

General Specific wrote:

Virus111 wrote:I'm not at all an artistic person, more of a concept dude. XD But I agree with Edich when he said that we should focus on Bosses and Mini-bosses first. I also think that we should have the ruin concepts there first, so we know what kind of reaverbots to have in each one. I'm not saying that we shouldn't be drawing reaverbots yet, because I LOVE the designs we have so far. I also think that ruin design will give the designers a more focus direction to be heading. On the other side, the reaverbots people design could influence entire ruins. XD Anyway! I think what we have so far is pretty good! So, I suppose I could pitch a reaverbot here to not make this a useless post. XD

I'd rather get ruin concepts down first, then making context-specific Reaverbot designs based on said concepts. Generally, though, we need mission context and ruin context to get started on Reaverbots and non-Reaverbot enemies—that should be the first goal outside of actually nailing the physics and playability for the player character.

Virus111 wrote:What if we had a reaverbot that somewhat resembled the Slenderman? I don't really know much about the Slenderman, aside from what it supposedly looks like. However, I think it would be interesting if we had a reaverbot that would VERY RARELY appear in the ruins, grab Mega Man, and return him to the start of the dungeon? It could be very frustrating, so it would have to be a really rare reaverbot, and it would have to be avoidable. No one would want to have to be sent back to the beginning of the dungeon because they turned out unlucky. If it was completely avoidable though, there would be no motivation to fight it. Maybe it could be an optional mini-boss that would drop a weapon part if defeated? Maybe the reaverbot moving Mega Man back to the start would be an attack that it would use when it gets weak enough, and it would have different attacks that it would use on Mega Man during the other part of the fight?

Iunno. Just throwing out ideas. XD

General Specific wrote:As long as the arrival is telegraphed to some extent, that the player might know what's coming, this trap Reaverbot is a good idea, and can be used in all ruins that have puzzles and complex exploration, where they'd be guarding the big shiny from the player. Traps, for me, are a sticky issue because you have to design them in a way that really gets to the player, without just raping the player immediately and leaving the player frustrated—matters of luck, I do not care for in games!

General Specific wrote:Those Reaverbots were generally multi-context, such as cannon-fodder like the Zakobons—we'll be doing some of those for this game, as well.

jadzxa wrote:Wow Ringu sounds like a seriously annoying Reaverbot but that's all the more awesome. The targeting thing really is unique. The design is pretty good as well. I imagine it spinning itself and once you lock it stops looking at you or something. I also really like the Anteropii it seems as if it'd make a good mini boss foe at some time. Much like the wolf Reaverbot's from legends and legends 2.

Overall nice design work there.

HBV-05-E Raiden wrote:The Antelope, while nice and really captures the basic design elements of later Reaverbots, doesn't seem like something I'd see typically. I think we should try to do less natural and animal-based designs. We could still do some animals, but we'd really have to spice them up; like the Mammoos were similar, yet very different from mammoths/elephants.

Even then, we should still limit ourselves, since I think Elder System designs were more like Legends 1's designs, although we can still do the other types.

General Specific wrote:I like the concept, as it forces players to learn how to use a quick-turn maneuver—it's effectively a Legends equivalent to Boo. Contrary to what I've said, this is good stuff you've been pumping out. You're still the most active designer on the team, after all.