Click to PLAY Gunslinger
| Name - Surname | Titles |
|---|---|
| Egehan EMRE | Scrum Master / Product Owner / Developer |
| Dursun Can AYDIN | Game Artist |
| GUNSLINGER |
|---|
Gunslinger is a Roguelike, Turn-Based Card game. The game’s core gameplay revolves around strategically managing a limited number of cards with different effects in your deck to defeat enemies in complex, turn-based battles and progress through map. As players progress, they can achieve different cards through combat and item drops to alter the gameplay loop for each run and future runs by unlocking new cards and weapons that permanently appear in subsequent runs to provide replayability.
Gunslinger is a Roguelike, Turn-Based Card game that places players in a challenging and strategic enviroment where every decision can mean the difference between victory and defeat. The gameplay is centered around a unique bullet system integrated with card mechanics, creating complex, turn-based battles that require thoughtful planning and adaptability.
In Gunsliner, each card in your deck represents a specific action or bullet type which you must use strategically to create chain combos and advance through levels. Players start with a basic deck, but as they progress, they can acquire new cards through combat and item drops and also unlock permanent unlocks for the next playthroughs. This deck-building mechanic allows for extensive customization, enabling players to develop unique strategies tailored to their playstyle.
Our approach for combat in Gunslinger is turn-based, with a focus on anticipating and countering enemy actions. Each card played adds a bullet to your magazine, which is fired at the end of your turn. Observing the enemy intents is crucial as it allows you to place your own bullets strategically to counter their moves effectively. This layer of strategy distinguishes our product from traditional card games, adding depth and complexity to each encounter.
One of the standout features we have in our game is in it's approach to deck-building mechanics, we introduce different card types such as attack/effect/buff cards. Players start with a basic deck but can customize and enhance it by acquiring new cards through gameplay leading to insane chain combos if used right. This system not only allows for significant player choice and strategic depth but also includes a permanent unlock system. This means that new cards and weapons unlocked during runs will appear in future playthroughs, providing ongoing opportunities for evolving strategies and ensuring that each game session feels fresh and engaging.
This game is for those who enjoy: Strategy Games, Turn-Based Combat, and for our fellow Card Game Enthusiasts.
Estimated Points to Complete in the Sprint: 13 Points
How to complete points: We have a total of 40 points worth of backlog that need to be completed throughout the project. When divided into 3 sprints, it was decided that the first sprint should start with 13 points.
Daily Scrum: Our Daily Scrum meetings were held on Discord. Examples of Daily Scrum meetings are shared below:
-
Sprint board update:
State of the game:
- We finished the most of the playable prototype, mechanics are mostly working as intended on the coding side of things, we haven't done much on the art side since it was in the prototyping stage.
- Team Changes and Role Adjustments: We experienced team changes with 2 members leaving and 1 new member joining. Accordingly, roles were adjusted, and the Scrum Master was changed.
- Task Distribution Reorganization: It was decided to reorganize the task distribution within the team for the upcoming sprint to ensure more effective collaboration and workload balance.
Estimated Points to Complete in the Sprint: 14 Points
How to complete points: We have a total of 40 points worth of backlog that need to be completed throughout the project. In first sprint we finished 13 story point worth of content. When divided into 3 sprints, it was decided that the second sprint should have 14 points.
Daily Scrum: Our Daily Scrum meetings were held on Discord but we decide to do sprints on text format and only have meetings when important stuff happens. Examples of Daily Scrum meetings are shared below:
- Since our other members were not active during the sprint, we only had 2 people working on the project for this sprint, we drew most of our card and element sprites, connected them to game through code to create scriptable cards, turn system, combat manager, map algorithm, enemy ai etc. game is in playable state but needs adjustments to establish a DEMO version.
- Team and Role Management: Two members were mostly inactive for the entire sprint, they failed to establish task given to them even when those were considered easier tasks, One member had to do others tasks to meet the requirements for the sprint by overworking himself. Artist and Programmer done their part.
Sprint board update:
State of the game:
Estimated Points to Complete in the Sprint: 13 Points
How to complete points: We have a total backlog of 40 points to complete throughout the project. We completed 13 story points worth of content in the first sprint and 14 story points worth of content in the second sprint. When divided into 3 sprints, it was decided that the third sprint should have 13 points.
Daily Scrum: In the previous sprint, we decided to hold our daily scrum meetings in text format on Discord and only meet when important things happened, we continued this. Examples of daily scrum meetings are shared below:
-
Sprint board update:
Final visuals of the game:
- We focused on completing the art and structuring the interface. While doing this, we added the animations and audio files. Finally, we fixed the major bugs, made the necessary adjustments and finished the playable demo.
- Art and Interface Completion: The focus on completing the art assets and structuring the interface was successful. The final visuals of the game are polished and cohesive.
- Animations and Audio Integration: Integrating animations and audio files added a layer of polish to the game.
- Bug Fixes and Adjustments: Major bugs were successfully addressed, and necessary adjustments were made to ensure a smooth and enjoyable gameplay experience.
- Playable Demo Completion: The team successfully completed the playable demo.