======MTB1======
Only task headings have been provided. You are not expected to know how to do the task given by just that description (although in some cases it can be adequately figured out). Instead, if no further information is yet present, ASK FOR DETAILS on the discord, then contribute that clarity here.

If something is present but needs polish: spruce it up.

If something is present but is incorrect: please fix it.

This is intended to be an informative, useful document that all can benefit from.

Those with prior experience, please be mindful not to gobble up all the low-hanging fruit from the newcomers.

=====Design your sprites / custom texture=====

====Specifying Texture in XML====

====Selecting Texture====
Just like in C, selecting a texture is simple

In C to select a texture we can use:
<code>
select_texture( int texture_id );
</code>

In Assembly the process is similar, as the command is simply:
<code>
out GPU_SelectedTexture texture_id
</code>
Where texture_id is either the immediate value of the texture id, or a register containing the texture id\\
**NOTE: To select any BIOS texture, such as the built in font, you need to use the texture id -1**
====Defining Region====
Defining a region is where assembly becomes much less simple, as in C one can use a variety of built in functions that handle everything, whereas in assembly we have to send the GPU every value ourselves

This looks like:
<code>
out GPU_SelectedRegion #
out GPU_RegionMinX #
out GPU_RegionMinY #
out GPU_RegionMaxX #
out GPU_RegionMaxY #
out GPU_RegionHotspotX #
out GPU_RegionHotspotY #
</code>
Once again with # corresponding to an immediate value or register containing the values we want to input
====Selecting Region====
Selecting texture is where the Assembly code once again directly mirrors the C code, as the instruction to select a region is simply:
<code>
out GPU_SelectedRegion region_id
</code>
**NOTE: if you are trying to print text, the region_id for each character is the ASCII value associated with it.\\
For example, to print the character '0' to the screen you need to use region_id 0x30 or 48<fs x-small>10</fs>**
=====Check for keypresses=====

====Selecting joystick====
Selecting a joystick is very similar to the C process and only takes one command.
In C, we use:
<code>
select_gamepad( gamepadID );
</code>
Where gamepadID is the value of the gamepad you wish to select.

In assembly we use:
<code>
out INP_SelectedGamepad, gamepadID
</code>
Where again, gamepadID is the gamepad we wish the use.


====Reading joystick value====
Reading the joystick values is also similar to the C version, the C version is the following:
<code>
variableName = gamepad_left();
</code>
Where variableName is a integer variable

In assembly we use registers instead of variables to store the returned value
<code>
in R0, INP_GamepadLeft
</code>
Reading the other directions can be done by using up/down/right instead of left
====translating read joystick value into X and Y====
The value returned by the gamepad is the number of frames it has been in that state

This value can be converted into a boolean with ige:
<code>
ige R0, 0
</code>
Where R0 is a joystick direction value

After you have the boolean version, you can either use a conditional jump to a label that does whatever you want when a certain direction is pressed, or directly add/subtract the value to the x/y position
<code>
jt R0 _label
</code>
or
<code>
iadd R1, R0
</code>
Where R1 is a x/y position
=====Playfield bounds checking=====

====Vircon32 screen resolution====

====How to check if our sprite has reached a bound====
Checking the bounds of the screen can be done using greater than/less than instructions

Remember that instructions overwrite the register
<code>
mov R0, R1
ilt R0, YMIN
jt  R0, _upper_bound
</code>
and
<code>
mov R0, R1
igt R0, YMAX
jt  R0, _lower_bound
</code>
Where R1 is a the y position and YMIN/YMAX are the min and max bounds
====How to limit our sprite from leaving the playfield====

====How to cause our sprite to wrap-around on the playfield====