At that time, I was playing Tales of the Tempest, one of the worst Tales games, and thought what it would have been like if Tales of Tempest R wasn't scrapped. This is essentially just a rough example if what a Tales of the Tempest R could have been. It is very unfinished, so don't expect it a completely working product. In its current state, you can travel around the world map(Although some areas don't have collisions), access the artes menu and configure your artes, and also make contact with the enemy, who will seek you out until it makes contact. From there, you will enter the battle system. The battle system is mostly functional, with the player being able to pull off combos in typical tales fashion. There's Attack > Base Arte > Master Arte > Arcane Arte, with the player having access to 2 of each, all of which can be reset by dash-cancelling or jump-cancelling. Each hit simply does one damage, and the enemies don't fight back. Killing all of the enemies likely results in going back to the overworld. Nothing lost, nothing gained.

This game requires a controller to play. The game naturally supports DS3, DS4, Xbox One, Xperia Play, and Nvidia Shield Controllers, whether that be via OTG or Bluetooth. Controllers connected via OTG cables tend to work best due to the input delay associated with bluetooth among many Android devices. In the case you would like to use another controller, do the following:

1. Bring up the configuration menu. This can be done at anytime while the application is running by either touching down on the screen for approximately 3 seconds or in the case you are using an Android TV device, holding the Pause/Play(Keycode 85: KEYCODE_MEDIA_PLAY_PAUSE) button on the remote control for roughly a second. In the case your remote controller doesn't have this button on it, you can use the Android TV Remote application to have access to it.

2.Once the menu has been activated, you will be able to see all of the controllers you have connected, and modify what they are being interpreted as. The bottom bar displays all of the controllers that have been recognized. A controller is recognized by pressing any key on the controller. The numbers are grey if no controller occupies that slot. If the controller slot is highlighted, that means that it is the active controller to be configured. All of the squares in the center of the screen control what the the game interprets the active controller as. This is indicated as a green square. You can tap onto any square to change the configuration of the controller, or use the DPAD on your remote control. If the controller you are using isn't on the list, you will have to configure it as a custom controller. If you would like to change the active controller, either tap the controller slot you would like to make active or hold the left or right on the DPAD on your remote controller to slide to the adjacent controller.

3. In order to configure a custom controller, either use the DPAD to navigate to the custom button or touch the button. Once you do this, a dialog box will pop up, commanding you to press the corresponding key on your controller. For each key, press the button on your controller that you would like to bind it to. If the key doesn't apply to your controller, tap on the skip button, or press the Pause/Play(Keycode 85: KEYCODE_MEDIA_PLAY_PAUSE) button on the remote control to skip to the next input. If you would like to start over, press the clear button or hold the Pause/Play(Keycode 85: KEYCODE_MEDIA_PLAY_PAUSE) button on the remote control.

4. Once you have assigned all of the inputs, your controller is ready to use and you will return to the main configuration menu. Press the cross button in the upper left to close the menu, or hold the Pause/Play(Keycode 85: KEYCODE_MEDIA_PLAY_PAUSE) button on the remote control. Also, you can press the cross button in the bottom left to disconnect all of the controllers.

5. The button inputs are stored in a file labeled config.cfg. This file is stored within the application's directory on your device's external storage. Should you have any issues binding the keys of your controller, you can manually insert the keycodes in that file, and modify the array of input codes at the end of the file to 10(The Input Code for Custom Controllers.) Here is a list of input codes:

0 = Keyboard, 1 = DS3 OTG, 2 = DS3 Sixaxis 3 = DS4 OTG, 4 = DS4 Sixaxis, 5 = Xperia Play, 6 = Xbox One Bluetooth, 7 = DS4 Bluetooth, 8 = Nvidia Shield Portable, 9 = Shield Controller (2015), 10 = Joycon(L), 11 = Joycon(R), 12 = Custom Controller