MDPro4 — FAQ & Support

MDPro4 is a community Yu-Gi-Oh! simulator built in Unity, combining YGOPro-style dueling with Master Duel assets and presentation.

Its modes, supported cards and features follow MDPro4's own releases. It is a separate community project, so an update or feature in the official Master Duel game does not automatically appear here.

New here? Start with the download instructions for your platform, then check the card and online-play guides below.

Check #announcements for the latest playable release for your platform. Compare its version with the one shown in your game and follow the matching installation or update instructions in #mdpro4-download.

A development version number is not a release announcement. Entries described as synthetic updater fixtures are for testing the updater, not for playing the game.

Platform releases can become available at different times, so use the package specifically announced for your device.

You can choose UI Language and Card Language separately in Settings → General.

The language set includes English, Spanish, French, German, Italian, Japanese, Korean, Portuguese, Thai, Simplified Chinese and Traditional Chinese.

Card translations and prerelease translations can have different coverage. If a card is missing or its text looks wrong, include the card name/ID, selected language, game version and a screenshot in your report.

MDPro4 has its own development and release process. A feature needs working game logic, interface controls, assets and platform support before it can be offered reliably.

Sharing Master Duel's visual style does not mean every mode, event, animation or online service is available. Features may also depend on the selected duel engine.

For a request, describe what you want to do and include an example. For a broken existing feature, include your version, platform, mode and steps to reproduce it.

There is no announced iOS release or release date in this FAQ. Follow the project's release announcements for any change.

An Android APK cannot be installed as an iPhone app. Please use only a package explicitly released for your device.

You need internet access to download the game, get updates and use online services. The current base installers contain their resources for offline installation once the complete set has been downloaded.

Local play uses the content included in your installed release. Online duels, account services and downloading optional or newer packs require a connection.

An unfinished base installation must still be completed before ordinary play and patching can proceed.

MDPro4 includes an in-game update system for published, supported update routes. Finish the complete base installation first, then follow the update prompts.

You can usually skip intermediate releases when a cumulative patch is published for your installed version. On Android, an update that changes the application may also require a matching APK.

If no route is offered for your version, follow the release announcement. Patches replace changed files; they are not a full repair scan for every missing or damaged file.

Keep enough free space for downloads, extraction and temporary backups, and allow installation or recovery to finish.

Use #mdpro4-download and the matching post in #announcements. Choose the package released for your platform and follow its installation instructions.

Download the complete installer set from the same release. Windows, Android, Linux and macOS use different packages; keep the original part filenames.

The download channel also contains the community installation guide. Follow the instructions for your exact release if an older guide shows different steps.

A GitHub Source code ZIP is not a ready-to-play installation. Synthetic updater fixtures are not the game either.

Keep the exact error message—it tells us where installation stopped.

1. Check that every required part is present and belongs to the same platform, version and installer set.
2. Keep the original filenames. On desktop, place all parts beside the installer.
3. Check free space for both the downloaded files and the extracted game.
4. If a part fails verification, download that part again from an announced mirror.

On Android, install and open each numbered APK in order; wait for its completion message before the next one.

Still failing? Report your device/OS, release version, filename or part number, download source and exact error. Preserve any recovery or backup folder mentioned by the game.

Try another mirror listed in the same release announcement, or try the affected host again later.

A host's quota message does not mean your installed game is broken. Keep any parts that finished correctly and get the missing parts from another announced mirror of the exact same installer set.

If every listed source fails, report the release, filename, mirror and exact message so the download links can be checked.

It is looking for the next installer part. You do not need a physical disc.

Download all numbered files listed for that release and keep them together beside the setup program. Keep their original names, including extensions. A browser-added suffix such as (1) can prevent the installer from finding a part.

If it still asks, check that the file finished downloading and belongs to the same installer set. Use the release's file list or checksums when available. Do not mix files from an older or rebuilt set, even if the displayed game version matches.

Yes, if the mirrors provide identical files from the exact same installer set.

For example, you can get Parts 1–3 from one announced mirror and Part 4 from another. Keep the original filenames and verify checksums when supplied.

Match the platform, release and set—not just the version number. A repackaged installer can have different split boundaries while keeping the same game version. Never mix old and refreshed parts.

This helps you obtain the complete set. It does not combine several hosts into one faster download.

Downgrading an installed game is not supported by the updater. Do not apply an older patch or copy an old executable over a newer installation: the player, data and assets need to match.

If you need an older version for a specific reason, ask in #troubleshoot with your current version and platform. An older complete release, if still available, would need separate release-specific instructions.

Back up or export your decks, replays and custom content before changing installations. Newer saved data may not work in an older version, and uninstalling an Android app can remove its data.

After the complete installation finishes and the game opens successfully, you can remove the downloaded setup archives or APK copies to save space. Keeping a backup set is useful if you want to reinstall without downloading everything again.

Delete only the installer files you downloaded. Keep the installed game, its resource folders, decks and replays. On Android, finish every required APK part before removing your downloaded copies.

Do not manually delete update recovery or backup folders while installation is running or an error still needs investigation.

Each APK installs another part of the same offline resource set.

1. Download the complete set for the announced Android release.
2. Install Part 1, open the game, and wait until that part finishes.
3. When the game says the part installed successfully, close it and install the next APK as an update to the same app.
4. Open the game after every part and continue until the full set is complete.

Keep enough free space for downloaded APKs and extracted resources. Do not uninstall the app between parts: the completed resources must stay in place. Installing all APKs without opening them in between does not extract each part.

If it stops, report the part number, completed count, device and exact message.

Usually no—use the update offered for your installed version. A published cumulative patch can take a supported older installation directly to the target release.

Windows can also apply a supported chain through its updater. Android, Linux and macOS use their explicitly published routes; if instructions offer a staged route, finish and restart after each step before taking the next one.

Do not apply a patch for another starting version or platform. If no route is offered, follow the full-installation guidance in the release announcement. A patch still needs a complete base installation; it is not a replacement for missing installer parts.

Install MDPro4 as a fresh installation and keep a backup of your MDPro3 files. The Workshop distribution treats MDPro4 as a new baseline, including a different Android app identity.

Export or copy the decks, replays and custom content you want to retain, then import supported files into MDPro4. Check them in the new game before removing the old installation.

Do not merge the entire MDPro3 game folder into MDPro4: old player files, bundles and configuration can conflict with the new release. Compatibility of every old replay or custom pack is not guaranteed.

No. Releases described as synthetic updater fixtures exist to test the update system. They are not complete game releases or ordinary patches for your main installation.

Use only the playable release and update channel announced for players. Test fixtures belong in disposable test installations following the maintainer's instructions.

Pre-Release card packs are a separate feature: they add newer card content and should not be confused with updater test builds.

The total changes with game data updates, Pre-Release packs, alternate artwork, and installed custom packs. Standard and Rush Duel also have different card pools.

For a specific card, search the Deck Editor with the relevant pool selected and restrictive filters cleared. Include your game version, language, and card ID/name when asking about something missing.

We avoid a fixed FAQ total because it would quickly become outdated.

Check the card in the Deck Editor first. Update the relevant Standard or Rush Pre-Release pack if it is a newer card, then clear search filters that could hide it.

A card appearing in the editor confirms that its data is installed. It does not prove every interaction has been tested or that every online server supports it.

If you need help, give us the set name, exact card name or ID, game version, language, and mode/server.

Pre-Release packs add newer cards and their scripts before they are included in the regular card data. Their translations and effects may change as the cards are reviewed.

Standard and Rush Duel use separate packs. Update the pack you need from Settings → Expansions, outside an active duel.

Having a card installed does not automatically make it legal or supported on every online server.

The project is now called Pre-Release Translations. The old TransSuperpre download location is retired.

These packs extend the ocgcore card pool; they do not add effects to the separate Master Duel native engine.

The physical release date and the simulator update schedule are separate. A card still needs to reach the game's data and scripts; translated packs can also need review before publication.

First update the relevant pack under Settings → Expansions and check your Deck Editor filters.

If it is still missing, tell us the exact card name or ID, your language, and your game version. The release of a physical set does not guarantee same-day availability in every language.

1. Check whether it belongs to Standard or Rush Duel.
2. Outside a duel, open Settings → Expansions and update that Pre-Release pack.
3. Clear restrictive Deck Editor filters and check the relevant card pool.
4. Search by card ID if available; translated names can differ.

The pack follows your selected interface language. After changing languages, update the relevant pack again.

If it remains missing, report the card name/ID, language, game version, and any update error. Different languages may receive reviewed cards at different times; an update check cannot download unpublished content.

Alternate artwork is added after its official OCG/TCG release, as part of a later game/data update. An announcement or preview image does not mean the artwork is already included.

Check the current release notes and the card’s available artwork variants. If an artwork that should be present is missing, include the card name, a reference image/link, game version and platform.

This helps us distinguish artwork awaiting inclusion from an installed image that is failing to load.

The ocgcore and Master Duel native engines use different card data. If your build offers engine selection, switching can change which cards and modes are available.

Pre-Release packs and ordinary custom Lua cards extend the ocgcore card pool. They do not automatically add those cards or effects to the native engine.

When reporting a missing card, effect problem or replay issue, include the selected engine, card name/ID, mode and game version. Attach the replay saved by that mode; keep its original file extension.

MDPro4 checks its hosted banlist feed when the game starts online. Standard, Genesys and Rush lists are refreshed automatically; you do not need a Cloudflare account or a separate manual download.

Open the Deck Editor and select the format and dated banlist you want to build for. If an update cannot be downloaded or is invalid, the game keeps its last valid installed lists. You can still use those lists offline. Locally installed historical and custom lists absent from the feed are retained.

Online legality still follows the server or room's selected rules. Updating your local lists does not change a public server's banlist. For a missing or incorrect restriction, report the format, list name/date, card and game version.

Open Settings → Duel → Banlist History and choose All, Latest 5 per format, or Latest 1 per format.

This controls which installed OCG, TCG, MD and AE lists appear in the Deck Editor. Rush and custom lists remain available. The setting filters the menu; it does not delete old lists or change an online room's rules.

For a Progression Series, use that series' banlist settings instead. A series can follow historical OCG/TCG lists as its packs advance, use a fixed list, or use N/A. The organizer can change this policy between duels and share the updated series with Player 2.

Deck Sync was added in 1.0.5. It uses an independent MDPro4 account; no email address or MyCard account is required.

1. Open Settings → Duel → MDPro4 Deck Sync → Create sync account.
2. Choose your display name and save the recovery key somewhere private. The game shows the key once and does not save it for you.
3. Choose Upload local decks to copy your existing decks into the account's sync group. Keep using those copies for future cloud edits.
4. On a signed-in device, choose Link another device. On the other device, choose Link this device and enter the one-use link key before it expires (10 minutes).
5. Use Sync now on each device when you want to exchange changes.

Restore with recovery key reconnects to an existing account. Do not create a second account to recover the first one's decks. Manage linked devices lets you revoke an old device. Keep recovery and link keys out of screenshots and public reports; losing every linked device and the recovery key can leave you unable to recover the account.

Each account supports 600 deck identities. The service limit was raised from 100 to 600 on 28 October 2026 and applies to existing accounts without creating a new account or installing a new client. Ordinary local decks outside sync are not counted.

Editing or renaming an existing managed deck keeps its identity and does not use another slot. Uploading a separate deck or preserving a conflict as a new deck does use a slot. Deleted cloud decks still count because their deletion records must reach devices that have been offline; deleting decks does not reclaim identity slots. Existing identities can still be edited at capacity.

Older clients may still mention 100 in the capacity error text. The server enforces 600; the upcoming 1.0.6 client updates that message.

The bracketed code is a sync ID added to the local filename so separate decks with the same title cannot overwrite each other. It is not a card-list problem and does not mean the deck was corrupted.

The upcoming 1.0.6 client fix hides this internal suffix from deck tiles, title searches, selection buttons and the editor name field. The filename and sync identity remain intact, so opening or saving the deck still updates the same cloud deck. User renames retain their existing sync identity.

You do not need to rename files manually or re-upload the decks to remove the code from the display. This display fix requires the updated game client; the server-side 600-deck limit is already active.

Yes, this is intentional. Deck Sync keeps its managed copies in a dedicated account group, shown as MDSync or MDPro4 Sync in the deck selector. Those are usable local deck files, not a read-only view of the cloud.

Upload local decks creates managed copies and leaves the originals in their regular groups. The original and its sync copy are independent. Deleting the original does not remove its cloud copy, and syncing does not rebuild the original's ordinary group.

Open and edit the deck inside the sync group to keep working on the same cloud deck. You do not need to copy it out first. If you want a separate ordinary local copy, you can keep one, but changes to that independent copy will not automatically update the managed deck.

Save the deck inside the sync group, then press Sync now. Being signed in does not enable continuous automatic syncing.

1. On device A, open the managed deck from the sync group, make your changes and save it.
2. Open Settings → Duel → MDPro4 Deck Sync → Sync now and wait for it to finish successfully.
3. On device B, sign in to the same account and press Sync now before opening that deck.

Editing or renaming the managed deck keeps its cloud identity. Modifying an independent copy in an ordinary group and uploading it can create another cloud deck, even if the names match; that is not how to update the managed original. Changing the original regular-group deck also does not change the copy already uploaded.

If changes do not arrive, check which group you edited, whether you saved, whether both devices use the same account, and the sync result. An expired or revoked session needs to be linked or restored again. Report the exact error and version, without sharing your recovery key.

First check which copies were deleted. If decks still open from the MDSync group, the synced local copies are present. An empty ordinary group is expected: syncing does not recreate the original folders from before upload.

If the managed files themselves were deleted, 1.0.5 and 1.0.5.1 have a recovery bug. The account can still list those cloud decks, but Sync now may leave the missing managed files absent. Restarting alone does not repair them. Do not use Remove cloud deck as a repair step; that removes the remote copy.

The upcoming 1.0.6 fix makes Sync now fetch the latest cloud content for missing tracked files and restore them into the account's sync group, keeping the same cloud identities. Check the release announcement before relying on that behavior; this FAQ does not mean 1.0.6 has been published.

On an older build, keep the cloud entries and any remaining local copies. A newly linked second device with no previous sync state can download the account's decks with Sync now. If you cannot recover them that way, report your version, the deleted group and whether the cloud entries remain visible. Never post the recovery key.

To remove a deck from the cloud, use MDPro4 Deck Sync → Remove cloud deck. This keeps its local file and stops that file from being tracked as the same cloud deck. Signing out also keeps local decks.

Moving or deleting a managed file locally does not delete its cloud entry. With the upcoming 1.0.6 recovery fix, Sync now can recreate a missing managed copy; a copy moved elsewhere remains independent. Use the explicit cloud-removal action when you want the remote deck removed.

If two devices edit the same deck before syncing, the game preserves conflicting changes as a separate conflict copy. Compare the copies, keep the changes you want and sync again. Sync before editing on another device to reduce conflicts.

Deck Sync is useful for exchanging current decks, but it is not an unlimited version-history backup. Keep separate backups of decks you do not want to lose. Delete sync account is a different action that removes the account's cloud content, including its community Combo Sheets.

Open Deck Editor → Submenu → Combo Sheets. Combo Sheets were added in 1.0.5. Installed examples and your local drafts work offline.

• Start with Examples, including the Chimera and Chaos Ritual guides. Select a variant and combo, then use View full combo to follow its steps. Card previews, starting hands and endboards help explain the route.
• Use My combo sheets to create a named guide or copy an example into an editable draft. Add variants, starting/required cards, numbered steps and an endboard. The visual-flow editor can show actions, locations, arrows and alternatives.
• Save the draft before leaving. Saving locally does not publish it. Combo Sheets explain plays; they do not execute the combo for you.

Planned for 1.0.6: Test Hand can create a draft through Save Combo Sheet in duel settings or From last Test Hand in My combo sheets. Review and edit the captured actions and the draft's recording limits before sharing. Check the release announcement for availability.

Sign in through Settings → Duel → MDPro4 Deck Sync. Community Combo Sheets use that same account; they do not need another registration.

1. Open Deck Editor → Submenu → Combo Sheets → Community to browse or search. Use archetype or custom tags to narrow the list.
2. Read a guide, inspect its cards and vote if it helped you. The uploader name and vote totals belong to that publication; votes are not a guarantee that a route is correct for every ruleset.
3. To share your own work, open a saved draft in My combo sheets and choose Publish combo sheet. Publication includes the entire sheet, with every variant and combo. Review all of it before confirming.
4. Find your publications in My uploads. Unpublish combo sheet removes the community upload and keeps your local copy ready to edit or publish again.

Copying a community guide creates an independent local draft. Editing that copy does not change the original author's upload. Include the sheet title, variant and step when reporting an incorrect route.

Open Adventures → Progression Series. The mode arrived in 1.0.5; use 1.0.5.1 or later because that follow-up restores the booster-track file missing from 1.0.5.

1. Create a series and choose OCG or TCG, the starting set, set track, packs per set, duels per set and duel rules. Review these before creating: most series rules are fixed afterward.
2. Choose Open Packs. Both duelists receive separate saved collections. Skipping the animation does not lose the cards or reroll the opening; use Review Opened Cards to see them again.
3. Choose Edit Deck and build from your earned collection. Main, Extra and Side Deck copies all count toward what you own. Saving here updates the series deck, not an ordinary local deck.
4. Choose Duel. The organizer can play Local AI, or arrange LAN/Evolution games with a friend. Start from the series so the correct deck and result are used.
5. After a win, choose a prize. When the required number of duels is complete, choose Next Set, open the next packs and continue. Earlier cards remain in your collection.

Pack rarity weights are simulation settings, not a promise of real booster-box odds. A series can use historical, fixed or N/A banlists. Ordinary Deck Sync does not synchronize this saved series; use Series & Sharing for that.

Use one shared series, with one organizer and one Player 2. Both players need compatible versions and matching card data. Creating two series with the same title does not link them.

1. The organizer creates the series, opens the packs and saves their deck. Use Series & Sharing → Export Series File and send the resulting .mdprog file to the friend.
2. The friend uses Import Series → Import Series File, which assigns Player 2, then builds their own deck with Edit Deck. For a short copied series code, use Import as Player 2 instead. Full set tracks are better shared as files.
3. From Duel, the organizer creates a LAN or supported Evolution room and shares its room invitation. Player 2 uses Duel → Join Room from the imported series and follows the invitation prompt. Evolution requires both players to sign in; LAN requires a reachable host address and port.
4. The organizer confirms the intended opponent, then both play. After the result, the organizer chooses the winner's prize, consulting Player 2 if they won.
5. The organizer exports the updated series and Player 2 imports it before the next duel. Share again after advancing sets and opening packs. Player 2's valid saved deck is retained.

Waiting for the organizer means import their new series file, not press ordinary Deck Sync. The organizer controls results, prizes and advancement. Play with trusted friends: this file exchange is not a server-managed competitive economy.

The upcoming 1.0.6 update adds a clearer Join Room text field with Paste; older builds use their existing invitation prompt.

Evolution is an online duel service. Progression Series is the pack-opening campaign in Adventures. A Progression game can use an Evolution room, but the two features have different accounts and saved state.

Open Online → Evolution, sign in to that service, choose a format and select a legal deck. Choose one of the supported ranked queues for matchmaking, or use casual rooms to play with friends. Casual room controls offer the supported duel types and rules, including Tag duels where available.

Check the chosen format, room rules and server banlist before joining. An ordinary duel launched directly from Online does not advance a Progression Series; launch it from that series' Duel action instead.

Your Evolution login is separate from the email-free MDPro4 Deck Sync account. Being signed in to one does not sign you in to the other. If a server rejects the deck or connection, keep the exact error and include the format and game version in your report.

On a supported desktop build, start the Discord desktop app, then open Settings → General → Discord Rich Presence in MDPro4 and turn it on. It is optional and off by default. Check the status shown beneath the setting.

Presence can show activities such as editing a deck, waiting in a room, dueling or watching a replay. It does not publish your deck contents, room password or login credentials. Turning it off clears the game's activity.

This integration targets Windows, Linux and macOS desktop builds. It is unavailable on Android, and Discord in a browser does not replace the desktop app. If the setting says it is waiting for Discord, check that the desktop app is running and that Discord's activity-sharing settings allow the game to appear.

Discord game invitations is a separate opt-in setting. Rich Presence alone does not make every room joinable.

Enable both Settings → General → Discord Rich Presence and Discord game invitations. Your friend also needs a compatible desktop MDPro4 build, Discord running and the invitation settings enabled.

Join a public waiting room with a free player seat on a service that supports MDPro4's Discord invitations. Use Discord's game-invitation or join controls when they are offered. The receiving game asks for confirmation and any required service sign-in before joining with the selected deck.

Private/password-protected rooms, full rooms, active duels and reserved matchmaking rooms do not become public invitations. Server support is required; ordinary presence can work even when a server does not offer invitations. If you are already in a room, duel or editing session, finish or leave it before accepting the pending invitation.

If the room has closed or filled up, ask for a new invitation. You can also use MDPro4's normal Copy join link and Online room-code/connection controls. Discord does not make an unreachable LAN address accessible to a friend.

Open Adventures → Overview and select Duel Expedition. It was added in 1.0.5 and offers a saved solo run through The Forgotten Sanctuary.

Choose a starter deck, reward path and difficulty, then take on successive duel stages. Between duels, rewards and encounters let you improve the run's deck. Standard, Veteran and Expert begin with three, two and one life respectively; a confirmed defeat costs a life.

Runs and progress save locally, so return to the mode to continue. This is separate from a Progression Series and from Deck Sync. Newer run rules include camp, event and merchant encounters, while older saved runs keep their original rules.

The finished-run history lets you review recent routes and decks. You can export a completed expedition deck into your normal deck collection without replacing existing files.

Open Online and choose the service or room you want to use. Both players need a compatible game version and the same server/room details.

Inviting a friend
Use Copy link for the selected server/room, or Connection details → Copy join link inside a room. Your friend can open the invitation or paste it into Online’s room-code field and select Connect.

Playing over LAN
One player creates the local room; the others connect using the host’s reachable IP address and the port shown in its connection details.

A LAN invitation does not create a network connection by itself. Room links may contain the password, so share them with the intended players.

The host is the player who created the local room. Other players need that host’s reachable IP address and the actual room port.

• On the same local network, use the host’s local network address.
• Through a shared VPN, use the host’s address on that VPN.
• 127.0.0.1 / localhost points to your own device—do not send it to a friend as the host address.

Copy the port from the room’s connection details. Hosting normally searches from 7911, but another available port may be used.

Across different networks, simply sharing a local IP address is not enough; the devices must have a reachable network route.

The server decides which cards and decks it accepts. A card appearing in your editor does not guarantee that it is available or legal on that server.

Possible reasons include the room’s card pool, banlist, deck-size rules, unsupported prerelease/custom cards, or different client/server data versions.

Read the exact rejection message and check the room settings. If it still seems wrong, include the server, room rules, game version, card name/ID and complete error message.

Use compatible releases on the same supported server or room. Both players must use compatible game data and any required custom content.

The operating system alone does not determine whether the connection will work: server compatibility, version differences and network reachability also matter.

If a mixed-platform connection fails, report both platforms, both game versions, the server/room type and the exact error. For LAN, check the host’s IP address and room port as well.

Where the mode offers banlist selection, choose an installed list marked MD and check its date. Hosted banlist updates are checked when the game starts online.

If an older installed list is hidden, open Settings → Duel → Banlist History and choose All. This changes the Deck Editor's list display, not an online room's rules.

For online duels, the server or host's selected rules decide which cards are legal. Selecting an MD list in the Deck Editor helps you build for it, but does not change an existing server's rules.

If the list you need is still missing, report its name/date and your game version after checking the latest release/data information.

A room list is not a count of every MDPro4 player. You may be viewing a particular service, room type or filter, and other players may be using a different service or private room.

Check the selected server and any filters. When joining a friend, ask for their exact server and room invitation/code instead of waiting for the room to appear.

If the list fails to load or shows an error, include the service, time, game version and exact message in your report.

The server controls timeouts and match results. The displayed clock is an estimate of the time information sent by that server; different services can also have separate inactivity rules.

A negative or clearly incorrect display should be reported. Include your game version, server, screenshot/video, when it started and a replay if available.

Do not assume that a frozen clock means the server has stopped counting time.

Check these in order:

1. The host has created the room and is still in it.
2. Everyone is using compatible game versions.
3. The guest entered the host’s reachable IP address and the room’s exact port.
4. Both devices are on the same reachable local network or shared VPN.
5. The host’s firewall permits MDPro4 on the intended network.

A guest should not use 127.0.0.1 to reach someone else’s device. Guest Wi-Fi or network isolation can also prevent devices from reaching each other.

If it still fails, include the platforms, versions, network type, exact error and whether the room appears at all. Keep private room passwords out of public screenshots.

Report the exact registration message and the step where it appears. Account registration is handled by the account service, so reinstalling the game will not necessarily change it.

Check the registration form's requirements and any current service announcement. If the form fails inside the client, try the registration page linked by the service in your browser.

For help, include whether you used the client or browser, the time of the attempt and a screenshot with private details hidden. Never include your password or verification code in a public report.

A normal Extra Deck is limited to 15 cards.

The editor may hold a larger list for custom use, but that does not make it legal in a normal duel. Automatic additions start going to the Side Deck once the Extra Deck reaches 15.

The selected mode and the room/server decide whether a deck is accepted. For ordinary duels, keep the Extra Deck within the allowed limit.

The Solo bot list is included with the game data.

• Clear any active search or filter.
• Check the selected UI language.
• Make sure installation finished and all required game-data parts were installed.

If the list is still empty, report your game version, platform and UI language, with a screenshot of the Solo screen and any loading error.

Use the data files supplied for your release; mixing bot catalogs or decks from unrelated versions can create missing entries or broken references.

WindBot uses programmed strategies for particular decks. Giving a bot a different deck does not teach it that deck’s combos.

Start with the bot’s supplied deck. Custom-deck performance depends on its existing strategy and how well that strategy fits the cards you give it; unusual builds may produce weak or incorrect decisions.

To report a bot decision, include the bot name, deck, game version, replay and the turn/action where the problem occurs. Explain the play you expected it to make.

The bundled local WindBot deck does not automatically rebuild itself around the banlist you selected in the Deck Editor. Local Solo can therefore include cards that are forbidden in your preferred competitive format.

Check the bot’s deck, the duel mode and its deck-check settings. Online servers apply their own room rules. A card being forbidden in another format is different from an effect resolving incorrectly.

If you suspect an illegal effect or extra draw, attach the replay, bot name, card name and turn so the full game state can be checked.

Open your deck, select Test Hand, set Starting Hand to 1, then press Start.

The setup also lets you change Life Points, the rule, shuffling and whether a replay is saved when leaving. Turn No Shuffle off when you want a shuffled draw.

If your version does not show these options, check the current release information. If Test Hand stalls or Retry fails, report your version, selected rule, settings and deck.

Check Settings → Audio → Music:

• Music can follow your field or your opponent’s field.
• Custom Duel Music can replace the usual field soundtrack.
• Some fields share music, and some change tracks as the duel progresses.

If music is missing, also check the BGM volume. If the wrong track still plays, report the field, music settings, game version and when it happens; a short recording helps.

Start with the last message shown on screen. A loading problem can come from an incomplete installation, missing data, unavailable storage or a specific startup error.

1. Confirm that installation and all required resource parts completed.
2. Check free space and that the installed game folder is accessible.
3. On Android, a message telling you to install the next APK means the base set is still incomplete. Follow that instruction.
4. If an error is displayed, copy it or take a screenshot before changing files.

Report your version, device/OS, last loading message and whether this followed an installation or update. Attach the game log if available.

Running as administrator is not a general fix; investigate a permissions error only when the message points to one.

Android restricts access to app data folders, so a file manager may be unable to open Android/data.

Use the game's Import and Export controls for supported files such as decks, replays and expansion packs. Place files you want to import in an ordinary user-accessible folder, then select them through the file picker.

Export anything you want to keep before uninstalling or clearing app data. If an import fails, report the Android version, file type and exact message.

Android storage restrictions

Check that you have a player name, the correct server address and port, and the right room code/password. Read any message shown near the action or in the game’s notifications.

If you are opening a room invitation, finish or leave an active room, duel or deck-editing session first; the invitation may wait until that session ends.

For account-based services, also check that you are signed in. If the action still fails, report the service, exact button/screen, version, platform and any error, ideally with a short video. Remove passwords or private account information from attachments.

In builds with the updated controller system, controller navigation includes duel selections, with button remapping under Settings → Controls. Follow the on-screen hints, which reflect the active bindings.

If an action cannot be reached, report the controller model, USB/Bluetooth connection, platform, game version and exact screen or duel prompt. Mention whether the same action works with mouse/touch and whether you changed the bindings.

For a duel issue, attach the replay and a short video showing the input problem when possible.

First check whether the whole screen is affected or only certain cards.

If the issue appears when animated artwork plays, try turning Animated Card Art off in Settings → Appearance, then reopen the same screen. Older versions may place this option under General. This is a diagnostic workaround for animation-related problems.

If static art is also missing, verify that the complete resource installation finished. A missing artwork file or platform asset problem needs a different fix.

If it persists, report your device/GPU, OS, game version, affected card names/IDs, screenshot and whether disabling animation changed anything.

“UNKNOWN” does not identify one specific cause. The client may be missing the card's data, using the wrong card pool, or failing to load its database.

If many or all cards are affected, check that the full installation completed and note any database/startup error. If only a few cards are affected, include their IDs and check whether they belong to a custom or Pre-Release pack.

On Windows, a missing-runtime or DLL error may require the matching Microsoft Visual C++ Redistributable. Follow the error and release instructions; installing every runtime is not a universal solution.

Report your version, OS, language, selected mode/engine, screenshot and relevant log. A deliberately hidden opponent card is different from a known card unexpectedly becoming UNKNOWN.

Report one issue at a time and show how to reproduce it.

Client/version:
Device and OS:
Game language:
Mode/server/engine:
Steps:

Expected result:
Actual result / exact error:
Frequency:
Attachments:

For card effects or rulings, attach the duel replay (.yrp3d for an ocgcore duel), card names/IDs and the turn where it happens. If no replay could be saved, explain why. For an ocgcore Local AI issue, compare with Server AI when possible. For native-engine Solo, identify the engine and attach its saved .mdreplay if available.

For updates, add the previous and target versions, filename/part number and download source. For translation, add the current text, language and suggested correction.

Screenshots and videos help; the replay is especially useful for reconstructing a duel state.

For ocgcore custom cards, use a private/LAN host that supports the custom pack. Everyone needs matching card data, and the duel host needs the matching scripts.

Installing a custom card on your device does not upload it to a public server. A public server's Custom cards option refers to the card pool that server supports.

Agree on the same pack version and compatible game version before testing. If the room rejects the deck, check its permitted card pool and rules as well as whether the host has the pack.

For MDPro4 crashes, installation/update failures, interface issues, artwork, controller behavior or translations, use this server’s bug-report area and its template. Search existing reports first and keep one issue per report.

For suspected YGOPro/ocgcore card-effect or script problems, use MyCard Forum. Include the .yrp3d replay, card names and the turn/action. If it happened in Local AI, compare with Server AI when possible.

If the issue occurs specifically in an MDPro4 native-engine mode, report it here with that engine named and its saved replay if available. Native replay files use .mdreplay; do not rename them to .yrp3d. Do not send a client-only visual issue as a card-script bug.

Include your exact version and clear reproduction steps; a public ticket makes the investigation easier to follow.

WindBot deck logic is written in C#. A .ydk file supplies the cards; a deck executor teaches the bot when and how to use them.

Start with an existing executor close to your deck in windbot-elder, then implement and test the decisions your cards need.

Changing the deck list alone does not teach new combos. When asking for help, include the executor code, deck list, a reproducible situation, and the move you expected.

First decide what you want to make: card art, a summon cut-in, a wallpaper, a character, or a full animation. They use different formats and workflows.

For a first project, begin with supported DIY images or a character pack. Full animations need compatible assets, effects, and support for the target platform; exporting an animation file alone is not enough to make it work in-game.

When asking for help, include your goal, platform, game version, and a short preview. Use the instructions supplied with your installed version, since newer customization features may not be in older releases.

For the ocgcore engine, a working custom card has three parts:

• Database: ID, name, text, type, and stats.
• Lua script: what the effects actually do.
• Artwork: how the card looks.

Use DataEditorX to edit the database and scripts. Follow MDPro4 Sacred Book for the learning path, functions, and examples.

Start with one simple effect, keep its database ID and script filename consistent, and test locally. Writing effect text in the database does not implement the effect.

Some DataEditorX menus still use the MDPro3 name.

Interface text and card text use different workflows.

For menus, buttons and messages, report the screen, language, current wording and suggested correction, preferably with a screenshot.

For card names, effects or prompts, include the card ID/name and language. To help with Pre-Release cards, start with the Pre-Release translator guide, which explains the language workspace and DataEditorX workflow.

Translate text while keeping card IDs and gameplay values unchanged. You can report a small correction without setting up the whole toolchain.

Start with MDPro4 Sacred Book.

• Learn: Lua essentials, your first card, activation flow, and debugging.
• API: functions and constants when you need an exact call.
• Examples: real card scripts to study.
• Script Explorer: find cards and existing patterns by text, ID, or function use.

Rush Duel also has its own lessons and helper reference.

Keep DataEditorX open beside the guide and build one small, testable effect at a time.