Differences

This shows you the differences between two versions of the page.

--- haas:spring2022:comporg:projects:ticx [2022/02/01 21:16] – [Task] wedge
+++ haas:spring2022:comporg:projects:ticx [2022/04/17 14:11] (current) – [topic: a bigger TIC-80 game experience] wedge
@@ Line 28: / Line 28: @@
 |  6  |  tic6  |  [[#topicfull_palette|full palette setting]]  |  3  |  39  |
 |  7  |  tic7  |  [[#topictiming_the_palette_to_get_more_colors|time-enhanced colors]]  |  4  |  52  |
-|  8  |  tic8  |    |  4  |  52  |
+|  8  |  tic8  |  choice: [[#topica_bigger_tic-80_game_experience|TIC80 game]] or [[#topicswitching_this_up_and_coding_in_assembly_on_the_nes6502|NES game]]  |  4  |  52  |
-|  9  |  tic9  |    |  5  |  65  |
+|  9  |  tic9  |  continuation of choice  |  5  |  65  |
-|  10  |  ticA  |    |  5  |  65  |
+|  10  |  ticA  |  continuation of choice  |  5  |  65  |
-|  11  |  ticB  |    |  6  |  78  |
+|  11  |  ticB  |  continuation of choice  |  6  |  78  |
-|  12  |  ticC  |    |  6  |  78  |
+|  12  |  ticC  |  completed game  |  6  |  78  |
 ====topic: palette and persistence====
@@ Line 88: / Line 88: @@
 And, it should be beyond obvious: don't just lift tutorial code you find and pass it off in its entirely (with author comments stripped) as your own. You can refer to examples, but I want the final program you submit to be an effort all your own.
+====topic: a bigger TIC-80 game experience====
+We have spent some time exploring the basics of memory access, peripheral control, and resource manipulation across various aspects of TIC-80. We now move into a larger phase where you bring it all together in some larger, original creation.
+You are to implement over the next span of weeks, a more sophisticated game of sufficient detail and utilization of TIC-80 resources that is commensurate with the timeframe involved and experiences gained.
+There will be 5 checkpoints that you will submit prototype/draft versions of your game (each week):
+  * week8: initial explorations into your game. Identity in comments or a separate README file what you are looking to do, laying out a timeline for where you hope to be and what you aim to accomplish each week. You don't necessarily have to stick with this timetable or do things in order, but some manner of consistent, overall planning should be taking place.
+  * week9: snapshot of what you have. Be sure to identify what you have worked on, what works, what doesn't, and where you are thinking of going next.
+  * week10: snapshot of what you have. As above, identify what you have done, what works and doesn't and what's next.
+  * week11: snapshot of what you have. As above, identify what you have done, what works and doesn't and what's next.
+  * week12: finished product.
+Aspects that need to be present in your finished product:
+  * utilization of some peripheral for gameplay (joystick, mouse)
+    * exclusive access of peripheral data via memory peeks and bitwise logic
+  * use of persistent memory
+  * code-based alteration of the palette
+    * game must utilize at least 48 unique colors
+  * some manner of sound, music (audio) must be present
+    * generated by code, stored to memory
+The game can be based on an existing one (a tetris clone, a doom implementation, etc.) but the code should be your own, and it should be sufficiently involved for a multiple week effort.
+It should go without saying: the code you write should be your own. Don't copy anything.
+It should also go without saying: you are to be submitting code. In earlier weeks it doesn't necessarily have to be complete or even functional, but you are communicating your progress through submitted code and any commentary you provide.
+====topic: switching this up and coding in assembly on the NES/6502====
+For those that want to dive a little deeper into the inner-workings of how a computer works, you can elect to diverge from the TIC80 path for this next set of projects, and instead learn and implement a simple game in 6502 assembly for the NES.
+The game can be something like breakout, asteroids, dig dug, etc. or some original idea, but does not have to be as expansive as the multi-week TIC80 game effort.
+NOTE: the game cannot be pong, hopefully for obvious reasons.
+To start, check out the Nerdy Nights tutorials:
+  * https://taywee.github.io/NerdyNights/
+Do note: the aim here is to learn 6502 ASSEMBLY LANGUAGE for the NES, creating ROMs to run in an NES emultor.
+There will be 5 checkpoints along the way where you will submit a snapshot of what is being explored/worked on. Note that unlike the big TIC80 effort, each weekly snapshot does not have to pertain to the final game being pursued; the early weeks could be prototype code/explorations, but variations if using whatever runnable content exists in a tutorial (ie don't just submit a ROM of something all the code has been given for).
+  * week8: NES prototyping, exploring
+  * week9: more exploring
+  * week10: perhaps the first signs of work breaking ground on the game
+  * week11: some in-progress snapshot of your game
+  * week12: NES ROM game complete and submitted
+It should go without saying: the code you write should be your own. Don't copy anything.
+It should also go without saying: you are to be submitting code. In earlier weeks it doesn't necessarily have to be complete or even functional, but you are communicating your progress through submitted code and any commentary you provide.
 =====Submission=====

Lab46 Wiki

User Tools

Site Tools

Differences

Page Tools