is there a way to store variable inside a code or modify the code itself using ONLY ti basic?

If you only want to store variables between runs of the program, I'd suggest you look into lists. You can create lists with custom names, and they can hold a lot of information (999 numbers to be exact)

If you do 55->dim(_LLIST), then you create a list named LIST that can hold 55 numbers. If the list already exists, it will be cropped to the correct size with zeros being added for elements that didn't exist previously (this also means that executing this code when the list already exists doesn't modify the list). A newly created list will be automatically filled with zeros.

An alternate way of creating a list is like this:
{0,1,2,3,4,5,6,7,8,9}->_LLIST, which will store all those elements into a new list of the correct size. If the list already existed, it will be completely overwritten.

Every one of those can be used as a variable like this:
_LLIST(5) will return the value of the variable, kinda like simply using A. You can also modify variables like this: 8->_LLIST(5)
It even works when you use a variable inside the brackets: _LLIST(A) will return the Ath element in the list.

So, is it now possible to run a full linux installation, with GUI and such included, on an nspire CX? Or is it a lightweight command-line only version?

First off, sorry for the necropost, but I have an anouncement to make about this project:

As you may or may not know, this project started with a small team of people, but quite soon after developement started, the activity of my team mates decreased (mainly because they had a lot more work for school and such), so afther a while, I was basically working alone on it. And off course, working alone means that progress goes a lot slower. It happened regularly that I was working for hours for a small feature or bugfix that's only barely noticable, which off course didn't give me a lot of motivation to keep up with it. I think that most of the time, the only thing that kept my motivation just high enough to not declare it dead is that this game is the first programming project I ever started (or joined, since I didn't start it alone).

But life stories aside, here's the real anouncement: I decided to stop working on this project for now, because this project is way to big to be able to finish it by myself. I'm not declaring it dead just yet, but untill we (the team behind this game) have time (and motivation) to work on it again, there won't be any progress on this game at all. That's why I'll declare it as in 'deep coma': it's not quite dead yet, but it's chances of survival are - unfurtunately - very slim.

Well, you may have been able to guess what was above, but there's still something that might make this necropost worth it: You may have noticed how most of my projects are open-source, but not this one. Well, I'm not confortable with uploading the source to be downloadable by anyone, but if you want to view the source of this project, or want to use some textures/models, send me a PM. In the case of models, I'm not sure I can give them to you though, since not all of them are made by me.

I don't think it was that much of an issue on Desolate, as you had no level and making the game faster also makes the enimies more annoying.
But if a big speedup due to a low greyscale setting is a problem, can't it be more or less fixed by adding boundaries to the setting so that it's still possible to adjust the greyscale frequency, while the gameplay speed won't be that moch different. Alternatively, I guess that it should be possible to add an artificial delay to the greyscale frequencies that speed up the gameplay too much, though that would be harder.

I decided to write a C entry mainly to learn C, but I've also submited it here.

I'd like to thank Eiyeron and KermM for helping me with this entry, because I wouldn't have gotten it to work witouth them.

- Sooooooo it is quite a long time that I've haven't post anything,but don't worry I am not leaving calc community 
 -

 - something big is also coming, but I won't tell you more 

- That's good to hear. I was thinking about not having heared about you for a while yesterday.
 - Is that per-pixel lighting you're showing there? Or high-res textures/textures with dither patterns? It's kinda hard to see, and it seems to be a bit broken on my computer, as some parts appear as white (not calculator green white, but real white) and shades of grey. Anyway, it looks cool, good work.
 - Does it start with an A? I think I know what it is

BTW: Are billboards planned? If not, then I'll probably try to 'mod' them in after that 'something big'.

This is cool to hear. However, I would have suggestions for future OPRT products:

-Cross-post progress and updates over Omni, so that non-Github users are aware that they are being worked on or exist at all. For example, I didn't know about that Dodge game until I checked this thread tonight. It would also help increasing Omnimaga forum activity. Yesterday there were only 10 posts on Omnimaga and 14 Saturday.

-Those who really can't help on projects could simply post suggestions or feedback on other people's projects (at least the non-quadratic solver ones), to give encouragement and criticism for improvements.

- Ok, I'll try to post more updates here. I agree that it's getting a little bit quiet here, and I'd love to see more activity.

 - I like your 2nd point as well. It would make it more clear for the programmers on what they should focus, and more feetback may also increase motivation. And as a reminder (to everyone): everyone can suggest any projects to finish, even if you are not in the team, and even if it's not your project you want to suggest.

Can I have an invite to the organisation too?
I'm https://github.com/Vijfhoek.

Off course. I sent you an invite.

Quote from: ben_g on September 15, 2014, 10:28:53 am

I also forked wxWabbitemu to the OPRT GitHub page. The work that needs to be done isn't posted in issues yet, but please let us know if you're working on a certain part to reduce the chances of doing double work. I'm currently still learning C/C++, but I'll join as soon as I understand them well enough.

Awesome! I'll start filing relevant issues as starting points for things to work on.

Do you want the issues to be filed on the original repository or the OPRT? (Either way is fine.)

Quote from: ben_g on September 15, 2014, 10:28:53 am

Finally, if anyone is still interested in joining the team, please post your GitHub name here (or tell it to a team member on IRC or in a PM).

I'll join! (Just to watch over, of course. )

I'd prefer it if you add the issues in the OPRT repository, to keep all of it mostly in one place.
And I've sent you an invite.