← Files Game Development StudioARCHIVED FILE
TERMS.md
3.46 KB · Oct 2, 2026 · 00:31 UTC
# Terms of use Effective: 28 August 2026 Game Development Studio is provided under the MIT license. These terms clarify the responsibilities around its optional provider and project-execution workflows; they do not replace the license. ## Your responsibility You are responsible for: - reviewing commands and dry-run plans before authorizing writes or execution - keeping provider credentials and accounts secure - setting appropriate provider budgets and understanding that local estimates are not invoices - having the right to upload, transform, distribute, and vendor each input or generated asset - checking third-party licenses, provider terms, export rules, and project requirements - validating assets and captures in the actual target game and hardware ## Third-party services and software Tripo, Leonardo, Blender, Apple tools, game engines, and other integrations are independent products governed by their own terms. Their availability, pricing, outputs, and behavior can change. No affiliation or endorsement is implied. ### User-operated provider boundary Optional Tripo and Leonardo routes are user-operated requests to independent third-party services. They are not a publisher-operated provider account, proxy, marketplace, reseller, service bureau, shared-credential service, or generation service for other users. Before enabling a provider route, you must hold and control the applicable provider account, API entitlement or credits, credential, and the rights and permissions required for every submitted prompt, file, model, audio clip, image, or other input. You independently approve each provider request and any associated provider charge. The publisher does not provide, pool, transfer, receive, share, or resell provider credentials or provider access. Do not use another person's credential, use your credential to submit another person's request, or use the software to offer provider generation to third parties. Provider credentials must be configured outside the plugin conversation in a local mechanism the account holder controls. Provider use remains governed by the provider's current account terms, API rules, pricing, content rules, privacy policy, and output-rights rules. Tripo's [API documentation](https://developers.tripo3d.ai/en/docs/quick-start) and [terms](https://www.tripo3d.ai/terms), and Leonardo's [API documentation](https://docs.leonardo.ai/v1.0/docs/getting-started) and [terms](https://leonardo.ai/terms-of-service), are the applicable starting points. Provider outputs are not promised to be exclusive, commercially cleared, privately visible, or fit for a particular purpose. Tripo and Leonardo are independent third-party services and trademarks. No affiliation, sponsorship, endorsement, certification, partnership, or official integration is claimed. ## No production guarantee Static inspection, test fixtures, generated heatmaps, and adapter telemetry are diagnostic aids. They do not guarantee artistic quality, legal clearance, target-engine compatibility, GPU correctness, performance, signing, notarization, or acceptance by a store or reviewer. ## Warranty and liability The MIT license's warranty disclaimer and limitation of liability apply. To the maximum extent permitted by law, you use provider calls, generated content, project commands, and vendored assets at your own risk. ## Changes Material changes will be recorded in repository history with a new effective date. A released plugin version remains reviewable from its tagged source.
SHA-256: 3fc670e4dfd9c3be9fc8af755bd93871b0d3fbce7bfbb7a87bdcde8dcbd4e576