- SDramps module
- 8x8x9.5 inch print bed
- Heated print bed
- 0.4 mm extruder tip
- I use PLA mostly

Cons:
- Does not do bridges well but I am quite sure it is the way I have it set up

1. Go to the home screen and press PRGM
2. Go to NEW and enter a name
3. You are now in the Ti-84+ IDE

4. From now on the key strokes are in the screen shot

5. Time to run the program, can you guess what it will do?!

If you have figured it out open this!

[close]

First of all lets create a program:

Spoiler

[close]

We will be making a loop that counts X from 0 to 10 and then displays some text:
The first step is to set X to equal 0 and to make our loop

Spoiler

[close]

Now we have to tell the loop when to run:

Spoiler

[close]

This just says WHILE X is less than 0 run this code!

The next step is to tel the loop what to execute:

Spoiler

[close]

This makes X's value go up by one every time the loop is run

Now we have to give visual feedback when the loop completes!
CHALLENGE: Do this by your self and see what you can come up with (it doesn't need to be exactly like mine)

Only open if you wish to spoil the CHALLENGE

Outputs:

But wait the output is cut off how can wee fix this?!
Look in the next step to find out really how simple it is

[close]

All you need to do is separate it into two commands!

Spoiler

[close]

Now you may be asking how on earth do we get that ugly prgmLOOPS off of the homescreen, that is also very easy

Spoiler

Just add ClrHome to the first line in your program

[close]

Now you will get this:

Spoiler

[close]

Now for that pesky Done at the end:

Spoiler

All we do here is add a Pause at the end and that makes all line execution stop until the user presses enter

[close]

It should give you this:

Spoiler

[close]

Congrats you have finished part 2!!!!

Sneak peak for next lesson:

Spoiler

[close]

GETTIME(); returns the time in a list: {H,M,S}
GETDATE(); returns the date in a list: {Y,M,D}
RUNPROG(Prog); runs Prog (but has the same limitation as SIFS right now (it cannot run programs with arguments in the main function ))

I am not responsible for any rage this game causes comparable to flappy bird, also in higher tier levels you make have seizures if so consult your doctor promptly and see if this is right for you

Collision / Block durability:
what I do here is I use a GROB that is the same size as the world dimensions. If the pixel at your coordinates is black then it is free to move through, if it is anything else and you will not be able to go through it. And its color value is the block durability.

Storing worlds and world data:
This is where I really need Apps. With AFilesB() you can return and store individual bytes directly into the App files. So I can use this as a super compact and small list that makes up the world, they will then be formed into a matrix that will be used to store data while the game is executing. Then when the user quits it turns the matrix into a list and stores it into the App. If this is a acceptable way to do it it would be nice to have some feedback, especially from @timwessman.

Drawing the world/ terrain:
For this I am going to use a method I used in the last versions quite allot. I will make a GROB which will be one block larger on all sides, this will allow for smooth scrolling and also decrease lag if you are not moving much.

Player Movement:
This will be where 4.0 really shines, it will have movement like Zampy's Quest (for those that don't remember, it let you move one pixel at a time) not that it is super cool but it is something the other versions lacked. But unlike Zampy's Quest it will have impeccable collision because it uses pixels. Why Pixels are so great at collision is because they will only position at the integral part of the number (ex: PIXON_P(1.9999,1.9999,#FFFFFF) and PIXON_P(1,1,#FFFFFF) both make the pixel at (1,1) white).

I hope this wan't so confusing but I explained it all the best I could

blocks

Times all block ID's after 1-10 by 10 (so block 2(dirt) would be 20 and block 3(grass) would be 30 this gives me room to add block durability )
1-9 - Break animations
10-Stone
20-Dirt
30-Grass
40-Cobblestone
50-Bedrock
60-Oak Leaves
70-Tall Grass
80-Bricks
90-Refined Stone
100-Oak Planks
110-Mossy Cobblestone
120-Gold
130-Iron
140-Coal
150-Diamond
160-RedStone
170-Glass
180-Monster Spawner
190-Torch
200-Lapiz lazuli ore
210-Lapiz lazuli Block
220-Iron Block
230-Gold Block
240-Diamond Block
250-Emerald Block
260-Sand
270-Sandstone
280-Netherbrick
290-White Wool
300-Black wool
310-Dark gray wool
320-red wool
330-Pink wool
340-Green wool
350-Lime green wool
360-Brown wool
370-yellow wool
380-blue wool
390-light blue wool
400-magenta wool
410-Purple wool
420-Cyan wool
430-orange wool
440-light gray wool
450-Obsidian
460-enchanting table
470-dragon egg
480-command block
490-jungle leaves
500-cactus
510-spruce leaves
520-foot of bed
530-head of bed
540-Iron bars
550-ladder
560-bottom door
570-top door
580-mossy stone brick
590-cracked stone brick
600-spruce log
610-birch log
620-pumpkin
630-jack o'lantern

NAME - ID - MODIFIER / DAMAGE (Blank if none, once mining is added all blocks will have a damage count)
AIR - 0
BEDROCK - 1
DIRT - 2
GRASS - 3