> For the complete documentation index, see [llms.txt](https://oprp.gitbook.io/staff-handbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://oprp.gitbook.io/staff-handbook/staff-guidelines/staff-activity.md).
# Staff Activity
{% hint style="info" %}
### Information
This page highlights the staff quota depending on ranks and other important activity information.
{% endhint %}
As a staff member, you are expected to be active in-game and in the Discord server.\
Ontario Provincial Roleplay has a strict requirement of 50 messages per week for all staff. The following are items that contribute to this count:
* Text messages in any channel
* Images in any channel
* Bot commands in any channel
You are also expected to engage in conversations regularly and involve yourself in the community.\
Although we don't yet have a quota for in-game activity, you should still make an attempt to involve yourself in game sessions. We won't punish you for this unless you've tried to attend less than 2 sessions in a month.
Staff Checks happen once a week, and inactive staff members are punished according to the table below. The Director is the only person to do staff checks as of right now. This may change once more ranks are filled.
Inactivity Strikes
The base punishment for any kind of inactivity (failing to react to a staff check or failing the quota) is a strike.
You may receive a maximum of 2 inactivity strikes per month, 4 per 2 months, and 6 per 4 months.\
These strikes will expire 2 weeks after inactivity stops, and a 2 week promotion freeze will be applied with each infraction.
Inactivity Demotions
If you receive too many inactivity strikes, you will be demoted. Inactivity demotions set you back 1 rank.
You may receive a maximum of 1 inactivity demotions per 2 months and 2 per 4 months.
Inactivity Terminations
If you receive too many inactivity demotions, you will be terminated. Your rank is irrelevant when deciding to terminate. To be terminated, you will have to be extremely inactive throughout the server.
Sometimes, you will be unable to complete your mod duties. When this happens, an LoA is a good idea. LoA stands for 'Leave of Absence', and it is a term used to reference a temporary leave from server duties.\
All staff are allowed to take a maximum of 2 weeks off, or up to 6 with approval from the ***Directorate Team***. If you are requesting a leave longer than 6 weeks, it will be denied. Your LoA might be denied for one of these reasons:
* You're requesting LoA's too quickly
* Your LoA is too long
* Your LoA is for an invalid reason
* You are requesting LoA as a result of a punishment
Your LoA might also be denied for one of the reasons not listed above. To request an LoA, run the **/leave request** command in [#staff-commands](https://discord.com/channels/1204208655508176926/1204208658892857394). Please do not ask an HR to review your request once it's submitted.
---
# 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://oprp.gitbook.io/staff-handbook/staff-guidelines/staff-activity.md?ask=&goal=
```
`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.