> For the complete documentation index, see [llms.txt](https://docs.velorarp.dk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.velorarp.dk/documentation/spillerguide/ny-spiller-guide.md).

# Ny spiller-guide

Lær de vigtigste rolleplay-begreber, før du går i gang.

### Opret din karakter

Giv din karakter et navn, en baggrund og klare mål. Lad karakterens handlinger passe til den historie.

Start enkelt. Nye relationer og oplevelser skaber bedre historier end en færdig, fejlfri baggrund.

### IC og OOC

**In character (IC)** er alt, din karakter ved og gør. **Out of character (OOC)** er kommunikation mellem spillere.

Hold de to adskilt. Brug ikke Discord, streams eller anden ekstern viden i en IC-situation.

### Konflikter

Giv modparten tid til at svare. Byg spænding gennem dialog og handlinger.

* Spil konsekvenserne af dine valg.
* Prioritér scenen frem for at vinde den.
* Fortsæt ikke en konflikt efter den er afsluttet.

### Når en scene går galt

Undgå at diskutere regler midt i rp. Afslut situationen roligt, gem dokumentation og kontakt staff bagefter.


---

# 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://docs.velorarp.dk/documentation/spillerguide/ny-spiller-guide.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.