the difference is that the script checks if a button is pressed and released, and the button press only checks if the button is currently pressed. Which means the non-script solution can detect a button press multiple times, the script commands waits until the button is released.
Does that mean that whenever this ends up working, if someone holds down the left or right button it'll just flip through the pages extremely fast? I'd rather it just be one page at a time so they wouldn't accidentally miss something
If you don't even get to the show picture, then the problem is not in the loop but in the wait. Something freezes the game in the seven frames while this event waits, and most likely that is something else entirely elsewhere.
Remove the wait completely and test again.
If that results in the event working, the freeze comes from somewhere else in another event.
If the event still freezes and doesn't show the picture after removing the wait, the problem is in how you call the common event and we'll need to see the trigger and the skill.
Removed the wait, no difference. When I remove the loop command, the picture shows up again. I decided maybe I should do this with labels, and but this isn't working either (granted I have never worked with labels before). It DOES show the very first picture, but nothing works after that. I can still move my character around but the page turning functions don't do anything.
This is the page for the diary item that calls the event:
The <item type: 2> is just part of a script to put it in the key items category in my menu.
I was thinking maybe I could just do this with choices, "Next Page, Previous Page, Close Book" but with how high up the choices are it would cover up the text. If there's perhaps a script that moves down the choices box when there is no text below it I could do that...