Talk:Sealed/@comment-5672532-20130211044755/@comment-5672532-20130211060729

Well, that implies that it knows each hseanwave parameter so much that it can just cut to whatever variable is called - I suppose you could end up creating a new variable past the highest called, and see what running *hseanwave does?

For the latter: I'm confused as to why *damage is a subroutine, or where it's properly calculated. In theory, could that mean we just run damage and an increasing multiplier, or does MGQ not handle those - or do we even know?