> 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/for-mod-creators-theory/files-and-what-they-do/crowds-random-npcs.md).

# Crowds: random NPCs

Crowd generation,  and how to influence it

Inside the communityTemplate, this file defines appearances for **crowd pools:**

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-79de7cc9cb95c054459fae22b866f9ea855f5d2b%2Fcrowd_community_file_explained.png?alt=media" alt=""><figcaption></figcaption></figure>

## How can I find a specific file?

You can use `Find Files Using This` from the context menu of the corresponding .app or .ent file and follow the daisy chain until you find the .community file.

(as of October 02 2032, this is still broken)

#### Is there another way?

As of 8., Wolvenkit only lets you search **for** files, not **in** them. For that reason, we'll have to use a workaround.

{% hint style="info" %}
I have completed step 1 -3 for you and put the results on my [Mega](https://mega.nz/file/2QNmkIba#xAKtk0uM1ya0dJpY85wPRvNpb5k1anLBeRaYw6o7QDM).
{% endhint %}

1. add [all `.community` files](https://wiki.redmodding.org/wolvenkit/wolvenkit-app/usage/wolvenkit-search-finding-files) to your project
2. [export them to json](https://wiki.redmodding.org/wolvenkit/wolvenkit-app/usage/import-export/import-export-as-json#export-as-json)
3. Delete the original .community files (you'll re-add them later)
4. Use Notepad++ to search inside the directory for your appearance name
   * If nothing shows up, try partial matches
5. Note the names of the files under `.raw`
6. search for the file name in Wolvenkit, then add it back and make your edits

## How can I change a spawn?


---

# 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/for-mod-creators-theory/files-and-what-they-do/crowds-random-npcs.md?ask=<question>&goal=<user_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.