A collection of minigames made in the raylib library with c++.
Race is a game played with two players. The two players race against eachother to get to the red finish line at the end.
Test is not a game, it justs tests the bouncing mechanic used in Sumo and the circle Blockers.
Sumo is a game where one player trys to knock the other player out of the circle. The circle decreases over time, and at the end of each round the winner's score gets incremented, and the game is reset. When a game resets, the players are not allowed to move for a couple of seconds as to minimize players accidentally moving out of the circle on their own. The top left corner shows when player can move; Ready meaning the players cannot move, Go! meaning the players can move. The score of both the players is located in the top right of the screen, with colors corresponding to the colors of the players.
Connect 4 is pretty self explanatory, it is a connect four clone. The players have alternating turns trying to get four of their pieces in a horizontal, vertical, or diagonal line. Whenever a player wins, a message will appear in the top right corner, and players will no longer be able to place their pieces. A preimage of where the piece will go appears when the mouse is in a column of the connect 4 board. A piece will drop where the preimage indicates when the player hits the left mouse button.
Boundaries.cpp defines the Blocker class, a rudimentary collider (I probably should change the name of the file). It defines the various methods that a Blocker uses to draw to the screen and interact with the player.
Dist is a function that returns the distance between two cartesian coordinates. It is used for detecting collision when the Blocker is a circle.
This is a function that draws the Blocker to the screen. If the Blocker is a circle, it draws a circle to the screen using the Blocker's x, y radius, and color. If the Blocker is a rectangle, it draws a rectangle to the screen using the Blocker's x, y, width, height, and color.
insideOfRect is a complicated function that returns a boolean value based on whether the player will move into the bounds of the Blocker based on the player velocities. It does not actually check if the player will move inside of the visible part of the Blocker, but a larger rectangle that accounts for the fact that the players position is the center of the visible player circle. This allows the player to realistically collide with rectangle Blockers.
This is a function that moves the player outside of a Blocker if the player is inside of it. Players usually only get stuck inside of Rectangle Blockers, and only if the player manages to hit the exact corner of the Blocker. This function is not very good, and I will change it later. It only really works on relatively square shaped Blockers. To move it to a non-surprising location outside of the Blocker, it gets the angle from the center of the Blocker to the player, and uses the polar coordinate system converting to cartesian to put the player outside of the Blocker.
This is a function that handles most of the collision logic with the player. It sets the players velocities to zero if the player will move inside the Blocker on the next frame. The collision is relatively easy for circle Blockers, but the Rectangle Blockers have the use the insideOfRect helper function. The Rectangle Blockers also only set the velocity that makes the player enter the Blocker to zero, not both velocities. This allows the player to slide along the sides of Rectangle Blockers without getting stuck.
Just a header file that declares the Blocker class, its constructor, and its methods.
This is the file that defines the methods that the Button class uses. Buttons are used to go between Loaders, aka levels. They also can be used as text boxes, like in the main menu and the credits page.
This is the method that draws the Button, which includes the outline, the actual background, and the text of the Button.
This is a method that handles when the mouse cursor is over the Button, and what happens when the player actually presses the Button. It first checks if the button is an actualButton, which is just a boolean that determines if the Button should change color if the mouse is hovering over it. Then, it checks if the mouse is within the bounds of the button, and if it is then the Button changes to its hoverOverColor. Then it checks if the mouse is being pressed, and if it is the level (Loader) will change.
This is the method that causes the Button to change a boolean when it is pressed. This is used for the quit button in the main menu.
Basically the same as above, but with integers. This method allows the choice to increment a variable or assign a variable.
Just a header that declares the Button class and its methods.
The header file that declares the Connect4Piece class.
This defines the methods of the Enemy class, which isn't currently being used by any game.
The method that draws the Enemy to the screen, which is just a black circle.
Here are the commands that I used to build the executable
echo > Setup required Environment
echo -------------------------------------
SET RAYLIB_PATH=C:\raylib
SET COMPILER_PATH=C:\raylib\MinGW\bin
ENV_SET PATH=$(COMPILER_PATH)
SET CC=g++
SET CFLAGS=$(RAYLIB_PATH)\raylib\src\raylib.rc.data -s -static -O2 -std=c99 -Wall -Iexternal -I$(RAYLIB_PATH)/src -DPLATFORM_DESKTOP
SET LDFLAGS=-lraylib -lopengl32 -lgdi32 -lwinmm
cd $(CURRENT_DIRECTORY)
echo
echo > Clean latest build
echo ------------------------
cmd /c IF EXIST
echo
echo > Saving Current File
echo -------------------------
npp_save
echo
echo > Compile program
echo -----------------------
echo
echo > Reset Environment
echo --------------------------
ENV_UNSET PATH
echo
echo > Execute program
echo -----------------------
cmd /c IF EXIST (build/$(NAME_PART).exe) (build/$(NAME_PART).exe)
This is just a slightly modified version of the commands used to build files in the notepad++ IDE thats built specifically for raylib. I personally make modifications in VSCode and use notepad++ just to build the exe.