Tower of Heaven fan

Surprised there's no setting or version that makes it blow downward instead...

Where insert this code?: [JSL TOHFan_TowerOfHeavenFan] in what .asm or document text? In Uber or GPS?

While it would be easier to ask, it is likely better to try it out yourself. Also, if you know how to edit the code, making a down version should be relatively easy.

Can you make a down version of this, compatible with swimming? Also does this work under water?

Note to anyone interested in making blocks that would execute once per frame: When multiple collision points are touching the block, they all execute in a single frame. Thus a single increment by 1 could have all 10 increments in a single frame, causing an increment of 10 per frame instead of 1, this is why uberasm tool, as well as cooldown timers are needed to prevent multi-activation.

Worked fine. Accepted.

Cool!

tbh if a block is inefficiently coded to the point of using uberASM code when it's not needed at all, I question if it's worth accepting.

i cant get the uberasm to work so i guess i'm not using this block

@chineesmw

Wind blocks does not accelerate. My fan blocks leave the player with momentum after leaving the block.

What's the difference between this and the Wind Blocks?

Sorry. It's because that when using all offsets of a block, the acceleration is more rapid. This is because touching multiple offsets would execute the block's code multiple times per frame.
EDIT: Also, for the sound effects, blocks can't really tell if the sound is currently playing and also cannot detect when you leave the block, therefore, uberasm and freeram is needed.

I'll update it to reuse the same byte, the bit idea was a smart move.

So... this block.
It works so I accepted it but I'm really not happy with it.

The code doesn't seem to work on gamemode14 at all. Either that or I'm just doing it wrong but I know for a fact that changes to $15 in gamemode14 have no effect since it runs before the controller is updated, so the whole...



... is useless in gamemode14. While on that topic, why not put the LDA inside the if?
Anyway, putting minor coding related things aside (such as using BRA .return instead of just RTS) I have two real problems with this code:

1. The wast of a freeRAM. If all you're doing is using freeRAM as a flag to check if something has happened (LDA !flag : BEQ .skip) you really don't need a second freeRAM address, just set the bits of the first address for different meanings:

!Freeram_Fanned = $60 ; ---- --si
; i=inside block
; s=sfx played

2. The use of uberASM. I know there are certain things you can't do using just block code, but here it just seems wasteful. Basically, all your block does is set a flag and let uberASM do all the rest. This is more of a personal oppinion but I always hate it when I download a block and see if I have to patch something else to make it work.
Anyway, back to topic, in this blocks case, I don't get it. Since, if you remove the SFX sound effect (which gets pretty anoying after a while anyway) you can do everything inside the block code without using uberASM at all, by simply copying the code between .AccelUp and .OffRan to where LDA #$01 : STA !Freeram_Fanned is.
Not only does that remove the need for uberASM but also for any freeRAM..

Gotta admit though, with the SFX, you probably need it. Even so, I'd like this a lot more if the code was layouted in a way that the block works on it's own and you have the option to use freeRAM + uberASM for the sound effect.

Good block

GHB, i'm your fan