@faz808 Well you inspired me to do it and found that rather excellent tutorial so without you it wouldn't have happened. I still need to figure out why longer codes aren't working and sometimes byte encoding even with shorter ones. As I said the 2 references do not always produce the same results even though both work! This seems odd to me unless it is just the error correction kicking in

@waldron said in Twin Stick Shooter 'Fuzeotron': So is this finished now? can i finally share with you my other idea..... jk jk look forward to playing this later :) I hope so, sick of seeing it and I have other things I want to do. Hopefully this wont have any issues and I can then do the alternate graphics version.

No, nothing wrong, but you asked about the code blocks and it's all in there :)

New texture added. wolfy-ceiling3 ID: XDXS2MND15

That's an expensive signed photo and tour :D

@waldron . Thanks, I didn't know that although I was aware of the power of 2 thing wrt terrains. Still, it would be nice to know if it is getting fixed. Terrains too for that matter.

If I can tack on to the wish list: The object groups are already very powerful. Could I suggest: that all objects in object group can be removed with single command (e.g., removeObject) that objects in a group can be accessed, perhaps as though the object group is like an array Both of these tweaks would take a nice load off of "manual bookkeeping".

I found it in the italian eshop so i think that you are good in eu countryes but outside can be problematic

@waldron In case you're complimenting the implementation, then: thank you 😊 But of course, as the game title suggests, the credits for the idea go to the mathematician John Conway (1937 - 2020).

So A month is over In may i tried to finish the veriables. What we have now: Now we have some simple if statements A simple for loop While True And a hopefully working print function Some stuff works some stuff is a bit buggy. I also stoped developing on my interpretor. I think i will teach me How to build a good tokenizer. Also I see a big problem that we dont have functions like list() I think I have to write for almost everything a workaround. But I am looking forward to future updates of fuze which hopefully will take some work. So you can download the latest "stable version" with my sharecode. You can find it on this page or on the great list of game codes. I want to really do this project. I say thanks to the people who helped me with this. I am also thinking about building an own programming language in fuze cause then i wouldnt had to keep close to the python syntaxt. Next Post will come next month between the next post enjoy the projects here see you David

@DomDom hahaa no your correct im a big noel edmunds fan and that is in fact mister blobbly XD

Title: Missing Mike & the Many Coincidences Description: A short narrative adventure as a private eye. ID: NXU84DND1Y https://fuzearena.com/forum/topic/1217/missing-mike/17

@AtomAlexander @JonnyLaw It’s shared now ID: DV8Q3MND1Y

@lawyerlounge you CAN draw them pixel by pixel in the editor but when I greeted myself with the editor it was unwelcoming and just something else I had to understand and wrap my mind around which is what led me to finding the work around. If you check one of my last posts that was a reply to pianofire you can see that this method allows for animation of the sprites as well I'm just not understanding how to do it completely but I've only had Fuze4 for about a week so it's probably natural I don't understand how to do it yet. I am not a fan of image editing to begin with, I don't have a mouse and keyboard set up, and so on and so forth. Everything you are seeing is being done with the onscreen keyboard. The image editor using the analog sticks didn't seem "smart" or like a good idea to me because if the stick moves your pixel is then out of place. Setting it up using the arrays guarantees that your pixel is being placed EXACTLY where you want it. Personally I think the issue is a matter of opinion on which method is better or easier to use. I could see people being able to implement the image editor in a manner that works for them but it's just more learning I have to do to crank out artwork that otherwise can be cranked out using my method that I already know how to use, somewhat. The only thing I am lacking is an understanding of the coding involved in the animation process using this method.

@Willpowered said in Smile Basic: @niconii Haven't tested the following code, but I think these changes to your game loop might speed it up slightly (with some inline comment explanations): unfortunately the opposite seems to happen, dropping the fps down to 25 or so... i even tried applying just the advice about changing sprites[i] to s but it seemed to drop the fps a small amount. perhaps s = sprites[i] copies the sprite handle and is somewhat slow as a result, but i don't know much about fuze's internals so that's just speculation on my part i know this talk of benchmarks is getting on some people's nerves, but i think both the smilebasic and fuze programs are about as optimized as they're going to get now (at least i don't expect more than a 2~3 fps increase), so don't worry, i'll move on from this topic now the final results for the time being are ~218 fps for smilebasic and ~40 fps for fuze: i look forward to fuze's bytecode compiler once it's ready, and i'll revisit this benchmark at that time