Yeah. I figured people could more easily customize it if they customized the prompt too. I use a variation for FiveM, Aion2 etc. One note - enabling SSL (https) was for accepting text to speech from the iPad, but it actually works better and faster having a button trigger Windows TTS and kind of unnecessary on an internal home network, so please read through and edit to your preferences.
Thank you! - I thought about it, but I don't really want to maintain anything, so I asked my agent for a prompt you could share with yours. Grab my screenshot and give it to your agent with this:
Build me a complete, working “WoWpad”: a customizable touch command deck for World of Warcraft. I’ll open it on an iPad beside my Windows gaming PC and tap buttons to send commands or key presses to WoW.
Create the actual application, launchers, setup instructions, and tests. Continue through implementation and verification.
PERSONALIZE IT
Ask me in one short message:
- Which WoW edition I play: Retail, Classic, or another client.
- My client language, class/spec, and preferred actions.
- Whether I want touch only or optional voice chat.
If I don’t have preferences, use an English, touch-only deck with editable starter actions. Detect technical details such as local network addresses yourself. Don’t assume another player’s bindings, installed game path, or character abilities match mine.
HOW IT WORKS
- A local Windows companion serves the interface over my private home network.
- My iPad connects in Safari and pairs using a six-digit code shown on the PC.
- Display the PC’s localhost address and the iPad’s LAN address clearly.
- Support Safari’s Add to Home Screen with an icon and full-screen layout.
- Use a fixed, documented port and explain port conflicts.
- Keep the core app local, without accounts, API keys, cloud hosting, or a required WoW addon.
DESIGN
Make it feel like a polished fantasy game interface: dark textured panels, gold frames, red active tabs, colorful original icons, and large readable labels.
Prioritize comfortable iPad use in landscape and portrait. Use large touch targets and action grids that fit the screen, with numbered pages when needed. Keep navigation, chat, connection status, and a pause button easy to reach. Support phones and desktop browsers too. Avoid clipped labels, overlapping controls, and accidental sends while editing.
DECK FEATURES
- Categories: Favorites, Social, Party, Travel, Professions, Utility, Keybinds, and Custom. Include Housing when supported by my edition.
- Search, category filters, favorites, and editable button labels.
- Starter actions such as emotes, ready checks, rolls, party messages, map, bags, and configurable mount or hearthstone actions.
- Each button sends either one slash command or one keyboard combination.
- Custom buttons with editable labels, commands/bindings, notes, and optional confirmation.
- Setup cards for actions that require assigning a binding first. Tapping an unconfigured card opens setup without sending input.
- A chat composer with edition-appropriate channels and named whispers.
- Confirmation for disruptive actions such as leaving a group.
- Browser persistence and validated JSON export/import.
- Separate saved settings and pairing data if multiple editions are implemented.
Research commands and bindings for my chosen edition using current, credible sources. Include a short compatibility guide with sources. Mark uncertain or character-dependent actions clearly. Treat suggested bindings as editable examples.
WINDOWS INPUT
Use a Windows input bridge, such as PowerShell/C# with SendInput.
- Send input only while the intended WoW client is in the foreground.
- Match the appropriate executable and distinguish editions where necessary.
- Never automatically focus or launch the game.
- Recheck foreground focus before each input-down event; abort if focus changes.
- Always attempt to release modifiers after errors.
- Reject dangerous operating-system shortcuts and refuse input while physical modifiers are held.
- Serialize input, reject duplicate taps, and discard busy requests instead of queueing delayed actions. Never automatically retry a failed send.
- For slash commands, press / to open command chat, type the remainder, then press Enter. Make chat-opening delay configurable.
- Explain that game chat must initially be closed and the slash-to-chat binding must be enabled.
- For multiline macros, instruct me to create the macro inside WoW, bind it to an action-bar key, and assign that key to a button.
Do not implement rotations, unattended gameplay, timed input sequences, automatic repeats, anti-AFK behavior, memory reading, or restriction bypasses.
PAIRING AND STATUS
Require authentication for all input and control requests. Persist pairing across restarts using device tokens stored in the browser and token hashes stored on the PC. Support permanent unpairing, rate-limit pairing attempts, and validate requests, origins, hosts, and imported decks.
Provide Preview mode that exercises validation without sending keyboard input. Require localhost access to enable Live mode; allow paired devices to pause it. Show disconnected, unpaired, preview, busy, and waiting-for-game-focus states.
“Sent” must mean Windows accepted the input, not that the game successfully performed the action. Explain partial chat input after an interrupted send.
OPTIONAL VOICE
Only implement voice if I request it.
- Prefer explicit-start PC microphone recognition using local Windows speech recognition.
- Recognize phrases beginning with “say” or “reply” and send only final, accepted messages.
- Provide clear listening status and stop controls.
- Share the touch input validation, focus checks, and busy guard.
- Never start listening automatically, save recordings/transcripts, or retry failed sends.
- If adding iPad browser speech, explain secure-context requirements, browser limitations, and whether its speech service sends audio off-device. Keep touch usable without voice setup.
DELIVERY AND VERIFICATION
Prefer Node.js with vanilla HTML/CSS/JavaScript, minimal dependencies, and no build step. Provide a double-click Windows launcher and clear instructions for pairing, customization, stopping, and troubleshooting.
Document any optional firewall rule narrowly for the private local subnet. Don’t automatically change firewall settings or certificate trust.
Test authentication, pairing persistence/revocation, validation, unsafe imports, duplicate taps, edition isolation, and preview dispatch using mock input. Tests must never send real game input.
Inspect the rendered interface at tablet and phone sizes. Finish with the working files, test results, startup instructions, and a short manual checklist for checking Safari pairing and one harmless action in WoW. Clearly distinguish verified behavior from anything still requiring a live device/game check.
Awesome! It's what I saw in my mind's eye when I read Snowcrash and Neuromancer.
What do you think of an open framework or protocol so that if someone visits your home they'd see what you built in XR and you theirs? Maybe extend it with creators' feeds you could subscribe to for public spaces and cities? Nab it for the public before shared XR ends up an Apple service...
@aesthetica_s@AyakaMods My Skyrim VR install has hundreds (one example) so the premium was worth it. I looked it up and I guess it was like $50 spent back in 2007. Not sure that counts as support at this point though lol.
@aesthetica_s@AyakaMods I bought a lifetime sub for like $5 back when they were just getting started. Still get premium speeds and automation when downloading large collections, etc.
But I know what you mean.
@Qwik Artists using a platform granted for entertainment to speak their political views are insufferable. Talent and wealth != intellectual capacity, even when they put on their glasses. Put it into the music, painting, or role i.e. "Eye of the Beholder".
@alexandr_wang We can Muse if we want to
We can leave your friends behind
'Cause your friends don't Muse
And if they don't Muse
Well, they're no friends of mine
How about a gritty, historical geopolitical thriller that plays out like a tribal Vinland Saga: THE GREAT CLEARING.
Set entirely in North America in the 1400s long before European contact. The narrative follows the brutal, calculated campaigns of territorial expansion and forced consolidation that tore through the Northeast. At the center is Tadodaho (Atotarho), recontextualized not as a mythic monster, but as a ruthless, highly pragmatic military warlord who uses the aggressive warrior host of the Onondaga Nation to launch an unyielding campaign of subjugation against the neighboring Cayuga and Seneca Nations.
The focus is entirely on the raw reality of pre-contact land-grabbing. No open-field chivalry—this is ugly, total warfare. It’s built around massive winter siege operations targeting fortified Mohawk, Oneida, and Cayuga palisade villages, the systematic burning of crops to starve out whole regions, and the weaponization of the "Mourning War" cycle. Captives aren't just prisoners; they are systematically stripped of their former tribal identities and forcefully assimilated into the conquerors' longhouses to swell their military ranks. It’s a raw, historically accurate look at how blood, siege craft, and raw territorial ambition redrew the map of the ancient Northeast.
(I used AI to focus my idea)