I can't give the complete code due to it being a part of my new secret project...
However:
The character uses some ice attacks. Actuall, i managed to store all his 4 moves in a single file.
After i added the 4th move, a strange bug started to occur: Whenever the T3 (file) was summoned, some ice shards were spawned, completely regardless of the state or frame number.
Looked quite nice for some moves, but one of them spawned multiple versions of this file with some nice star effects... now it spawned hundreds of ice shards instead XD
I looked at the Data, made a random pick and WTFGDH found the error on the first try:
Frame 0 had state 13 (Frozen). I set the state back to 15 and voila, the bug disappeared.
Seems like frame 0 is some kind of "main frame" for an object, regardless on which action it's summoned. And since state: 13 seems to be (hardcoded) somewhat related to the broken ice shards effect from frame 202, this strange bug occurs.
I tested multiple files, the bug does ALWAYS occur (for T3s) if the frame 0 contains a state: 13.
You're free to test/replicate the bug for yourself ^^
Dunno whether somebody could actually get a use of it...
But it's a prove for LF2 still having it's secrets
However:
The character uses some ice attacks. Actuall, i managed to store all his 4 moves in a single file.
After i added the 4th move, a strange bug started to occur: Whenever the T3 (file) was summoned, some ice shards were spawned, completely regardless of the state or frame number.
Looked quite nice for some moves, but one of them spawned multiple versions of this file with some nice star effects... now it spawned hundreds of ice shards instead XD
I looked at the Data, made a random pick and WTFGDH found the error on the first try:
Frame 0 had state 13 (Frozen). I set the state back to 15 and voila, the bug disappeared.
Seems like frame 0 is some kind of "main frame" for an object, regardless on which action it's summoned. And since state: 13 seems to be (hardcoded) somewhat related to the broken ice shards effect from frame 202, this strange bug occurs.
I tested multiple files, the bug does ALWAYS occur (for T3s) if the frame 0 contains a state: 13.
You're free to test/replicate the bug for yourself ^^
Dunno whether somebody could actually get a use of it...
But it's a prove for LF2 still having it's secrets

My Creations: (Click to View)
Return (String) System.getNewsOfTheDay();
Barely active, expect slow responses. If at all.
Greetz,
Alblaka