I noticed that in gothon’s code, there’s

pf = {f.z, 0, -f.x}

Whereas in the blog post I linked, she has

Camright = (-camForward.z, 0.0f, camForward.x)

I’m guessing the difference in which ones are reversed with the - sign is something to do with ‘right-handed’ or ‘left-handed’ coordinate system.

This is a thing which tripped me up/confused me for a while. Just wanted to highlight it.

I think it might have been a bug. Because it was the exact same code as the tutorial. So then i copied the code from the tutorial and it was exactly the same but it worked. Not sure why???

"\n" is the escape code for a new line character, but I noticed in a program of mine that it generated an extra character of white space. It seems it actually generates a linefeed and a space character chr(32) + chr(10), so I am not surprised that if k == "\n" then ... doesn't work for reading the keystroke.

Request for 'continue' duly noted - there's no petitioning for new features :)

In the meantime:

example_list = [1, 1, 0, 1, 1, 1, 0, 1, 0, 1] still_zeros = True while still_zeros loop for index = 0 to len(example_list) loop if example_list[index] == 0 then example_list[index] == 1 break //This breaks out of the for loop, but not the while loop endif repeat // index will only get to equal len(example_list) if it // got all the way through without finding any more zeros to replace if index == len(example_list) then still_zeros = false endif repeat

I'm not at my switch at present but doesn't that simplify things somewhat?
NB: If the loop isn't iterating over as you might expect try adding int index = 0 just before the for loop. It sounds counter-intuitive but Fuze has needed it up until now due to scoping issues. I haven't tested yet if that is still the case in the latest patch.

Just start off with one plain room, one enemy, and one player sprite, and work out from there. A top down zelda game is totally doable in fuze :)

Ok i will check that out and test if i can do the bullet board (enemy turn) and the dialog/menu(player turn) with that but idk if i could just colide with a location lets say like corners x 50 and 100 and y 4 and 36 so i could collide with the location itself instead of the box()

Thx @toxibunny it worked also i just copy paste it i isn't that much to write with repetitive parterns :)

Ps ty @toxibunny too i will see if is bether the way that you or waldron showed me for now thanks you two

Thanks I’ll try it out

Yes exactly like that.

@waldron i appreciate that guidance. I will do it like this.

I think you want something like:

setSpriteSpeed (plr,100*c.lx,-100*c.ly)

Though 100 seems fast, but is in line with what you had.

@toxibunny That's great!
I actually also do the global array of structs approach. For my functions that manipulate an individual entity/object, I just pass the array index as an argument. Then I manipulate the strict within the global array itself, without needing to worry about copying structs.
That works well in my game, too, without me noticing or measuring any real performance penalty.

@pianofire I normally wouldn't remember any score. But recently I played it on an arcade cabinet one of my bros built, and I had the "local" high score for a 2 days. Haha.

Good spot! I overlooked that. But yeah, I guess since the highest 3 bits are not being used for the actual morse then maybe they could be used to indicate the number of leading zeros? I think that would work?

That’s the way I would have done it if I’d remembered how. I like the way spt suggested though. The ’lock’ metaphor is easy to remember.