Games & code sample
For an initial review, start with a 2–5 minute gameplay clip or store link, a repository summary and build evidence. If development history was requested, add a few agreed weeks of changes and the records explaining them.
What to collect
- Game and build
- Show the core mechanic. Give the engine and version, language, platform, build target, clean-build result and available automated tests.
- Repository summary
- Report development duration, commit or changelist count, PR count where applicable, and first-party code size. Count third-party engine code, SDKs and plugins separately.
- A change you can trace
- Where requested, include the task description, comments, status changes, design notes, diff and review for the same change. Use consistent author aliases across exports.
- Rights and dependencies
- Explain which code, assets and history the studio controls and whether the proposed scope is evaluation, training, non-exclusive licensing or an IP sale. Identify the owner who can approve the deal. Give an indicative price or preferred structure if requested, and flag unresolved rights.
Omit credentials, player records and third-party code or assets without clearance. Provide a full runnable build or repository only when the agreed scope calls for it.
Export from your systems
Pack and check
Put the README and manifest at the top of the folder, with a subfolder for each system. The manifest is a file index a reviewer can read without opening every file.
Download blank manifest (.csv) ↓Example manifest entry
- File in the package
history/change-042.patch- Matching key
revision = 042- Related record
- tasks/GAME-18.json names revision 042
Includes all systems for this sample type and your current checks.
Share through your private workspace.
Once Maryah confirms the scope and permission to share, open the matching dataset and choose Samples. Follow the size and format limits shown there.
Open my datasetsFor a larger package or help locating your dataset, contact Maryah for a private transfer route. Include your dataset reference and file size.