Mabinogi World Wiki is brought to you by Coty C., 808idiotz, our other patrons, and contributors like you!!
Want to make the wiki better? Contribute towards getting larger projects done on our Patreon!

Repair Cost & Dura Loss

Just going to leave this here, this is based on testing my friends and I did:

  • CRK Bash Enhance multiplies Bash damage by 1.1. At rank 1 bash, this is 460% * 1.1 = 506%.
  • CRK Critical Enhance adds 7% critical to all attacks. So, at rank 1 critical, with no other modifiers, your crits do an additional 157% of your maximum damage.
  • CRK Durability Loss Decreases cuts durability loss of ALL items by 50%. (Not sure if this point is wholly accurate, blessed + VIP + CRKs resulted in a 50% cut over just blessed + VIP, but that could be impacted by how the modifiers are applied. Someone should test unblessed and without VIP to be sure)
Your friendly Server Status Script admin, Xcelled19421:36, 14 June 2015

Unless it's 50% overriding VIP, it's only a 33% reduction (2/3*3/4=1/2, and half is what VIP users lose with it unblessed, 1/4 blessed.). Need non-VIP to test. The above testing already shows that it is not a 50% cut over normal swords with the same, at least on a VIP account.

Callback (talk)00:09, 15 June 2015

I gathered explicit numbers that showed 6-7 loss with VIP+Bless and 3-4 with VIP+Bless+crk.

Your friendly Server Status Script admin, Xcelled19405:18, 15 June 2015

Tested without VIP. Results:

  • Blessing cut: 50%
  • VIP Cut: ~25%
  • CRK Set Cut: 30%

Final dura is calculated by multiplying them all together, eg 16 * .5 * .75 * 7 = 4.2.

This data was gathered using bash, which has a fixed dura loss, as mentioned elsewhere.

The numbers worked out such that the 30% of the crk was close enough to 50% to be confusing on previous tests.

Your friendly Server Status Script admin, Xcelled19423:56, 19 June 2015

30 is indeed correct. Likewise from the above values, truncation lead me to believe it was a fuller 33%, but after finding non-VIP who owned a pair to test, 30% is the correct number.

Callback (talk)11:52, 24 June 2015