Note: I am in the middle of making my post and accidently hit enter, I'm not done typing outIf you do still want to keep the berry growth parallel process, here's how I'd recommend setting it up:
In total, you'll need 1 common event, and as many variables as you have berry bushes.
Firstly, the bush itself. Create an event, and call it bush1. The bush event will need 2 event pages.
The first page is the harvest-able bush. Set the event to give you the berries, and set the Bush1 variable equil to 30.
For the second page, set the event condition to variable Bush1 is greater than 0. This is the empty bush.
Lastly, for the common event itself. Make the common event a parallel process. Set a wait command for 600 frames (10 seconds). After that, have all the bush variables decrease by 1.
And there you have it! Each berry bush can now be harvested 300 seconds (with at most 10 seconds of inaccuracy) after they are harvested. The wait commands in the common event aren't necessarily needed, but it keeps the parallel process from running too often.
Hey, and no problem. I put together a little demo to double check what I had suggested a year back, and with a slight tweak, I think I have something that should work for you.I now understand more about Rpg Maker and this now makes sense. I'm testing this out right now but I have a question.
You didn't have to go through the trouble. (But thank you) There is only one part I'm having trouble with. With this current set up you shared a year ago, page two takes priority and thus page one never shows.The bush event will need 2 event pages.
The first page is the harvest-able bush. Set the event to give you the berries, and set the Bush1 variable equil to 30.
For the second page, set the event condition to variable Bush1 is greater than 0. This is the empty bush.
No problem, hope it helps!With this current set up you shared a year ago, page two takes priority and thus page one never shows.
I think it has to do with the second page's condition where 0 is greater than or equal to.
I'm confused. Your post from a year ago suggested to use greater than or equal to 0 as a page condition for page 2 of the event. If I am understanding right, the only option for variables as page conditions is the condition line where you choose a variable and a number that is greater than or equal to.No problem, hope it helps!
And huh, that's odd that page 2 is causing issues. Variables are able to hold negative values, so once Berry Tree 1's variable dips below 0, it should no longer trigger page 2.
You could try changing page 2's condition to greater or equal to 1 to see if that changes anything. Otherwise though, you could post screenshots of the berry tree's 2 pages and the common event, and I'll take a look to see if I notice anything out of the ordinary.
Yep, that's correct. Once you pick the berry using the first event page, the variable is set to 30, and that will trigger the second event page.If variable starts as 0, but when plucked it is set 30, wouldn't that make page 2 the priority? (I'm only trying to understand, please correct me if I am wrong)
It actually crossed my mind if the bush needed to start at another number than 0 but I didn't think any further than that. This makes more sense now. So I just need to reset the bushes to -1 and have then set up to reset at -1 after the event plays itself?Yep, that's correct. Once you pick the berry using the first event page, the variable is set to 30, and that will trigger the second event page.
The second page is just meant to be empty, so you aren't able to pick any more berries. Once the variable reaches below 0 again, the second page will turn off, allowing you to pick a new berry.
Edit: Just realized what you might be having problems with. Try setting the tree variables to -1 at the start of the game.
With the current setup, you should only have to set the variables to -1 once, at the start of the game.It actually crossed my mind if the bush needed to start at another number than 0 but I didn't think any further than that. This makes more sense now. So I just need to reset the bushes to -1 and have then set up to reset at -1 after the event plays itself?
So I could create a conditional branch in the common event that checks and resets it to -1. Right?
That's because the variable was "set" to "-1" correct? That negative 1 will remain constant. (Unless otherwise changed) Am I understanding correctly?With the current setup, you should only have to set the variables to -1 once, at the start of the game.
The only reason I mention setting them to -1 is because otherwise, the trees won't be ready at the start of the game until you wait 1 "wait cycle".
Yep, having the variable set to negative 1 at the start of the game allows the trees to be harvested as soon as the game starts.That's because the variable was "set" to "-1" correct? That negative 1 will remain constant. (Unless otherwise changed) Am I understanding correctly?
What about the variable counting pass negative 1? Will that cause any problems?
Haha, glad I could help!
Just let me know if you run into any other questions.