> For the complete documentation index, see [llms.txt](https://ss3d.gitbook.io/dev-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ss3d.gitbook.io/dev-guide/guidelines/the-c-style-guide/nomenclature/methods.md).

# Methods

Methods are written in **PascalCase**. For example <mark style="color:green;">`DoSomething`</mark>`()`.

<details>

<summary>Methods that are used as the <mark style="color:blue;">OnChange</mark> callback of a [<mark style="color:purple;">SyncVar</mark>]</summary>

Should have the **`Sync`** prefix, as in:

```
[SyncVar(OnChange = nameof(SyncUsername))] string _username;
```

```
private void SyncUsername(string oldUsername, string newUsername, bool asServer) {}
```

</details>

<details>

<summary>Methods that listen to an <mark style="color:blue;">event</mark></summary>

Should have the prefix Handle, as in:

```
clownBomb.OnExploded += HandleClownBombExploded;
```

```
private void HandleClownBombExploded() 
{
    Honk();
}
```

</details>

<details>

<summary>Methods that are preceded by the [<mark style="color:purple;">Server</mark>] attribute</summary>

Do not need to have the `Server` prefix on them. This is still something we are thinking about, both uses are fine for now.

As in:

```
[Server]
public void ServerKillPlayer() {}
[Server]
public void KillPlayer() {}
```

</details>

<details>

<summary>Methods that are preceded by the [<mark style="color:purple;">ServerRpc</mark>] attribute</summary>

Need to have the `Cmd` prefix on them, as in:

```
[ServerRpc]
public void CmdSpawnItem(GameItems item) 
{
    SpawnItem(item);
}
```

</details>

<details>

<summary>Methods that are preceded by the [<mark style="color:purple;">ObserversRpc</mark>] attribute</summary>

Need to have the `Rpc` prefix on them, as in:

```
[ObserversRpc]
private void RpcSpawnVisualProjectives() 
{
   _particleSystem.Play();   
}
```

</details>


---

# 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://ss3d.gitbook.io/dev-guide/guidelines/the-c-style-guide/nomenclature/methods.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.