Siege

Siege is a mechanic in CivRealms which allows for the "assault" of a Prison Pearl from afar, without having to actually break into a vault. This can make the practice of "permapearling" (fueling a pearl indefinitely with stamina) somewhat more difficult.

Command syntax

/siege [user 1] [user 2] ... [user n]

Where [user 1]...[user n] are each the usernames of someone when they first joined CivRealms to be sieged; so if a user has changed their minecraft username since they joined the server, the command will not work with their new name (their pearl will be regarded as invalid when the siege begins).

All users after user 1 are optional for the siege.

So, to attempt to siege the users Crimeo, Mike0War and JohnSmith, you would use (assuming they have not changed their usernames since joining the server):

/siege Crimeo Mike0War JohnSmith

To stop a siege after you've initiated it, run the command with no users as parameters:

/siege

Mechanics

After executing the command, a 24 hour countdown will be initiated. After it completes, the siege will begin next time you receive stamina for logging on.

Each name in the siege list will be checked in a random order. If it is possible to siege the user (they must be a real user currently pearled, and their pearl has only been sieged at most 2 times already that day), 2.5 stamina will be taken from you and the user's pearl will lose 1.25 stamina of fuel. If the pearl runs out of fuel, it will be freed. It will continue to siege up to one more valid user in the list - you can only perform two sieges a day. Once two users in the list have been sieged, no more sieges will occur. Note that sieging is not automatically reoccurring from the first time you run the command - if you want to siege someone twice, you will have to use the siege command once and then again after the first siege.

Again, a user's pearl can only be sieged up to 3 times a day; if someone tries to siege their pearl a 4th time in the same day, their pearl will be regarded as invalid to the command.

So, again using the example of the command above:

/siege Crimeo Mike0War JohnSmith

After the siege begins, it will be checked, in a random order, whether Crimeo, Mike0War and JohnSmith are valid users to siege. Every time a valid user is encountered, they will be sieged; if 2 valid users have been sieged, the siege will end.

For instance, let's say all users above are valid, and Mike0War's pearl is randomly chosen to be checked first, followed by JohnSmith and Crimeo. Crimeo will not be sieged, because by the time his name is reached, 2 users will have already been sieged. The process will look like this:

• Check Mike0War's pearl --> pearl is valid --> pearl is sieged, 1 more siege possible
• Check JohnSmith's pearl --> pearl is valid --> pearl is sieged, no more sieges possible, stopping

Now, let's say Mike0War is an invalid user to siege, and the same order for checking is chosen. Now, Crimeo's pearl will be sieged, because the process will go like this:

• Check Mike0War's pearl --> pearl is invalid --> pearl is not sieged, 2 more sieges possible
• Check JohnSmith's pearl --> pearl is valid --> pearl is sieged, 1 more siege possible
• Check Crimeo's pearl --> pearl is valid --> pearl is sieged, no more sieges possible, stopping (but the last name in the siege list was reached anyways)