HAVING TROUBLE WITH A BOSS BATTLE/ENEMY SHOWN ON SCREEN
Posts
Pages:
1
Hello, I am new to the Rpg Maker world, and have just purchased Rpg Maker MV as my son and I would like to make a fun game together. I don't have any programming knowledge so have been trying to educate myself with switches and what i wish to do is make a Boss appear on screen, say as an enemy sprite and then a battle commences and afterwards he disappears. The problem is the boss keeps coming back on screen, no matter what I try, i will paste what i have done and see if anyone can see what i did wrong.
Thank you.
On the first event page I set it to this
◆Battle Processing:Orc
◆Control Switches:#0002 OrcSmellyDefeat = ON
◆Control Self Switch:A = ON
On the second event page i did this
Removed the sprite of the orc.
and i clicked self switch A on left hand side.
◆Control Switches:#0002 OrcSmellyDefeat = OFF
◆Control Self Switch:A = OFF
Thank you.
On the first event page I set it to this
◆Battle Processing:Orc
◆Control Switches:#0002 OrcSmellyDefeat = ON
◆Control Self Switch:A = ON
On the second event page i did this
Removed the sprite of the orc.
and i clicked self switch A on left hand side.
◆Control Switches:#0002 OrcSmellyDefeat = OFF
◆Control Self Switch:A = OFF
Isn't there a remove enemy command or force battle to end command. That might work. I don't have a lot of experience using control switches in battle. I usually have commands span each turn and check certain things.
I think your problem is that you're turning the switches back off in the second page. When the switches are turned off (most critically the self-switch A, from the description it doesn't sound like OrcSmellyDefeat currently does anything) the second event page no longer meets its conditions for being active, so the system goes back to the first page where the orc is active.
From what it sounds, yes, disabling Self-Switch A on Page 2 would have the effect of having Page 1 reactivate, as Page 2 requires that Self-Switch A is active. However, Page 2's events would not necessarily run after Page 1 concludes unless the trigger for Page 2 was "Aurorun" or "Parallel process". If it was "Action Button", "Hero Touch", or "Event Touch", Page 1 would not re-activate right away.
Saying that, the advice to remove Page 2's event-commands into a blank page is still good, from what I can tell.
Saying that, the advice to remove Page 2's event-commands into a blank page is still good, from what I can tell.
Pages:
1















