Skip to content

Commit dfff31d

Browse files
authored
Update and rename battle.txt to battle.md
1 parent c164ae2 commit dfff31d

File tree

2 files changed

+36
-0
lines changed

2 files changed

+36
-0
lines changed

topics/battle.md

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
# Battle
2+
3+
> A simple but exciting fun game for you to play with your friends.
4+
5+
## About
6+
7+
Except server management, we also provide a small amount of fun commands. You can set them up in your server to increase diversity of events.
8+
9+
## Quick Setup
10+
11+
Pretty easy, you just need to setup:
12+
13+
- Manager Role (optional): Basically event manager. They can start and clear a game without fulfilling the `Manage Guild` default permission requirement, they can also participate in a game.
14+
- Game Channel (required): People cannot play this game outside of this channel.
15+
- Access Role (required): Participants will be granted this role to access the game channel.
16+
17+
Don't forget to configure permission overwrites in the game channel properly.
18+
19+
```py
20+
View Channel Send Messages
21+
Default true false
22+
Manager Role true true
23+
Access Role true true
24+
```
25+
26+
## Start a new game
27+
28+
You can start a game with `[p]battle start` and tell your friends how to play by showing the `[p]battle` embed. Each game cannot have less than 2 participants or have more than 30 participants. Access role will be assigned after starting a new game and channel permission overwrites will also be changed, both will be done automatically.
29+
30+
## Cancel or clear a game
31+
32+
You can cancel a currently active game or clear a previously ended game by running `[p]battle clear`, access role will not be removed automatically if you suddenly cancel a currently active game.
33+
34+
## Relevant Commands
35+
36+
- [battle](/traditional-commands/fun/battle/battle.md)

topics/battle.txt

Whitespace-only changes.

0 commit comments

Comments
 (0)