Difference between revisions of "Tips"
| Line 2: | Line 2: | ||
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). | 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| | 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, [[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| | 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= | ||
Revision as of 15:28, 27 May 2018
s vs Higher Rarities
A lot of units share the same (or very similar) skill sets across rarities. For example, 
Arsalan, 
Choji, and 
Triton are the exact same across rarities, just different costs and base stats. Because of this, it might seem that raising his 
is the way to go, but in reality, focusing on his 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 
Shiro who slightly have different skills. On paper, it seems like his 's [Phase Start] CP gain 100% of the time is a good thing, and having his 's [After Moving] skill seems kind of pointless. However, due to how [When Attacking] skills are handled during a Charge, "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.</br></br>However, you have units like [[SMW" contains a listed "[" character as part of the property label and has therefore been classified as invalid.
Snow, 
Aizen, and now 
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 s.
When it comes to units with beneficial [When Attacking] different weapon spreads like 
Agyo and 
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, Agyo's and Benten's cards are better than their other forms, as they both have a wider weapon spread.
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 use units that looks nice adage is actually the way to go.
Additionally, recommending what units to use essentially boils down to "don't use this one", as, again, good units only shine in their late game. Harder quests only really exist as a challenge for veteran players who do have the units ready to tackle. New players simply lack a wide spread of units to pick and choose from, and Events typically give what you need through an Event unit or units with the focused skill in a gacha.
In short, if you're a new player, you don't have to worry about "playing right", just "playing wrong".
Transferring Your Data
Smart Way
To create a transfer code data, simply start up the game, go past the title screen to the map, and go to Options(オプション) on the bottom menu. Then hit Transfer Data (データ引継ぎ) in the middle left. Enter a password into both boxes of your choosing (English letters only) and hit the bottom-most button. Write down the Code it gives you AND the password you used. When you're ready or need to use it, start up the game. At the Title Screen, hit the blue button (Account Transfer) on the bottom left. Enter the Code in the top box, and your custom password you made in the bottom box. Then hit the green button.
Since the version 3.1.3, the transfer codes expire after 14 days, so this is not a fully reliable way to keep your account backed up in case of phone data damage or a lost phone. It is recommended you keep your User ID handy and ask for help with contacting the developers in such an event. Or, recover your account using your AuthKey.
Risky Easy Way
Unlike using the transfer system as a way to recover data, on Android devices under /SD/Android/data/jp.co.lifewonders.housamo/files/Data/ is a file labelled AuthKey; this key is used to keep track of account information, and is used to transfer between devices (all the device transfer option does is remove the AuthKey from your device and write it to the new device). You can back this file up onto cold storage, but there's no guarantee that it'll work on further versions.
For iOS, it is unknown where exactly the app stores
AuthKey.
As of February 4, 2018. For iOS, the AuthKey location has been found and does not require jail-breaking your phone. However it requires two application tools TweakBox and FilzaEscaped in order for it to work. The AuthKey location is under /var/mobile/Containers/Data/Application/jp.co.lifewonders.housamo/Documents/Data.
Cross-Authkeys are verified to be possible as well. This will save issues for players who want to change new phone brands or devices altogether.
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.
AuthKey
You can also copy AuthKey to allow access to the same account on multiple devices, even at the same time (note: you can't abuse this to get double the rewards from a quest, but who knows what other bugs and """exploits""" may be possible).
On the flip side, you can also store multiple accounts on the same device; just back up your AuthKey and reload the app to create a new """account""".
Avoiding the initial grind
Expanding on the use of making the best use out of that AuthKey file; you're guaranteed 10 stones to get 2 companions with; although, you need to keep going through the tutorial and first battle again and again. Didn't get the companion you want? Just delete the AuthKey instead of deleting app data (deleting app data causes you to lose assets downloaded if you do this, but by clearing the AuthKey, you still keep your cache).
Restarting a battle with no AP loss
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.
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.
Technical Workings Under the Hood
From current understanding, on Android devices, the app stores game information and data under /SD/Android/data/jp.co.lifewonders.housamo/files/MasterDatas/ as base64 encoded strings; however, whether or not these files are further encrypted or obfuscated is unknown as well.
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.
MasterDataVersions
This file is located under /SD/Android/data/jp.co.lifewonders.housamo/files/Data/, its function specifically is unknown, but bits and pieces can be gleaned from unexpected behavior here. In this file is simply a number.
Under this malformed state, the game cannot function properly, as damage, and buffs/debuffs, fail to process. Through the "fix" here, it sheds some light that a mismatched MasterDataVersions and /SD/Android/data/jp.co.lifewonders.housamo/files/MasterDatas/ caused this.
An out-of-date MasterDataVersions and an in-date MasterDatas (say, from an old backup with your AuthKey on an updated copy of the game) will simply update MasterDataVersions, while, unfortunately, an out-of-date MasterDataVersions (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
/SD/Android/data/jp.co.lifewonders.housamo/files/Data/into a safe place. - From a clean slate, open the app.t
- Sometime during initialization / account creation, close the app.
- Return to
/SD/Android/data/jp.co.lifewonders.housamo/files/Data/and replace it with the copy from earlier - Start the app again, and enjoy.
While this is dependent on the contents of MasterDatas, it paves way to client-side modification and exploitation of the game through in-battles to ease/aid completion.
9 comments
[Show Comments]
The stories and information posted here are artistic works of fiction and falsehood. Only a fool would take anything posted here as fact.
Enable comment auto-refresher
Permalink |
Permalink |
Permalink |
Permalink |
Permalink |
Permalink |
Permalink |
Permalink |
Permalink |