Virtual Buttons and DPad

Aloe Guvner · 2018-04-18T03:48:56+0900

Virtual Buttons and DPad by Aloe Guvner Download Link Note: This plugin is not under active maintenance. Background: This plugin focuses on improving the user interface for mobile games created in RPG Maker MV, by allowing the developer to have virtual buttons on the screen that interact with touch input. The emphasis is on maximum flexibility for the developer, you can add as many or as few buttons as you want to the screen, and you can add these buttons on whichever screens you would like (i.e. map, menu, credits, title, etc.). Functionality: This plugin can create 3 different types of buttons: 1.) Directional Pad A single picture which is used for up, left, right, and down movement (also support diagonal movement when combined with a Diagonal Movement plugin). You control what scenes the DPad appears in. This button is optional. 2.) Key buttons These buttons can be used to represent any key. Common keys to use would be "ok" , "escape", "pagedown", "pageup". These can be any key, and there can be as many or as few as the developer would like, and you control what scenes they appear in. Buttons can run Common Events. You can also write custom code that will be run when the button is pressed! You may specify the type of input this button responds to: Triggered: Execute once when pressed (default) Pressed: Execute every frame while pressed Repeated: After 24 frames, execute every 6 frames while pressed Long Pressed: After 24 frames, execute every frame while pressed Released: Execute once when button is released 3.) Control button The control button, if pressed, will collapse and hide all other buttons on the screen. If pressed again, it will expand and show all other buttons on the screen. This allows the player to decide between using the virtual buttons or the standard touch input. The scenes that this button appears in can be defined. This button is optional. Use Cases and Screenshots: {clearly placeholder art below } Spoiler: Use Case example #1 This example uses the DPad and two Key Buttons ("ok" and "escape") to put simple keyboard controls as virtual buttons on the map screen (Scene_Map). Spoiler: Use Case example #2 This example uses buttons with the functionality of "pageup" and "pagedown" in the status screen. These buttons can be put in whichever screen you like. Page Up and Page Down move between actors in the menu, so this would make sense to go in the Status, Equip, and Skill screens (Scene_Status, Scene_Equip, Scene_Skill). Spoiler: Use Case example #3 A virtual button can call custom Javascript code. If you are familiar with the engine, this can be extremely flexible and powerful. In this simple use case, the item screen is opened by pressing the button. Setup: The setup requires a new folder to be created within the img folder of the project. This folder must be named "VirtualButtons". Put all virtual button images in this folder, and then they may be accessed in the plugin parameters. Plugin Commands: * All plugin commands begin with VirtualButtons (MobileUI is also valid, for backwards-compatibility). * All plugin commands are not case sensitive (i.e. "DPad" is the same as "dpad") hide Description: hides the specified button Allowed arguments: DPad Any key button defined by you Control All Examples: VirtualButtons hide DPad virtualbuttons hide Ok MobileUI hide PageDown show Description: shows the specified button Allowed arguments: DPad Any key button defined by you Control All Examples: VirtualButtons show DPad virtualbuttons show Ok MobileUI show PageDown opacity Description: change the opacity of a button Allowed arguments: DPad Any key button defined by you Control All Examples: VirtualButtons opacity dpad 100 VirtualButtons opacity all 50 Terms of Use: Free for use in commercial or non-commercial projects. Credits required to: Aloe Guvner Version History: v2.0.1 (May 13 2019) Fix bug where DPad input wasn't cleared in menus v2.0.0 (May 4 2019) Clears input state on transfer to mitigate stuck DPad input bug Improves clearing of input state each frame to mitigate bug Buttons hidden via plugin command will stay hidden until the show plugin command Key buttons can trigger common events Option to use a "hot" image that shows when the button is pressed Delay parameter to fade-in Plugin command option to show all buttons Plugin command option to hide all buttons Plugin command to change button opacity Add plugin parameter to toggle whether the buttons are hidden during dialogue Fix bug where the DPad would not clear the direction after a parallel event checking for a input direction triggered a Show Choices event command v1.4.0 (December 13 2018) Added ability to configure which buttons are affected by the "control" button Can be used to create dynamic menus v1.3.1 (October 30 2018) Added a parameter to control whether diagonal movement is detected as a possible fix for a hard to reproduce movement bug. v1.3.0 (September 27 2018) Added a parameter to choose to disable the normal touch inpu…

● ARCHIVED · READ-ONLY

Started by Aloe Guvner Apr 17, 2018, 06:48 PM 229 posts Page 12 of 12 View original ↗

ray_stride07

#221 Jul 28, 2022, 07:00 AM Source

Eliaquim said:
Just attach the dash button keyboard to a button image on the plugin parameters.

Like this ?
Eliaquim

#222 Jul 28, 2022, 08:14 PM Source

ray_stride07 said:
View attachment 235955

Like this ?
It seems so. Did you test it?
mauigamestudio

#223 Oct 6, 2022, 10:16 PM Source

I have an issue with this plugin where sometimes it speeds through dialogue, even when I'm not touching the screen. Anyone else deal with something similar?
blinker

#224 Apr 9, 2023, 01:23 AM Source

Hello everything is fine?
This plugin is amazing because it was everything I was looking for, however I have some problems with it, so excuse my ignorance, because I wanted to know how to add the buttons in the Shop window, and I also wanted to know if anyone can add a function to change the position of the buttons individually only during messages and then returning to the previous position?
Thank you all for your attention, I'm sorry for the google translate English!
Antimtr

#225 Jun 28, 2023, 01:57 PM Source

I admittedly didn't read through all 12 pages of the thread but is there a way to make these controls hidden on desktop and visible on mobile? Like a screen size call parameter or the like? Sorry if it's already answered somewhere in here!
aliensanfo

#226 Jun 30, 2023, 03:11 PM Source

Eliaquim said:
Just attach the dash button keyboard to a button image on the plugin parameters.
Hi Eliaquim!
It doesn't work on Android, even with multitouch plugin active.
I used "shift" as InputCode.
Can u give a look and try? Thank you!
PauloWanderson

#227 Mar 8, 2024, 12:52 AM Source

Aloe Guvner said:
Portanto, o motivo pelo qual ele não funcionará em versões MV anteriores a 1.6.0 é que escrevi o plug-in usando recursos e sintaxe do padrão 2015 de Javascript . Versões do MV anteriores a 1.6.0 não suportam o padrão 2015, elas suportam apenas um padrão anterior (de 2009). Sempre tento usar novos recursos e, às vezes, isso significa que são necessárias atualizações para usá-los. Estou satisfeito com a versão 1.6.1 do MV, eles corrigiram todos os bugs da versão 1.6.0 e mantiveram todas as melhorias.

Agora, ouvi dizer que existe uma maneira de transpilar o Javascript para funcionar em mecanismos mais antigos para compatibilidade com versões anteriores, então, se eu encontrar algum tempo, posso tentar descobrir como fazer isso.
how to place buttons X and Z and B?
getthat

#228 Sep 14, 2024, 11:01 PM Source

Thanks to Aloe Guvner for the plugin. I used it to add touch controls to my games. I also created an add-on that adds an option to enable or disable Virtual Buttons in the options menu and includes the ability to disable two-finger touch/RMB while Virtual Buttons are visible. Since people still use MV and this plugin, I decided to share my add-on. It is available on GitHub and Itch.
Leffuel

#229 Oct 16, 2024, 05:35 PM Source

Sorry, guys. A total noob here. But how do I fix this?