User Tools

Site Tools


notes:cprog:spring2025:projects:mtb4

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
notes:cprog:spring2025:projects:mtb4 [2025/03/12 20:30] – [power ups] tstricklnotes:cprog:spring2025:projects:mtb4 [2025/03/13 03:45] (current) – [power ups] bdildine
Line 60: Line 60:
  
 then create a struct with the desired powerup and position: then create a struct with the desired powerup and position:
 +<code>
 void main() void main()
 { {
Line 68: Line 68:
  ptrPowerup->type = DUPLICATE;                   //set the type variable within the powerup struct to DUPLICATE, which represent the underlying value of 1  ptrPowerup->type = DUPLICATE;                   //set the type variable within the powerup struct to DUPLICATE, which represent the underlying value of 1
 } }
 +</code>
 now everytime that you call ptrPowerup->type it will return DUPLICATE, which under the hood, represents 1. now everytime that you call ptrPowerup->type it will return DUPLICATE, which under the hood, represents 1.
  
 +Some Power-Ups you could make could range from trivial to more difficult. One could be a Power-Up that increases the size of your paddle.
 +You can accomplish this by checking if the Power-Up is active, then selecting a different region before drawing the paddle and the given coordinates.
 +You will of course need to change the boundaries in which the ball collides with the bigger paddle as well.
 +If you are using an array to track your Power-Ups, it would look something like:
 +<code>
 +if ( PowerUpCollected[1] == true )
 +{
 +    select_region( RegionLargePaddle );
 +} else {
 +    select_region( RegionPaddle );
 +}
 +draw_region_at( PaddleX, PaddleY );
 +</code>
notes/cprog/spring2025/projects/mtb4.1741811449.txt.gz · Last modified: 2025/03/12 20:30 by tstrickl