MyArcadePlugin Pro - WordPress Plugin

MyArcadePlugin Pro Guide: Building and Maintaining a WordPress Game Portal

MyArcadePlugin Pro is useful when a game section needs to be managed as more than a random collection of embedded pages. It provides a controlled workflow: pull game cards from an authorized source or add your own game, review the data, assign categories, prepare a post, and only then make it available to visitors. This guide focuses on that workflow. It helps you launch a catalog without losing control as the number of games grows, publishing queues appear, leaderboards are added, and automated tasks begin running.

The plugin has its own MyArcade dashboard, where game fetching, manual imports, review of accumulated items, publishing, and score management are separated. That separation matters: fetching a game does not mean it has been published, and a published post is not automatically a verified page. This approach is especially important for sites with advertising, user accounts, or their own HTML5 games.

This guide does not cover purchasing, license keys, or ways to bypass licensing. It is about safely configuring an existing installation of MyArcadePlugin Pro: from preparing WordPress to creating a repeatable import workflow, publishing a controlled test, reviewing the public-facing page, and troubleshooting issues. Dashboard item names are shown as they appear in the documentation, although individual fields and the available game sources may differ in your installed build.

More Than a Link Directory: A Game Publishing Pipeline

The most useful way to understand the plugin is as five connected states: the game source, a fetched game card, a reviewed card, a published WordPress post, and an observable outcome on the site. MyArcadePlugin Pro connects these states, but it does not remove the site owner’s editorial responsibility. The plugin can retrieve details from a supported distributor, save them in its own database, let you open and edit the game in Manage Games, and then create a post through Publish Games. The documentation describes different workflows for bulk and individual publishing, so this is not one anonymous, one-size-fits-all process.

This separation addresses a common issue with game portals: if everything from an external catalog is published immediately, the site can end up with duplicates, weak descriptions, unsuitable categories, games with broken embeds, or pages that offer no clear path for the visitor. By collecting games in a queue first, the administrator can review incoming material separately from the public site. They can check the title, description, instructions, tags, category, image, launch method, and compliance with the source’s rules.

Inputs, Workflow, and Outcome

The input may be an item from a connected game distributor or an individual import. The official Pro description mentions automatic game fetching and manual import methods, including HTML5 archives, embed code, and iframe imports, as well as certain legacy formats. Internally, the plugin does more than place a link on a page: it stores game parameters, creates or fills a future WordPress post, connects tags and categories, can attach a thumbnail as the featured image, and maintains separate data associated with the game.

The outcome should be visible in two places. In the admin area, you should have a meaningful post with the expected status, category, and game data. On the public site, the game page should open without its container overflowing the theme layout, visitors should understand what to do, and nearby template elements should remain intact. If leaderboards are enabled, an additional expected outcome is that a compatible game accepts a test score correctly. Verification means observing the expected state, not simply seeing a message that a button was clicked.

Who This Approach Works For

MyArcadePlugin Pro is a good fit for an independent WordPress portal with browser-based games when the owner needs a content queue, categories, individual game pages, and the ability to control publishing through a familiar CMS. It is especially appropriate when the catalog is updated regularly but the editor wants to retain control over game selection, descriptions, and the pace at which new pages go live. The plugin can also be useful for a game section within an existing blog: the documentation describes selecting a parent category, publishing into a single category, and working with custom post types, so the game section does not have to be mixed with news content.

For a small site with one original game, this pipeline may be excessive. If the task is limited to a single static page and the developer has already prepared a safe file deployment, there is little reason to build a large automated catalog. The plugin is also not a good choice when you do not have permission to publish or embed games from the selected source: technical access to data does not grant the right to republish it. Finally, automated publishing does not replace moderation because metadata quality and the availability of an external game remain outside factors.

Three Product-Specific Features That Shape Your Setup

The first feature is the separation between Fetch Games and Publish Games. The list is populated first, and only then are selected items turned into posts. The second is that categories and the post template are not cosmetic choices: they determine where the game appears, how visitors find it in archives, and how useful the game page itself will be. The third is that automation has two independent paths: fetching and publishing. Do not enable both at once without a small test, or it becomes difficult to identify where an error occurred.

Another product-specific area is game data. The developer documentation lists meta fields for the game URL or code, width and height, thumbnail, screenshots, and leaderboard status. An editor does not need to modify these fields manually, but knowing they exist helps with troubleshooting: if the post exists but the game block does not appear, check not only the template but also whether the specific game has its underlying data. Likewise, a theme that displays a game card needs to know which post type and fields were selected.

Before Installation: Define the Boundaries of Your Catalog

A successful installation begins not with uploading a ZIP file, but with deciding what qualifies as a game on your site. Make a short list: which sources are allowed, which genres are needed, whether you will host your own HTML5 games, where categories will live, whether registered users are required, whether you need a leaderboard, and who is allowed to publish new posts. This list is for configuration, not bureaucracy. Without it, you cannot make informed decisions about categories, publishing status, or automation.

Check Content Rights Before Connecting a Source

A distributor, game archive, and game developer may all impose different rules on embedding, advertising, local file storage, display on another domain, and score submission. Start with the official terms for the source you intend to connect. Do not move someone else’s game into your site archive simply because the plugin can technically download a file or accept a ZIP archive. In the MyArcadePlugin Pro interface, the ability to download game files, thumbnails, and screenshots is contrasted with link-based mode: a local copy makes the site less dependent on the distributor, but it increases disk usage and traffic. It does not override license terms.

For your own HTML5 project, prepare an archive whose entry file and related resources actually work after extraction. The official MyArcadePlugin documentation describes importing an HTML5 game from a ZIP file: the plugin extracts the archive and looks for index.html. This is a convenient mechanism, but it cannot repair an incomplete archive. Before importing, test the game in a separate browser environment, make sure paths to JavaScript, images, audio, and fonts are relative, and confirm that no external server blocks required requests.

Separate Your WordPress Content Types

Decide in advance whether games will use regular posts or a dedicated custom post type. The official settings page states that MyArcadePlugin Pro can work with a selected post type, and that a custom type must be created before you select it in the settings. The rule is simple: set up your WordPress content structure first, then select it in MyArcadePlugin Pro. Do not switch post types after bulk publishing until you have tested a copy of the site. The change may affect archives, theme templates, search visibility, and menu links.

For a mixed project, a dedicated content type can work well, such as a game section with its own categories. This keeps news and reviews out of the same archive as games and gives the editor a clear boundary between content types. If you do not plan to create a custom post type, a parent category is an alternative: the plugin instructions describe creating game categories under a selected parent category and publishing all games into one selected category. This is simpler, but it requires discipline on an existing blog.

Prepare the Theme, Permalinks, and a Rollback Path

In a test installation, open a standard post and assess the maximum content width, sidebar placement, caching, and the single-post template. MyArcadePlugin Pro includes a maximum game width setting that the documentation recommends for preventing an oversized container from breaking the theme. Record that value before importing instead of choosing a size at random. Also review WordPress permalinks: the documentation specifically notes that, for some IBPArcade score-submission workflows, the default permalink format must be changed to a human-readable one. Do not alter the permalink structure on a live site without a backup and redirect testing.

You also need a simple rollback path. Create a backup of the database and files, disable automated publishing, and run the first test with one game in Draft status. If caching is enabled, prepare a way to clear the cache for a specific page and its archives. This is not a peculiar requirement of MyArcadePlugin Pro: game containers, thumbnails, and new posts are often cached at different layers, so an outdated page can look like an import failure.

Checkpoint before installation: you know the source and its rules, have prepared the post structure, can restore the site, and have selected one test game. Do not enable bulk fetching or automated publishing until you have passed this checkpoint.

Installing the Plugin and Running a First Check Without Bulk Changes

The MyArcadePlugin Pro package may be delivered as a general archive containing several components and instructions. On its support page, the developer specifically addresses the Plugin install failed error and explains that, in this case, the downloaded package must first be extracted and the plugin itself installed from the nested archive. This is not a reason to look for another ZIP file: the error often means WordPress received the distribution bundle rather than the plugin root.

A Safe Installation Sequence

1. Create a backup of the site database and files, especially if a game section already exists.
2. Extract the received package locally and read the included instructions to identify the archive intended specifically for MyArcadePlugin Pro.
3. In the WordPress admin area, open Plugins, upload the correct ZIP archive, and complete the standard installation.
4. Activate the plugin and confirm that a MyArcade item appears in the admin navigation.
5. Open MyArcadePlugin Dashboard, but do not fetch games until you have checked the basic settings.

After activation, do not try to populate the entire portal immediately. First, record the starting state: how many regular posts existed in WordPress, which category structure was in use, whether the public site opens correctly, and whether there are obvious errors in the server log. This quick check makes it easier to distinguish installation effects from issues caused by initial configuration or import.

What to Inspect Immediately After Activation

The MyArcade dashboard provides access to the key working areas: overview, game fetching, publishing, importing, game management, score management, and settings. If the menu appears but an individual page returns an access error, first check the current user’s role and confirm that the rest of the WordPress admin area works normally. Do not edit plugin files to solve this kind of issue. Manual changes to the plugin core make updates harder and can hide the actual cause.

The documentation publishes minimum server guidelines, including JSON support, permalink functionality, and sufficient memory limits. Some of these figures come from older documentation revisions, so do not treat them as a compatibility statement for a modern server. The practical point remains valid: your hosting environment must allow WordPress to make background requests, extract permitted archives, write required files, and process game data without failing due to memory or time limits. Check the exact requirements against your package and the developer’s current page.

How to Return to the Original State

If the site becomes unstable after activation, first deactivate the plugin normally and see whether the symptom disappears. If it does, restore the test copy or review the error log instead of deleting tables, folders, or posts at random. MyArcadePlugin Pro settings include destructive actions for deleting fetched games, deleting scores, and restoring default settings. These actions affect data; they are not a safe way to undo installation. A rollback should be based on a backup and a known cause, not a cleanup button.

The MyArcade Dashboard: Where Fetching Ends and Editorial Review Begins

After installation, it is worth walking through the dashboard once in the correct order without publishing anything. The official description calls MyArcadePlugin Dashboard a place for reviewing status, settings, and news. That is the starting point, but daily work usually centers on four pages: Fetch Games, Manage Games, Publish Games, and Import Games. Understanding the distinction greatly reduces the risk of accidentally opening the portal to an unreviewed queue.

Fetching Games Creates a Queue, Not Site Pages

On Fetch Games, MyArcadePlugin Pro retrieves data from selected distributors and stores it in its own database. According to the documentation, these games can be published later, meaning that fetching does not have to create public posts. For the first run, choose one tested source, a limited set of categories, and a small sample. If the interface lets you configure individual distributors separately, do not enable every available option at once: it becomes much harder to troubleshoot duplicates, outdated details, or games that do not meet the site’s policy.

Do not assume an empty fetch result means something is broken. Start with the obvious: is the source enabled, is at least one game type or genre selected, does the source allow access, and does it require its own parameters? The official documentation explicitly states that you must select at least one game category for fetching. Then compare the number of retrieved items with what appears in Manage Games, not just with the message shown on the fetching page.

Manage Games Is the Editorial Gate

In Manage Games, you can view, edit, delete, or launch a game before publication. This is the key quality-control page. Open each card not only as an administrator reviewing fields, but as a future visitor. Check whether the title is clear, the description language is appropriate, the instructions are understandable, the genre and tags are correct, the game area size is suitable, the thumbnail is present, and the source is clear. If the game is expected to save scores, look for an indication of leaderboard compatibility, but do not promise a leaderboard until you have completed a test game.

A useful editorial practice is to define short selection rules: do not publish games without a proper title, do not leave machine-generated text unreviewed, do not use Other as a permanent dumping ground for unknown items, and do not release a card if a test launch displays an empty container. The plugin speeds up the workflow, but it does not define your quality standard.

Publish Games Sets the Pace and Status

Publish Games creates WordPress posts from selected items. The documentation describes filters on this page and a setting for the number of games published per run. Start with one post in Draft status. Then open the draft in the standard WordPress editor, review which post type and categories were applied, and check the public view after publishing. Only after that should you increase the batch size or use a schedule.

Status is a risk-management tool. With Publish, content goes live immediately. Draft leaves it for editorial review. Scheduled publishing provides a middle ground: pages are already prepared, but their release is spread over time. For a new project, drafts are almost always better. For an established site, scheduling is useful only after you have confirmed that every source, category, and template produces predictable output.

Import Games Supports a Different Workflow

Import Games is intended for individual imports rather than catalog queues. The form changes depending on the selected method because ZIP files, embed code, and iframe imports require different inputs. Do not try to fill in every field generically. When importing your own HTML5 archive, pay close attention to file structure. When using an embed, confirm that the provider permits this type of display and does not block iframe use through security headers.

Your first outcome should be small and reversible: one fetched or imported game, one reviewed card, one draft, and one published test page. Once you have completed this chain, the dashboard becomes easier to understand without the risk of filling the site with hundreds of unreviewed items.

Settings That Determine the Quality of the Game Section

The Settings page is not a collection of checkboxes to enable all at once. It defines the rules by which a future game becomes a WordPress post. Configure content structure and publishing first, then post appearance, and only afterward add file storage, scores, translation, and automation if needed. This order makes it easier to see the relationship between a setting and its effect.

Categories and Source Category Mapping

A game source may use different category names than your site. MyArcadePlugin Pro provides category mapping, allowing incoming items to be assigned to your own categories instead of retaining source labels. This is particularly useful when visitors need concise navigation while the provider supplies overly granular or English-language genres. First, sketch the final category tree: for example, logic puzzles, racing, sports games, and kids’ games. Then map incoming labels to that tree.

Do not create dozens of new categories on the first day. Every category should have a purpose: an archive page, menu item, collection, or filter. Plugin settings can automatically create selected categories and assign a parent category. This can make sense for a new project. On an existing site, it is safer to create a few target categories manually, review the theme archives, and only then allow automatic creation. If a game has multiple categories, Use Only The First Category limits it to the first category. That simplifies navigation but may hide useful context. Publish In A Single Category is even stricter and is appropriate only for a deliberately chosen section model.

Checking Your Mapping

Fetch one game from each required genre without publishing the entire batch. Review which categories are assigned in Manage Games, then create a draft and check the categories on the WordPress side as well. If one game appears in two unexpected archives, return to the mapping rules rather than blaming the theme. If changes on the mapping page are saved automatically, as the documentation indicates, do not look for a separate save button; refresh the page and verify the outcome again.

Quantity, Status, and the Editorial Pause

The publishing quantity field determines how many items are created in a single Publish Games run. A large number may look like a quick solution, but it raises the cost of an error during the initial stage. If the post template applies the wrong width or category, fixing one draft is easy; fixing one hundred is not. Start with one, then move to a small batch. Scale a verified workflow, not an untested configuration.

Selecting Draft creates an editorial pause. Use it to review the text, tags, thumbnail, game area, permalink, and internal theme blocks. Scheduled is useful when the workflow is already stable and you need content to go live evenly, but it does not solve quality problems. Check how your theme displays scheduled posts in archives and whether publication caching creates a page snapshot too early.

The Game Post Template and Meaningful Fields

The general settings documentation describes Game Post Template and placeholders you can use to assemble post content. Published placeholders include %TITLE%, %TAGS%, %THUMB%, %DESCRIPTION%, and %INSCTRUCTIONS%. This is a powerful but potentially risky tool because the template creates the repeated structure of game pages. Do not add artificial promotional phrases, dozens of repetitive keywords, or code you cannot verify.

A good base post answers a visitor’s basic questions: what the game is, how to control it, which category it belongs to, and where the game area is located. If the source supplies weak instructions, it is better to leave the post as a draft for manual editing than to display confusing text automatically. Test the template first with one game that has a long title, multiple tags, no thumbnail, and multi-line instructions. This reveals overflow, double spaces, and empty blocks before they spread across the catalog.

Do not enable the template, theme formatting, and an additional page builder at the same time without a clear reason. Each layer may render an image or description differently. Choose one primary markup source and use the others only as confirmed additions. The fewer independent mechanisms that shape a single game page, the easier it is to identify where an error should be fixed.

Post Type, Taxonomies, and Thumbnails

The Post Type setting connects MyArcadePlugin Pro to regular posts or a pre-created custom post type. If a custom type is selected, check editor role permissions, the single-post template, and the archive. The documentation mentions mapping custom taxonomies to game tags and categories. This can be useful when genres and ordinary tags serve different purposes, but do not turn your structure into a maze. One category system and one understandable tag set are usually enough at the start.

The Featured Image option lets you attach a game thumbnail as the post’s featured image. In a standard theme, this helps archives, widgets, and cards display the game without additional customization. Before enabling it in bulk, however, make sure the source actually returns suitable images and that the theme does not display the thumbnail twice. If you use a specialized game theme, the documentation notes that this option may not be necessary. Do not treat that as a guarantee for every theme: test the page and archive output.

Download Files or Link to the Source

Settings for downloading game files, thumbnails, and screenshots involve an important tradeoff. With local storage, the site depends less on an external source, but disk usage, traffic, backups, and responsibility for distribution rights all increase. With link-based mode, your server carries less load, but a game or image may disappear, change, or stop opening because of external policies. There is no one setting that fits every case.

Start small and document the decision for each source. For an archive you own the rights to, local storage is usually sensible. For a third-party catalog, follow its terms and verify whether local copying is permitted. Documentation for older sections mentions game and thumbnail directories, while later changes in the public Lite code mention a move to the standard WordPress uploads directory. Because of this difference, do not manually create a path based on an old example. Check which directories your own build uses, which are writable, and which are included in backups.

The option to delete associated game files when a post is deleted requires even more care. It is useful when a local file clearly belongs to the game being removed, but it is risky when paths are confused or a folder is shared. Before enabling it, delete one test game on a copy of the site, confirm which file disappears, and verify that other posts are unaffected. If the answer is not obvious, leave automatic deletion disabled and remove data through a documented, confirmed procedure.

Scores, Guest Plays, and Fair Results

The Save User Scores setting only makes sense for compatible formats and games that actually submit results. Official Score Bridge materials show a different HTML5 workflow: the game includes myarcadebridge.js and calls functions to submit a score or achievement. In other words, enabling a checkbox will not make every game instantly support rankings. It only permits the site to accept supported data.

For leaderboards, run a separate test: play a short compatible game as a test user, finish a round normally, and check for the record in Manage Scores or on the public page. Do not simulate a score by editing the database manually. If no result appears, review the specific chain: the game ended, the bridge or supported format worked, permalinks are suitable, the request is not blocked, and the user has the required state. Storing only the best score per user and game works for a leaderboard, but not for analytics of every attempt.

The Guest Plays setting can offer registration after a defined number of launches. Use it as a clear rule for visitors, not as a hidden trap. Write a clear message, add a link to the registration page, and test the limit in a private browser window. According to the documentation, a value of zero disables the check. If registration is not part of the portal’s value, do not make the first launch harder for guests.

Translation: Do Not Replace Editing With Automation

The help documentation describes settings for automatically translating titles, descriptions, instructions, and tags through a selected external service called during publishing. This feature has two limitations. First, provider availability and interfaces can change, so confirm current availability in your installed version and in the service’s official documentation. Second, automatic translation of short game instructions often mishandles button names, genres, proper names, and control terms.

If translation is needed, enable only one field type on a test set and publish to drafts. Review the game title, player actions, tags, and warning text. Do not retranslate your own content imported manually: the documentation specifically notes that such material may not need another translation. A safe strategy is to let automation fill a draft and have a person review the visible content. This preserves speed without turning machine-generated text into the source of truth.

Automation and Two Independent Schedules

MyArcadePlugin Pro distinguishes between automatic fetching and automatic publishing. Its built-in mechanism may run when the site is visited after an interval has expired, or through an external trigger URL shown in the dashboard. The official cron material specifically describes two triggers: one for fetching and another for publishing. This makes it possible, for example, to fill the internal queue more frequently while releasing already approved content less often.

Do not enable both schedules on the first day. Set up automatic fetching for one source and verify that items appear in Manage Games without becoming visible to visitors. Then publish one draft manually. Only after both independent stages are proven should you add automated publishing with a small volume. Standard WP-Cron runs during WordPress visits, so execution time may be unpredictable on a low-traffic site. The official WordPress guide explains this behavior; for precise scheduling, the MyArcadePlugin developer describes an external cron with separate URLs. Do not publish or share those trigger addresses: they act as control endpoints.

Cleanup and Reset Are Last-Resort Operations

The advanced settings documentation lists options for deleting all fetched games, deleting marked items, clearing zero scores, clearing all scores, and loading default settings. These are not diagnostic buttons. Deleting fetched games may not affect already published posts, and according to the documentation, score submission for published games stops working after that action. Resetting settings overwrites parameters. Before performing any such operation, you need a backup, a precise goal, and an understanding of which data will remain.

It is safer to isolate the problem with one item first: correct the source, remove one test draft, and fetch one game again. Bulk cleanup is justified only when you are certain the entire internal queue is wrong and can restore the required data. The changelog shows fixes to distributor integrations and automation, so the issue may be a changed external source rather than your content. In that situation, updating, checking current documentation, and contacting support are more sensible than irreversible deletion.

Two Ways to Add Content: Source Catalogs and Your Own HTML5 Game

MyArcadePlugin Pro has two distinct content workflows, and it is important not to blur them together. The first begins with a configured source: the plugin fetches a list, you review it in Manage Games, and publish selected items. The second begins with one specific game: you open Import Games, choose a method, enter data for that game, and immediately verify the outcome. Their final publishing stage is similar, but their input risks are different.

When to Fetch From a Distributor

The catalog model is appropriate when a source officially permits use and regularly provides structured game cards. It works best with preconfigured genre mapping, a limited category list, and drafts at the beginning. Do not enable a source simply because its name appears in an old guide: integration lists change. The published MyArcadePlugin changelog shows that some connections were updated while nonworking services were removed. Review the actual list in your dashboard and the source status rather than relying on old screenshots.

After fetching, do not publish everything with one click. Sort games by the genres you need, open several cards, confirm that each received the expected categories, and make sure the information does not duplicate an existing post. The Lite changelog refers to duplicate checks as part of product development, but that does not remove the need for editorial review: two sources may describe the same game under different titles or metadata.

When to Choose an Individual Import

The manual workflow is intended for an original game, a permitted archive, or a specific embedded project that is not included in a connected catalog. First select the type in Import Games, then complete only the fields relevant to it. The documentation emphasizes that the form changes after you choose a method. Do not move a URL from an iframe field into a ZIP import or the other way around: similar-looking actions rely on different launch methods.

For an HTML5 ZIP file, check the architecture: the archive must contain a valid entry document, resource paths must not point to your local computer, and file permissions must not prevent reading. The official HTML5 import note describes automatic extraction and a search for index.html, but it does not guarantee that every game will work correctly on every hosting environment. For an external iframe, test not only the loading view but also game startup, round completion, sound, and fullscreen mode if it is needed.

Decide on Local Storage Per Game

Your own HTML5 archive is often best stored within the site infrastructure so visitors do not depend on a third-party domain. At the same time, backups must include the actual game resources, and archive updates should not overwrite a verified version without testing. For an external game, link-based mode may be more appropriate if it complies with the source’s rules. A mixed strategy is perfectly valid: what matters is not one checkbox for every game, but a clear editorial record of where content comes from and who is responsible for its availability.

After any manual import, compare not only the game view itself but also the information around it. Open the page in a clean browser, review the title and instructions, make sure the URL does not lead to an administrative page, and check for mixed content. If the game works for an administrator but not for a guest, the cause is often caching, an external-domain policy, authentication, or content settings rather than an import that "did not save."

Practical Workflow: Publishing One HTML5 Game With a Verifiable Outcome

The following workflow does not depend on a specific distributor and lets you learn the main mechanisms without bulk publishing. The goal is to add one HTML5 game, prepare a clear page for it, assign a category, publish it from a draft, and confirm that visitors receive a working game experience. If you do not have your own game, the same workflow applies to one fetched card: simply begin with Manage Games instead of Import Games.

Goal and Preparation

Imagine that your site has a logic-game section and you have rights to an HTML5 archive. A "Puzzles" category has already been created in WordPress, and the content area width has been checked in the theme. Page cache can be cleared manually for now, while automatic fetching and publishing are disabled. The administrator is working in a test environment or has a recent backup. That is enough to observe the outcome and easily reverse a mistaken step.

Step 1: Check the Archive Outside the Plugin

Open the archive locally in a prepared test environment or with the game developer and confirm that it launches the exact version you plan to publish. Check the opening view, one game round, the completion screen, and loading of key resources. Record the title, short description, instructions, and category. If the game uses external requests, an analytics service, or advertising, assess them against site policies and user consent requirements before importing.

This may seem unnecessary, but it saves time. If the game does not work before WordPress, MyArcadePlugin Pro is not required to repair its packaging. If it works locally but breaks after import, you have a clear troubleshooting boundary: the archive structure and the game itself have already been verified, leaving deployment, URLs, and server conditions to review.

Step 2: Import in Test Mode

In the MyArcade dashboard, open Import Games, choose the HTML5 method relevant to the archive, and complete the fields according to the prompts in the current form. Do not insert arbitrary embed code if you are working with a ZIP file. After saving, find the game in Manage Games. At this point, you are no longer checking archive quality, but the data the plugin prepared for publication: title, description, instructions, category, dimensions, and image.

If the card looks incomplete, correct it before creating a post. For example, add an editorial description that tells visitors what they need to do rather than repeating the title. Check the genre. Make sure the description contains no third-party promotional code and does not promise features the game does not have. For the first publication, do not add automatic translation, scores, guest-play limits, or additional integrations. Those should be separate tests later.

Step 3: Create a Draft Through Publish Games

Open Publish Games, locate the one prepared item, and create it with Draft status. If the settings specify a quantity greater than one, reduce it temporarily or use an individual action. After the draft is created, open the post in the regular WordPress admin area. This is a good time to confirm that the correct post type was selected, the "Puzzles" category was actually applied, and the permalink looks meaningful.

Open the preview and compare it with your plan. The content area should contain the game, not an empty rectangle. The title should not be duplicated across several blocks. Instructions should be readable, and the thumbnail should not overflow the archive card. If the game width exceeds the theme container, return to the maximum-width setting in MyArcadePlugin Pro or use a purpose-built theme template instead of applying random inline styles.

Step 4: Test the Game as a Regular Visitor

Sign out of the administrator account or use a private browser window. Open the draft permalink after temporarily publishing it in a closed test environment, or publish it on a staging site first. Refresh the page after clearing the cache. Go through every important state: opening, starting, player action, round completion, and returning to the normal page. Check the width in a typical desktop window and in a narrow browser window, but do not draw conclusions about mobile compatibility simply by shrinking the browser.

Then open the category archive. The game should appear where expected with a clear card and the correct thumbnail. If it appears on the single page but is missing from the archive, the issue may be in the theme settings or post type. If it appears in the archive but the page itself is blank, inspect the game-code source, external-domain restrictions, and metadata for that specific game.

Step 5: Add Scores Only for a Compatible Workflow

If the HTML5 game implements MyArcadeScoreBridge, the next separate stage is test score submission. The official API documentation shows that the game includes myarcadebridge.js and calls score submission after the game ends. Do not add this file to someone else’s archive without the developer’s permission, and do not assume it is compatible with every engine. For your own game, ask the developer to implement the bridge according to the official specification, then enable score storage in MyArcadePlugin Pro and complete one real test attempt.

Verification is not an icon on the page, but a record in score management and the expected leaderboard position. If the score does not appear, disable extra restrictions, play one round again, and trace the chain from the game to the dashboard. After a successful test, you can decide whether best-score-only mode is needed and what registration requirement should apply to players.

Step 6: Document the Working Configuration

Once one game passes all checks, save a short procedure for the team: import type, selected category, file-storage mode, publication status, post template, game container width, cache-clearing method, and test outcome. This document is more useful than trying to remember a successful set of checkboxes. You can now repeat the workflow with two or three games of a different type. Only after consistently good outcomes should you increase the publishing batch or automate fetching.

How to Confirm the Portal Works After Configuration

Verification should not be limited to refreshing a page once. A game portal includes public pages, archives, plugin data, schedules, and sometimes leaderboards. Each layer should have its own observable indicator. This makes it easier to distinguish a theme issue from an import issue, a cache issue from an external-source issue, and a failed schedule from an empty queue.

Check the Public Page

Open the game as a guest, not as an administrator. The page should load through its permalink, and the title and instructions should relate to the game itself. The container should not be clipped or overlap the sidebar. Launch the game and complete at least one action that changes its state. If the loading view appears but the game does not respond, that is not yet a successful outcome. Also check the page after clearing the cache and in another browser to rule out a saved administrator session.

Check Administrative Data

In Manage Games, find the source card, and in WordPress, find the created post. Compare the title, category, status, image, post type, and connection to the template. If the plugin settings describe game metadata, do not edit it at random, but use it as a troubleshooting reference. A difference between what is stored in the MyArcadePlugin Pro card and what appears in the WordPress post indicates the stage where data was lost.

Check Archives and Navigation

Open the game category, search page, game-section menu, and related cards if the theme includes them. A visitor should be able to find the new game, not only reach it through a direct link. Missing archive entries are often related to a custom post type, theme configuration, or archive caching. Do not try to fix this by republishing the same game: first check how many posts have already been created and whether duplicates appeared.

Check Automated Tasks

For automatic fetching, create a separate test: note the time, the number of items in Manage Games, and the selected source. After the expected run, check the increase in the queue specifically. For automated publishing, run a different test with one pre-approved game and draft status. According to WordPress materials, WP-Cron depends on visits, so a lack of traffic may explain a delay. When using an external trigger, do not expose its URL in public materials and confirm that it initiates only the intended action.

Check Scores and Player Data

Evaluate a leaderboard with a test game, not only with a visual block. Sign in as a separate user, complete a compatible round, refresh the page, and review Manage Scores. If guest-play limits are used, separately test the counter in a private window: guests should receive a clear warning, while registered users should not unexpectedly lose access. Do not use test accounts with administrative privileges for these checks.

Readiness indicator: one game correctly follows the path "internal card - draft - public page - archive," and when a compatible leaderboard is enabled, the test result appears where the administrator expects it. Only then does it make sense to increase the flow.

HTML5, Ruffle, and Scores: Different Mechanisms That Should Not Be Confused

A modern game portal often contains HTML5 games, but older catalogs may also include projects associated with Flash. The MyArcadePlugin Pro changelog notes Ruffle integration: the plugin can detect Flash games and play them through this emulator. This can be useful for a legacy catalog, but it is not an argument for building a new project around an outdated format. Ruffle, the game source, content rights, and the behavior of the specific file still require separate testing.

Working With an Older Game Starts With Compatibility Testing

If an older game appears in the queue, do not publish it in bulk simply because you recognize the file extension. Create one draft, test loading and a primary action in a supported browser, then check whether the page conflicts with the modern theme or security policy. The changelog also shows that Ruffle integration has been updated, so expected appearance and behavior may differ between builds. Do not promise that every historical file will play.

If the game does not open, do not replace it with a random external embed. First determine whether the rights holder or an authorized source offers a current HTML5 version. If not, it is better to remove the game from publication than to show visitors an empty container. In a catalog, quality matters more than the formal number of cards.

Score Bridge Belongs to the Game, Not the Page Layout

MyArcadeScoreBridge is intended for HTML5 games whose code includes bridge support. The official documentation indicates that a game can submit a score through myarcade_submit_score and achievements through myarcade_submit_achievement. This is an interface for the game developer, not a button an editor should add to a post template. If you do not own the source code and the developer does not claim compatibility, do not promise visitors a leaderboard.

For your own game, organize this as a small acceptance workflow: the developer connects the official bridge, a test environment receives one score and one achievement, the administrator confirms the record in the dashboard, and only then is the feature allowed on the public site. For imported catalogs, limit testing to games that actually submit results. This ensures the leaderboard reflects real data rather than creating a false expectation.

Theme, Custom Post Type, and the Technical Boundaries of Customization

MyArcadePlugin Pro can work with a standard WordPress theme, while the developer documentation describes an API and a set of custom fields for deeper integration. These two levels should not be confused. An editorial site can usually rely on plugin settings, the game post template, and a well-configured theme. Theme development or custom rendering is needed only when the standard page does not solve a specific navigation, card, or leaderboard requirement.

First Prove the Problem Is in the Template

If a game exceeds the content width, its thumbnail disappears, or the description is duplicated, first compare one test post with a standard WordPress post. Check the maximum width, featured-image setting, post template in MyArcadePlugin Pro, and custom post type. Only when the source data is clearly present but the theme does not render it correctly should you move on to template customization.

The developer documentation identifies meta fields containing game code or a URL, dimensions, thumbnails, screenshots, and leaderboard status, as well as API functions for displaying data in a theme. This confirms that a theme developer can build a game layout using actual plugin data. However, function names and the location of the included API are part of a technical integration, so do not insert PHP snippets into an active theme without a backup and a developer who understands the WordPress lifecycle. An incorrect customization can break the entire site, not just one game.

A Safe Improvement Without Editing the Core

The safest improvement for an editor is not code, but template discipline. Create one consistent game-post structure with a title, short description, instructions, category link, and a clear launch check. Change it in the standard Game Post Template field only after copying the current text into a backup note. Then publish one draft and review the page. If the outcome is worse, restore the previous template and clear the cache. This rollback is reversible and does not require changing WordPress or plugin files.

If real PHP rendering is required, use a child theme or a separate development branch instead of editing MyArcadePlugin Pro files. Describe the task to the developer in terms of data: the page for a specific post type needs to display a thumbnail, screenshots, instructions, or leaderboard status. They should rely on current Theme API documentation and test the solution on staging. This guide intentionally contains no unverified code: public interfaces change, and preserving a standard, safe workflow is better than inventing a hook.

Troubleshooting MyArcadePlugin Pro: Symptoms, Checks, and Safe Rollback

On game portals, the same visible problem can have several different causes. A blank page may result from an unavailable game, the wrong import method, an external-domain restriction, caching, or a template. Conversely, successfully fetching a list does not prove it can be published. Troubleshooting should therefore follow the point where the chain breaks: installation, fetching, the internal card, the WordPress post, the public page, scores, or automation.

WordPress Says the Archive Does Not Contain a Plugin

Symptom: when uploading, you see a message such as Plugin install failed, or WordPress cannot find a valid plugin. Likely cause: you uploaded the general distribution bundle rather than the nested plugin archive. The MyArcadePlugin support page specifically describes this situation. What to check: extract the downloaded package locally and check whether it contains a separate installation ZIP and instructions. Fix: install the plugin archive through the standard Plugins screen. Rollback: if a working version was installed previously, do not delete data at random; deactivate the failed installation and restore the test copy if necessary.

Fetch Games Completes, but the Queue Is Empty

Symptom: the fetch command completes, but nothing appears in Manage Games. Likely causes: no category is selected, the source is not enabled, its account parameters are incomplete, the external catalog is temporarily unavailable, or the integration list has changed. What to check: begin with category settings because the documentation requires at least one category; then review the specific distributor and its connection state. Confirm that the selected source exists in your current dashboard, not only in an old guide. Fix: enable one source and one category, then fetch a small test set again. Rollback: if settings were changed in bulk, restore only the source parameters from your recorded working state rather than using a global settings reset.

The Game Appears in Manage Games but Is Not Created or Visible as a Post

Symptom: the card was retrieved, but it is not visible on the site. Likely cause: the game has not yet been published, the post remains in Draft or Scheduled status, a different post type was used, or the theme archive does not display that type. What to check: find the created post in WordPress and review its status, date, post type, and categories. Then open its permalink directly. Fix: for testing, create one post manually through Publish Games with draft status, edit it, and publish it normally. Rollback: delete only the test draft if it was created by mistake, not the entire fetched-game queue.

The Page Is Published, but the Game Area Is Blank or Breaks the Theme Layout

Symptom: the title and description are visible, but the game does not launch, is clipped, or breaks the layout. Likely causes: an external resource is unavailable, the archive was imported incompletely, an external site blocks display in an iframe, the import method is wrong, the theme constrains the container, or cache is displaying outdated markup. What to check: open the page in a private window, clear the cache, launch one round, and compare dimensions in the MyArcadePlugin Pro card with the maximum-width setting. For an HTML5 ZIP file, separately confirm the presence of index.html and resources. Fix: correct the specific import method or width restriction, then retest one game. Rollback: restore the previous post template or hide the unverified page without editing the plugin core.

Automatic Fetching or Publishing Runs Inconsistently

Symptom: games do not appear or publish at the expected time. Likely cause: standard WP-Cron depends on visits, fetch and publishing intervals are confused, there is not enough content in the queue, or the external trigger is configured incorrectly. What to check: separate the diagnosis: after a fetch run, count items in Manage Games; after a publishing run, look for a created post. Do not assess both operations using one indicator. Fix: first disable automated publishing, prove the manual workflow, then configure separate intervals. If you need an exact schedule, use the documented external cron and treat its URL as a secret control address. Rollback: disable only the automation checkboxes and continue working manually until the cause is found.

Scores Do Not Appear Even Though Saving Is Enabled

Symptom: a player completed a round, but the leaderboard is empty. Likely causes: the specific game does not support score submission, a format requirement is not met, permalinks are unsuitable for a legacy IBPArcade workflow, a request is blocked, or the test was performed under the wrong user. What to check: use one known-compatible game, sign in as a separate test user, complete a round normally, and open Manage Scores. For your own HTML5 game, confirm that the developer connected Score Bridge. Fix: resolve the break in the specific link of the chain rather than creating a score manually. Rollback: if the experiment damaged data, restore the test environment backup; use mass score cleanup only when it is demonstrably necessary.

Changing Categories Created Strange Archives or Duplicates

Symptom: one game appears in several unintended sections, or duplicate posts are visible in an archive. Likely causes: multiple categories are enabled, mapping is configured incorrectly, the game was republished after an attempted fix, or the theme displays multiple post types. What to check: open one post, its categories, its internal game card, and the history of created posts. Fix: correct the mapping, enable the first-category rule on a test set if necessary, and manually remove only a confirmed duplicate. Rollback: do not run Delete All Fetched Games because of one incorrect genre.

Collect Evidence Before Contacting Support

A support request is shorter and more useful when it includes the WordPress and MyArcadePlugin Pro versions shown in your dashboard, the exact page where the symptom appears, one safe reproduction step, the test game status, the import type, an error-log excerpt without secrets, and the result of a private-window check. Do not send keys, external cron trigger URLs, passwords, or a complete database dump. Official support recommends consulting documentation and the community first, then using the product support channel for the issue.

Setup Video: How to Use an Older Demonstration Productively

The specific video How to Configure MyArcadePlugin Pro demonstrates plugin configuration and the general route to automated publishing. It covers an earlier version, so do not copy its source names, number of distributors, or the appearance of every field literally. Its practical value lies elsewhere: it shows how source configuration, fetching, and publishing are separated, allowing you to compare that workflow with the current dashboard and documentation.

Watch the video after reading the settings section: pause at the Fetch Games - review - Publish Games workflow, and verify every parameter against your installed version. This supports the intent of "how to configure MyArcadePlugin Pro" without replacing current documentation with an old interface.

When MyArcadePlugin Pro Is a Strong Foundation for a Portal

MyArcadePlugin Pro works best on a site where process matters more than volume: there are authorized sources or original games, a clear category structure, editorial review, a test workflow, and a willingness to maintain published pages. Its main strength is not one button, but the separation of fetching, editing, publishing, scores, and automation. When you complete these stages in sequence, WordPress remains a manageable part of a game project rather than a storage space for random embeds.

Before taking the next step, repeat the control workflow with one game: a card in Manage Games, a draft, a public page, a category archive, and, if needed, a test score. When this route is repeatable without surprises, you can download MyArcadePlugin Pro and prepare a working installation using the same procedure. If even one link in the chain has not been verified, stay in the test environment and resolve the cause before enabling automation.