What the Boilerplate Web Script Includes

The included web script is more than a basic login form. It already provides the foundation for a polished user account system and a product-driven portal.

• User authentication Login, logout, registration, email verification, and password reset flows
• Member dashboard A web portal where signed-in users can access their products and downloads
• Product system Create digital products, assign SKUs, pricing, imagery, and descriptions
• Downloads by product Attach files or downloadable assets to individual product SKUs
• Storefront pages Public-facing store pages that list active purchasable products
• API key management Create and rotate project API keys used by the launcher integration
• Access control Role and product-based access checks for launcher logic and gated areas
• Branding and Stripe settings Configure your logo, titles, emails, and payment details from the admin area

Before You Upload Anything

Before starting, make sure you have a standard PHP hosting environment and a domain or subfolder ready. Most users place the script in a dedicated folder such as:

You can also use a subdomain if you prefer a cleaner separation, such as:

Step 1: Upload the Files to Your Hosting

Upload the entire web script package to your chosen folder or subdomain. Keep the folder structure intact. Do not cherry-pick only the pages you recognize. The boilerplate relies on multiple admin pages, public pages, API routes, and shared application files working together.

Recommended upload method

• Use your hosting file manager for a quick setup.
• Use FTP or SFTP if you prefer desktop deployment.
• Use Git deployment if you are a developer and want version control.

Once uploaded, visit the folder in your browser. If the script is installed correctly, you should be able to access the public entry pages such as the home area and store area.

Step 2: Complete the Initial Configuration

Out of the box, the script is designed to be configurable from the admin area. From the files provided, the admin settings include global site, branding, security, and Stripe configuration sections.

The most important settings to configure first

Step 3: Configure Email Delivery

The script supports account verification and password reset flows, which means email delivery matters. If email sending is not configured properly, registrations may succeed but users will not receive their verification or reset emails.

For a basic internal test, a simple mail transport may be enough. For production, a proper SMTP provider is the safer choice.

When email is used

• New user email verification codes
• Resent verification requests
• Forgot password and reset flows
• Potential future account-related messaging

Step 4: Create Your First API Key

The launcher side needs credentials to talk to your hosted web script. The admin area includes an API Key manager that lets you create project-specific keys and rotate them later when needed.

Recommended workflow

1. Create a new API key in the admin panel for your launcher project.
2. Give it a clear project name so you know which launcher it belongs to later.
3. Copy the generated key details and keep them safe.
4. Use those details when configuring the Launcher Login Plugin inside the editor.

This is the bridge between your web script and your launcher. Without it, the launcher has no trusted way to identify the target project connection.

Step 5: Create Products

The product system is what turns your script from a login panel into a proper delivery platform. Products are used for storefront listings, user ownership checks, and download assignment.

What a product can represent

• A full launcher-enabled game
• A premium edition or founder pack
• Downloadable DLC or expansion content
• A support tier or member pass
• A tool, plugin, or utility download

Recommended product fields

Step 6: Create Memberships and Access Rules

From the API and access-related files provided, the script supports role and product-based access checks. In practical terms, this means you can assign users access through ownership and membership-style structures.

Two common ways to treat memberships

• Product membership: A user buys a product such as a pass, subscription-style access item, or member package.
• Role membership: A user is assigned a role such as member, vip, beta_tester, or staff.

Both approaches can work well. For many creators, products are easier to understand because they map directly to the store. For more advanced projects, roles are excellent for internal access control and special permissions.

Good use cases for memberships

• Premium support areas
• Alpha and beta access groups
• Monthly content packs
• VIP launcher themes or plugins
• Private game server access

Once your membership or access logic exists in the script, the launcher can react to it through product checks, role checks, and access checks using the editor plugin configuration.

Step 7: Attach Downloads to Products

The dashboard and API are already built to return downloads grouped by product. That means once a user owns a product, the system can expose the relevant download entries to both the web portal and the launcher.

Typical download examples

• Main installer package
• Patch zip or launcher bootstrapper
• Premium content pack
• Documentation PDF or bonus asset pack
• Platform-specific build downloads

When the user logs into the web portal, they can see the products attached to their account and any downloads assigned to those products. When the launcher logs in through the plugin, it can retrieve that same entitlement picture and build logic around it.

Step 8: Sell Products Through the Storefront

The included store page is built to display active products that have a valid price. That gives you a ready-made front-end starting point for selling digital goods from your own server.

What the storefront does

• Lists active products in a public grid layout
• Displays product image, name, short description, and price
• Links users into product detail and purchase flow
• Works with the Stripe settings configured in admin

Stripe setup checklist

• Choose test mode or live mode in settings
• Enter your publishable key and secret key
• Set your currency code
• Add your webhook signing secret
• Test a product purchase before going live

How This Relates to the Launcher

Once the web script is live, configured, and holding real products and users, the launcher can start behaving like a connected account platform rather than a static front-end.

The relationship is simple

• The web script stores users, products, access, and downloads
• The Launcher Login Plugin connects your launcher to that data
• The launcher UI reacts based on who the user is and what they own

For example, your launcher could:

• Show a premium page only if the user owns a certain product
• Display a download panel for entitled files
• Block non-members from accessing certain features
• Skip manual login if a valid session already exists

That is exactly where the Launcher Login Plugin documentation comes in next.

Recommended First-Day Setup Path

Advice for Developers and Power Users

If you are more technical, this boilerplate gives you a very solid base to extend. The provided files show separate API endpoints for authentication, user profile data, access checks, and admin operations. That makes it practical to:

• Integrate with your existing frontend branding
• Expand the dashboard pages
• Add more product metadata
• Implement your own access conventions
• Build additional internal tools around the admin APIs
• Separate staging and production environments cleanly

The main win is speed. Instead of building account logic, purchase logic, download entitlement logic, and launcher connectivity from scratch, you start with a working platform and tailor it to your own business model.

Common Beginner Questions

Do I need to sell products through the built-in store?

No. You can use the boilerplate purely as a login and entitlement system if you want. The storefront is included as a convenience, not a requirement.

Can I create free products?

Yes. A product can still be useful for ownership, downloads, and launcher logic even if it is not sold publicly at a price.

Can I use this for memberships instead of simple products?

Yes. Many creators treat products or roles as memberships, passes, tiers, or entitlements. The important part is how you model access for your project.

Do I need coding knowledge to get started?

No, not for the basic setup. A beginner can upload the files, configure branding and URLs, create a product, and test login flow. Developers can then take it much further if needed.

Summary

The Launcher Login Web Script is the hosted backbone for your account-driven launcher ecosystem. It gives you a practical starting point for user accounts, verification, password recovery, API keys, store products, memberships, downloads, and customer delivery from your own server.

For beginners, the simplest route is to upload it, configure the basics, create one product, attach one download, and test one user. For professionals, it is a clean platform to extend into a much larger product and access system.