Skip to content

Week3 - #3

Open
Noratho wants to merge 66 commits into
mainfrom
week3
Open

Week3#3
Noratho wants to merge 66 commits into
mainfrom
week3

Conversation

@Noratho

@Noratho Noratho commented Dec 9, 2020

Copy link
Copy Markdown
Contributor

-Added circle drawing function
-completed input parser
-completed input maps
-completed json for character data
-*Created a new class to handle moves(very time consuming) :(
-Moved certain data structs into different files for better organization
-added specs and a lot more comments
-added visuals for the moves
-refactored move models to allow for changing velocity and multiple sets of hitboxes

I'm tired but happy with what I've learned during this project and throughout the overall semester. A lot of that is thanks to you. So thank you very much for all of the help you have given me.
https://cdn.discordapp.com/attachments/501225658060636171/786092990648549396/bueno.jpg

…reated skeletons for generate player and parse input
…throw for more specification on moves. I also created default constructors and added json parsing macros.
…throw for more specification on moves. I also created default constructors and added json parsing macros.
…s the input parsing to allow for combo input leniency
…tboxes will be stored in the hitbox data class until called to create the temporary fixtures
…ges mid attack like a lunge kick. Also updated the json to match
…reation into different methods as well as created different initiate move overrides the initiate move method as well as created a method to clean up inputs
…hitboxes and changes the velocity based on the frame

@ishitarao ishitarao left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bob Game is the culmination of your efforts this semester; I hope you're proud of what you've made (I thought you were going to call it Antares, given the namespace/file names). I also hope you decide to continue working on Bob Game and then make it a public repository.

While doing the bare minimum for your README in the context of this assignment is okay, I really recommend learning how to use Markdown and learning how to create descriptive, well-written READMEs. If you want people to look at, appreciate, and use your code, then a good README is key.

I'm happy to see how much you've improved over this semester, and I hope you'll keep writing good-looking code. Good luck. :)

/**Json macro*/
NLOHMANN_DEFINE_TYPE_INTRUSIVE(AirAttacks, neutral_air, forward_air,
back_air, up_air, down_air);

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

forward_air. back_air. up_air. down_air. Long ago, the four nations lived in harmony. Then, everything changed when the up_air nation attacked. Only the neutral_air, master of all four elements, could stop them. But when the world needed him the most, he vanished. A 100 years passed and my brother and I discovered the new neutral_air, a down_airbender named Aang. And although his down_airbending skills are great, he has a lot to learn before he's ready to save anyone. But I believe, Aang can save the world.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(As a sidenote, the macros look great!)

Comment on lines +56 to +64
Attack neutral_air;
/**forward Air Attack*/
Attack forward_air;
/**back Air Attack*/
Attack back_air;
/**up Air Attack*/
Attack up_air;
/**down Air Attack*/
Attack down_air;

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For related variables, you can use a single CDoc describing their purpose.

b2Body* player_body_;

/**Bool that shows whether a move is in progress*/
bool is_move_in_progress_ = false;

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't initialise non-const variables in the header file.

Comment thread include/core/move_model.h
Comment on lines +34 to +39
/**Color R value*/
int r;
/**Color G value*/
int g;
/**Color BR value*/
int b;

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

An std::tuple would be good here, although I'm pretty sure Cinder already has something for RGB colours.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did it like this to avoid making the macro even more messy as I didn't want to mess around too much with getting tuples to register, though they might already.

Comment thread include/core/move_model.h
Comment on lines +30 to +32
float x;
/**circle y position*/
float y;

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

An std::pair is always recommended for x-y pairs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants