| 1 |
[q]Units always drop debris or a wreck. There is no 'colossal damage' category. The observations about Dgun dealing colossal damage in the previous thread are most likely because Dgun deals massive damage over a few frames, so kills the debris shortly after it is created. There may be a few outdated scripts where this is untrue, or a bug.[/q]
|
1 |
[q]Units always drop debris or a wreck. There is no 'colossal damage' category. The observations about Dgun dealing colossal damage in the previous thread are most likely because Dgun deals massive damage over a few frames, so kills the debris shortly after it is created. There may be a few outdated scripts where this is untrue, or a bug.[/q]
|
| 2 |
\n
|
2 |
\n
|
| 3 |
A welcome insight, thanks.
|
3 |
A welcome insight, thanks.
|
| 4 |
\n
|
4 |
\n
|
| 5 |
\n
|
5 |
\n
|
| 6 |
[q]Whether a unit turns into debris or a wreck is determined by a variable called 'recentDamage', not the just the last instance. I never learnt the details of this, it will be something deep in the engine.[/q]
|
6 |
[q]Whether a unit turns into debris or a wreck is determined by a variable called 'recentDamage', not the just the last instance. I never learnt the details of this, it will be something deep in the engine.[/q]
|
| 7 |
\n
|
7 |
\n
|
| 8 |
This is surprising in all regards. I was pretty sure that at least SOMEONE should know every line of code in ZK, and the most probable person is none other than you. (Yes I know that Spring and ZK are different things by different devs)
|
8 |
This is surprising in all regards. I was pretty sure that at least SOMEONE should know every line of code in ZK, and the most probable person is none other than you. (Yes I know that Spring and ZK are different things by different devs)
|
| 9 |
\n
|
9 |
\n
|
| 10 |
[q]Units that have never been completed return 100% their metal value when reclaimed.[/q]
|
10 |
[q]Units that have never been completed return 100% their metal value when reclaimed.[/q]
|
| 11 |
\n
|
11 |
\n
|
| 12 |
Your sentence carries an important ambiguity in regards to whereabouts of a unit.
|
12 |
Your sentence carries an important ambiguity in regards to whereabouts of a unit.
|
|
|
13 |
\n
|
| 13 |
[i]Edit: I have thought it out, and its not ambiguous, it is just wrong, and harmfully so. Imagine some noob reclaiming an almost finished Detriment thinking he would get his, e.g. 20000 of 24000 metal back.[/i]
|
14 |
[i]Edit: I have thought it out, and its not ambiguous, it is just wrong, and harmfully so. Imagine some noob reclaiming an almost finished Detriment thinking he would get his, e.g. 20000 of 24000 metal back.[/i]
|
|
|
15 |
\n
|
| 14 |
It is absolutely crucial whether an unit is being made at factory or plate or it is being made via Stride Hub or Athena.
|
16 |
It is absolutely crucial whether an unit is being made at factory or plate or it is being made via Stride Hub or Athena.
|
|
|
17 |
\n
|
| 15 |
In the first case, unit nanoframe is clearly associated with that factory or plate, is destroyed when factory or plate is destroyed, and returns 100% of metal value when cancelled. Cancel is an independent mechanic from reclaim, and cancel amounts to just clicking a button on unit roster tab.
|
18 |
In the first case, unit nanoframe is clearly associated with that factory or plate, is destroyed when factory or plate is destroyed, and returns 100% of metal value when cancelled. Cancel is an independent mechanic from reclaim, and cancel amounts to just clicking a button on unit roster tab.
|
| 16 |
\n
|
19 |
\n
|
| 17 |
When Strider Hub, or Athena plops a nanoframe, and then metal is feeded into it, and then nanoframe is reclaimed - you get 50% of value, in all cases. NANOFRAME ALWAYS RETURNS 50% when reclaimed. Also, when reclaimng ANYTHING, you can NEVER get 100% return.
|
20 |
When Strider Hub, or Athena plops a nanoframe, and then metal is feeded into it, and then nanoframe is reclaimed - you get 50% of value, in all cases. NANOFRAME ALWAYS RETURNS 50% when reclaimed. Also, when reclaimng ANYTHING, you can NEVER get 100% return.
|
Wreck values