Rules Update - CRP

[squakhawk 6395]

Hi everyone,

With the advent of Honor based CRP Default, for a long time both Moderation and Story have wanted to work on combat rules to replace our antiquated, and very abuseable system. With fixed movement, we found that there would be things such as infinite chases. With no detail of vertical play, we found issue where there was no solid definition on climbing and falling. Another complaint we've found by majority with the CRP rules, has been the issue of a lack of a CRP Lock - that without so, combat can drag on far longer than intended as more and more combatants get involved. While Honor-default based CRP remains unchanged, this system replaces the prior issues the CRP rules had, with a rename to clarify the difference in system.

What are the changes?

As with any of our recent Administrative changes, these are subject to change and modification based on wider testing. However, we have added a good deal of changes to multiple aspects of combat. Below, is The Short, and The Long.

 

The Short

-CRP is having a name change, from "Combat Rules" to Balance-Default Combat Rules. This is due to the fact that these rules are not  applying to Honor-Based CRP, unless the combatants involved would wish to use such a system, or are forced to by moderator. 
-Balance-Default Rules have differing levels of movespeed based on certain conditions, such as being upon a mount or sprinting.
-Balance-Default Rules now account for vertical play and actions, such as falling 
-Balance-Default Rules account for speech in emotes, and limiting so
-Balance-Default Rules account for people leaving and returning to combat, and a 10-Minute Combat Lock
-Balance-Default rules clarify the limit of medical roleplay within combat
-Balance-Default Rules clarify mechanical v.s. roleplay standards of weapons and items

 

 

The Long (Spoilered)

Spoiler

1) You may only move four blocks per emote whenever performing an action relevant to combat. This includes swinging a melee weapon, blocking an incoming strike, aiming a ranged weapon or preparing to throw a projectile as well as casting certain magics.

     1A) This also applies to characters on the receiving end of an action, such as being tackled, shot or hit. 

2) You may only move eight blocks per emote when your character is solely focused on sprinting.

3) You may only move eight blocks per emote whenever performing an action relevant to combat whilst mounted.

     3A) This also applies to characters on the receiving end of an action, such as being tackled, shot or hit. 
 

4) You may only move twelve blocks per emote when your character is solely focused on riding a mount.
 

5) You may fall any distance in one emote.
     5A) You may drop up six blocks vertically and continue action unhindered. Dropping up to nine blocks will result in a stumble, reducing movement to half for one emote thereafter. Dropping up to twelve blocks will result in a broken leg, reducing movement to one quarter for the remainder of the combat and thereafter until healed. Dropping up to fifteen blocks will result in serious injury and a character becoming incapacitated or unconscious atop broken limbs. Dropping up to eighteen blocks will result in a character’s death. 
     5B) Characters can drop an additional three blocks if landing in water or a haystack that is three blocks deep or more. 

6) You may only say one sentence (approximately fifteen words) of speech in character per emote whilst combat is ongoing. 
 

7) You may not relay messages to characters outside of shout range in combat. This means the use of couriers, messenger birds and other forms of long distance communication are prohibited. 
 

8) When a character leaves a combat scenario they are unable to return until the ongoing combat has been concluded, as agreed by both sides, nor may they leave and rally others to join the combat roleplay they were not otherwise present for. Exceptions can be made to this if both sides agree. 

9) Combat is considered “Locked” 10 minutes after the beginning of combat, preventing others from joining unless both sides agree. 
 

10) Surgery and other medical procedures beyond first aid cannot be performed in combat. 

11) Combat roleplay does not adhere to mechanical standards and instead follows common sense logic. For example: your character can not pull a boat out of their pocket even if there is a boat in your minecraft inventory.
     11A) The sole exception to this rule is with regards to special items used in combat like weaponry, potions and magical objects that must be in your mechanical inventory where appropriate to be used in combat roleplay.

I've went ahead and compiled a list of lores which may need changing in accordance to the rules. Most specifically, ones which affect hard-block counts, rather than generalizations. Lores which state something akin to "Halved" or "Doubled" movement will likely stay unchanged, but ones which reference block-amounts specifically will see rebalancing.

Make sure to join The ST Discord and check the ST-Audit-Log for updates.

Looking forward to seeing these in action,  

Squak

[subatomic 880]

ok

[satinkira 3494]

What's behind the word limit? Don't really see the logic there

[wowj 1641]

nub wae

[Laeonathan 3101]

I cry

[ReveredOwl 4661]

4 minutes ago, SquakHawk said:

9) Combat is considered “Locked” 10 minutes after the beginning of combat, preventing others from joining unless both sides agree. 

Absolutely ridiculous, what are guards, for example, supposed to do if they see people fighting 11 minutes after it started? Just pretend its not happening? If you're going to allow for uncapped raids all you're gonna have are the raiders forcing pvp as quickly as they can so they don't have a sizable force against them. Dumb.

[Tabby64 1180]

Nub wae

[1_Language_1 1633]

damn time to memorize shiz

[louislxix 3033]

balance-default, sounds epic

[MissToni 2997]

Well... This just became a LOT to remember

[Xarkly 10845]

Word limit per emote is unbelievably silly

[Althea_ 273]

I really like those new rules, but this here is indeed prone to lead into odd situations

 

9 minutes ago, ReveredOwl said:

Absolutely ridiculous, what are guards, for example, supposed to do if they see people fighting 11 minutes after it started? Just pretend its not happening? If you're going to allow for uncapped raids all you're gonna have are the raiders forcing pvp as quickly as they can so they don't have a sizable force against them. Dumb.

 

So in order to solution it, I believe there should be an exception when such combat takes place within a nation's capital. The guards, in this case alone, should still be able to join combat, as it's just truly ridiculous otherwise.

 

Though, this could be limited by forcing them to start a X distance away from the bulk of the fight, among other things. 

 

Or instead 'reinforcements' could only be allowed to join in after a certain amount of time (10+ minutes for example).

[Sakrat 75]

everyday i am happy i dont play lotc

[chacmul 266]

goofy ahhh (reverting to *slashes at your arm* now, i'm done with para rp)

[The King Of The Moon 4871]

Make it area locked at the initiation of combat (ie only people in the capital can respond to a fight going on in the city centre; troops can’t be rallied across continents for an ongoing fistfight after all) rather than time locked. ‘10 minutes’ has no tangible meaning when it takes some people 15 minutes to emote