Poison

A counter goes up by 1 on every beat. When it reaches 10 the passive publishes one hit and resets the counter, so Poison hits once every 10 seconds. The hit is the unit's Max Health x the Poison stack count x 0.01, as a fixed value with no damage type.

When it runs: The passive subscribes to the game's logical refresh beat (once a second at normal speed) while the effect sits on the unit.

What it applies to: The unit carrying the effect. The hit has no damage type, so neither physical nor magic resistance applies to it.

Things the tooltip does not tell you

• The 1 percent is a constant in the method, multiplied by the stack count. The row's FloatValues (1) are not read, so the tooltip's number only matches the code by coincidence.
• The shipped English tooltip says magic damage every second. The code and the Korean design note both say typeless damage every 10 seconds.
• Stacking: the generic affecter applier adds new stacks up to the row's MaxStack (100) for a unit that already has Poison, and nothing special-cases Poison, so the design note's 'cannot stack' does not hold in code. Each stack adds 1 percent of Max Health to the hit.
• No skill row, trait or code path applies Poison in this build: the AFFECTER_Poison literal is loaded only by the immunity check and the Liquid Monster passive.
• Since build 25846389 the 10 second counter is not reset when the effect is carried over to a new map, so the next hit keeps its timing. A fresh Poison still starts at 0. The flag is PassiveAction.IsTransferAttach (+0x51), new in this build. Its name and the v0.4.29 patch note ('progress states and internal timers ... not reset when moving between the settlement and dungeons') say it is set when the passive is re-attached by a map transfer. No direct call to its setter was found in the slice (the write is inlined), so the exact moments it is set were not traced.

Read out of the game binary of build 25846389. AFFECTER_Poison.Passive_Poison.OnEnable@0x96BBB4, AFFECTER_Poison.Passive_Poison.Damage@0x96BDB4, AFFECTER_Poison.Passive_Poison.<DamageRoutine>d__5.MoveNext@0x96BF04, Refactor.Tick.DataApply.AffecterApplier.Apply@0xAB0634