Launcher Login - Quick Start
Launcher Login Web Script Quick Start in 10 Minutes
This page is the fastest route from “I’ve got the files” to “my account system is live and talking to my launcher”. The web script gives you a ready-made base for user accounts, products, memberships, downloads, access checks, API keys, and storefront sales from your own server.
Once this is configured, you can connect it to your launcher through the Launcher Login Plugin and start building a proper account-driven Custom Launcher experience.
This is the short version for getting up and running quickly. For the fuller walkthrough, setup concepts, storefront ideas, and product structure guidance, refer to the main Launcher Login Web Script tutorial page.
What You Will Have by the End
- A live account system Users can register, verify, sign in, and reset passwords
- One API key Ready to paste into the launcher login configuration
- One product A clean SKU and product entry inside the admin area
- One download Assigned to that product and available to entitled users
- A verified test user Able to log in and access the product
- A working launcher connection Your launcher can authenticate against your own hosted system
What Ships Out of the Box
The boilerplate already includes the major building blocks you need. You are not starting from a blank login form and a prayer.
| Included Area | What it does |
|---|---|
| Auth | Login, register, verify, resend verification, forgot password, reset password |
| Users | Create, search, edit, verify, lock, manage grants |
| Roles | Membership-style access groups and permission layers |
| Products | Store items, ownership records, SKU-based product access |
| Downloads | Attach downloadable items to products and expose them to entitled users |
| API Keys | Create and rotate project credentials for launcher connections |
| Access Checks | Validate whether a user has a role, product, or specific access entitlement |
| Storefront | Public product listing pages for front-end sales |
1. Install the Script
Installation Placeholder
Replace this section with your final install instructions later.
Suggested topics to cover here:
- Uploading the package to hosting
- Database creation and credentials
- Any setup wizard or bootstrap steps
- Folder permissions if needed
- Admin login creation
- Recommended HTTPS setup
Do not publish your production system until installation, database setup, and HTTPS are fully complete. Account systems are not the place for cowboy deployment habits.
2. Configure the Basics
Once installed, head straight to the admin settings and fill in the basics first. This gets the project into a usable state fast.
| Set This First | Why |
|---|---|
| Base URL | This tells the system what its own public address is |
| Admin email | Used for ownership and core contact identity |
| Support email | Shown to users for help and account contact |
| Branding | Sets your logo, titles, and overall identity |
| Email verification | Choose whether new users must verify before full access |
Quick Win
Do not get lost tweaking advanced settings immediately. For a first launch, correct URLs, working email delivery, and one valid API key matter far more than polishing every admin option.
3. Create an API Key
Your launcher needs a trusted project key so it can communicate with your hosted login system. The admin area includes API key creation and rotation support out of the box.
- Open the API Keys area in admin.
- Create a new key for your launcher project.
- Give it a clear project name.
- Copy the generated key details and store them safely.
This will later be entered into the Launcher Login Plugin configuration in the editor.
If you ever need to replace a key later, the system supports rotation. That is a lovely feature when you want good security without the usual “burn the whole house down and rebuild it” routine.
4. Create One Test Product
Products are the backbone of ownership, store listings, entitlement checks, and download assignment. Even if you are not selling through the storefront yet, create one test product now.
Recommended test product
| Field | Example |
|---|---|
| SKU | STARTER_PACK |
| Name | Starter Pack |
| Price | Optional for testing |
| Status | Active |
Keep the SKU short, clean, and permanent. Your launcher logic can later use product SKUs for ownership and access checks.
5. Create One Download and Assign It
Downloads are managed separately and then assigned to products. This is a smart structure because one product can have one or many downloadable items, and user access remains entitlement-driven.
- Create a new download entry.
- Enter a name and file URL.
- Set the status to active.
- Assign that download to your test product.
Example
- Download Name: Windows Installer
- File URL: Your hosted installer URL
- Assigned Product:
STARTER_PACK
Once a user owns the linked product, this download becomes available to them in both the account portal and the launcher-side entitlement flow.
6. Create a Test User
Now make a real test account so you can validate the whole loop from sign-up to access.
Fastest route
- Create a user manually in the admin area
- Or register through the public account flow
- Verify the account if verification is enabled
- Grant the user your test product
The user management area supports manual verification, lock states, and individual grant control. That makes testing much easier while you are still building out your project.
7. Test the Portal
Before touching the launcher, test the hosted portal directly in the browser.
- Sign in with your test user
- Confirm the account works
- Confirm the product is attached to the user
- Confirm the assigned download appears
- Confirm password reset and verification flow if needed
This step saves time. If the web side is wrong, the launcher side will only reflect that problem more dramatically and with more swearing.
8. Connect the Launcher
Now you are ready to connect the hosted system to your launcher project.
- Add the Launcher Login object to your launcher project
- Enter the Base URL of your hosted script
- Enter the API Key you created earlier
- Keep the default endpoint paths unless you have customized your hosted script
From there, your launcher can sign users in, refresh ownership, check roles, check products, and retrieve download data using the secure project connection you configured.
For the full editor-side configuration, mapped variables, object events, and launcher actions, see the Launcher Login Plugin documentation.
9. Optional: Create a Membership Role
If you want more than plain product ownership, create a role such as member, vip, or beta_tester. This is a great way to build private areas, early access groups, or internal staff privileges.
A good fast setup is:
- Create a role named vip
- Grant it to your test user
- Use role checks in your launcher logic later
This gives you both product-based access and role-based access, which is a very flexible combination for a Custom Game Launcher.
10. Optional: Turn On Storefront Sales
If you want to sell products directly from the included front-end store, configure your payment settings and mark your products as active with valid pricing. You MUST ensure you do lots of testing in "Test Mode" with Stripe before going to LIVE as you want to ensure everything works accordingly before publishing your products for sale.
Storefront checklist
- Configure your payment provider settings
- Set your currency
- Create a product with a visible price
- Make sure the product is active
- Test the purchase flow before going live
You can also skip this entirely and use the system purely for login, account management, ownership, memberships, and download delivery.
10 Minute Checklist
- Install the script
- Set base URL and branding
- Create an API key
- Create one test product
- Create one test download
- Assign the download to the product
- Create or register one test user
- Grant the product to that user
- Verify the portal works
- Connect the launcher
What Happens Behind the Scenes
Here is a quick breif:
- The hosted script manages users, products, roles, downloads, and access
- Your launcher securely connects to that hosted project
- The launcher reacts based on the current user and their entitlements
That means you can think of it like this: the web script is the account brain, and the launcher is the polished front-end experience.
That is all you need to understand to start building with confidence, while the deeper platform internals remain safely under the hood where they belong.
We recommend following the video tutorial also.
After this, we recommend that you just simply "Trial and Error" by liaising back and forth with the documentation provided here on this site.
You can get support via Discord if needs be, but we recommend working through the documentation first.
Note: Any issues serverside, we may not be able to help with as they're not our servers so you would need to liaise with your website provider or server provider if you run into serious issues as we have no control over the servers and their technologies.
Summary
The fastest path is simple: install the script, configure the basics, create an API key, add one product, add one download, make one user, test the portal, then connect your launcher. That gives you a live foundation for accounts, memberships, ownership, downloads, and store-ready product delivery.
Once this quick start is complete, move on to the Launcher Login Plugin documentation to wire the hosted system into your launcher project.