DOOMED2DIE'S PROFILE

How important are UP's? Because since this isn't a large scale project where we have thousands of players, it'd be really easy to go into the game without UP and keep losing, no?

The problem with ATB is how it's pulled off.

I don't intend to do anything with an ATB until I finish JAVA and then learn Ruby and then master the RGSS2. (or 3). THEN I will most likely MAKE one or completely edit one to my liking. Why? Because you have to be familiar with the coding of to make good systems for an ATB battle system. That's a major thing because with the innovation streak and after having played 100 RPGS that do the same basic pattern, I crave new systems so I'd have to do that.

SO, there's 1 fundamental issue: Coders =/= developers and very few projects have very devoted coders so everything that developers want to do won't get coded in the end.

The other fundamental issue is simply this: They're too slow! Why do I have to wait 3-8 seconds for my next character's turn? Isn't ATB ACTION time battle? The whole point was to break the monotony of a simple turn based combat system! Yet, it falls into the same traps of repeated patterns and simplicity. It also falls back to the pattern of slowness which, in our fast paced world, people are conditioned to hate.

So, it's just terribly designed. A well done ATB forces a player to react to individual situations and micromanage each individual character before quickly moving on to the next. Not choosing 1 action and waiting for the next. That's exactly what makes me reluctant to play RM2K3 games.




The potential merits are, paradoxically, the polar opposites of their issues.

The potentials for codes in an ATB spawn a much larger variety. I could have cast times for my spells that transcend simple turn systems (wait 3 seconds, BOOM). I can delay before powerful attacks or slow down my opponent. I can steal my opponent's time and I can have cooldowns or limits. I can have a time threshold to complete requirements. Or take down a boss's armor for a limited amount of time to damage him within the threshold. The availability of a new, complex, and versatile resource (time) is what makes ATB's so potentially awesome.

The other great potential merit is what I noted earlier. In ATB's the games should be very fast paced (I can imagine a few exceptions but let's generalize for simplicity's sake instead of looking at every possible exception). It can force a player to micromanage one of his heroes, move on, micromanage the next, and move on. This allows a player to be on his or her toes for an entire fight and have a legitimately fast paced battle. Also, they have to account for the speed differences between their heroes now. Maybe that cleric decked out in plate mail isn't such a good idea now...



ATB's (in a fast paced environment) have to utilize the flexible element of time in their battles. Both the player's perception of time (their time management in managing their individual heroes) to the actual resource of measured time (cast times for example). The potential is massive but the potential for failure is... Calamitous. Simply put.

Story I'm not of the belief that a mediocre story is in any way, a detriment. In fact, I think you did what may have been intended: Move the game along in a story while focusing more on gameplay aspects. I completely agree.

Aesthetics It's not a massive problem, as noted. I just noted it to be in fair in criticism and to address all major issues.

Gameplay In terms of side-quests, there were VERY few early in the game but that's fine. 100+ sidequests is a dream. :P

I entirely agree that RM2K3's limitations are largely at fault for many of the problems I note in your game. I'm aware of side-scripts which may have extended the functions far enough for you to address some of these issues (or lots and lots of eventing as well) but they weren't out IIRC back when this came out. And you did fairly well considering your limitations.

I did note that the engine was partly at fault (especially noted in the complaints about speed.) In terms of the Magic attribute, the way it was set up, it seemed as though your Mind_f (or whatever they called it way back when lol) was at 1 or 2. That means, essentially, only 10-20% of your Mind actually affects your magical damage output. That is bad :P

I understand the balancing issues behind status effects and weaknesses but for every detriment, there should be return as well. Nonetheless, I'm quite aware of how difficult it is to manage a project of this size. You did well considering your limitations


I'm busy but I'll get around to finishing this... Eventually lol.

I disagree with the wrong build thing; equipment builds can be sold as noted and enemies drop off basic equipment for you anyway.

For skill builds, the synergies are extremely self evident (I thought) and my builds were simple enough.

Perhaps, but isn't it a define flaw in of itself where we have to wait to think for a game? I'm more used to games that start good and end bad; at least those I have a reason to keep playing at the start.

Nonetheless, RM2k3 doesn't give a large variety of options for exploring battles; I don't expect anyone to go through hundreds of lines of complex eventing to make a unique and awesome boss at all.