Developing 'Protect the King': A Game Jam Journey in Unity

The speaker welcomes viewers to their stream, mentioning participation in a new game jam, specifically the Unity Game Jam, indicating excitement and engagement with the audience.

The speaker discusses their project, an isometric beat 'em up game where the objective is to protect a king. They mention having created tiles for the game and express a sense of challenge as they have never developed an isometric game before.

The speaker encounters issues with their development environment, specifically preferring to use Visual Studio Code over Rider for scripting. They navigate through Unity's preferences to set their preferred IDE, demonstrating a hands-on approach to resolving technical difficulties.

While working on player movement, the speaker faces challenges with the isometric character render component, initially encountering errors. After troubleshooting, they successfully implement movement for the character, indicating progress in their game development.

The speaker adjusts the gravity settings for the character, ensuring that the game mechanics align with their design vision. They express satisfaction with the movement functionality, indicating a positive development experience.

The speaker expresses uncertainty about the animation aspect of their project, noting that the implementation is interesting but unfamiliar. They acknowledge the need to figure it out as they proceed with the development.

The speaker contemplates the order of tasks, deciding to create the map before adding the leader character. They mention the importance of logical progression in their development process.

The speaker begins working on the art for the game, specifically focusing on the map design. They reference taking inspiration from other maps and making adjustments to improve the visual appeal.

As the speaker continues to refine the art, they compare their design to recognizable elements, such as a Minecraft logo. They experiment with different shapes and shading techniques to enhance the overall look.

The speaker discusses the layering of colors and transparency in their design, indicating that they are starting to see the shape of their creation take form. They express satisfaction with the progress made so far.

The speaker comments on the effectiveness of their shading techniques, noting that it significantly enhances the visual quality of the art. They express excitement about how the shading contributes to the overall design.

The speaker reflects on the potential complexity of the game if they were to add a race platform feature, which could complicate AI implementation. They decide to keep the current design simple for now, considering future adjustments.

Realizing the need for character art, the speaker acknowledges the importance of creating animations for the characters. They contemplate a design approach where the camera moves to different levels as players progress, simplifying the animation process.

The speaker contemplates the design of a game level, considering the addition of trees and decorations to enhance the environment. They express uncertainty about whether to implement these features immediately or later, indicating a desire to create a visually appealing playground scene.

The speaker reflects on the possibility of making the level procedurally generated but acknowledges the time constraints, noting they only have one week to complete the project. They admit to lacking sufficient experience in procedural content generation, which adds to their hesitation.

The speaker decides to place enemies in the game without randomization for the time being, focusing on creating a more controlled environment. They plan to add trees and decorations to the scene while minimizing unnecessary camera movement.

The speaker begins developing the 'King' character, initially rendering it as a simple circle. They discuss the mechanics of making the King walk within the game, contemplating how to maintain camera immersion while allowing the character to move.

The speaker outlines the need for a camera movement system, considering how to implement it effectively. They express a desire to create a smooth transition for the camera as the King character moves, indicating a focus on user experience.

The speaker discusses the coding aspects of the game, including the use of key codes for camera movement and the implementation of interpolation over time. They experiment with different coding techniques to achieve the desired movement and functionality.

The speaker encounters issues with the game code, particularly with the visibility of sprites and the functionality of the camera. They express frustration over the disappearing sprites and troubleshoot the code to resolve the problems, indicating a hands-on approach to debugging.

The speaker discusses the need to reset the position of an object in their project, indicating that the current setup is causing issues, particularly with the Z-axis value being set to minus 10. They realize that maintaining this specific Z value is crucial for the functionality of the camera.

The speaker finds using ChatGPT for coding assistance to be very useful, expressing a desire to understand how it works better. They successfully implement a solution that allows the camera to function correctly while maintaining the necessary Z value.

The speaker contemplates the design of game levels, considering the creation of eight directional movements for characters. They plan to create a total of 16 sprites, with eight for normal movement and four for attack animations, deciding to animate them later after establishing a basic layout.

The speaker considers making the game turn-based, but decides against it due to potential pacing issues. Instead, they plan to separate player stats and create a simple enemy character, which they envision as a red figure. They also brainstorm the idea of a click-based game mechanic where players click on enemies.

The main objective of the game is to protect the king, and the speaker decides to simplify the mechanics by having the king as the primary focus of protection. They plan to introduce waves of enemies that the player must fend off, with the knight character gaining upgrades as more enemies are defeated.

The speaker reflects on the overall structure of the game, noting that the enemy movement and interactions are starting to take shape in their mind. They express confidence in their design choices and the direction the game is heading, indicating a clear vision for the gameplay mechanics.

The speaker discusses the functionality of tagging game objects, specifically mentioning the ability to make the 'king' character panic and run around. This indicates a focus on game mechanics and character behavior.

The speaker outlines the process of finding game objects using tags, emphasizing the ease of implementation. They plan to adjust the king's movement later, indicating a structured approach to game development.

The speaker attempts to implement movement mechanics for the king character, noting the importance of keeping the z-axis constant. They express a need to sort game objects and decide to delete the player object, suggesting a focus on refining the game environment.

The speaker checks the targeting system for the king character, realizing that the movement function is not triggering as expected. They explore the possibility of using a 'move towards' function, indicating a troubleshooting phase in the development process.

The speaker identifies an issue with enemy movement, realizing that the enemy has a rigid body component that is affecting its behavior. They consider using the rigid body method to resolve the movement issues, showcasing a problem-solving mindset.

The speaker contemplates implementing a damage system for the king character when it collides with enemies. They express a desire to make the game mechanics more extensible and manageable, indicating a focus on gameplay balance.

The speaker discusses the design of game interactions, specifically how clicking on enemies will deal damage. They consider visual elements like a sword cursor and express concerns about balancing the game mechanics within a limited timeframe.

The speaker introduces their game concept during a live stream, describing it as a 2D roguelike where the player must protect a king from attacking monsters. They emphasize the simplicity of the game design due to time constraints, aiming to create an engaging yet straightforward experience.

The speaker considers adding a health bar as a visual indicator for the king's status, reflecting a focus on user experience and gameplay clarity. They also mention committing changes to their project, indicating an organized development process.

The speaker discusses the need to enhance the game by giving the king character health points (HP) and combining enemy stats for better gameplay. They express a desire to polish the game mechanics, indicating a focus on refining the overall experience.

The speaker emphasizes the importance of creating a collider for the king character to ensure that enemy attacks can interact properly, potentially causing damage. They mention the need for particle effects to enhance the visual feedback of sword attacks.

The speaker contemplates different types of enemies that will interact with the king: one that touches the king, another that slashes for more damage, and a ranged enemy that attacks from a distance. They consider making the king character more visually distinct by naming it 'King' and adding HP.

The speaker successfully implements a damage system for the king, allowing it to take continuous damage from enemies. They express satisfaction with the progress, noting that the king can now be affected by enemy attacks, which adds a layer of challenge to the game.

During a stream, the speaker explains the game's concept, which involves protecting the king from enemies. They describe it as a click-based game where players must click on enemies to defeat them, highlighting that the game is still in a rough development stage but showing steady progress.

The speaker discusses the progress of their game development project, specifically mentioning that while the enemy mechanics are not yet complete, they are considering how to implement damage mechanics that activate with animations. They express excitement about the potential for dynamic interactions in the game.

Upon returning from a break, the speaker shifts focus to creating art for the game. They plan to keep the ground design simple but consider adding some decorative elements. The speaker experiments with color choices, opting for darker brown shades, and reflects on the aesthetics of pixel art, indicating a desire for a visually appealing yet straightforward design.

The speaker elaborates on their game concept, describing it as a clicking game where the player controls a knight with an enchanted sword. The gameplay involves clicking on enemies until they are defeated, with the player following a king character through different maps. They mention having a week to complete this project, indicating a manageable timeline for development.

In a conversation about career paths, the speaker inquires about their friend's academic pursuits, specifically whether they are pursuing a master's degree or seeking employment. The speaker shares their own experience of job hunting, expressing some frustration over the lack of success but maintaining a positive outlook. They mention currently working full-time in a sports insurance role, highlighting the balance between work and personal projects.

The speaker reflects on their recent game development activities, noting that the first two days were primarily spent on concepting and creating tiles. They mention completing movement programming on the third day and deciding to add some art elements, specifically trees, to the game.

The speaker shares that one of their games, titled 'Night City,' is currently under review for upload on Steam. They created this game as part of their game design coursework and set a price of approximately $2 to participate in Steam sales, such as the summer and winter sales. They express uncertainty about their future in game development versus returning to university.

The speaker contemplates adding extra content to 'Night City,' such as a sewer level, to enhance gameplay. They also discuss potential additions like apples to the game environment, indicating a focus on detail and creativity in their design process.

As the speaker continues working on the game, they mention completing a tree design and considering other elements like grass and tree stumps. They express satisfaction with their progress and brainstorm additional features to include in the game.

The speaker discusses ideas for gameplay mechanics, such as adding barrels that can be destroyed for potential health rewards. They express enthusiasm for these concepts, indicating a creative and engaging approach to game design. They also mention the need to refine aspects of the game, including combat mechanics.

The speaker discusses adding a cooldown feature to mouse clicks while creating a game. They begin designing a tree stump and grass elements, indicating a focus on environmental details for the game. The speaker expresses satisfaction with the design choices, suggesting a hands-on approach to game asset creation.

The speaker introduces their game project, a simple 'Protect the King' game, which they are developing within a seven-day timeframe. They explain that the king is central to the gameplay, surrounded by enemies that players must click to defeat. The game is designed to be a roguelike, emphasizing the challenge of protecting the king from continuous enemy attacks.

The speaker elaborates on the game's mechanics, where players receive tasks from the king to protect him as he travels to another kingdom. An enchanted sword, given by a wizard, allows players to defeat enemies. The sword's power increases with each enemy defeated, offering players choices for upgrades that can enhance damage or add elemental effects, such as ice or fire.

The speaker draws a comparison between their game and 'Archero,' noting that while 'Archero' involves players moving to defeat enemies, their game features enemies approaching the player. This reflection indicates an awareness of existing game mechanics and a desire to innovate within the genre.

The speaker discusses their experience with a popular mobile game called 'Archero,' mentioning that they played it extensively and created a game analysis video on YouTube. They express enthusiasm for the first game but are uncertain about the second game, indicating they haven't tried it yet.

The speaker contemplates the development of a new game, considering the creation of characters, including a king and various enemies. They ponder whether to implement eight-directional movement for the enemies, reflecting on the complexity of the game mechanics.

While brainstorming names for the new game, the speaker suggests 'Protect the King' but dismisses it as unoriginal. They express a desire for a more unique title and joke about using a random name generator if they can't come up with something suitable during development.

The speaker outlines plans for three types of enemies in the game: a slime enemy that bites the king, a tank-like orc enemy that is harder to defeat, and an archer goblin that shoots arrows from a distance. They detail the mechanics of how each enemy will interact with the player, emphasizing the strategic elements of the gameplay.

The speaker discusses the implementation of player mechanics, including damage and cooldown systems. They express a desire to avoid 'magic numbers' in coding and plan to create a player stats class to manage damage values, initially setting the damage to 20. They also contemplate the balance between allowing players to spam attacks and maintaining game enjoyment.

The speaker discusses the implementation of a damage system in their game, noting the need to add damage functionality. They plan to create a player object to manage player interactions and damage calculations, indicating that the player will take damage as an integer value.

The player is set to deal a fixed amount of 20 damage, but the speaker realizes they need to integrate an attack mechanism into the player script. They contemplate the player's maximum damage capacity, suggesting a maximum of 100 damage, which aligns with the enemy's health, specifically a slime with 100 health points. They propose that after each level completion, the player's attack could increase by 5.

The speaker envisions the game as potentially suitable for mobile platforms, imagining a gameplay mechanic where players tap the screen to defeat enemies. They consider the enemy's behavior, pondering whether it should move towards the player, and reflect on the mechanics of health and damage in relation to the game's design.

The speaker contemplates the artistic direction of the game, weighing the benefits of creating eight-directional animations against the time investment required. They express concern that a non-directional design may appear stiff, but consider rotating the slime character to maintain visual interest. They also engage with a viewer in the stream, discussing their ongoing game development process.

During the stream, the speaker interacts with a viewer named K Tani, welcoming them and discussing their current project, a Unity game for a game jam. They express interest in creating a slime character, seeking inspiration and considering color choices to ensure good contrast with the game environment.

The speaker recalls a previous conversation about a visual novel project that the viewer was developing, indicating a shared interest in game development genres. They express a desire to create a unique slime character, deciding against a green color to enhance visual contrast.

The speaker shares their ongoing struggle to find a job, mentioning that they haven't had much luck but are managing by participating in a game jam.

The speaker discusses their game development process, noting that they are currently working on a game that is not yet fully released but receives regular updates. They express a desire to improve their graphic design skills over time.

The speaker mentions that their game is not available on Steam due to a lack of digital funds, and they inquire about the possibility of hosting it on platforms like itch.io, which allows free game uploads.

The game being developed is titled 'Time Will Travel.' The speaker expresses excitement about the name and discusses its detailed description, indicating that it is well-developed.

The speaker clarifies that their game will remain free even after full development, contrasting this with another project, 'Night City,' which will be a paid game on Steam to recover costs associated with uploading.

The speaker reflects on the importance of advertising for paid games on platforms like Steam, suggesting that games tend to perform better during sales and promotions.

The speaker contemplates the potential for making their games paid in the future, depending on their progress in art and coding skills, indicating a long-term vision for their game development career.

The speaker discusses plans to create animations for their game, specifically focusing on the mechanics of an attack feature, showcasing their commitment to enhancing gameplay.

The speaker discusses the process of editing sprites, initially considering a spreadsheet format but ultimately deciding on a more suitable method. They mention applying a filter and compression settings, specifically using RGBA 32-bit for sprite graphics, indicating a focus on optimizing visual elements for a game.

The conversation shifts to the narrative structure of a game, with the speaker inquiring about the potential for branching endings based on player choices, similar to mechanics found in visual novels. They express interest in how character stats, such as Charisma, could influence the outcomes of the story, leading to various endings.

The speaker reveals the implementation of a stat system inspired by 'Fallout: Las Vegas,' where character attributes like Charisma and money affect the game's narrative and combat outcomes. They highlight the importance of these stats in determining the success of player choices and the overall gameplay experience.

The discussion includes the integration of combat mechanics within the visual novel framework, with the speaker noting the existence of a persistence stat that increases HP. They express surprise at the combination of combat and visual novel elements, indicating a desire to explore this innovative approach further.

The speaker elaborates on the choice stats of strength, charisma, and intelligence, explaining that higher values in these stats enhance the likelihood of success in specific scenarios. They also mention a karma system that requires careful decision-making, adding depth to the gameplay.

The speaker discusses the animation of a slime character, noting its jiggly movement but expressing a need to adjust the speed for better gameplay experience. They seek to orient the slime towards enemies, indicating a desire for more dynamic interactions within the game environment.

The conversation touches on quality of life features in game development, with the speaker acknowledging the benefits of new functionalities that enhance gameplay. They reflect on the continuous improvement of their game, emphasizing the importance of integrating user-friendly features to enrich player experience.

The speaker discusses the challenges of positioning an object correctly in a game environment, expressing frustration over the object's orientation being backwards. They experiment with different placements and rotations, trying to achieve the desired visual effect.

The speaker realizes that the collider needs to be adjusted to match the new orientation of the object. They contemplate the necessity of flipping both the object and the collider to ensure proper alignment, indicating a deeper understanding of game mechanics.

The speaker outlines a plan for implementing enemy behavior in the game. They decide that the enemy should always face left initially and discuss the importance of making certain properties protected rather than public, indicating a focus on encapsulation in their coding approach.

The speaker acknowledges that the current state of the game is still a prototype, emphasizing that while it is functional, it is not yet perfect. They set the maximum health of an enemy character, the slime, to 100, indicating a specific design choice in gameplay mechanics.

The speaker contemplates the purpose of a sorting layer in the game but decides to leave it at its default setting for the time being. This reflects a cautious approach to game design, prioritizing functionality over complexity at this stage.

The speaker devises a logic for the enemy's orientation based on its position relative to the player (the king). They plan to flip the enemy when it is on the left side of the target and leave it unflipped when on the right side, showcasing a strategic approach to enemy AI behavior.

The speaker reflects on the efficiency of their coding logic, noting that the flipping mechanism runs every frame, which may not be the most efficient method. However, they conclude that it is acceptable for the current stage of development, indicating a balance between performance and functionality.

The speaker discusses the process of game development, specifically focusing on implementing overrides in C#. They mention the need for a 'virtual void' declaration to enable overrides, indicating a technical understanding of object-oriented programming principles.

The speaker elaborates on sprite rendering, particularly how to flip the sprite based on the enemy's position. They decide to implement a protected variable for the sprite renderer to avoid code repetition, demonstrating a focus on efficient coding practices.

The speaker transitions to managing box colliders, discussing how to resize them through code. They express a need to set default sizes and offsets for colliders, indicating a meticulous approach to ensuring proper collision detection in the game.

The speaker continues configuring colliders, specifying the default collider size and offset values. They mention using specific vector values, such as 0.84 and 0.59 for size, and -0.76 and 0.229 for offset, showcasing attention to detail in the collider setup.

The speaker tests the functionality of the colliders and sprite flipping, noting that the mechanics are working as intended. They describe the flipping behavior as a 'cheesy strategy' but acknowledge its effectiveness, reflecting a practical mindset in game design.

The speaker briefly acknowledges a message from a colleague named Wes, indicating a collaborative environment. They express uncertainty about whether they missed the message or just saw it, highlighting the informal nature of their communication.

The speaker discusses the mechanics of enemy spawning in their game, planning to have a total of 10 slimes spawn every 2 seconds. They express the need to create a spawner for each enemy individually, which they anticipate will be a cumbersome task. The speaker contemplates how to make this process more efficient and extendable.

The speaker emphasizes the importance of implementing a user interface that displays the health of enemies. They suggest adding a small health bar on top of the enemies, along with other UI elements such as player art and sword art. This UI will enhance gameplay by providing players with crucial information about enemy health.

The speaker plans to create a visual feedback mechanism for when enemies are damaged. They intend to make the enemy flash red upon being clicked, utilizing the existing sprite renderer. The implementation involves changing the color of the sprite to red temporarily to indicate damage, followed by reverting it back to its original color.

Reflecting on their progress, the speaker notes that they have made significant advancements in the game within a 3-hour stream. They mention completing various tasks, including asset creation and programming, and express satisfaction with the amount of work accomplished. The speaker indicates a desire to continue working on the game to fulfill their jam submission.

As the stream comes to an end, the speaker contemplates taking a break but expresses a commitment to continue developing the game. They thank the viewers for joining the stream, describing it as a chill experience where they managed to achieve a lot in a relatively short time. The speaker concludes with a friendly farewell, indicating they will return for future streams.