Amiibo drops: Difference between revisions
Jump to navigation
Jump to search
→ItemAmiiboCreateFromDropTable::enter
imported>Leoetlino No edit summary |
imported>Leoetlino |
||
| Line 29: | Line 29: | ||
**Finally, AmiiboLastTouchDate is set to <code>10000 * now.year + 100 * now.month + now.day</code>. | **Finally, AmiiboLastTouchDate is set to <code>10000 * now.year + 100 * now.month + now.day</code>. | ||
== ItemAmiiboCreateFromDropTable: | == Logic == | ||
* | [[AIDef:Action/ItemAmiiboCreateFromDropTable]] (the action that is responsible for determining the drop table and spawning the drops) follows the following process: | ||
* | *Get the number of times the amiibo has been scanned for the current day (using AmiiboTouchHistory). | ||
* ... | *Get the number of times the amiibo has been scanned (using AmiiboTouchHistoryTotal). | ||
*Determine the drop table category to use. | |||
**''Remain'' if Find_4Relic_1stClear is set | |||
**''Parasail'' if IsGet_PlayerStole2 is set | |||
**''Normal'' otherwise | |||
*Determine the "adjust rate". | |||
**When the amiibo has been scanned 0 to $HitRateAdjustStart times, the adjust rate is 0%. | |||
**This value increases linearly and reaches its maximum (100%) when the amiibo scan count is >= $HitRateAdjustEnd. | |||
**In practice, because HitRateAdjustStart and HitRateAdjustEnd are both set to the same value (5), the formula can be simplified: the rate is 100% if the scan count >= $HitRateAdjustEnd and 0% otherwise. | |||
== References == | == References == | ||