Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags

TIC-80

Fantasy computer for making, playing and sharing tiny games. · By Nesbox

TIC-80 PRO no code limit when exporting to exe

A topic by Sleepless Creator created Jan 15, 2018 Views: 2,312 Replies: 5
Viewing posts 1 to 3
(1 edit)

So I am new and proud owner of TIC-80 PRO. I was wondering if it would be possible to remove code limit (other limits?) when game is exported to plain exe? While it is necessary to have one when uploading game to the central repository, if we could specify that game will be only exported to exe it could allow for more than 'normal' exporting. PICO-8 is doing it in a way that if you go over limit it doesn't allow you to export your game to the uploadable format, but you can still save and run it.


Edit: Saw that in 0.60 you can expand space for everything except code limit, so my question stands only for code limit.

Developer

Pro version has 8 banks each 64KB of code, so you have 512KB of code limit in total

(2 edits)

I missed this information, sounds awesome, thank you! Does that mean I can use this in 'normal' uploadable games? I am looking at sync command (https://github.com/nesbox/TIC-80/wiki/sync#parameters) and it looks like it should work 'anywhere'. But regarding code limit, do I need to call sync or switch bank somehow to utilize 512kb or does it work 'automagically'?

Edit:

I opened TIC80 Pro and i see banks for code editor, but how do I make use of this if I am working with code from external editor (and loading it via command line?)

Developer

yes, banks work everywhere, with PRO version you can switch and edit them in the TIC's Editors
with sync() api you can load game resources like sprites/map/sound from a bank you want to the 80K RAM in runtime

you don't need to call sync() for the code, all the code automatically loads on game startup from 7th bank to 0

to edit banks in external editor pls use text cart format, switch bank in Code Editor, type some code, go to console and use 'save game.lua' command, then you can open 'game.lua' in any text editor (TIC will automatically reload cart when you save it), you should see <CODE1>... section

Thanks :)

(1 edit)

Hello :)

I tested that method but it seems to be a bug where the code ends up both in bank1 and bank2. In bank1 I can still see the comment -- <CODE1> etc. when I save it in the external editor. 

So, it ends up both in bank 1 and 2

Edit:

Saw a potential fix for it on github but I guess I'll have to compile it myself to get it working or?