> For the complete documentation index, see [llms.txt](https://hellstreet.gitbook.io/hellstreet-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hellstreet.gitbook.io/hellstreet-docs/introduction/what-is-hellstreet-create-hsc.md).

# 🛠️ What is HellStreet Create (HSC)

<figure><img src="/files/rtf6me6JS2QSazHVxRTc" alt=""><figcaption></figcaption></figure>

HS Create is the hands-on creator platform and live publishing ecosystem that powers HellStreet’s world-building, showcases, and creator economy. It’s where ideas become playable spaces: creators design scenes, manage assets, stage events, and push finished worlds into HellStreet’s Exchange and live hubs. Think Dream. Create. Play. — the exact promise you see on the HSC site — made real with practical tooling, collaboration features, and a polished publish pipeline.

{% hint style="info" %}
Below is a thorough, documentation-level breakdown of HSC purpose, core capabilities, typical workflows, and how creators and teams interact with it
{% endhint %}

***

<figure><img src="/files/qGIAjdcGmwJxINTGrzrb" alt=""><figcaption></figcaption></figure>

***

#### Core identity & positioning 🎯 <a href="#core-identity-and-positioning" id="core-identity-and-positioning"></a>

* **What it is:** HSC is an integrated open-world sandbox & authoring platform aimed at creators of all skill levels — from hobbyists to professional studios. It combines a visual editor, an asset vault, staging/publish pipelines, and community-facing discovery (Showcase / Worlds).
* **Where it sits:** HSC is the visible creation layer of HellStreet — not a hidden backend — and it’s the primary place creators spend time designing, testing, and shipping experiences.
* **Current state:** Helstreet Create is in closed alpha (waitlist + Discord prioritization), with public docs and a growing showcase of pilot worlds and trailers on the official site. (See the HellStreet Create homepage for the waitlist and showcase visuals.)

***

<figure><img src="/files/9WIvUA4Lyltw47yrWjpL" alt=""><figcaption></figcaption></figure>

***

#### Primary capabilities (what HSC gives you) 🛠️ <a href="#primary-capabilities-what-hsc-gives-you" id="primary-capabilities-what-hsc-gives-you"></a>

```
Visual World Editor
```

Drag-and-drop scene assembly with modular tiles, prefab props, and editable gameplay objects (triggers, spawners, NPC controllers). Node-based logic / visual scripting for non-coders (timers, event triggers, simple AI flows) plus an advanced scripting hook for studios. Preview & test mode: quick local playtests and multi-user staging for small groups.

***

```
Vault & Asset Management
```

Centralized vault for assets (models, textures, animations, audio) with versioning, descriptive metadata, and lineage tracking so teams can reuse and iterate without losing history. Permission controls for team collaboration (owner / editor / contributor roles) and a lightweight content review flow.

***

```
Publish Pipeline & Staging
```

One-click package → staging → QA → publish. Packages include metadata (title, description, tags), preview media (thumbnail, 10–30s trailer), royalty settings, and optional monetization hooks (access passes, per-session fees). Automated validation checks: file size limits, polycount budgets, animation loops, and metadata completeness to reduce broken uploads and marketplace friction.

***

<figure><img src="/files/7BmHYkoxRAFSPdgqvK7C" alt=""><figcaption></figcaption></figure>

***

```
Monetization Primitives
```

Built-in hooks for access passes, per-session fees, in-world vendors, and revenue-split configuration (creator ↔ landowner ↔ platform). Creators can declare royalty splits and item pricing at publish time. Support for minting drops and attaching NFTs (ERC-721 / ERC-1155 style flows) to in-world items or access tokens.

***

```
Creator Analytics & Iteration Tools
```

Heatmaps, session funnels, retention cohorts, and revenue dashboards that reveal how players move through a world, where they drop off, and which assets generate sales. A/B testing support for different entrance flows, pricing, or layout variations to improve engagement and monetization.

***

```
Showcase & Community Discovery
```

Curated Showcase pages where standout worlds are featured with trailers and editorial blurbs; creators can submit for spotlight consideration. Integration with community channels (Discord) and waitlist/early access programs to build early audiences.

***

<figure><img src="/files/7yCl8NeZAHXgMQancYLf" alt=""><figcaption></figcaption></figure>

***

#### Typical creator workflow (practical) 🚧 <a href="#typical-creator-workflow-practical" id="typical-creator-workflow-practical"></a>

**Prototype:** Build a small playable loop in the visual editor using prefabs and logic nodes. **Vault & iterate:** Save assets to the Vault, version them, and invite collaborators. **Stage:** Push to staging for multi-user QA (invite testers, run playtests, gather heatmaps). **Publish:** Configure metadata, pricing/royalties, attach preview media, and publish to the Exchange / Showcase. **Operate & iterate:** Monitor analytics, release hotfixes, and run events (ticketed shows, timed drops).

*This loop allows creators to ship quickly, learn from real usage data, and monetize without building custom infra.*

***

#### Who HS Create is for (audience) 👥 <a href="#who-hs-create-is-for-audience" id="who-hs-create-is-for-audience"></a>

**Indie creators & hobbyists** who want powerful visual tooling without writing engine code. **Small studios** that need rapid iteration, staging, and analytics to polish live experiences. **Large teams / partners** that require asset lineage, access controls, and white-glove publishing support. **Event producers & brands** that want to run ticketed or branded experiences inside HellStreet.

***

<figure><img src="/files/0FLoeRDHfswJwHxs7fxL" alt=""><figcaption></figcaption></figure>

***

#### Collaboration & governance ✍️ <a href="#collaboration-and-governance" id="collaboration-and-governance"></a>

Team roles and permissioning in HSC let creators collaborate safely; grant programs and spotlight opportunities surface high-quality work. Submission and curation flows feed the Showcase — community engagement (Discord activity, referrals) can influence waitlist priority and promotional placement.

***

#### Safety, QA & policy checks ⚖️ <a href="#safety-qa-and-policy-checks" id="safety-qa-and-policy-checks"></a>

HSC's publish pipeline includes automated content checks (copyright flags, NSFW scanning, metadata validation) plus human moderation for contested claims. Marketplace publish rules enforce clear IP declarations and royalty settings; disputes follow a documented support & appeals process.

***

<figure><img src="/files/tPalufgR4U3sND4syM4D" alt=""><figcaption></figcaption></figure>

***

#### How HSC ties to HellStreet’s economy & live worlds 🔗 <a href="#how-hsc-ties-to-hellstreets-economy-and-live-worlds" id="how-hsc-ties-to-hellstreets-economy-and-live-worlds"></a>

Worlds built in HSC publish directly to HellStreet’s live hubs and Exchange. Items and passes created in HSC carry metadata and provenance that connect to on-chain receipts or internal ownership records. HellStreet Create exposes monetization primitives so creators can sell access, list items, or set up rent/lease models for LAND holders — allowing a single authoring environment to feed the broader HellStreet economy.

***

#### Access, docs & community (how to get started) 🚪 <a href="#access-docs-and-community-how-to-get-started" id="access-docs-and-community-how-to-get-started"></a>

**Closed alpha / waitlist:** sign up on the HSC homepage to request early access; active community participation (Discord) helps move you up the list. **Docs & tutorials:** official docs include editor walkthroughs, metadata schemas, asset guidelines, and publishing checklists — review them before your first publish. **Showcase & examples:** watch trailers and sample worlds for design inspiration and to understand the platform’s production values.

***

<figure><img src="/files/JbGPZfN4JBWl6qCrtnXN" alt=""><figcaption></figcaption></figure>

***

#### Practical tips & best practices ✅ <a href="#practical-tips-and-best-practices" id="practical-tips-and-best-practices"></a>

* Start small: ship a 3–5 minute playable loop before building out large areas.
* Use the Vault’s versioning: it saves time and prevents regressions during iteration.
* Add clear metadata and a short trailer — worlds with good previews convert better in the Exchange.
* Monitor heatmaps after publish and prioritize fixes for high-traffic choke points.

***

#### Why HS Create matters for HellStreet 🌟 <a href="#why-hs-create-matters-for-hellstreet" id="why-hs-create-matters-for-hellstreet"></a>

HSC is the creator engine of HellStreet: the place where community imagination turns into playable worlds, and where creators have the tools to iterate, publish, and earn. By combining approachable visual tools, rigorous staging/publish flows, and integrated monetization & analytics, HSC makes it practical for anyone to become a world-builder — and gives HellStreet a steady pipeline of fresh, discoverable experiences.

***

<figure><img src="/files/b7sAic6XMrs3cccyrHsh" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://hellstreet.gitbook.io/hellstreet-docs/introduction/what-is-hellstreet-create-hsc.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.