BULMABRIEFS144'S PROFILE

Oh. Well, this mostly has to do with the fact that characters have physical attacks with different weapons. And it's explained during battle that the character needs something to hit the target with.

It was a bug. Character 3 when they attacked an elemental immune, I found it was set to Character 1 StunAll. Fixed now, and it seems to run smoothly.

News bubble, huh? Bugmenot created it awhile back. It allows you to add stuff to attacks like the ability to be unreflectable.

??? You responded to something regarding RPS+ earlier.

author=Milennin

author=bugmenot
Fixed a bug with self-destructing enemies when using the RPS+ patch:
download RPS+

This is an interesting patch. The miss on skills that wouldn't increase any stats always bothered me, and I like the "immune" effect. I'll try this out some time.

Just make sure you've got dynrpg 0.30 or 0.40 whatever, the one Pepsi made. It should create a plugins folder. Download the RPS+ patch. Add to the attributes menu twelve new "elements" called %1 to %12. These basically go with the Immune effect, and add traits to attacks.

%1 (Row control, I think it ignores rows or something)
%2 (Piercing, it changes damage based on enemy defense. I think the more defense an enemy has the worse it is)
%3 (No Reflect skills)
%4 (Skills can be evaded. Put it on weapons to make them hit evading enemies)
%5 (Skip skill name)
%6 (Fast, speeds up ATB)
%7 (Slow, slows down ATB)
%8 (Delay, slows down enemy ATB)
%9-11 (turns switches on if skill used, hits, or misses in that order)
%12 (A is minimum damage, I set to 1, B if 0 is no maximum otherwise maximum damage up to B, negative damage and immunity applies)

Oh yea, I understand that, as I do alot of switches like this.

I think at the development phase of Tales, I was making monsters, and the first time I did it, I was like 50 or 70 into it, and like "I reaaaally hate doing this for each party member, so I tried to figure out how to make stuff so I could copy-paste as much as possible without changing stuff.

I basically have three "types" of physical immunity, which have battle animation messages pop up. And one type of magic immunity.

Magic Block same as yours. However, because my characters have sort of themed magic (life/death/etc) some monsters are selectively immune to death magic or life magic.
Physical Block the basic one. This is usually monsters where you attack and the attack does nothing (think ghosts). Generally, having astral weapons overcomes this (or just hit them with spells)
Miss is for flying or swimming monsters. You need to be floating to hit enemies like this.
Elemental Block basically requires you to have one of the elemental weapons to attack.

I wanted to have more stuff, but I can't think of anything. Still, it's cool that I was able to do this.

Than Fade. It is all internalized (except for a simple if MonsterImmune is ON switch which shows the animation). It was ALOT of work, but it paid off big. I basically got your idea, from looking at the code, and then was like "man that's good, but I want it less all over the place because I'll have to copy it a zillion times and don't want it to stall monster creation." So I just sorta tweaked stuff until I had a copy that just took like four lines.

author=Milennin
On the subject of scary battle codes, that's one of the reasons I've considered upgrading to the new engine. I have no idea how much code RPG Maker 2003 can handle before it's starting to cause slow downs. Seeing how I still have a lot of stuff to add, I wonder if it'll be able to keep up. But maybe I'm worrying about nothing...

It's actually just scary because if all code isn't just so, the battlers basically stop moving in terms of turns. I remember trying to rebalance that dragon (since I didn't like it moving as fast in terms of healing and casting that meteor), and I changed one page to try to switch phys shield and myst shield, and the monster no longer attacked or something.

You would be surprised. I have 19 pages, and the Turn 1x ones (I have two, which unfortunately messes up turns somewhat) if written out would be like 10 pages long, since I have about 11 characters, and each of them has commands that activate stuff. The key to fast processing is common events. When you common event, processing is done on another screen, and it seems to be done faster. This means, if you have alot of events that happen for every battle, common event pretty much makes it run smoothly. Ideally, we would have the new 2k3 have dynrpg and be able to copy paste entire stuff to common events, AND run the turn based plugins. I have over 500 common events, and the are rather long, and yet there is not significant lag except in screens that had 300+ events (again, events on the screen vs off). Despite that some of these are parallel processes that run constantly, common events run VERY fast. As in, I used the date/time plugin as part of my game, to give the month, day, weekday, year, hour and minute. I check it in a common event, and follow up with another common event, that goes through the process of setting the weekday as a name, the month name, checks whether anyone's birthday is around, and so on. It's extremely long and complicated, since this also includes my famed menstrual cycle status. I can walk around with no lag whatsoever. A big map with too many events, nah, I'm lagging. The big lag contributors are pictures that update or rotate while characters are talking, weather (mainly because you ask it to wait), and stuff like switches and variables that activate in battle outside common events.

Yea, jot the stuff you got down on a piece of paper. Oracle of Tao was actually a high school idea for the C++ programming class (until we all realized none of us could make games this way) that I worked on with a friend. I found the notes years later, and was able to start from there. Dialogue doesn't need to be spot on, so much as the plot/characters/motivations/etc of the game.

I would say keep your game, and finish the story. Recreating the game can put you in perma-hiatus.

That said, MV looks like a good engine. I'd say save it for a sequel, if you have one.