VirtualInput Skill

When to Use

User asks to click a button, test a UI flow, interact with game UI, simulate input
Keywords: click, tap, type, input, interact, test button, fill textbox, scroll, zoom, pan, drag, UI test, walkthrough, VirtualInput, simulate, press key, camera look

Always Play mode — VirtualInput requires a live game with PlayerGui populated. Start play mode before any interaction.
Click is the core primitive — almost everything starts with finding an element and clicking it.
Screenshot after every interaction — the interact-then-verify loop is how you confirm success.
CoreGUI is restricted — interactions targeting CoreGUI elements (top bar, chat, escape menu) throw a runtime exception. If the user asks to interact with CoreGUI, explain that it is not possible.
Button state tracking — you cannot press a button that is already pressed. Always pair down with up. No wait needed between them for a standard click.
Single execute_luau per interaction — find element + inject input in one call to avoid race conditions.