# Commands

### **/pointlogs \<user> \<keyword>**

You will use this to check what their points was spent on, keywords pat(patreon), add(to see added points by staff), rec(points that were gifted by another player), gift(points that the player gifted to others), tra(check how many points they received when transferring their fossils)

### **/fossillogs \<user> \<keyword>**

You will use this to see the logs on their fossils, keywords would be add(to check fossils added by staff), que(fossils received for completing quest), mig(fossils received for completing migrations), tra(check how many fossils were transferred to points), pas(this will show you their fossils they’ve earned passively)

### **!addpoints \<user @ or discord ID> \<x>**

Use this points when you are adding points for patreons, events, or refunds. Be sure to only do this in tickets or when approved.&#x20;

### **!addmanypoints \<user @ or discord ID> \<x>**&#x20;

Same as addpoints except you can do multiple users; generally what you would use when paying out placements in events.&#x20;

### **!addfossils \<x>**

You would generally do this to refund lost quests or migration fossils.

### **!addmanyfossils <@ or discord ID> \<x>**

Same as addfossils but multiple users; this would likely rarely be used other than select events that rewards fossils rather than points.&#x20;

### **!rmsteam \<steam ID>**

Use this when a player wants their steam unlinked from the discord, you may need to transfer points and fossils over.

### **/patreon**

Tell users to use this command if they lost their patreon role but are linked. It should give them the role back.


---

# Agent Instructions: 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:

```
GET https://staffdocs.zoomingislander.lol/mod-guide/ticket-training-1/commands.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.