Community controls
Controller settings → Community controls browses source catalogs and imports or exports .ddcontrols.zip packs and controller-skin ZIPs. A DroidDeck starter gamepad is bundled for offline use. The ARMSX2 community catalog is a remote source: none of its artwork is shipped in this repository or the APK. Selecting it fetches its manifest and previews; selecting a skin downloads it directly from that source for local installation.
Sources and sharing
The Source selector includes DroidDeck and bagasromadon/ARMSX2-CustomControllerSkins. Connect another source accepts a public GitHub repository URL, a GitHub manifest file link, or a direct HTTPS catalog URL. Repository URLs try main/catalog.json, then main/manifest.json; use a file URL for another branch or a catalog in a subdirectory. Connected sources persist locally and can be removed. Native manifests use controls; ARMSX2 manifests use skins. Relative paths stay within the manifest directory, with spaces encoded when downloading. No account credentials are stored in DroidDeck.
Export this layout and actions creates a portable DroidDeck pack. Export skin artwork creates an ARMSX2-compatible PNG-only ZIP when the selected layout has suitable artwork. Share either ZIP directly, or use Open source submissions to visit the selected source's issue page and attach it there. GitHub requires an account. Source owners manage submissions and publication; the app does not automatically publish uploads. For other HTTPS hosts, the button opens the catalog URL; use that host's own upload process. A native controls pack includes layouts and bindings, while an artwork ZIP includes only controller images.
The DroidDeck issue template accepts exported packs and screenshots for review. Maintainers add approved packs to packs/ and entries to catalog.json, with name, author, optional game, license, relative file path, SHA-256, optional preview path, and screen (MAIN, SECONDARY, or BOTH). Keep the bundled starter copies under app/src/main/assets/community-controls in sync. Remote entries are namespaced by source. Native pack downloads require the manifest's SHA-256; ARMSX2 manifests may omit it, so their files are obtained over HTTPS and validated as bounded PNG archives. Do not infer artwork redistribution rights from the application's code license.
Applying controls
Native controls packs create an independent copy for the chosen profile and screen. ARMSX2/iOS skin archives match image names to the selected layout's native controller actions (cross → A, circle → B, square → X, triangle → Y, shoulders, triggers, system and directional buttons). Positions, actions, and stick-click bindings are preserved. Generic and separate left/right analog base/thumb images are supported. Unsupported images are ignored, missing artwork keeps the existing appearance, and a skin with no matching controls is rejected. Source images are sampled to at most 512 pixels before storage. Skin ZIPs can also be imported locally.
For game-specific controls, create a named input profile and apply the pack or skin to it. Select that profile in the game's settings under On-screen controls profile. Automatic selection follows the focused Steam game, or the launched game for direct launches. Returning to Steam restores general controls. Explicit quick-menu profile or screen choices take priority until Auto is restored. Physical controller bindings follow the general selection. Missing/deleted profiles fall back to general controls. Use Profile controls mode for the second display.
Native pack format
A ZIP contains controls.json and the exact images/<filename> PNGs referenced by the layout. The JSON has format: "droiddeck-controls", version: 1, and layout / bindings objects using the input library serialization. All supported actions, stick clicks, geometry, style, and artwork (including separate moving-stick images) are retained. Local IDs and image names are regenerated on import. Import validates the library, image dimensions, file count, byte limits, and entry paths before offering Apply; saving uses the library recovery path. Legacy .icp import/export remains in Saved layouts.
Upstream inspiration
The source catalog flow and controller-skin filename conventions were researched directly from ARMSX2 commit 9144e4ff1fed43756809d8e68b3efc2505a51078, particularly SkinRepo.kt, ControllerSkinStore.kt, and ui/settings/SkinsTab.kt. ARMSX2's COPYING.GPLv3 and pcsx2/Docs/License.txt license its program under GPLv3 or later, compatible with DroidDeck's GPLv3. This implementation uses DroidDeck's input model and renderer. No upstream source or artwork files are copied into the source tree. The bundled starter is original DroidDeck data under GPL-3.0.