Shotgun fists seem to be, unable to use clay Pidgeon despite technically counting as shotguns.

Ghosthands currently do not stop Riposte from triggering.  To replicate:

1.  Equip Ghosthands, fight a player or mob with Riposte.
2.  Swing a melee weapon at the Riposting enemy a few times.
3.  Observe that they Riposte you despite the equipped Ghosthands.

Range increases don't apply to Holy Word's unique AoE, as far as I know there are many other odd Basic Attack patterns that can have range increases such as Firthrower or Anchor Edge's range.

I don't think it'd be a big deal either since realistically only Volley and Volley formation should apply.

With the release of Yokoshura the current state of Korvara/SL2's Conflict Rules has become far more apparent to most given the heavy emphasis the lore Yokoshura brings has on sparking conflict in some shape or form.

While we're still 5 days or so away from the grace period ending, recent events have brought the conversation to light on how the system can be improved to better facilitate conflict or curtail it for those who'd rather not without detracting from the experience of others.

For context, here are the Conflict Rules, sourced from the SL2 Wiki that Dev was originally working on. The Korvara Conflict Rules are pretty short and can be summarized to DL1 always being enforced and the option to apply for Forced Danger Level, which I'll get into later.

Quote:What is 'conflict'?
This term will be used frequently. Conflict is defined as any serious scenario that results in violence, or other similar serious consequences, against one or more player character(s).

Quote:Rule of Roleplay

1. Prior to conflict, roleplay between both parties must occur. This RP must be done in an interactive way; you cannot simple RP 'at' someone when you're looking for a fight.
   
2. PVP is not mandatory for conflict RP. If both players agree to RP the scenario instead of PVP, that is perfectly acceptable, but follows all of the same rules.
   
3. Your conflict and the level of extremity (see Rule of Consent section) must have some IC reason supporting it. Certain things may not be used as the sole justification, for example:
   • My character is just evil.
     
   • My character is simply insane.
     
   • My character hates (race) and/or (gender) characters.
     

Quote:Rule of Consent

1. Both parties must give consent to the 'danger level' of a conflict encounter.
   • Danger Levels:
     • Level 1: Simple non-life threatening injuries.
       
     • Level 2: Robbery. (See Robbery section)
       
     • Level 3: Maiming (IE, limb loss), destroying a vampire or lich's body. (IE, non-permanent character death.)
       
     • Level 4: Permanent character death.
       
2. In the event that no danger level is clearly established, both parties assume that it is level 1.
   
3. For Level 1/2, consent may be given through IC roleplay that explicitly implies that the other party is about to be, for example, punched or robbed.
   
4. For Level 3/4, explicit consent but must be given beforehand in the LOOC channel by both parties. Simply implying it is not allowed in these cases, as they have permanent consequences.
   
5. Once consent is given, it cannot be revoked without the approval of the other party, or the intervention of a GM. Do not give consent if you are unwilling to follow the consequences!
   
6. Consent cannot be forced in conflict between two parties. Furthermore, attempts to force or coerce someone into giving consent for something they do not want to do is not allowed. Do not harass them OOC - simply accept it and continue roleplaying, or move on.
   • NOTE: If one party is, for example, egging on or insulting another party, and the insulted party makes it clear that they'd better stop or they'll retaliate. In instances like these, continuing to egg on or insult them would be the same as giving consent for the conflict (at level 1). Do not try to use this rule as a shield.
     
7. Just because consent is given for a particular danger level does not mean that the victor has to follow through with it. For example, although consent is given for a robbery, the victor of the conflict may later choose not to actually rob the loser.
   
8. Consent only applies for the specific encounter. (IE, just because someone consents to being robbed once does not mean they are giving consent for you to rob them in the future.)
   

Quote:Rule of Avoidance

1. To avoid never-ending cycles of revenge conflict, both parties must avoid interacting for at least 12 real-time hours following the resolution of the conflict.
   
2. Interacting means interacting; both parties have a responsibility to make sure their characters are not in the same place where conflict would begin again. For example, do not go taunt your victim/aggressor after the conflict.
   
3. Naturally, it is forbidden to use different character(s) the player(s) own to try and get around this.
   
4. This rule may be waived in the event that both parties amicably agree to do so. (IE, you wish to continue the RP).
   
5. Always keep in mind that the spirit of this rule is to prevent nonsensical, repeated headbutting, and to avoid OOC drama which may arise otherwise.
   

Quote:Scene Locking
First and foremost: Roleplay is a collaborative activity, not a competitive one. All parties involved in a scene, be it in conflict or not, should strive to make the scene fun and interactive for as many people as possible. Please keep that in mind when reading these rules.

1. Once conflict has begun, except in one of the listed circumstances, the scene is considered 'locked'. This means that the participants in the conflict at that time are the only ones who can participate - meaning that if someone happens across the scene, they may observe OOCly, but cannot interfere or interact with it, and for the purposes of the scene, they are not there ICly.
   
2. Once the conflict concludes, only participants may obstruct either party from leaving the scene, and only if it makes sense with how the scene played out. Non-participants cannot pursue leaving parties or interact with them regarding the scene for 10 real-time minutes (to give a little padding for antagonistic characters from being immediately pulled into another conflict).
   
3. KEEP IN MIND: If you stumble across such a scene, you are observing OOCly. The way it plays out and any information divulged is NOT IC knowledge to you - using it as such is considered metagaming. This includes if your character was 'secretly watching' - if you did not participate (by roleplaying) in the scene from the start, you are not there ICly.
   

Quote:Rule of Consent Adjustments

1. Korvara conflict is always assumed to have a consented Danger Level 1 (simple non-life threatening injuries).
   • This means that, provided supporting RP is done, you can't refuse to participate in a conflict.
     
   • This does not mean that you can attack anyone at any time; the Rule of Roleplay still applies.
     
2. A certain Danger Level can be forced in certain circumstances.
   • See the section below for details.
     

Quote:As per the Conflict Rules, there is a Danger Level associated with conflict that determines how far the consequences can go. However, on Korvara, it is possible to 'force' a Danger Level in certain circumstances, by following the rules and guidelines listed below.

1. Positions of influence, such as leadership roles, advisors, ambassadors, etc. are subject to the guidelines below.
   
2. Characters in general can also be subject to them, especially if they engage in conflict-oriented RP.
   • Some examples would be characters who are bandits or other serious criminals, hostile military actions, characters who have killed or harmed others with this rule, and so on.
     

Simplified Explanation
Make a txt, google doc, or some other organized document, with the following:

1. What your character's exact goal is.
   
2. The IC reasoning that your character wishes to try this.
   
3. As many additional details as possible that you feel would bolster your chances of being approved.
   
4. Screenshots or chat logs of in-game RP of your character working towards this goal.
   

Send the document to a GM for private discussion, and wait for them to get back to you.
Detailed Explanation
For this section, there will be a common example scenario provided; "My character wants to kill the Premier and take his/her position."

1. What is your character's exact goal?
   • AKA 'What do I hope to accomplish?'; in our example, it's quite clear. I wish to kill the Premier so that I can become Premier myself.
     
2. The IC reasoning that your character wishes to try this.
   • AKA 'Why am I doing this?'; in our example, perhaps I am simply am ambitious character who craves power. Or, perhaps, the Premier harmed or killed a dear person to me, and I want revenge on them.
     
3. As many additional details as possible that you feel would bolster your chances of being approved.
   • This is an important section that can contain many questions and answers.
     
   • What is my plan to carry this out?
     • You will need to establish the scenario in which you will accomplish this. In all likelihood, you are not going to get carteblanche to attack someone whenever it suits you.
       
     • In our example, my plan is to lure the Premier into a private meeting, where I will attack them with a poisoned knife.
       
   • When am I going to enact my plan?
     • A general idea is fine, as scheduling conflicts may occur for whatever reason.
       
     • In our example, I will say that I am going to enact this plot the next time I have a private meeting with the Premier.
       
   • How am I going to enact my plan?
     • You are not guaranteed to succeed in your goal. When your target inevitably uses their agency to resist, how will you settle matters?
       
     • Are you planning to settle it with PvP, or via RP (perhaps with dice rolls or coin flips)?
       
     • If you suspect you will want or need a GM to observe the conflict to ensure fairness, please state that as well.
       • In the event that you and your target cannot agree on a method, the GM will have you both state your case, and decide from there. They can also act as a mediator/judge for RP.
         
   • Who is going to help me? Who is going to obstruct me?
     • While you are welcome to try something ambitious on your own, you should consider your allies, as well as your enemies; some will aid you, some will try and stop you.
       
     • In our example, perhaps I have recruited the head of the guards on my side, who will prevent them from slaughtering me after I attack. That's an ally.
       
     • Also in our example, perhaps the Premier has a bodyguard outside of the guards. That's an enemy who will interfere with my plan. Perhaps I will have him drugged or distracted so they cannot.
       
   • If I'm successful, what is the logical progression?
     • Actions have consequences. You should think ahead of time, based on the questions above, what will happen afterwards.
       
     • In our example, I have killed the Premier. I have the guards on my side, who will serve as muscle to legitimize my claim to be the new Premier.
       
     • If I'm doing it for revenge, however, maybe I'll just flee town quickly. If anyone stops me, for some reason, they might notice the blood on my hands, though...
       
   • If I'm unsuccessful, what is the logical progression?
     • Failure is a possibility, so you should consider what would happen if it occurs. Acknowledging the risks is important.
       
     • Perhaps someone I wasn't expecting intervened, or the Premier turned the tables on me. There is a high likelihood I will be imprisoned, or even executed.
       
   • Am I going to give the other character an 'out'?
     • An 'out' would be a lesser consequence of this plot, while still achieving the goal. While not strictly necessary, it can help progress a plot while minimalizing 'feel bad' moments between players.
       
     • In our example, I am trying to kill the Premier. If I'm ambitious, then all I really want is their power. My request can say that, once I have the Premier at my mercy, I plan to offer them an 'out' by having them willingly surrender power to me, and then exiling them.
       
     • This way, the Premier has a choice; die heroically denouncing my villainy, or save themself and continue their story.
       
   • Is the target's player aware this is coming?
     • Your target does not need to be aware of your intentions. They will, however, be told that someone non-specific may be after their life, if your request is approved.
       
     • The more cooperative both parties are willing to be towards each other, the more likely the request will be approved. It will also ensure that both parties will have time to carry it out in-game.
       
4. Screenshots or chat logs of in-game RP of your character working towards this goal.
   • AKA 'What have I done in service of my goal?';
     • I might include the RP that I did with the head of the guards to earn their loyalty.
       
     • I might also include RP of my character speaking with an alchemist familiar with poisons, to help me develop the poisoned knife I planned to use.
       
     • Furthermore, I can include any other examples of my character's ambitious nature.
       

Once you have received approval from a GM...

1. The GM will notify you of your approval, as well as the target of the conflict that they are being targeted (OOCly).
   • They will not tell the target anything about who is plotting against them.
     
   • Otherwise, this is important for fairness reasons.
     
2. The GM will give you a time frame in which you have approval to carry out your plot.
   • Once the time frame has passed, your approval is automatically revoked and you must apply for it again.
     
   • Otherwise, people would sit on approval for long periods at a time, even if the situation changed in the meantime.
     
3. A GM may give you and your target a 'passphrase'.
   • This is a secret passphrase that can be used to verify between the two of you that what is happening was a request handled by a GM.
     
4. You will be expected to follow the information and answers given in your request.
   • Naturally, your request is only allowed to be carried out by your character. You cannot make a request for another player's character, nor can another player's character carry out your plot, unless explicit permission is given by the GM.
     
   • If you falsified information regarding your intentions, etc., you may be punished and in certain cases, the RP may be reversed.
     
   • Please, just be mature and fair with others, and only act with IC in mind.
     

If a GM denies your request, or asks you to amend it...

1. They will inform you of what they found lacking in your request, or the grounds for its refusal.
   • You may be lacking in supporting RP, for example. In this case, provide more supporting RP you left out, or do it IC.
     
2. Once you have corrected the issue the GM has pointed out, you may submit the request to them again.
   

Applicable BYOND Key (And Discord) - Polkjm

Character Name - Joe

Request Type - Power

Request Details -  This power is two-fold.

1: The chicken farmer can detect how much chicken a person has consumed in their life simply by observing them intently. This can be circumvented by a skilled illusion mage or someone with mental defenses.

2: Against a defeated or immobilized foe, the farmer's chicken companion can inflict a curse that makes the victim allergic to chicken. This curse can be dispelled by a competent master of the hexer arts, or whatever way you want. But I'm sure you won't find one of those in Korvara!

Reason why you are making this request (if applicable) - This is a funny and harmless way to add an element of conflict to the character and a minor consequence to add a little stakes. I think it's a fitting way to do conflict for a "funny" antagonist.

Roleplay & Lore supporting your request - Chicken Farmer's schtick is that he's a druid who specifically befriended chicken spirits. The chickens informed him that they don't want to be farmed for food anymore, and they want to get revenge. Thus, the farmer and his companion roam the lands to punish chicken-eaters. His hope is that it will harm the chicken industry. The source of his special power is the anger of the chicken spirits he has befriended.

If you Click on the screen while Targeting a tile (In this case, Haunting)...

You will auto-confirm the action, and do it.

Phoenix Talon says that it "Enchants your kicks." This lead me to believe its an enchant-class skill. Despite this however Prolong isn't affecting it at all. Either it shouldn't say it enchants your kicks or it should be considered an enchantment, I think.

Now counts as a casting tool for Mercalan-domain spells

The trash can(?) button in the top left of the skill/win quote window doesn't actually delete any quotes.



Edit: Another weird thing I just noticed, certain characters, " for one, during the textbox animation go letter by letter through the html &#34 ; notation before suddenly snapping to the actual character once it's finished. Here's an example of it midway through, both in the menu preview and in-battle textbox.





One more small thing, I don't know if it's meant to function, but I can't get skill quotes to work with Instant Guardian, trying both Instant Guardian and Summon Izabe as the skill name. (The latter works with normal summoning but not the autosummon.)

The skill works as intended: when you use Show Mercy, it applies a status effect, and on their next turn, the target chooses whether to flee or stay and fight to the end.

However, I'd like to request a small change to make the roleplay intent behind the skill and trait more consistent.

Make the Show Mercy status's acceptance condition a guaranteed 100% chance if the target is at or below 10 HP. In return, while they are under said Show Mercy status applied by you, your attacks (and damage) can't reduce their HP below 1.

Similar to how Tekagen or Kiddy Gloves behave, but only toward the Show Mercy target.

This would allow the trait to reliably activate based on player intent rather than RNG, and would prevent situations where a player accidentally kills someone they meant to spare with that random Riposte, item effect, status effect or field effect that is completely out of their control.