(Added page to Legacy category) |
m (Text replacement - "Legacy" to "Classic") |
||
(2 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
{{Meta}}{{I18n}} | {{Meta}}{{I18n}} | ||
{{Category Classicplayerinfo}} | |||
{| style="float: right" border="0" cellpadding="5" | {| style="float: right" border="0" cellpadding="5" | ||
| {{Quest_dev | | {{Quest_dev | ||
Line 62: | Line 64: | ||
This option calls the "fightclub_EmergencyWipe" function which empty the queue and clear all temporary variables. This function should be the equivalent of rebooting the server. | This option calls the "fightclub_EmergencyWipe" function which empty the queue and clear all temporary variables. This function should be the equivalent of rebooting the server. | ||
</spoiler> | </spoiler> | ||
[[Category: | [[Category:Classic]] | ||
[[Category: | [[Category:Classic]] |
Latest revision as of 16:02, 30 December 2022
This article contains information for players or people interested in playing on the Classic server. If you are looking for information for The Mana World, go here The Mana World.
See also the Classic Portal
|
Commands
The fight club commands are used the same way as spells but do not require any level of magic and do not consume mana points.
Send a duel request
To challenge someone to a duel, write #duel
If the command worked, you will see dark-red particles on your character and on your target. If it failed, it will do nothing and display an error in the Debug chat window. Once you challenge someone, that person must talk to Rouge to accept or decline. The battle will use the rules of the player who request the duel, not the player who accept it.
Ignore incoming requests
If you are getting spammed with duel requests, you can either wait for your queue to be full or you can write #dueloff
This command will ignore all incoming requests. To un-ignore, cast the same command again
Rules
You can set your own rules by talking to Rouge.
Debug Commands
<spoiler>You can access the fightclub debug menu by clicking on Debug (only on the test server) or by wearing a dev cap while talking to Rouge.
$Duel_Enabled ($fightclub_enabled % 5)
This variable is like the main breaker of the fight club. When set to 0, all timers are stopped, users can no longer call #duel and Rouge do not offer any option related to the fight club. Turning this off will completely disable the fight club.
$fightclub_bm_enabled ($fightclub_enabled % 6)
This variable enable or disable the Battle Master. If players are already in the PVP cave or at Brodomir's while this variable gets disabled, they will still go through the cleanup procedure and get warped to the fight club when they quit.
$@fightclub_password$
This variable is the password that is asked when you enter the fight club. It has no practical purpose. If you set the password to "random" (without quotes) a random password will be shown every time someone trigger the trapdoor.
$@Duel_TimeBeforeNext
This variable is the number of time (in seconds) to wait between each battle. When a battle ends, a timer is started and the next battle is scheduled after.
$@Duel_TimeBeforeWarp
This variable is the number of time (in seconds) to wait before warping the players into the ring. This is the "The next battle is foo vs bar. this battle will start in X seconds"
$@Duel_TimeBeforeStart
This variable is the number of time (in seconds) to wait after all players are in the ring to start the battle. When players are warped into the ring they see the message "Get Ready" and X seconds later "Go!". This allows both players to move to desired location before getting @killer
$@Duel_TimeLimit
This variable is the number of time (in seconds) before ending the battle with no winner.
$@Duel_QueueLimit
This variable is the maximum number of duels that can be queued at once. When the queue is full, players have to wait to add another battle to it.
Restart fightclub
This option calls the "fightclub_EmergencyWipe" function which empty the queue and clear all temporary variables. This function should be the equivalent of rebooting the server. </spoiler>