> For the complete documentation index, see [llms.txt](https://wiki.redmodding.org/cyberpunk-2077-modding/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.redmodding.org/cyberpunk-2077-modding/modding-guides/quest/how-to-use-worldcommunityregistry-and-worldcompiledcommunity.md). # How to use worldCommunityRegistry and worldCompiledCommunity This page describes how to use worldCompiledCommunityAreaNode and worldCommunityRegistryNode {% hint style="warning" %} This guide explains the theory on how to setup communties, and how they tie into quests For actually creating communities, it is recommended to instead follow the [communities with Object Spawner guide](/cyberpunk-2077-modding/modding-guides/world-editing/ai-and-npcs/creating-communities.md) {% endhint %} ## Summary **Published:** Nov 10 by [Sergey](mailto:undefined)\ Last documented update: Dec 4 by [Sergey](mailto:undefined) ### Wait, this is not what I want! * If you want to learn about [Quests & Scenes](/cyberpunk-2077-modding/modding-guides/quest.md), please check the corresponding section. * If you want to learn about [World Editing](/cyberpunk-2077-modding/modding-guides/world-editing.md), please check the corresponding section. * [NodeRefs](/cyberpunk-2077-modding/for-mod-creators-theory/files-and-what-they-do/file-formats/the-whole-world-.streamingsector/noderefs.md) explained ## Requirements * [ArchiveXL](/cyberpunk-2077-modding/for-mod-creators-theory/core-mods-explained/archivexl.md) 1.17.0+ ## Basics There are two types `worldCompiledCommunityAreaNode` and `worldCompiledCommunityAreaNode_Streamable` The difference between them is only that `worldCompiledCommunityAreaNode` must be registered in `AlwaysLoaded` type of `.streamingsector` `worldCompiledCommunityAreaNode_Streamable` can be registered in other types of `.streamingsector` (exterior/quest/etc) ## Theory Working with `worldCompiledCommunityAreaNode` and `worldCommunityRegistryNode` In general, we are specifying in `worldCompiledCommunityAreaNode` all our spots where we want to spawn NPCs/etc by its `entryName`/`phase`. For example in the quest **Riders on the Storm** CDPR reactivates all needed NPCs by their reference, entry name, and phase name.

Setup your Wkit project. Create `.questphase` `.streamingblock` and `.streamingsector` files

1. Create `archiveXL` file and specify your `.streamingblock` and `.questphase` files

2. Create NodeRefs for `worldAiSpotNode` and `worldCompiledCommunityAreaNode`

3. Create `worldAiSpotNode` and its `worldNodeData` and assign created `NodeRef`before

In the spot property u need to specify workspot that you want to use

4. Create `worldCompiledCommunityAreaNode` and its `worldNodeData`

**Important**:\ \- In the `Node/area/entriesData` we specify an `entryName/phaseName/spotId(AiSpoNodeHash)` so in the future, we can `Activate/Reactivate/Deactivate` its entities by these params\ \- `sourceObjectId` - it should match `id`of registry item 5. Create `worldCommunityRegistryNode` and its `worldNodeData`

Details about the registry: **Important:** `communitiesData` - there are we specifying the type of NPC its template, entryName, and all possible phases

In this example, i set Panam with entryName panam and phase A to be able to activate on the spot we created earlier

`workspotsPersistentData` - there we are adding a new spot into the engine's global registry by the hash of our `AiSpotNode`

Trying to spawn: I set the point in front of H10 V's apartment so we should see Panam spawning once we send a command. To do so we need to create a few nodes in our `.questphase` In our .xl file, we set that`.questphase` will trigger whenever we enter the apartment.

Then you can deactivate/reactive with SpawnManager --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://wiki.redmodding.org/cyberpunk-2077-modding/modding-guides/quest/how-to-use-worldcommunityregistry-and-worldcompiledcommunity.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.