Read-only archive of the Armageddon Games Forums Archive (2000–2026) · About this archive

FFC sensitivity and Change in Behavior re: Full Screen Warp

4 replies · 1,449 views · Started 16 October 2006

I've got a new concern.

Freeform combos seem to be VERY persnickity about whether they're touching an attribute changing FFC or not. For instance, if the FFC is moving sufficently fast, it can blow right past them without even registering. Some of this sensitivity is nice, as it allows you to set up complex "figure 8s" and such by slightly off-setting one portion of the figure 8. But it makes complex movement that isn't horizontal or vertical a challange.

Second, FFCs seem to act bizzarely when you full-screen warp to the screen they are on. For example: I have a room set up surrounded by traps. Link steps into the room and he's instawarped to a boss room where the traps are supposed to slide into the center and back out ala' the boss of the Dark Woods in LttP, Mothra or whatever. What actually happens is they trigger immediately, without waiting the 250 ticks or so. One of the traps even ignores the att chg FFC that is supposed to make it return to the border, and shoots off to infinity. In the editor, they behave appropriately, sequentially moving in and out.

Some scripting can probably replace the use of att chg FFCs, but they're so simple to use that I'd rather they worked predictibley.

Freeform combos seem to be VERY persnickity about whether they're touching an attribute changing FFC or not. For instance, if the FFC is moving sufficently fast, it can blow right past them without even registering.
It was mentioned earlier that their X and Y values must match exactly.

Right, but this limits the top speed for FFCs. At some speed, it seems like they move from a to c without even registering that they went over b. Moving more than one pixel at a time, I guess. This leads to odd behavior. For instance, if an FFC is traveling East at a high speed with a Y coordinate of 100, it may well entirely ignore an att chg FFC placed on Y coordinate 100 because it "hopped" over it. This behavior can be corrected by doing some math (where am I starting from, how many pixels am I moving, etc) and trial and error. But the behavior will probably be confusing to some users.

Update

C-Dawg wrote:"FFC sensitivity and Change in Behavior re: Full Screen Warp" - Not a bug?
This is probably more of a suggestion on changing how high-speed FFCs react to changers.

I fixed FFC changer interaction a while ago - FFCs should detect the changer as long as their path of motion takes the *exactly* over the changer. So, for instance, an FFC at (10,10) with an x velocity of 100 should detect the changer at (20,10).

Post a test quest if you have a situation where this behavior isn't respected.