PASUM - Curated Resources by Yours Truly :3

Old Resources (Pre-2025) Notes PASUM 25/26 Resources

Semester 1 - Game Development Project

Project Sem 1 File

To most of you who are reading this, you have never touched a single line of code in your life, much less made a game before. This task will seem incredibly daunting to you guys, which I assure you, you aren't alone.

Through referencing the documents and trying to stay in line with the requirements of the documents, and intensive questioning with Ms Mardiah, I will try my best to demystify the approach on Game Development.

Part 1: How do I start?

Group Representative

As a group representative, your role is to distribute the tasks amongst your team members, and to ensure that the roles given are fulfilled by your members as well as possible, whilst ensuring your group has enough time and resources to complete the first prototype.

Assuming you're an incredibly capable leader, that could do the ideation, the art, the programming, the documentations all by yourself. That's great! However, you shouldn't forget that this is still a group project. Your team members will still be tested on their knowledge on the development of the game. Start with the Proposal Template. Let's get things done as soon as soon possible. Fill in the followings as soon as possible:

Group Name - This can be temporary, but it gives you something to call your project by.
Group Members - Get your children in order.
Supervisor - Whoever is your tutorial teacher. (FL3 is Ms. Mardiah)

Once you're done, the Group Representative will have to start assigning roles. So far, I've recognized four most important roles a team needs to have.

Project Manager - Usually the Group Representative, this ensures that someone is responsible for the project to keep going.
Programmer - I don't think I need to explain this one.
Visuals/Asset Manager - These people will be the ones handling the visual, audio, or any other types of resources required for the game.
Documentator - The people who keeps track of the progress and write them down for the project proposal. Other members should try to report to the documentator with sufficient information for them to jot down such that they could do their respective jobs properly. They will have to be the one to create the Problem-Analysis Chart, Input-Processing-Output chart, Flowchart, and Pseudocode. The documentator may need to ask the other members as well.

Great! You're done with distribution.

Group Members

Your role here is equally as important as the Group Representative. Hopefully, at this point, you've already been assigned a role.

Programmer

Your role here is straight-forward. You need to bring the game to life. Unfortuntely, it isn't easy. Here are some of the things that you must learn to use:

C++ - You need to know the general syntax and logic flows. If you've never touched it before, it is an incredibly good time to do so, because not only does it help with programming, it'll help a lot in Physics and Advanced Mathematics as well. A little encouragement for more people to pick up programming!
Raylib - This is my suggestion of a tool you will use to make a game with. It's a lot more easier to use Raylib than any other alternative such as Unreal Engine 5, SDL2, OpenGL, or Vulkan as it removes a lot of complexity that comes with having to program your games 100% from scratch.
Code Editor/IDE - You can use anything, as long as you find it comfortable to write in. For regular users, I suggest VSCode, Microsoft Visual Studio, or Code::Block if that's still even relevant.

Visuals/Asset Manager

The difficulty of your role will scale according to how difficult of an idea your group has thought of. You will be working alongside the programmer most of the time, and it's your job to provide the programmer something to work with such that the game looks more polished. Speaking from experience, the programmer also needs to see the game become more and more done to not demotivate them.

You will to create or to get free assets from sites like itch.io. Additionally, unless any one of your members is capable of creating any sort of music or sound effects, your job is to also provide the audio files for the programmers to use.

Documentator

Arguably the most important role. You need to learn to create diagrams, format your documents well, interview your group members every so often, and jot everything down. The quality of the final presentation depends heavily on the documentator, which also dictates the amount of marks given to your group. The documentator will also have to present and brief your team members on what they have written, so in the case where the tutorial teacher grills one of your non-presenting team members, they will be able to respond. The documentator is the multiplier to your efforts.