Topic: Petit Computer

ahh, thanks but I forgot to mention... in my game I cannot use VSYNC or WAIT. Is it even possible to make a timer without it?

ok take out the waits and just make it so when it reaches a higher number it does it. put in a vsync 1. it wont hurt it. ex:
@START
TIME=1
@TIMER
PRINT ""TIME""
TIME=TIME+1
IF TIME==120(one minute) THEN DO SOMETHING
VSYNC 1
GOTO @TIMER

I really appreciate the help, but in this case a VSYNC 1 would hurt. In my game the player taps as fast as they can, if I use VSYNC at all, even VSYNC 0.01, the player can't tap nearly as fast.

@Leviceljir I couldn't not show you.

oh ok

@noxuss a timer and practically anything is near impossible with VSYNC 1
VSYNC 1 just keeps it from flickering and stuff
try this code:
ACLS:CLEAR
@LOOP
<insert code>
TIME=TIME+0.1
?FLOOR(TIME)
VSYNC 1
GOTO @LOOP
change the 0.1 to whatever number you want

Sadly I figured that. I found out a few ways to do timers, but they all need vsync. is there anyway to use VSYNC and still let the player tap as fast as they want?

the player can still tap as fast as they want the VSYNC just stops flickering and stuff and makes a timer possible
if it doesn't work then i'm going to need some code

You can also make a timer by using the MAINCOUNTL system variable and not use VSYNC at all.

EDIT: @Hansausage about a GLSL shader algorithm in Minecraft DS. NO

Can you? would you mind giving me an example, with a 1 second timer?

Can you? would you mind giving me an example, with a 1 second timer?

@noxuss

@LOOP

your code here

IF MAINCOUNTL>=NEXTCOUNT THEN NEXTCOUNT=MAINCOUNTL+60:TIMER=TIMER+1

GOTO @LOOP

LOCATE 0,0:?TIMER

This is untested, but I believe it'll work. The timer increments by 1 each second.

AOTTG progress update:
i added a few cutscenes to the boss battles and they look great so far. i'm also making a lot of improvements to the titans (specifically bosses) and now they're near impossible if you make one mistake >:3 if you get hit by the armoured titan while it's running then you get knocked on the ground (or die) and get stunned for a bit and it keeps running and keeps hitting you so basically if the armoured titan hits you you're dead. the colossal titan has really slow (like 250 frames) but deadly attacks. it doesn't matter which character you are it will still kill you with one hit.
i've also been working on sprites a lot and i decided to make the colossal titan a combination of sprites and graphics, and the sprites are just the face and they're 64x64 so they're really detailed so it's 15x scarier than before
i'm also adding more detail to the backgrounds and lots of new special effects. i'm also experimenting with a sound system so if you're closer to the noise it's louder and if you're farther it's more quiet. right now i only have it working for the swords when you drop them.
tl;dr the game is going great and it may be released soon
EDIT: i'm also trying to get screenshots working but it may take some time due to having so many large sprites but when i get it working so it's not just the player i'll post a screenshot of the colossal titan

This makes sense, I'll try it in a minute. Also should NEXTCOUNT start at 0?

yeah just put a CLEAR command at the start of the program

Yesss, I got it working relative to my program, thanks

Guys, I demand you to fix my problems. hehe, jk, but I do need help. I need to know why when I "purchase" an ingame item and take away the current money (corn), the display of it is extremely weird.

Here's the qr to test it out. AFKCORN means how much corn is given without clicking per second.

SPQRs:

PRGQR:

@JLMan nope. Thats not how it works. It does go by number of frames elapsed, but thats not how many frames are drawn. Thats why MAINCOUNTL is used for FPS systems

Can someone tell me why this happens. The player has 150 dollars and they buy an item that costs 150, and now the money is displayed as 050. I used a floor commands to round it up, since you earn money by decimals, so the 050 means 0.5. anyone to make this simply say 0? It really bugs me.

once again, we're going to need to see some code so we know what you're doing wrong