create account

The Repair Ability Problem by underlock

View this thread on: hive.blogpeakd.comecency.com
· @underlock · (edited)
$34.09
The Repair Ability Problem
<center>![](https://files.peakd.com/file/peakd-hive/underlock/48PTBARYPru1xE8wGhDcsqvWEC6q37Vm7ewgBDNbaRH8kBsRV2jUN71M95UwPB5AqL.png "The Repair Ability Problem")</center>

<div class="text-justify">

### **Translated by [ChatGPT](https://chat.openai.com/ "chatgpt")**.

Another week of **Brawls**, and this time it was even tougher. Unlike last week, where I managed a 7/1 record, this time I at least stayed positive with 5 wins and 4 losses. During one of these battles in **[Splinterlands](https://splinterlands.com?ref=underlock "underlock")**, I observed that the **Repair** ability has a rather *"problematic"* aspect that hinders its optimization.

I put *"problematic"* in quotes because the developers may have deliberately designed it this way for balance reasons, or there might be criteria defining the target of **Repair** that I am not aware of. The fact is, this ability can provide interesting survivability for your team, and depending on the situation, it can make your card *"immortal"*, preventing the opponent from eliminating it because the attack never reaches its health.

https://d36mxiodymuqjm.cloudfront.net/website/abilities/ability_repair.png

However, if someone is focusing on your support card with this ability and your frontline, the chosen card to receive the benefits of **Repair** may not be the best option. In my view, self-protection should be an additional mechanism of this ability so that, in dangerous situations, the focus of the effect would be on the card itself. It might sound confusing, but let's visualize it in practice.

<center>[![Battle.](https://files.peakd.com/file/peakd-hive/underlock/Eo8M4dNqYn7SZa1G4mQGV6aSBi2gYyQKGAtHUMxfKLyGBqxccKzG4qTRq7dKYtLy9y6.jpeg)](https://splinterlands.com/?p=battle&id=sm_fBlmUVjrMHgqoVkPHQLI&ref=underlock)</center>

*(Please excuse the image quality; I'm traveling and using my phone to create this post.)*

In this match, the opponent had two cards focusing on **Uriel the Purifier**, and one attacking **Adelade Brightwing**. In this specific situation, I would lose anyway, but let's imagine that instead of **Pelacor Arbalest**, there was a card with only 1 damage. Adding this damage to the 2 from the enemy Adelade, they would cause 3 damage per round, which would be completely healed by Uriel's **Heal**.

Meanwhile, in the backline, the Harpy would be focusing its attacks on my Adelade. The problem is that in this situation, the focus of **Repair** is on Uriel, so regardless of whether he needs that armor regeneration, Adelade will target the Repair on him and eventually be eliminated, losing the support ability and the possibility of using **Resurrect**. This is a significant drawback of this ability that needs to be taken into consideration. If there were a self-preservation mechanism, Adelade could regenerate her own armor and *"trap"* the Harpy's attacks on her, buying enough time for Uriel to eliminate the opponent's cards.

https://images.hive.blog/400x400/https://files.peakd.com/file/peakd-hive/underlock/23w2ctGWE2a9sWbxvuEA1h3qapbTQ3pYHqM2pWoKb2PcVrNzTPk8arB5W5ahvDNYV9nht.jpeg

Now, I ask those who know exactly how the **Repair** ability works, is the information available somewhere about the rules for determining the focus of who will receive the ability's effect?

This information is valuable and can assist in the development of strategies focused on this ability, so I greatly appreciate it if someone can share it with us in the comments!

Thank you so much to everyone who read this far, I hope you enjoyed it. If you like my content, I ask you to send your vote on the post and follow my profile so you can read future posts.

<center>[![If the king doesn't move then his subjects won't follow.](https://i.imgur.com/LmtzIG2.gif)](https://inleo.io/profile/underlock "inleo")</center>

<center>[![Twitter.](https://i.imgur.com/FJmxTyF.gif)](https://twitter.com/Underllock "twitter x")</center>

<center>https://i.imgur.com/E6s4rZU.png</center>

<center>![](https://files.peakd.com/file/peakd-hive/underlock/48PTBARYPru1xE8wGhDcsqvWEC6q37Vm7ewgBDNbaRH8kBsRV2jUN71M95UwPB5AqL.png "The Repair Ability Problem")</center>

<div class="text-justify">

Mais uma semana de **Brawls** e dessa vez foi ainda mais difícil. Diferente da semana passada em que eu consegui 7/1, desta vez eu consegui ao menos permanecer positivo atingindo 5 vitórias e 4 derrotas. Durante uma dessas batalhas no **[Splinterlands](https://splinterlands.com?ref=underlock "underlock")** eu observei que a habilidade **Repair** possui um *"problema"* muito ruim que atrapalha a otimização do seu uso.

Chamo de problema entre áspas pois os desenvolvedores podem ter simplesmente escolhido que ela funcionasse assim para questões de equilíbrio, ou então existem critérios que definem o alvo do **Repair** que eu ainda não conheça. Fato é que essa habilidade pode fornecer uma sobrevida muito interessante para o seu time e dependendo da situação será possível ficar *"imortal"*, fazendo com que o oponente não consiga eliminar sua carta pois o ataque nunca atingirá a vida.

https://d36mxiodymuqjm.cloudfront.net/website/abilities/ability_repair.png

Porém se houver alguém focando sua carta de suporte que possui essa habilidade e a sua linha de frente, a carta escolhida para receber os benefícios do **Repair** pode não ser a melhor opção. Na minha visão, se auto proteger deveria ser um mecanismo adicional dessa habilidade para que em casos de perigo, o foco do efeito fosse a própria carta. Explicando pode parecer confuso, mas vamos visualizar na prática.

<center>[![Batalha.](https://files.peakd.com/file/peakd-hive/underlock/Eo8M4dNqYn7SZa1G4mQGV6aSBi2gYyQKGAtHUMxfKLyGBqxccKzG4qTRq7dKYtLy9y6.jpeg)](https://splinterlands.com/?p=battle&id=sm_fBlmUVjrMHgqoVkPHQLI&ref=underlock)</center>

*(relevem a qualidade da imagem, estou viajando e por isso estou utilizando o celular para criar essa postagem.)*

Nesse confronto o oponente havia duas cartas focando o **Uriel the Purifier** e uma atacando a **Adelade Brightwing**. Nessa situação específica eu perderia de qualquer forma, mas vamos imaginar que no lugar do **Pelacor Arbalest** existisse uma carta com apenas 1 de dano. Somando esse dano com os 2 da Adelade inimiga, eles causariam 3 de dano por rodada que seria completamente curado pelo **Heal** do Uriel.

Enquanto isso na linha de trás a Harpy estaria focado seus ataques contra minha Adelade. O problema é que nessa situação, o foco do **Repair** está no Uriel, então independente dele precisar dessa regeneração de armadura, a Adelade focará o Repair nele e eventualmente será eliminada, perdendo essa habilidade de suporte e a possibilidade de usar **Resurrect**. Esse é um grande malefício dessa habilidade que deve ser levado em consideração. Caso houvesse um mecanismo de auto preservação, a Adelade poderia regenerar sua própria armadura e *"prender"* os ataques da Harpy nela, comprando tempo suficiente para que o Uriel pudesse eliminar as cartas do oponente.

https://images.hive.blog/400x400/https://files.peakd.com/file/peakd-hive/underlock/23w2ctGWE2a9sWbxvuEA1h3qapbTQ3pYHqM2pWoKb2PcVrNzTPk8arB5W5ahvDNYV9nht.jpeg

Agora eu pergunto à vocês que sabem como exatamente funciona a habilidade **Repair**, está disponibilizada a informação em algum lugar sobre como funciona as regras para definir o foco de quem receberá o efeito da habilidade?

Essa informação é bem útil e pode ajudar durante a elaboração de estratégias focadas nessa habilidade, por isso eu agradeço imensamente caso alguém consiga compartilhá-la conosco nos comentários!

Muito obrigado a todos que leram até aqui, espero que tenham gostado. Se vocês curtirem meus conteúdos, peço que deixem o seu voto na postagem e sigam o meu perfil para poderem acompanhar as futuras postagens.

<center>[![Se o Rei não se mover, seus súditos não irão segui-lo.](https://i.imgur.com/LmtzIG2.gif)](https://inleo.io/profile/underlock "inleo")</center>

<center>[![Twitter.](https://i.imgur.com/FJmxTyF.gif)](https://twitter.com/Underllock "twitter x")</center>

</div> 
👍  , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , and 314 others
properties (23)
authorunderlock
permlinkthe-repair-ability-problem
categoryhive-13323
json_metadata"{"app":"peakd/2023.11.3","description":"The Repair Ability Problem","format":"markdown","image":["https://files.peakd.com/file/peakd-hive/underlock/48PTBARYPru1xE8wGhDcsqvWEC6q37Vm7ewgBDNbaRH8kBsRV2jUN71M95UwPB5AqL.png","https://d36mxiodymuqjm.cloudfront.net/website/abilities/ability_repair.png","https://files.peakd.com/file/peakd-hive/underlock/Eo8M4dNqYn7SZa1G4mQGV6aSBi2gYyQKGAtHUMxfKLyGBqxccKzG4qTRq7dKYtLy9y6.jpeg","https://images.hive.blog/400x400/https://files.peakd.com/file/peakd-hive/underlock/23w2ctGWE2a9sWbxvuEA1h3qapbTQ3pYHqM2pWoKb2PcVrNzTPk8arB5W5ahvDNYV9nht.jpeg","https://i.imgur.com/LmtzIG2.gif","https://i.imgur.com/FJmxTyF.gif","https://i.imgur.com/E6s4rZU.png"],"tags":["splinterlands","inleo","neoxian","hivebr","thgaming","proofofbrain","hive-engine","pimp","play2earn","bdcommunity"],"users":[]}"
created2024-01-19 23:20:03
last_update2024-01-20 02:26:51
depth0
children10
last_payout2024-01-26 23:20:03
cashout_time1969-12-31 23:59:59
total_payout_value17.074 HBD
curator_payout_value17.018 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length8,054
author_reputation807,523,633,232,940
root_title"The Repair Ability Problem"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id130,618,977
net_rshares81,341,735,656,543
author_curate_reward""
vote details (378)
@ducecrypto ·
I always thought repair worked like triage, where it would repair the armor that took the most damage. then if two or more monsters took the same amount of armor damage in a round then it would repair at random.

I've always thought this is one of the biggest troubles with the game and competitive play that there isn't a rules interaction guide that is independent of "the way the code works," so that players would know if an interaction did not work as intended. then it would be easier to bring up gameplay bugs or just mistakenly thinking this is the way it is supposed to work!
properties (22)
authorducecrypto
permlinkre-underlock-s7l2v5
categoryhive-13323
json_metadata{"tags":["hive-13323"],"app":"peakd/2023.11.3"}
created2024-01-20 23:35:30
last_update2024-01-20 23:35:30
depth1
children1
last_payout2024-01-27 23:35:30
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length584
author_reputation43,570,935,302,275
root_title"The Repair Ability Problem"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id130,643,727
net_rshares0
@underlock ·
I agree with you. These slight nuances are what allow the best players to create the best possible strategies and increase their chance of winning
👍  
properties (23)
authorunderlock
permlinkre-ducecrypto-s7oq1h
categoryhive-13323
json_metadata{"tags":["hive-13323"],"app":"peakd/2023.11.3"}
created2024-01-22 22:44:15
last_update2024-01-22 22:44:15
depth2
children0
last_payout2024-01-29 22:44:15
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length146
author_reputation807,523,633,232,940
root_title"The Repair Ability Problem"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id130,696,593
net_rshares28,059,692,826
author_curate_reward""
vote details (1)
@hive-br.voter ·
<center> 
Your post was manually curated by @CrazyPhantomBR.
![banner_hiver_br_01.png](https://images.ecency.com/DQmcTb42obRrjKQYdtH2ZXjyQb1pn7HNgFgMpTeC6QKtPu4/banner_hiver_br_01.png)


Delegate your HP to the [hive-br.voter](https://ecency.com/@hive-br.voter/wallet) account and earn Hive daily!

| | | | | |
|----|----|----|----|----|
|<center>[50 HP](https://hivesigner.com/sign/delegateVestingShares?&delegatee=hive-br.voter&vesting_shares=50%20HP)</center>|<center>[100 HP](https://hivesigner.com/sign/delegateVestingShares?&delegatee=hive-br.voter&vesting_shares=100%20HP)</center>|<center>[200 HP](https://hivesigner.com/sign/delegateVestingShares?&delegatee=hive-br.voter&vesting_shares=200%20HP)</center>|<center>[500 HP](https://hivesigner.com/sign/delegateVestingShares?&delegatee=hive-br.voter&vesting_shares=500%20HP)</center>|<center>[1000 HP](https://hivesigner.com/sign/delegateVestingShares?&delegatee=hive-br.voter&vesting_shares=1000%20HP)</center>|

🔹 Follow our [Curation Trail](https://hive.vote/dash.php?i=1&trail=hive-br.voter) and don't miss voting! 🔹


</center>
properties (22)
authorhive-br.voter
permlink3,757,089,915
categoryhive-13323
json_metadata""
created2024-01-20 20:12:21
last_update2024-01-20 20:12:21
depth1
children0
last_payout2024-01-27 20:12:21
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length1,090
author_reputation165,200,417,191
root_title"The Repair Ability Problem"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id130,639,897
net_rshares0
@josediccus ·
I don't think there's any information anywhere on how the repair ability works. However I think that having multiple opportunity or sneak attack targeting for example the Adelaide, they'll eventually eliminate it because there's only so much the repair can do against constant multiple attack.
properties (22)
authorjosediccus
permlinks7k96g
categoryhive-13323
json_metadata{"app":"hiveblog/0.1"}
created2024-01-20 12:54:18
last_update2024-01-20 12:54:18
depth1
children1
last_payout2024-01-27 12:54:18
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length293
author_reputation2,104,932,063,262,421
root_title"The Repair Ability Problem"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id130,630,883
net_rshares0
@underlock ·
Exactly, against a single attacker Self Repair can be a great resource, against two opponents its effectiveness is greatly reduced
properties (22)
authorunderlock
permlinkre-josediccus-s7opyv
categoryhive-13323
json_metadata{"tags":["hive-13323"],"app":"peakd/2023.11.3"}
created2024-01-22 22:42:45
last_update2024-01-22 22:42:45
depth2
children0
last_payout2024-01-29 22:42:45
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length130
author_reputation807,523,633,232,940
root_title"The Repair Ability Problem"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id130,696,573
net_rshares0
@lincemarrom ·
Pelas minhas observações, funciona assim: a carta que perdeu mais armadura recebe a cura. O que confunde o pessoal é a descrição da habilidade "a unidade que sofreu mais dano", porque se duas cartas tem 1 ponto de armadura, e uma sofreu um ataque de 5 de dano e outra sofreu um ataque de 1 de dano, teoricamente a que levou 5 de ataque seria curada, porém o jogo considera como o mesmo dano sofrido, pois ambas perderam 1 ponto de armadura. E a preferência vai ser sempre a carta que estiver mais a frente da linha.
properties (22)
authorlincemarrom
permlinkre-underlock-s7vnu8
categoryhive-13323
json_metadata{"tags":["hive-13323"],"app":"peakd/2023.11.3"}
created2024-01-26 16:44:33
last_update2024-01-26 16:44:33
depth1
children0
last_payout2024-02-02 16:44:33
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length515
author_reputation101,831,714,758,425
root_title"The Repair Ability Problem"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id130,797,292
net_rshares0
@oadissin ·
Peace
Amazing element you shared in the community. What a brillant strategy in your gameplan!
Thank you for sharing this original composition in your article.
Conflicts section in the Splinterlands is coming. Are you ready to compete?
!CTP
#freecompliments
Regards
properties (22)
authoroadissin
permlinkre-underlock-2024120t22243778z
categoryhive-13323
json_metadata{"tags":["splinterlands","inleo","neoxian","hivebr","thgaming","proofofbrain","hive-engine","pimp","play2earn","bdcommunity"],"app":"ecency/3.0.37-vision","format":"markdown+html"}
created2024-01-20 01:22:45
last_update2024-01-20 01:22:45
depth1
children1
last_payout2024-01-27 01:22:45
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length264
author_reputation276,157,150,876,997
root_title"The Repair Ability Problem"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id130,620,825
net_rshares0
@underlock ·
We've got big news coming soon with Conflits, it's time to get ready!
properties (22)
authorunderlock
permlinkre-oadissin-s7opzz
categoryhive-13323
json_metadata{"tags":["hive-13323"],"app":"peakd/2023.11.3"}
created2024-01-22 22:43:24
last_update2024-01-22 22:43:24
depth2
children0
last_payout2024-01-29 22:43:24
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length69
author_reputation807,523,633,232,940
root_title"The Repair Ability Problem"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id130,696,580
net_rshares0
@perfilbrasil ·
Obrigado por postar
Obrigado por promover a comunidade Hive-BR em suas postagens.

Vamos seguir fortalecendo a Hive

<div class='text-right'><sup>Metade das recompensas dessa resposta serão destinadas ao autor do post.</sup></div><hr/><h4><center><a href='https://vote.hive.uno/@perfilbrasil'>Vote no @perfilbrasil para Testemunha Hive.</a></center></h4>
properties (22)
authorperfilbrasil
permlinkre-the-repair-ability-problem-1705706713
categoryhive-13323
json_metadata"{"tags": ["pt"], "description": "Obrigado por postar"}"
created2024-01-19 23:25:15
last_update2024-01-19 23:25:15
depth1
children0
last_payout2024-01-26 23:25:15
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length334
author_reputation5,285,724,210,482
root_title"The Repair Ability Problem"
beneficiaries
0.
accountunderlock
weight5,000
max_accepted_payout10.000 HBD
percent_hbd0
post_id130,619,072
net_rshares0
@splinterboost ·
 <center> This post has been supported by @Splinterboost with a 5% upvote! Delagate HP to Splinterboost to Earn Daily HIVE rewards for supporting the @Splinterlands community!</center> 

 <center> [ Delegate HP ](https://peakd.com/@splinterboost)  | [Join Discord](https://discord.gg/RK4ZHKmgcX) </center>
properties (22)
authorsplinterboost
permlinkthe-repair-ability-problem
categoryhive-13323
json_metadata{"app":"splinterboost/0.1"}
created2024-01-19 23:20:09
last_update2024-01-19 23:20:09
depth1
children0
last_payout2024-01-26 23:20:09
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length305
author_reputation15,073,156,611,698
root_title"The Repair Ability Problem"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id130,618,979
net_rshares0