> For the complete documentation index, see [llms.txt](https://wiki.helpch.at/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.helpch.at/glares-plugins/voteparty/changelogs/v2.24.md).

# v2.30

**Features**

* VoteParty Modes
* This update will include a new feature to allow you to modify how partys work. The are now 3 different modes.
* ```
  1) "everyone" - everyone can join the party whether they voted or not
  ```
* ```
  2) "daily" - everyone who voted in the past 24 hours can join the party
  ```
* ```
  3) "party" - everyone who voted in this specific party can join the party
  ```
* The config is defaulted to everyone, as that has been the normal logic of the plugin since we've gotten to this update.
* Players that did not meet the requirements will be sent a message (configurable in the lang file)
* Added a placeholder to get all of the votes of all time on the server (%voteparty\_votes\_total%)
* Added support for 1.18

**Bug Fixes**

* Fixed an issue with disabled worlds not listening properly for crates

**Changes**

* Allow doubles to be used for percent changes in the config


---

# 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://wiki.helpch.at/glares-plugins/voteparty/changelogs/v2.24.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.