Please include a readme.txt file with your files in the future. I noticed a new trend in the community where all BASIC/Lua programmers no longer include a stand-alone readme.txt file with their games or programs. Instead, they include the readme directly inside the TNS file, and I even noticed more and more people who don't even include any instructions such as controls.

There used to only be two people that did that before, including a member here, but now it's almost every Nspire BASIC and Lua programmers.

Sometimes, I like to be able to check how the game operates prior installing it on my calc, to make sure it will not be too hard to play for me or to see if it's really what I expect (example, if it's an RPG and it says to type numbers then enter to move around instead of pressing arrows, I will not bother downloading it). However, when you put the readme directly inside the game document, this is impossible, as I am forced to load it on my calc, an emulator or a document player, and it's annoying.

So please, in the future, could you please do like TI-83 Plus, TI-89T and Casio programmers and make your readme.txt separate from the BASIC/Lua TNS files or both? Thanks.

On the 83+, when I see a RPG on ticalc, the first thing I look for is if the controls says "Press number keys to select stuff in the menus" and that there are no character movement control. This automatically tells me it's a menu-only RPG. Now those are uploaded in a separate directory on ticalc.org, but some still sneak in the regular RPG section from time to time.

Better making a Readme readable by the calc (or even inside the prog) because when we send the prog to a friend, we can't always send the Readme.

Or even better than better : don't do any readme file. And we're fixed.

Or even better than better : don't do any readme file. And we're fixed.

It's generally bad software practice to not include one or more of the following things with your program:

- License(s)
- README(s)
- Contact information
- Additional Disclaimers
- If it includes the source files:
   - A build script / directions for building
   - All tools used to compile the source
      - License(s) for these
   - Reminders in the main source files about the license(s) that apply


While most people don't include most of these, READMEs are absolute necessities and licenses are only second to that.  I won't play a game with no README included in either a main or "about"/"resources" directory.  I won't consider helping out with a project if it has no license.

Well, that technically can be considered a license, depending on what it applies to with many calculator games it's fine (such as Axe or BASIC games).  I think it's just a bit unthoughtful though if someone writes something that includes either source or extreme documentation, in a language like assembly, Lua, C, or even non-calc projects -- when there's a good chance your code will be stolen for later use.  A disclaimer can work just fine, but for the paranoid like me the GPL v3 does wonders at protecting your work with some actual backing in court

I plan to release source code with TI-Boy, but I don't expect people to understand it haha

This reminds me definitely. If you're making an 'official-like' release on ticalc.org there should definitely be a readme. Unfortunately there are just so many files out there with single document files in .zips, and some don't even have instructions within the game!

I myself am kinda guilty in not posting a full 'how-to-play' readme, just an informational readme.