# Mobile Inputs

## How Mobile Inputs works in JU TPS

The Mobile Inputs are made up of Virtual Button, Touchfield, and Virtual Joystick. These scripts modify the Input Action Paths, which enables control through UI elements.

<figure><img src="/files/HgTPDvD1QX76RB3k0s9A" alt=""><figcaption></figcaption></figure>

You can use the scripts in the image below to rewrite the Input Action Path values ​​as you wish.

<div align="left" data-full-width="false"><figure><img src="/files/PxmA4nwQH7o16WLCvilH" alt=""><figcaption></figcaption></figure></div>

## The Mobile Rig

The Mobile Rig script controls default mobile screens and buttons.

Auto Setup Button finds all virtual buttons, joysticks and touchfields by names. You don't need to press it unless you're creating an own Mobile UI and want Mobile Rig to find the buttons.

<figure><img src="/files/52SEXJcYPNpZlOoypU4C" alt=""><figcaption></figcaption></figure>

The "Panels" settings are the default screens, they are two control screens(Normal, Driving) and a parent of the previous screens panels(Mobile Screen Panel), this screen enables if the application is running in mobile devices.&#x20;


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://julhiecio.gitbook.io/ju-tps-documentation/game-development/how-to-create-a-mobile-game-with-ju-tps/mobile-inputs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.