HODDMIMIR'S PROFILE

I love choices. However, I despise and loath dummy choices. If selecting option A and option B results in nothing but a slight change in dialogue, then I would rather not even have the options in the first place.

I was always of the opinion that if it worked in one scenario it should work in all of them or have a compelling reason why it doesn't. I mean why does Paralyze work on the Mini Gnome Assassin enemy but not on the Mega Gnome Dark Lord? Now obviously if you make all your normal enemies people and all your bosses robots, than we have a reason why things work different on bosses, but in general, if it is good enough for your mobs it should be good enough for your bosses. IMO.

Now as far as interesting approaches to status effects, I always liked the idea of taking as much of the randomness out of it as possible. The fact is the more chance based a thing is the less likely I am to rely on it in a game. Therefore, if my status effect moves have a random chance I already slightly favor my normal attacks. If it has a very low chance, well then why bother with it? It's more likely than not a waste of a turn.

I believe if you add it to your game than it needs to be something that is going to be used. I don't like to add useless features or objects and I don't like to play games with useless stuff either.

I'm on it. Give me some time to play it and write it all up for you. :)

How exactly does someone sift? I guess I'm not sure what that means really?

author=LDanarkos
I'd make a variable for each monster and start each variable at 5. Whenever you kill a monster party, the corresponding variable drops by 1. The plants on your map are events, and each one has a switch so that if you choose to chop it down, it turns the switch on. I would make an auto-start event that calls each plant event (it calls plant 1, plant 1 calls plant 2, etc.) and then deletes itself (is this command called Clear Timer in RM2K3?), and for each plant whose switch is off (i.e. it isn't chopped down), it will increase the corresponding monster's variable by 1 (perhaps up to a maximum of 10). Then, whichever plant event is last in this succession will call the monster generator. The monster generator will generate monster events according to how big their variable is.

Some balance may be required, because since the monsters' variables may go up much faster than they go down. One way of balancing it could be, instead of plants definitely increasing the variable by 1, you use a random number generator to give it a possibility of going up by 1 (i.e. random number X is 1-10. If X is 1, 2, or 3, then increase the monster variable by 1. So there's a 30% chance of it increasing).

Wouldn't take too long.

Oh! Thank you. That does sound like it would do the trick. :)