How to Use Arceus X Neo: Your First Session, Screen by Screen

You have installed it, keyed it, and the floating button is sitting in your game. Now what? This walkthrough follows the order our reviewer uses when introducing the tool, the same session described on Arceus X Neo, so your first hour builds real understanding instead of random tapping.

Start on the hub

Open the menu and stay on the Arceus Hub home screen. The three sliders, gravity, jump power and walk speed, apply live. Move walk speed a little, run around, reset it. Push gravity down and feel a jump change character. The hub teaches cause and effect faster than any tutorial, and nothing here can break your game session.

Then the script hub

Run one ready-made script from the script hub in a quiet game. Watch what it adds: a button, a panel, an effect. Then find the same script's idea inside the games hub for the experience you play most, and notice how collections are organised by game.

Finish in the executor

Open the Executor, write or paste a tiny script, execute it, and read the console. That loop (edit, run, read) is the whole craft of scripting, and the menu's editor-plus-console layout makes it comfortable on a phone. From here, the Lua basics guide takes you further. One structured first session turns Arceus X Neo from a mystery into a tool you own.

Building a repeatable session habit

The difference between users who love this tool and users who abandon it is rarely talent. It is sequence. Start every session the same way: check the status line, confirm the menu responds, then load only what this game needs. Players who open everything at once cannot tell which script caused a problem, while players with a fixed order spot the change immediately. That discipline is the whole lesson of the script hub guide, where one script at a time is the rule.

Keep a small notebook habit as well, even if it is just three lines in your notes app: the game, the script, and what it did. After a month you own a personal catalogue worth more than any list on the internet, because it describes your games, your phone and your taste. When a game updates and something breaks, your notes tell you exactly which behaviour changed, and the console output tells you why.

End sessions deliberately too. Close script interfaces you opened, reset sliders you moved, and glance at the console for warnings you might have missed mid-game. Then, when curiosity grows beyond ready-made scripts, the executor tour is waiting: editor, saved list and console, the workshop where a casual user quietly becomes a scripter. Good sessions are built, not stumbled into, and the build takes about a week of honest repetition.

Run this session twice and the menu stops feeling new. Arceus X Neo is built for that moment, when Arceus X Neo disappears into the background and only the game, plus your new options inside it, remain.