I COULD give you the extra-long code on request, but for now you'll get a text-form.
I've spent 2 hours now on hunting after a quite complicated bug.
What's meant to happen: Character obtains a upgrade (T3 following character via k8). Character uses Move A, whilst the wind-up, he spawns a T0bdy. The upgrade reacts to this T0bdy by spawning another T0bdy. Character reacts to this 2nd T0bdy and performs an upgraded move.
I seriously got no clue why, but the T3 will not react to the character-spawned T0bdy (upon wind-up) EXCEPT
and that's the ludicrous point
the character performed Move A directly after rowing.
Even more random, the direction of the rowing doesn't matter (<<, <>, >>, >< the combination of facing of the D>J move and rowing dont matter).
I sort of ran out of ideas where this bug could be located.
The fact it can only be done whilst rowing indicates the dvx after the rowing frames has an important effect... I double checked the x-bounds, there shouldn't be any issue.
My current guess is something along object priority, with the latter k8 "sticktocharacter" blocking the former k8 "reacttomoveAbdy"
edit: Damnit, definitely that sort of issue...
If I disable the sticking-effect, everything works fine...
editedit:
Created a 2-frame loop of 1-tick sticky and x tick check. Works, though it makes the sticky upgrade effect somewhat 'laggy'... Would prefer a real solution if somebody knows this issue.
I've spent 2 hours now on hunting after a quite complicated bug.
What's meant to happen: Character obtains a upgrade (T3 following character via k8). Character uses Move A, whilst the wind-up, he spawns a T0bdy. The upgrade reacts to this T0bdy by spawning another T0bdy. Character reacts to this 2nd T0bdy and performs an upgraded move.
I seriously got no clue why, but the T3 will not react to the character-spawned T0bdy (upon wind-up) EXCEPT
and that's the ludicrous point
the character performed Move A directly after rowing.
Even more random, the direction of the rowing doesn't matter (<<, <>, >>, >< the combination of facing of the D>J move and rowing dont matter).
I sort of ran out of ideas where this bug could be located.
The fact it can only be done whilst rowing indicates the dvx after the rowing frames has an important effect... I double checked the x-bounds, there shouldn't be any issue.
My current guess is something along object priority, with the latter k8 "sticktocharacter" blocking the former k8 "reacttomoveAbdy"
edit: Damnit, definitely that sort of issue...
If I disable the sticking-effect, everything works fine...
editedit:
Created a 2-frame loop of 1-tick sticky and x tick check. Works, though it makes the sticky upgrade effect somewhat 'laggy'... Would prefer a real solution if somebody knows this issue.
My Creations: (Click to View)
Return (String) System.getNewsOfTheDay();
Barely active, expect slow responses. If at all.
Greetz,
Alblaka