Difference between revisions of "Tips"

Jump to navigation Jump to search

Tips (view source)

Revision as of 06:48, 18 March 2019

1,599 bytes removed ,  06:48, 18 March 2019
this is also ancient information
(this is also ancient information)
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
={{Star|3}}s vs Higher Rarities=
={{Star|3}}s vs Higher Rarities=
A lot of units share the same (or very similar) skill sets across rarities. For example, {{Companion icon|Arsalan}}, {{Companion icon|Chouji}}, and {{Companion icon|Triton}} are the exact same across rarities, just different costs and base stats. Because of this, it might seem that raising his {{Star|4}} is the way to go, but in reality, focusing on his {{Star|3}} not only saves on party cost, but less resources are required to max him out (coin cost, stars, LB materials, etc).
A lot of units share the same (or very similar) skill sets across rarities. For example, {{Companion icon|Arsalan}}, {{Companion icon|Choji}}, and {{Companion icon|Triton}} are the exact same across rarities, just different costs and base stats. Because of this, it might seem that raising his {{Star|4}} is the way to go, but in reality, focusing on his {{Star|3}} not only saves on party cost, but less resources are required to max him out (coin cost, stars, LB materials, etc).


On the other hand, you have units like {{Companion icon|Shirou}} who slightly have different skills. On paper, it seems like his {{Star|4}}'s [Phase Start] CP gain 100% of the time is a good thing, and having his {{Star|3}}'s [After Moving] skill seems kind of pointless. However, due to how [When Attacking] skills are handled during a Charge, [[Shirou]] charging faster is more of a bad thing, as he won't be inflicting Curse as easily. Because of this, there's no shame in using his lower rarity variant.
On the other hand, you have units like {{Companion icon|Shiro}} who slightly have different skills. On paper, it seems like his {{Star|4}}'s [Phase Start] CP gain 100% of the time is a good thing, and having his {{Star|3}}'s [After Moving] skill seems kind of pointless. However, due to how [When Attacking] skills are handled during a Charge, [[Shirou|Shiro]] charging faster is more of a bad thing, as he won't be inflicting Curse as easily. Because of this, there's no shame in using his lower rarity variant.


However, you have units like {{Companion icon|Snow}}, {{Companion icon|Aizen}}, and now {{Companion icon|Wakan Tanka}}, who share similar skills, but an additional effect on their last skill that makes them a great magnitude better. These units are pretty unviable (namely [[Snow]]) as {{Star|3}}s.
However, you have units like {{Companion icon|Snow}}, {{Companion icon|Aizen}}, and now {{Companion icon|Wakan Tanka}}, who share similar skills, but an additional effect on their last skill that makes them a great magnitude better. These units are pretty unviable (namely [[Snow]]) as {{Star|3}}s.


When it comes to units with beneficial [When Attacking] different weapon spreads like {{Companion icon|Agyou}} and {{Companion icon|Benten}}, you need to consider that a wider range, while it inflicts less damage, are typically better at activating more, as each individual unit hit is a chance to activate a skill. In this case, [[Agyou]]'s {{Star|3}} and [[Benten]]'s {{Star|4}} cards are better than their other forms, as they both have a wider weapon spread.
When it comes to units with beneficial [When Attacking] different weapon spreads like {{Companion icon|Agyo}} and {{Companion icon|Benten}}, you need to consider that a wider range, while it inflicts less damage, are typically better at activating more, as each individual unit hit is a chance to activate a skill. In this case, [[Agyou|Agyo]]'s {{Star|3}} and [[Benten]]'s {{Star|4}} cards are better than their other forms, as they both have a wider weapon spread.
 
=Starting Party Composition=
=Starting Party Composition=
In the beginning, it's really hard to recommend a "go-to" party layout and units to aim for, as most units shine at their end game (that being, maxed out). The "difficulty" curve is minimal in the beginning, so focusing on a solid team is just not needed, and the old <em>use units that looks nice</em> adage is actually the way to go.
In the beginning, it's really hard to recommend a "go-to" party layout and units to aim for, as most units shine at their end game (that being, maxed out). The "difficulty" curve is minimal in the beginning, so focusing on a solid team is just not needed, and the old <em>use units that looks nice</em> adage is actually the way to go.
Line 32: Line 33:


NOTE: When you transfer your account to another device using this code, a new Authkey will be created in this device and your account will be bound to this new Authkey, while the previous Authkey will be bound to a new account. So remember to backup this new Authkey after transferring your data, as the previous Authkey will be rendered useless.
NOTE: When you transfer your account to another device using this code, a new Authkey will be created in this device and your account will be bound to this new Authkey, while the previous Authkey will be bound to a new account. So remember to backup this new Authkey after transferring your data, as the previous Authkey will be rendered useless.
NOTE-2: It's still recommended to transfer between devices using the in-game Account Transfer. It's been officially acknowledged that LW can "detect" this through the User-Agent your device sends out (make/model of phone), so please don't actually rely on this as a lazy way to transfer between two good phones. Whether you can just simply re-transfer to yourself on the same device will un-dirty your account state is unknown.


=AuthKey=
=AuthKey=
Line 43: Line 46:
When you lose (or know you will lose) simply force quit the app and then restart it. At the tittle screen you will be prompted with 3 choices.
When you lose (or know you will lose) simply force quit the app and then restart it. At the tittle screen you will be prompted with 3 choices.
Pressing the left button and then the left button again will restart the battle from the beginning. The position of the enemy units will stay consistent but yours might change, as might whether skills will activate or not. If you used any stones to continue they won't be reimbursed. The middle button will let you continue where you left off. The right button will make you give up the battle. You will lose your AP and any stones you might have used.
Pressing the left button and then the left button again will restart the battle from the beginning. The position of the enemy units will stay consistent but yours might change, as might whether skills will activate or not. If you used any stones to continue they won't be reimbursed. The middle button will let you continue where you left off. The right button will make you give up the battle. You will lose your AP and any stones you might have used.
=Changing your support unit=
<!--=Changing your support unit=
The leader of your current team can be used by other player as a support. In order to change your support unit, you first change the leader of your team and then enter a battle. Winning the battle is optional. There is a free quest in Shinjuku with cost of 2 stamina and if you have completed the main quest to a certain point, you can use a challenge quest in Minato with 0 cost.
The leader of your current team can be used by other player as a support. In order to change your support unit, you first change the leader of your team and then enter a battle. Winning the battle is optional. There is a free quest in Shinjuku with cost of 2 stamina and if you have completed the main quest to a certain point, you can use a challenge quest in Minato with 0 cost.
=Technical Workings Under the Hood=
-->
From current understanding, on Android devices, the app stores game information and data under <code>/SD/Android/data/jp.co.lifewonders.housamo/files/MasterDatas/</code> as base64 encoded strings; however, whether or not these files are further encrypted or obfuscated is unknown as well.
 
=Lag and Slowdown=
=Lag and Slowdown=
If you are on a Galaxy S6 or S7 and experience frequent slowdowns while playing, it is recommended you download the Game Tuner app (https://play.google.com/store/apps/details?id=com.samsung.android.gametuner.thin&hl=en) and reduce the resolution of the game to 50% or less.
If you are on a Galaxy S6 or S7 and experience frequent slowdowns while playing, it is recommended you download the Game Tuner app (https://play.google.com/store/apps/details?id=com.samsung.android.gametuner.thin&hl=en) and reduce the resolution of the game to 50% or less.
=MasterDataVersions=
This file is located under <code>/SD/Android/data/jp.co.lifewonders.housamo/files/Data/</code>, its function specifically is unknown, but bits and pieces can be gleaned from unexpected behavior [[Bugs#Malformed_Cache|here]]. In this file is simply a number.
Under [https://twitter.com/housamo_xyz_bot/status/919356671734042624 this malformed state], the game cannot function properly, as damage, and buffs/debuffs, fail to process. Through the "fix" [[Bugs#Malformed_Cache|here]], it sheds some light that a mismatched <code>MasterDataVersions</code> and <code>/SD/Android/data/jp.co.lifewonders.housamo/files/MasterDatas/</code> caused this.
An out-of-date <code>MasterDataVersions</code> and an in-date <code>MasterDatas</code> (say, from an old backup with your AuthKey on an updated copy of the game) will simply update <code>MasterDataVersions</code>, while, unfortunately, an out-of-date <code>MasterDataVersions</code> (say, from any copy of your AuthKey and an old/too fresh copy of the game) will do nothing except soft-brick.
The steps to (possibly) recreate this malformed state is as followed:
* From an already initialized system, copy everything from <code>/SD/Android/data/jp.co.lifewonders.housamo/files/Data/</code> into a safe place.
* From a clean slate, open the app.t
* Sometime during initialization / account creation, close the app.
* Return to <code>/SD/Android/data/jp.co.lifewonders.housamo/files/Data/</code> and replace it with the copy from earlier
* Start the app again, and enjoy.
While this is dependent on the contents of <code>MasterDatas</code>, it paves way to client-side modification and exploitation of the game through in-battles to ease/aid completion.
{{Guide}}
{{Guide}}
Retrieved from "https://housamo.wiki/Special:MobileDiff/15294...24269"

Navigation menu