Client source and modules
A separately maintained client repository with configuration, layouts, modules, interface systems and operator-controlled branding.
EVOMANIAS / CREATOR COLLECTION
Complete Client, Launcher, and Distribution Package
Own the entire player delivery experience.
A separate client-side package valued at $2,997: client source and modules, branded launcher workflow, release manifests, CDN distribution planning, staging and production channels, configuration guidance and operator manuals.
$2,997 standalone value
Source-oriented packagesStripe & PayPalManual, reviewed deliveryNo player data included
WHAT YOU CAN BUILD
Own the entire player delivery experience.
- 01Client source, modules, layouts and interface systems
- 02Launcher, manifest, patch and CDN distribution workflow
- 03Staging and production repository guide with operating manuals
SYSTEMS & RESPONSIBILITIES
The client delivery system, end to end.
Launcher workflow
Package a player-facing launcher, define the supported client baseline and direct players to approved release artifacts.
Manifest and patch channel
Version metadata, package checksums and direct-to-current upgrade paths support controlled client updates.
CDN distribution
Publish immutable versioned files to your own distribution origin while the website and launcher consume current metadata.
Environment lanes
Local development, staging acceptance and production releases keep different hosts, credentials and update channels.
Release verification
Confirm build output, signatures, manifests, public files and an actual fresh-client launch as separate evidence.
INSIDE THE PACKAGE
440 eligible source files auditedExplore the file structure
Selected filenames from the local source audit. Counts describe eligible files in reviewed folders, not a guaranteed delivery manifest. Full source and binaries are withheld from public previews.
Client application / evomanias.local.lua
CURATED SOURCE PREVIEW
evomanias.local.lua
A separate client-side package valued at $2,997: client source and modules, branded launcher workflow, release manifests, CDN distribution planning, staging and production channels, configuration guidance and operator manuals.
- Client source, modules, layouts and interface systems
- Launcher, manifest, patch and CDN distribution workflow
- Staging and production repository guide with operating manuals
Filename preview only. Implementation, complete scripts, map data and configuration values are not published here.
DELIVERY WORKFLOW
From repository to production.
Each checkpoint has a different purpose. A successful build, a published client artifact and a live server promotion are recorded and verified separately.
- 01
Clone the client into its own repository or protected workspace.
- 02
Set server endpoints, protocol, branding and asset paths for local development.
- 03
Build the Windows client and launcher, then test from a clean installation.
- 04
Publish a staging manifest and test every supported upgrade path.
- 05
Sign approved artifacts, upload versioned files to the CDN and update production metadata.
- 06
Verify download, checksum, patching, login and rollback behavior before announcement.
INCLUDED DOCUMENTATION
Guides for getting up and running.
Documentation is delivered with the approved package and tailored to the agreed environment and compatibility scope.
PLAN YOUR INTEGRATION
A clear path from files to staging.
These are source packages for technical operators. Compatibility, included dependencies and redistribution rights are confirmed for your project. Instant downloads and universal engine compatibility are not promised.
- Compatible Windows build environment and protocol
- Your own code-signing, hosting and CDN accounts
- Asset redistribution, opcode and release-channel review
- Confirm scope and licensing before manual delivery.
- Validate loading, progression and payment flows in staging before launch.
Get Complete Client, Launcher, and Distribution Package
One-time package purchase in USD. Manual delivery follows compatibility and licensing review. Your own hosting, provider fees and ongoing operation are separate.
Source previews are not downloads. Private credentials, player records and live payment data are excluded. Automation tooling requires permission for the target environment; executable builds and activation-key services require an agreed scope.