1.1.1 Patch Notes

[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