Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs

StinkerB06

16
Posts
1
Topics
A member registered Feb 21, 2018 · View creator page →

Recent community posts

  1. The clip() function just limits the drawing area of the the other drawing functions. You give it two coordinates (X and Y) specifying where the top-left corner of the drawing rectangle is located, and two size parameters (W and H) specifying its width and height, in pixels. After this call is made, subsequent drawing function-calls get limited to being drawn in the area specified by the rectangle, with all other pixels outside of it not being updated at all. This leaves quite a bit of border around the game when using clip() to emulate a smaller resolution.
  2. After loading a cart using `load`, press F1 to go into the code editor. You can see how the cart's author coded the whole thing.
  3. The TIC-80 is completely open-source under the MIT license, which means you can make your own mod of TIC-80, free of permission from nesbox.
(1 edit)

They are eight general-purpose flags assigned to each sprite individually, used for whatever purpose by your game. PICO-8 already has something similar, but there isn't any part of the TIC-80 API that has yet to do anything with these sprite flags (other than peek/poke).

Here's some sample code for you:

function fget(sprID,bit)
 return peek(0x14000+sprID)>>bit&1==1
end
function fset(sprID,bit,flag)
 local old=peek(0x14000+sprID)
 poke(0x14000+sprID,flag and old|(1<<bit) or old&~(1<<bit))
end

What was the TIC-80 snap all about? When I access its page, it says 404.

Type 3 (cover) is essentially a GIF image file. You can just copy any GIF image's binary data you want, as long as it's less than 65536 bytes. (Nesbox was wrong, only 2 bytes for size are actually being read, the 3rd byte is unused.)

Type 5 (code) is plain text. All other valid types are based on the TIC-80 RAM layouts for each of those assets.

Useful wiki pages:

https://github.com/nesbox/TIC-80/wiki/tic-File-Format
https://github.com/nesbox/TIC-80/wiki/RAM

Can you publish this on https://tic.computer?

What are your PC specs?

And I also find that the demo level of this is way harder for me. Stele, a copy of this game with different graphics and without the editors, I can beat more quicker. It requires VERY PRECISE timing in order to get past the spikes, because 99% of the time, I miss those green balls that make you reach the green heart and finish the level. TIC-80 really needs savestate support!

I wonder why you never released this on the TIC-80 website before Stele was released.

Do you have the *.tic file for this game? When I try to download the cart using the get command, it says file not downloaded :|.

I just want to play this outside of my browser.

There's textri() function now for rendering textured polygon triangles

Make a 32-bit Windows download

I suck at this game

What do you mean?

(1 edit)

Decide on your fantasy console's specifications. Include control input, graphics and audio capabilities.

The editors need at least some code or assembly language editor, a graphics editor, a map editor, and audio editors. There should be some command shell, and maybe a BASIC included.

You can reply to me all of your planned specifications here.

Also make your fantasy console support 32-bit

What do you mean? A TIC-80 game or a fantasy console that competes with TIC-80?

The PSP can operate up to a 333MHz CPU, and has a 480x272 screen, which I also thought it being four times the size of TIC-80's graphics buffer. However, lag will be more frequent than it is on more recent devices. If you'd really want to play FPS80 on your PSP, then you shat out of luck because FPS80 hogs CPU time, almost becoming unplayable under 333MHz.

I've heard that the PICO-8 requires at least 700MHz, and Voxatron requires at least 800MHz. So I suspect TIC-80 needs over 700MHz due to the better hardware specs than PICO-8.

The behavior with the frequency registers seem weird with the TIC-80 soundchip. It seems like it's a look-up table with a 1789773Hz frequency divider, playing a N Hz frequency with a value of N in the corresponding frequency register.

I'm concerned about the same thing!