1.1.1 Patch Notes

[Ellie]

Added new Mercenary changes.

[orangeandblack5]

Time to go look

[orangeandblack5]

Why can’t it be contracted to a Knight?

[Lily]

Because Cold Steel.

[orangeandblack5]

I don’t see how that’s an issue

Just don’t randomly CS lol

[Lily]

Well people are stupid not everyone is as smart as us.

[orangeandblack5]

Fair enough I guess

And actually I realized the real reason is probably Stand Guard lel

[orangeandblack5]

Wait don’t they survive a guard now???

[Marluxion]

I think the real reason is “Knight claims in 2018 LUL”

/S

[Lily]

Yeah i forgot that exists tbh i only see Knights die by randomly cs on night 3.

[Marluxion]

Just one
Both abilities revolve around them killing themselves

[Lily]

@orangeandblack5

Wait don’t they survive a guard now???

They do once.

[methomps]

@orangeandblack5

I don’t see how that’s an issue

Just don’t randomly CS lol

A lot of times a Prince will order a knight to CS

[Sketch]

Here are the updated changes to Mercenary:

@Ellie

Mercenary:

Stand Guard will now also prevent a player from dying.

This will prevent the contract from dying to Smite or the Hunter’s Bear. If the contract attacks someone guarded by a Knight, the Mercenary will die in the contract’s place.

A frenzied Assassin will still kill the contract.
Can no longer start contracted to the Inquisitor, Knight, or Prince.

I am happy to see the removal of Prince from possible contracts.
Removing Inquistor from contracts is a good idea. The Sorcerer has a hard enough time as it is.

Removing Knight is questionable. I would like to know the reason behind that change…

Edit: Ah. Knights frequently kill themselves and the new Merc cannot re-contract. That makes sense.

[methomps]

Any idea what message an assassin gets if he attacks a bear/guard and the merc takes the hit?

There’s going to be a few assassins busted for claiming knight with a merc.

[NightX]

I feel this is the way to go now that we have the one contract thing:

@Marluxion

A lot of people are complaining that it is against the rules to bus your first contract. I have a suggestion that would both fix this problem while simultaneously making the mercenary more fun to play.

Simply let the Mercenary choose their first contract!
If they haven’t picked a contract by N2, they commit suicide.

This puts the burden of choosing a good contract on the Mercenary themselves, so they can’t complain about ‘randomly rolling the NK’ and not wanting to protect them.

[Vandalay]

IMO this would also need to be combined with… contract does not require confirmation or grant notification to the recipient. The same blacklist should also be in play (no contracts for prince). Perhaps just a message for the merc saying “contract may not be selected”. but allow a re-use.

[Bart_Auringer]

Then Merc can find classses, which seems wrong.

“Oh he’s actually a knight like he says because I couldn’t contract him.”

And if the Prince-out meta ever leaves he’ll be able to find the Prince.

[Vandalay]

it is a good point there. Personally I’m fine with the random contract. Just saying IMO that should be required IF merc is going to pick it’s contract. The last thing we should want is either merc becoming non-scum claimable again via the confirmation pop-up, or making the prince out meta even more safe via prince demanding any merc’s to contract him on day 2.

[Firekitten]

I will refuse to contract a prince if he did that. I will make sure he dies somehow