1. Complete descriptions before payment
Each product page states format, curriculum, files, price, access period, support boundary, requirements and material exclusions before ordering. Product buttons open the complete description before any checkout link appears.
2. Versioned technical baseline
Before checkout opens, each technical product will publish:
- the Roblox Studio release, Luau baseline and supporting tools used for testing;
- the last material technical review date;
- known limitations, deprecated examples and device constraints; and
- a dated correction and material-change record.
3. Curriculum standard
- Lessons follow a visible path from core loop to release candidate and update record.
- Code examples explain state, client-server responsibility, dependencies and failure behaviour.
- Tests cover ordinary, invalid, repeated, disconnected and recovery paths where relevant.
- Security, performance, content maturity, asset rights and cross-device input appear before publication.
- No lesson promises moderation approval, discovery, players, income or commercial success.
4. Platform and tool changes
Roblox Studio, Luau, platform APIs and policy change. A verified error affecting the stated baseline will be corrected, replaced or clearly labelled. A later platform change may require an update note or revised lesson rather than silent rewriting. Learners must still check current official documentation before publication.
5. Project and asset integrity
Reference places are tested from clean copies and checked for accidental credentials. Example games use original, unbranded or rights-cleared content and do not copy another creator's experience. Buyers remain responsible for the licence, privacy and security status of assets, packages and services added to their own projects.
6. Technical delivery
Files are supplied in the formats stated on the product page and tested against the published baseline. If a buyer cannot access a purchased item, the Provider will attempt to restore access, provide an equivalent route or apply the Refund Policy.
7. Accessibility
The website supports keyboard navigation, visible focus, responsive layouts, reduced-motion preferences and useful image descriptions. Learning materials aim to use structured documents and captions or transcripts where the product page states they are included. Access needs can be raised before purchase.
8. Corrections and support
Factual errors, broken files and complaints can be reported through the published support contact. The target is an acknowledgement within two business days and a substantive response within five business days, although a complex technical investigation may take longer.
9. Honest portfolio and reviews
A Roblox experience is shown only with a verifiable public link, Pavlo's documented role and a last-checked date. Reviews, ratings, player figures and client claims are published only when their source, permission and current accuracy can be checked. This launch draft uses no invented testimonials or performance metrics.