#GamePrototyping

[pawzngauze]

Development Plans!

I had an idea to help me find which game resonates the most with viewers, so I decided to start a series of rapid prototypes that will last a month! Each prototype will be the "prologue" for a full game and will be available on itch.io. Whichever game gets the most support from fans - fanart, donations, fanfic, reblogs, and more! - will be turned into a full game. If multiple are extremely possible, I could develop more, but it will take longer. I think this could be a fun way to get others involved in the game development process!

[warilyshinyconstruct]

About Me – Brandon Alchin:

My name is Brandon Alchin, and ever since primary school, I’ve been fascinated by the “magic” found in video games. A big part of my childhood was spent playing games with my younger brother and parents, and there was something truly special about those shared experiences. Rather than growing out of it, I became even more curious—wanting to understand what made games feel so powerful, so immersive, and so emotionally resonant.

I began asking myself: what creates that feeling? Why do games draw us in the way they do? And how can I recreate that same sense of wonder for others? These questions sparked my interest in game development and eventually led me to study a Bachelor of Games and Interactive Environments at QUT.

My goal is to become a game developer who can create experiences that capture that same childhood magic—games that speak to people of all ages, backgrounds, and identities. I’m excited to explore how design, interactivity, and player-centered thinking come together to craft unforgettable experiences.

Platformer Game Elevator Pitch:

Backtrack: Lost in the Wild is a pixel-art survival platformer where a lone camper is stranded deep in a dangerous jungle. Armed with only a knife and his instincts, he must outsmart wild predators, use environmental traps, and uncover lost tools to survive and find his way back to safety. It's a game of action, timing, and tactical creativity where every decision could mean life or death.

Development Post – Backtrack: Lost in the Wild:

This week, I made major progress on my platformer prototype, Backtrack: Lost in the Wild. Set in a dense, dangerous forest, the player’s goal is to survive, adapt, and score by outlasting natural threats and defeating enemies in creative ways.

What I Built:

Created basic enemy AI, including patrolling guards and their defensive block ability, which reduces incoming melee damage by 50%.

Designed early level layouts, focusing on spaciousness and multiple traversal paths.

Midway through, I introduced a vine and boulder mechanic—cutting vines drops boulders, which can crush enemies or open new paths.

Added a score system based on time + enemies defeated. The final score is displayed at the end to encourage replayability.

Lessons Learned:

Implementing the boulder mechanic took longer than expected. I wasn’t fully comfortable with collision logic in GDevelop, especially when dealing with dynamic events (cutting vines triggering multiple interactions). Similarly, using a timer to calculate score was a new challenge for me. After a few failed attempts, I learned how to sync the timer with event triggers to track player performance accurately.

Design Insights:

Reading Fullerton’s Game Design Workshop helped me appreciate the importance of interactivity and consequence. By allowing the boulder to kill both enemies and the player, I added a layer of risk vs reward, which testers found interesting. This aligns with Fullerton’s principle of meaningful choices—players need to decide when and how to use the environment to their advantage.

Postmortem – Backtrack: Lost in the Wild:

With my Backtrack: Lost in the Wild prototype completed, I’ve taken some time to reflect on what went right, what didn’t, and how the project helped me grow as a designer.

What Worked:

The vine and boulder mechanic was a standout. It gave players options: crush enemies, unblock paths, or—if used carelessly—crush themselves. This added both strategy and tension.

The final score system encouraged replayability. Playtesters said they felt motivated to improve their time or get perfect runs, which was exactly the goal.

The forest setting and muted visuals (with 32x32 sprites) helped convey a grounded, survival-themed tone.

What Could Be Improved in Development:

I struggled with the enemy block mechanic. While it technically worked, most testers never used it or didn’t notice its effect. I think better visual feedback (e.g. animation, sound, or flashing block icon) would have helped.

The boulder collision logic was fragile—at times, it crushed unintended elements or wouldn’t fall correctly. I should have isolated it in a test scene first.

What Could Be Improved in Design:

I didn’t include any onboarding/tutorial—players had to figure out climbing, blocking, or boulder usage by trial and error. One said it was fun, but another struggled at first. I’ll include subtle prompts or signs next time.

The enemy health system needed more balance. Many enemies could be one-shotted unless they blocked, which led to some players ignoring the block feature entirely.

Playtest Feedback Highlights:

“I never used the block mechanic—enemies were too easy to kill.” “Loved that I could also crush myself with the boulder. Risky but fun!” “Beating it for the first time and getting a perfect score was super satisfying.”

Final Reflection:

Fullerton’s emphasis on the player-centric approach really resonated during this process. I realised I was designing around cool mechanics instead of for the player experience. When I reframed the game as a risk-and-reward survival challenge, everything clicked. I now understand how important iteration and playtesting are in aligning your design with the feelings you want to create.

Asteroid Game Elevator Pitch:

Void Runners is a fast-paced arcade shooter where players pilot a sleek spacecraft through asteroid fields and alien ambushes. Your mission: survive deep space while racking up a high score by blasting asteroids, dodging debris, and avoiding hostile drones.

The game combines classic Asteroids-style gameplay with modern twists like power-ups, enemy swarms, and combo scoring to encourage precision and speed. Designed with short sessions in mind, Void Runners offers high replay value and escalating challenge, perfect for players who love twitchy, reflex-based gameplay.

Void Runners is a retro-inspired space shooter where you dodge, destroy, and drift your way through asteroid belts and drone strikes. Fast action and risky power-ups keep each run intense. Can you master the void and top the leaderboard?

Development Post – Void Runners:

This week, I began building the core systems of my asteroid shooter prototype, Void Runners, in GDevelop 5. My primary focus was to get the player controls, asteroid spawning, and basic shooting mechanics functional.

What I Worked On:

Created a top-down movement system with rotation, inertia, and thrust.

Implemented asteroid generation at random angles and speeds.

Designed bullet shooting and collision effects, including temporary particle explosions when bullets hit asteroids.

Began experimenting with enemy drones that follow the player.

Design Goals:

My aim was to maintain the snappy feel of retro arcade games while adding small twists, like:

A combo system that rewards quick asteroid hits

Rare power-ups that increase fire rate or slow time

A danger meter that increases difficulty the longer you survive

What I Learned:

Creating smooth space-style controls was trickier than expected. Adding gradual acceleration and drift meant I had to carefully balance speed, rotation, and stop time to avoid the player feeling "floaty" or completely out of control.

According to Fullerton (2018), controls are part of the formal elements of gameplay. In tuning these, I’ve been trying to make the game “feel right” in the hands—even before enemies or scoring are added.

Postmortem – Void Runners:

Now that the prototype for Void Runners is complete, I’ve taken some time to reflect on what worked, what didn’t, and how to move forward with my design.

What Worked:

The core loop of shoot → dodge → repeat was tight and addictive. Players wanted “just one more run,” which is a good sign.

The random asteroid generator created enough variation in each run to avoid repetition.

Adding a combo score multiplier introduced tension: do you take risks for higher points or play it safe?

What Could Be Improved in Development:

I struggled with hitbox accuracy—sometimes bullets visually passed through asteroids without a collision triggering. I learned to adjust object points and collision masks in GDevelop to resolve this.

Implementing a high score system with local saving took more time than expected, especially since I was unfamiliar with variables and storage events in GDevelop.

What Could Be Improved in Design:

There was no onboarding/tutorial to explain controls. Some players didn’t realise they had inertia-based movement and kept trying to “stop” on a dime.

The enemy drones were too aggressive, especially for early levels. I need to pace enemy introduction more carefully or add visual indicators before spawning them.

Playtest Feedback:

“The movement is fun once you get the hang of it, but it took me a few tries.” “I liked the combo system, it made me want to be riskier.” “Maybe start with just asteroids before adding enemies. The first game felt overwhelming.”

Takeaway:

This project helped me better understand player feedback loops and how even simple mechanics can become engaging when balanced with risk and reward. As Fullerton notes, game mechanics should encourage mastery over time—next time, I’ll integrate tutorial moments more naturally and avoid front-loading difficulty too soon.

Racer Game Elevator Pitch:

Turbo Rush: Canyon Drift is a fast-paced, top-down arcade racer where players drift through narrow canyon tracks, dodge hazards, and battle the clock to set record-breaking lap times. Speed is everything—but so is control.

The game focuses on momentum, drift mechanics, and precision turning across visually distinct, obstacle-heavy tracks. Players can collect temporary speed boosts, avoid rockfalls, and chain drifts to maintain top speed while racing to earn gold, silver, or bronze rankings.

Turbo Rush is a time-attack canyon racer with physics-driven drifting and high replayability. Challenge your reflexes, shave seconds off your best laps, and climb the leaderboard—if you can stay on the road.

Development Post – Turbo Rush: Canyon Drift:

This week I began developing the foundational systems for my arcade-style racer, Turbo Rush: Canyon Drift, in GDevelop 5. The focus was on tight control, track collisions, and lap timing.

What I Built:

Created car movement system using acceleration, friction, and rotation for drift-like control.

Designed collision boundaries for canyon edges and off-road penalties.

Added lap detection system using invisible checkpoints to count progress and prevent cheating.

Implemented timer UI to track player lap time and determine medal thresholds.

Game Feel Goals:

The aim was to make drifting feel challenging but responsive. Inspired by classic top-down racers like Micro Machines, I wanted to reward smooth cornering and risk-taking without being punishing.

To test this, I tuned the car to gain traction slowly, allowing players to “slide” around corners with enough practice.

What I Learned:

Implementing realistic-feeling drift required balancing multiple values in GDevelop’s physics and velocity logic. At first, the car spun too freely—after tweaking deceleration and rotation dampening, I got something that felt playable.

Fullerton’s emphasis on iterative prototyping reminded me not to aim for perfection on the first try. The initial version didn’t feel “right,” but I was able to test and tweak small changes to get closer to the intended experience.

Postmortem - Turbo Rush: Canyon Drift:

Now that the first prototype of Turbo Rush: Canyon Drift is complete, I’ve taken time to reflect on the process and what I learned.

What Worked:

The drift mechanic landed well—after tuning, it felt smooth and gave skilled players an edge.

Players liked the lap-based goal structure, especially the visible time tiers (Gold/Silver/Bronze).

Track layout encouraged replayability, with multiple testers saying they “wanted to beat their last time.”

What Could Be Improved in Development:

I initially set up lap tracking with only a start/finish trigger, which led to players skipping chunks of the track. I later added checkpoints but wish I had planned that earlier.

I also spent too long on visual polish (dust trails, UI transitions) before the core game feel was ready. Next time, I’ll hold off polish until the game loop is locked.

What Could Be Improved in Design:

No tutorial or prompts meant some players didn’t realise drifting was key to faster laps. I should include visual cues (like ghost trails or icons) to guide behavior.

Tracks lacked variation in hazards. I’d like to add falling rocks, oil slicks, or collapsing bridges to mix things up in future versions.

Playtest Feedback:

“Drifting is super fun once you learn how to control it.” “I ignored the bronze/silver/gold system until I saw my friends comparing scores. Would be cool if it had a leaderboard!” “Wish there was more risk—maybe obstacles or destructible shortcuts?”

Final Reflection:

This prototype highlighted the value of iterative tuning. As Fullerton (2018) notes, good games aren’t born—they’re shaped by feedback, testing, and revision. I originally focused too much on how it looked. By the end, I saw how important it is to build around the player experience first. Speed, control, and competition now drive every mechanic.

Assignment 3 – Development Post: Echoes of the Tower:

This week, I made significant progress on my 2D platformer prototype, Echoes of the Tower. Set inside a dark, mysterious ruin, the game revolves around exploration, combat, and environmental navigation. Players must survive a crumbling tower filled with patrolling enemies and hidden vertical routes, using careful movement and strategic timing to reach the exit.

What I Built:

Implemented the core player movement system, including a ledge-latching mechanic that lets the player grab and climb ledges by pressing toward them.

Designed and tested enemy patrol AI, with basic line-of-sight movement and damage upon contact.

Added a respawn and health system, allowing the player to take damage and restart from checkpoints.

Developed a complete playable level that tests traversal, enemy avoidance, and exploration under pressure.

Lessons Learned:

The ledge-latching mechanic was surprisingly complex. I initially underestimated how unclear it might be to players—several testers struggled to discover how to use it. I learned that even well-functioning mechanics can feel “invisible” without feedback or tutorial cues. This taught me the importance of not just building mechanics, but also teaching them through intuitive design.

Design Insight:

Inspired by Fullerton’s Game Design Workshop, I focused on creating meaningful player decisions. The ledge-latching system became more than just a movement option—it represented a choice between risk and safety. Should players attempt a risky climb over a dangerous pit, or find a longer route? This kind of agency is key to keeping players engaged.

Assignment 3 – Playtesting Post: Echoes of the Tower:

This week, I ran a structured playtesting session with six naïve users to evaluate the prototype of Echoes of the Tower. The session focused on usability, player understanding of core mechanics, and overall experience.

Playtesting Setup:

Each participant played the game without prior instruction and was asked to “think aloud” while playing. After the session, they completed a detailed survey and participated in a feedback discussion. Four of the six users were from my game’s core demographic—players familiar with 2D platformers.

Key Observations:

The ledge-latching mechanic caused confusion. Multiple players did not understand how to use it, resulting in them getting stuck or assuming the game was broken. Once explained, most found it enjoyable.

The lack of onboarding or tutorial significantly impacted early gameplay. Without any visual cues or prompts, even experienced players were unsure how to proceed.

The visuals and atmosphere received positive feedback. Players praised the moody aesthetic and sense of isolation the environment created.

One of the most frequent requests was for better feedback systems—when something changes (e.g. a door opens, a checkpoint is reached), there needs to be a sound, animation, or camera cue to reinforce it.

Memorable Quotes:

“The movement feels great—but I had no idea I could climb that ledge.” “I got lost after beating the enemies. Wasn’t sure what I’d triggered.” “Loved the mood. It really felt like I was exploring something ancient and dangerous.”

These sessions were incredibly helpful in identifying gaps in player understanding. I now see how critical it is to test not just if a mechanic works, but how players discover and use it naturally.

Assignment 3 – Postmortem: Echoes of the Tower:

With the prototype for Echoes of the Tower now complete, I’ve taken time to reflect on the project’s highs, lows, and everything in between. This postmortem captures the most valuable lessons from this phase of development.

What Worked:

The ledge-latching mechanic, once understood, was a standout feature. It gave platforming a unique vertical rhythm and added challenge without needing complex level design.

The overall game atmosphere was praised by nearly all testers. The visual tone and ambient audio created a strong sense of place and tension.

The core gameplay loop (explore, survive, reach the exit) was simple but effective. Most players found the experience satisfying once they figured out the mechanics.

What Could Be Improved in Development:

I underestimated how confusing core mechanics would be without onboarding. A simple tutorial section would have saved many players from frustration.

There was little to no visual feedback when progress was made. Players needed clearer confirmation when things happened (e.g., unlocking a door).

The enemy AI was functional but basic. Adding attack tells or reaction animations could make encounters more dynamic.

What Could Be Improved in Design:

The prototype lacked context or narrative framing. Players wanted to know who they were, why they were in the tower, and what their goal was beyond survival.

The ledge-latching mechanic needs clearer visual indicators—perhaps a hand reach animation or glow when a ledge is grabbable.

There were no optional paths or secrets. Adding rewards for exploration would increase replay value.

Feedback Highlights:

“I loved the idea of the ledge grab—once I figured it out, it felt really smooth.” “It’s cool that you don’t explain everything, but I got stuck early on and thought it was a bug.” “I'd like to see more variety—maybe different enemy types or hidden rooms.”

Final Reflection:

Fullerton’s principle that “games are built through iteration” became a central theme throughout this project. I began designing around what I thought was cool. Through playtesting, I shifted focus to what players needed to understand and enjoy. That shift—from developer-centric to player-centric—was the most important lesson of all.

Next steps? Add a short tutorial section, improve visual clarity, and expand on the tower’s world. The foundation is strong—now it’s time to build something even better.

[vieiravortex]

ALWAYS VEILED 👁️ | C++ Game PROTOTYPE 🎮 | Happy Birthday Tribute to THE RING & THE OMEN ⚡ | From VIEIRA VORTEX 💖

🎮 Always Veiled — a heartfelt prototype (version v18.05.1982) from Vieira Vortex, created with love for someone very special (who we’re, uh, a bit shy to name 😉). While we're not sure she’ll ever see it, we can't help but hope for a little miracle — maybe just a glimpse of attention from her. 🌟

This prototype, inspired by classics like The Ring 🎬 and The Omen 👻, is just the beginning. It's far from the final vision, which will lean more into psychological horror in the style of Silent Hill 🏚️. For now, it’s lighthearted and simple, with whimsical graphics and a calming pace — though there’s just enough eerie mystery to keep you curious 😌👀.

And here’s something you might not expect: Always Veiled isn’t built on some pre-made engine. Nope, it’s all made from scratch using C++ and SFML. Sounds boring to some, but to programmers, it’s a small triumph of coding and dedication 🖥️🔥. It’s not a flashy engine—just raw code, custom-made to bring this world to life, and that’s part of what makes it special. (We know, it’s a bit geeky, but we’re proud of it!) 😏

We hope this prototype will one day reach the one it's meant for, though we know the chances are slim… but hey, miracles happen, right? ✨

The source code is available on GitHub, so if you're a fellow coder or just curious about how it all came together, take a peek! 🖥️🔍

More info at: alwaysveiled.fandom.com

This is just the beginning… and if it happens to catch the attention of the one it's dedicated to, well, that would be our miracle. 💫💖

Oh, and don’t get too comfy thinking this will stay 2D forever — the final game will be much more than this humble prototype, with a deeper, more immersive experience! 👀✨

[ydrhxx-gamedev]

Elevator Pitch: Fantasy World

For my first prototype in IGB120, I’ll be developing a side-scrolling adventure RPG using GDevelop. Before starting development, I wanted to establish a strong creative direction, focusing on worldbuilding, player growth, and engaging moment-to-moment gameplay.

Fantasy World is a retro-inspired platformer RPG that combines strategic combat with rich storytelling. Players step into the shoes of a young mage who awakens in a fallen kingdom filled with danger and mystery. Armed only with a glowing staff and fragments of lost memories, players must journey through corrupted forests, ruined cities, and forgotten caves to uncover who they are, and how to save what’s left of the world.

As players fight through increasingly dangerous regions, they gain XP to unlock new spells and skills through a visual skill tree. Abilities range from elemental attacks to protective shields and agility-based upgrades, allowing players to shape their playstyle and adapt to different enemy types. Combat emphasizes positioning, skill choice, and timing rather than random button presses.

What is your gameplay?

My game will focus on real-time spellcasting combat and movement-based exploration. Players will control a young mage who can run, jump, and use elemental spells to defeat enemies and navigate the world. As they level up, they unlock new abilities that enhance damage, defense, or movement. Some spells help clear enemies, while others provide mobility boosts or protective shields. Strategic use of skills is key to surviving tougher areas.

The world is divided into themed zones, each with new enemies, challenges, and story pieces. Checkpoints allow players to rest, recover, and access the upgrade shop. Players gain XP and gold by defeating enemies, which they can use to customise their build and unlock new paths forward.

Why will it be compelling?

Players will be engaged by the mix of story and skill-based action. As they progress, they uncover a deeper narrative about the mage’s past and the fall of the kingdom. Combat requires timing, positioning, and smart use of spells, rewarding creative play and experimentation.

The evolving skill tree gives players freedom to choose their own playstyle. Focusing on high damage, healing, or support abilities. Combined with colorful pixel art, atmospheric zones, and satisfying upgrades, the game creates a sense of discovery and purpose as players bring balance back to a fading world.

Game Controls: - WASD or arrow keys to move - Spacebar to jump - Z/X/1/2/3 for attacks and abilities - E or ESC to open the inventory and menu

Unique Selling Points: - Story-Driven Combat RPG: A rich narrative unfolds through in-game dialogue and cutscenes as players travel from zone to zone. - Skill Tree Progression: Players gain XP to unlock and customise powerful magic-based abilities for attack, defense, or mobility. - Tactical Encounters: Combat requires players to time their spells and use the right upgrades to overcome escalating enemy threats.

Target Audience: Ages 10 and up. Designed for fans of magic-based RPGs, pixel-art adventure games, and fantasy storytelling.

Setting: A once-magical kingdom now overtaken by dark energy and twisted creatures. Each area presents a new visual theme, atmosphere, and challenge.

Player Motivation: Players are driven by the story’s mystery, a desire to unlock stronger abilities, and the rewarding loop of exploring dangerous lands to restore light to a fading world.

[thethirdkate]

Photo Match Prototype #1

This is a prototype for a game where the has to explore the scene to take photos matching the target. The mechanic is functional - the player can:

- See the target, and hold alt to bring it up as an overlay

- Move around the scene and press space to take a photo

- Click the button to compare and see if their photo is a match

In terms of gameplay, the ultimate idea is that the player is not given an identical target, but a sketch or outline of some kind. They will take multiple photos, which will then form a collage to make one big final picture. The end result may be unexpected - for example, their pictures of plants and kitchenware add up to make a mosaic of a rabbit. I’d also like to explore a version using a wireframe shader to make lineart rather than colour blocks.

[codenamearagorn]

Dev Update #8

Once I’d changed the main theme of the game, I had to get back into Power Map and and changed it all.

If you want to know more, dowload the pdf bellow and enjoy :)

[valdram]

 • https://gamejolt.com/games/disk-2-little-tasks/492853  

https://www.facebook.com/Zolynh/posts/1718191624987324

https://vk.com/zolynh?w=wall-26248251_376

[redrustgame]

Modeling of the robocat is under way! #zbrush #gamecharacter #gameboss #gamedev #gameprototype https://www.instagram.com/p/BoMX3vnnYqz/?igshid=9hrszu0ycg8f

[carlestenorio]

Tercer y ultimo speed modelling de 10 minutos de hoy. Preparando material de formación y para primer proyecto indie del curso de Game Art 3D con Blender 2019-2020 de escola JOSO Sabadell @escolajososabadell . . Con este modelado de asset, explicare la potencia y versatilidad de las herramientas Bevel y Inset que tiene Blender. Tambien el Add-on de apoyo Loop Tools. Con estas herramientas es cómodo y agil modelar objetos con superficies esfericas y modelar agujeros dentro de ellas . . #escolajososabadell #jososabadell #artschool #gameart #gamedev #indiedev #videogames #blender #madewithblender #3dart #prototype #gameprototype https://www.instagram.com/p/B3Z-yxio9wi6VxMPAjs_Bad7rCpFuVSe7gOn3U0/?igshid=rm8porq11ldn

[devilsworkshop]

I have finally understood the concepts of ZDepth Sorting in Construct. These are the steps to follow to make a functioning ZDepth prototype.

1. Create a bunch of objects that needs to have ZDepth. They should all be on the same layer, else this wont work. In the animated gif above, the trees, and the car are the objects that will have ZDepth

2. Create a Family of those object you want to have ZDepth.

3. Assign a instance variable to the family.

This variable has a value of 0. In the example above- the instance variable is called ZorderFamily.

4. Instruct the game system to check if the objects from that family are on-screen. If they are on-screen, assign their current Y value o the their instant variable.

5. If they are still on-screen, tell the game system to sort all objects in that family, that are on-screen by their new Y value.

----------------------------------------------------------------------------------------------

Refer: https://devilsworkshop.tumblr.com/post/176223060971/with-some-unconditional-help-from-a-construct3

[maxiemax]

View this post on Instagram

A post shared by Games Driven Marketing (@naknickgames)

Prototyping a pizzle game 🀄 Would you play it? #gameprototype #gamedev #puzzlegame #puzzle #hypercasual #html5games #prototypegame https://www.instagram.com/p/ByheJOgj-CM/?igshid=16jbrlhr2t057

[imaginethatdesign-blog]

Our new Cocoa Rush boxes for prototypes have arrived. Now it's time to put them all together and send them out to publishers. Look out game publishers, Cocoa Rush may be coming your way. If you are interested and would like to consider our game, message us now. Thanks! #CocoaRush #prototype #gamedesign #gamedevelopment #ITDGames #tabletopgames #boardgames #kurtkeller #graphicdesign #bgg #boardgamegeek #tabletopgaming #games #prototyping #gameprototype https://www.instagram.com/p/BztIf1eB1Kb/?igshid=r5pts3082695

[giftcoursecoupon-blog]

#Unity #GameDev

[boardgamesfrancesco]

Per chi è interessato al Game Design segnalo FAI IL TUO GIOCO, corso di game design e gamification design ora in PROMO speciale fino al 2 maggio, al prezzo di 199 euro invece di 590 euro. Per chi pensa che un corso online in autonomia può portare a seguire poco e non dedicarci abbastanza impegno, con Fai il tuo gioco sarà diverso: ci sarà un gruppo fb con vari #QUIZ sui giochi, il #gamedesign e la gamification. Il CONTEST è questo: per ogni risposta esatta verrà dato un punto, chi ottiene il maggior punteggio VINCE un'ora aggiuntiva di consulenza personalizzata sul proprio prototipo di gioco da parte dei docenti game designer professionisti (con il docente più in linea con il genere del tuo progetto di gioco). Per info: pagina fb di Fai il tuo gioco (o tel. 3497869405) • • • • #giochidatavolo #corsogamedesign #boardgamedesign #corsoboardgame #faiiltuogioco #coaching #coachinggame #gamingitalia #corsogiochi #gamification #corsogamification #tesiteam #gameprototype #gamedesigner #formazioneonline #autoridigiochi #crearegiochi #gamewebinar https://www.instagram.com/p/B-_vzyNKt0S/?igshid=rmutn8i9yc4l

[shani-t8]

Currently working on my prototype 2 for class it's so close I'm pretty proud of it #gamesstudent #gamedesignstudent #igped #womanintech #unity #gameprototype https://www.instagram.com/p/B8isD0PnIIO/?igshid=1qwx4fvliuclx

[codenamearagorn]

Dev Update #3

After talk with Wayne, and learn a lot from him, I decided to put a prototype in place. nothing fancy, just to test if the game is fun enough. For the first look, I "borrowed" from a few other games some sprites and buttons and send all to Wayne. Lets find out how it go!