Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

TIC-80

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

State of TIC-80 - No new release since 1 year?

A topic by PJaros created Aug 25, 2019 Views: 1,491 Replies: 11
Viewing posts 1 to 3

I've bought pico-8 1 year ago but never really got around to do anything meaningful.

I've come back to it because my kids want to learn programming. After doing some research I came across TIC-80. I've found it in the Google-Playstore. I found out it is opensource. I love oss, I'm running Linux since ages and since 2 years I'm a devops at work supporting the RH-Servers.. anyway. Here are the bad things I've came across trying to install and use TIC-80

  • I've googled on how to install TIC-80 on Linux and was presented: https://github.com/nesbox/TIC-80/wiki/build-instructions Which tells me to
    sudo apt-get install git
    git clone --recursive https://github.com/nesbox/TIC-80
    cd TIC-80
    cmake .
    make
    Which ended with a

    Building for target : Linux
    CMake Error at 3rd-party/sdl2/CMakeLists.txt:2 (message):
    Prevented in-tree built. Please create a build directory outside of the SDL source code and call cmake from there
    As described in my issue here: https://github.com/nesbox/TIC-80/issues/914
    I
     only later found that the readme.md here https://github.com/nesbox/TIC-80
  • I've installed the demos in the virtual-console. I am pretty unimpressed. A single game without sound. A benchmark and unplayable demos :-/
  • The Games in the (chromium) browser have no sound at all as of this bug: https://github.com/nesbox/TIC-80/issues/590
  • The TIC-80 snap is 2 years old and doesn't work - It immediately crashed after installing and running with a page-fault https://snapcraft.io/tic80
  • On github the project lists 281 issues as of right now. Some are over a year old.
  • And last but not least: There hasn't been a release since over a year I couldn't find out why that is and what is blocking the release. Good software is released early and often. What is wrong with the current state of the project that hinders a release? Where am I supossed to get that information?

I really like the idea of this beeing a opensource kind-of-pico-8 but I hate to invest time into a project that has a uncertain future. I have three kids who would like to learn some game programming... I hate the idea I have to switch to another application in the midst of teaching them  because of the unstable state of this project.

Maybe I'm wrong and just had bad luck uncovering this in about 2 hours trying to find out about TIC-80. I would really like to give TIC-80 a chance, but as of right now I'm pretty unconvinced that TIC-80 has a workable base I'd like to build on.

(4 edits)

> And last but not least: There hasn't been a release since over a year I couldn't find out why that is and what is blocking the release. Good software is released early and often. What is wrong with the current state of the project that hinders a release? Where am I supossed to get that information?

have you checked on here?
https://builds.tic.computer/master

No I was not aware of the page.

There are only Tags up until v0.70.6 on the https://github.com/nesbox/TIC-80. Why is that? How does one know those builds are compiled from  https://github.com/nesbox/TIC-80 anyway?. How does one get the source to the specific release without the tags?

Now I have even more questions and those other questions from my first post are still unanswered. :(

(3 edits)

[ I would've answered earlier, but prep work for Hurricane Dorian took some focus. ]

ok, there are a few questions here.. and my answers will be an educated speculation based on observation, since I've never questioned the man's methods.

> There are only Tags up until v0.70.6 on the https://github.com/nesbox/TIC-80. Why is that?
I assume this question is in regards to what you find here [ https://github.com/nesbox/TIC-80/releases ]. If you notice he associates milestones [ https://github.com/nesbox/TIC-80/milestones ] in his workflow and that currently there are no more open bugs left for the 0.70.2 milestone tag. If I were him, since it seems we share similar workflows, this would mean that there are no valid reasons left to focus on  the 0.70.2 [ https://github.com/nesbox/TIC-80/milestone/24 ] milestone over the 0.80 [ https://github.com/nesbox/TIC-80/milestone/25 ] milestone release.

> How does one know those builds are compiled from  https://github.com/nesbox/TIC-80 anyway?
Simple enough - https://github.com/nesbox/TIC-80/issues/870

> How does one get the source to the specific release without the tags?
Code's being committed to the Master branch. From the 0.70.6 release page [ https://github.com/nesbox/TIC-80/releases/tag/v0.70.6 ] you can see how many commits have been made since that tagged release.

@netvip3r That's a new version is 0.80.0-dev

Like this


TIC-80 Command

Code Editor

- No New features

Sprite Editor

- Added 8 Sprite flags [ 0 1 2 3 4 5 6 7 ]

Map Editor

- No New features

SFX Editor

- Added Sound Left or Right Stereo

Music Editor

- No New features

Updates

RAM Info

RAM Info

- Added vram command 

- Added 2 New RAM address & name

(1 edit)

That's understood.. kind of like a 'pre-release' for lack of a better term.

The part of the question was particularly regarding not being able to find 'signs of change' for a whole year essentially..
> "There are only Tags up until v0.70.6"
.. admittedly the statement made on July 10 about the 0.80 builds and link are not readily obvious and requires a bit of digging.

I did not attempt to answer most points in the Original Post because, lots of points and Hurricane threat.. but I felt this was a quick and more immediate response to his situation and assumed someone would jump in and tackle the others.

Additionally, ty @Masternama8000 ... heck I didn't even know of some of those changes :)

(1 edit)

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

EDIT: Nevermind, it's working again.