Title: Support documentation
Last modified: March 10, 2018

---

# Support documentation

 *  Resolved [Mr Wood](https://wordpress.org/support/users/mr-wood/)
 * (@mr-wood)
 * [8 years, 2 months ago](https://wordpress.org/support/topic/support-documentation-3/)
 * Hi, great plugin. I got the heads up from a pdf of plugins recommended by WPEngine.
   
   Can you provide some instructions on how to use the “Select Game File” option.
   I’ve created some simple html5 games and uploaded them to my site, these work
   fine using an iframe in your “Game embed code” option, but I don’t want to expose
   the url where the game is located as it’s meant to be behind a paywall. I’ve 
   tried uploading a zipped version of the entire game, but it’s not being unpacked
   when uploaded, so I can’t point to the relevant html file.

Viewing 6 replies - 1 through 6 (of 6 total)

 *  Plugin Author [Bytephp](https://wordpress.org/support/users/bytephp/)
 * (@bytephp)
 * [8 years, 2 months ago](https://wordpress.org/support/topic/support-documentation-3/#post-10060181)
 * Hi Mr Wood,
 * Thank you for the kind words, and would you be able to direct me to said pdf 
   file by any chance?
 * The “Select Game File” option is meant to be used with .swf (adobe flash) files,
   so it would not work with html 5 games.
 * If I understand your need correctly, you want to embed your own games on your
   site, but hide the embed url? Would the games only be playable after the user
   made the payment?
 * Jay
 *  Thread Starter [Mr Wood](https://wordpress.org/support/users/mr-wood/)
 * (@mr-wood)
 * [8 years, 2 months ago](https://wordpress.org/support/topic/support-documentation-3/#post-10060373)
 * Yes, I’d like to add my own games to my web site. Some of the games will be accessible
   to any subscriber, but others will available only to paid members. I can restrict
   access to the entire post, but using the iframe method of embedding allows members
   with access to find and share a link to the game. I’ve only just started looking
   into this so I’m sure there are some obvious solutions, but your plugin seemed
   to fit the bill nicely.
    [https://wpengine.co.uk/resources/ebook-ultimate-guide-wordpress-plugins/](https://wpengine.co.uk/resources/ebook-ultimate-guide-wordpress-plugins/)
 *  Plugin Author [Bytephp](https://wordpress.org/support/users/bytephp/)
 * (@bytephp)
 * [8 years, 2 months ago](https://wordpress.org/support/topic/support-documentation-3/#post-10060526)
 * Hmmm. As far as I know there is no way to embed a html 5 game into a website 
   without exposing the javascript files (or iframe code) in one way or another.
 * The files have to be included on the page in order for the browser to be able
   to read them and know what to do with them.
 * The only way to restrict it somewhat is to do what you already said and what 
   I was going to suggest, restricting access to the page to all but paid members.
   But I am afraid that when push comes to shove and time to play the game, the 
   links have to be embedded and exposed to the user.
 * You could look into possibly changing the location of the embedded file automatically,
   so that is someone shares the link, the game will only be available through that
   link for a short time. Searching for link/url/file protector or link expiry should
   point you in the right direction.
 * Jay
 *  Plugin Author [Bytephp](https://wordpress.org/support/users/bytephp/)
 * (@bytephp)
 * [8 years, 2 months ago](https://wordpress.org/support/topic/support-documentation-3/#post-10060566)
 * Actually, I just thought of another way that could possibly work to hide the 
   true file location.
 * Instead of embedding the files themselves, you could make an ajax call and run
   a function to verify if the user is indeed a paid member, and if they are, then
   you load the js file content and return it to your gamepage and embed the code
   directly onto the page.
 * Or through the url URI with something like [http://domain.com/gamelink/?game=title](http://domain.com/gamelink/?game=title)
   and have a function doing essentially the same, unregistering the game javascript
   if the player isn’t a paid member
 * In these case, if a non paid user tries to access the link, the function would
   simply not output the javascript and nothing is exposed or playable.
 * These would require some custom coding with php/wordpress to achieve, and is 
   not something ArcadeReady does, but hopefully I have been able to point you in
   the right direction 🙂
 * Jay
    -  This reply was modified 8 years, 2 months ago by [Bytephp](https://wordpress.org/support/users/bytephp/).
 *  Thread Starter [Mr Wood](https://wordpress.org/support/users/mr-wood/)
 * (@mr-wood)
 * [8 years, 2 months ago](https://wordpress.org/support/topic/support-documentation-3/#post-10060634)
 * That’s great thanks for your help, I’ll look into your suggestions. Maybe some
   ideas for future developments of your plugin?
 *  Plugin Author [Bytephp](https://wordpress.org/support/users/bytephp/)
 * (@bytephp)
 * [8 years, 2 months ago](https://wordpress.org/support/topic/support-documentation-3/#post-10061795)
 * Glad I could help. It would not be impossible that I could add this feature, 
   though it is a bit of a special case so it probably won’t be a priority.
 * Jay

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Support documentation’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/arcadeready_abc3c9.svg)
 * [Arcade Ready](https://wordpress.org/plugins/arcadeready/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/arcadeready/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/arcadeready/)
 * [Active Topics](https://wordpress.org/support/plugin/arcadeready/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/arcadeready/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/arcadeready/reviews/)

 * 6 replies
 * 2 participants
 * Last reply from: [Bytephp](https://wordpress.org/support/users/bytephp/)
 * Last activity: [8 years, 2 months ago](https://wordpress.org/support/topic/support-documentation-3/#post-10061795)
 * Status: resolved