Adam House

Gday, My name is Adam.Im an Australian video game developer who uses Maya,3d coat, photoshop, and unity.my dream is too create my own fictional universe of my own characters and aliens https://hrhouse3.wixsite.com/adamhousegd

[adamtheamazing5]

Brickstar the lego man - A 3D model collection by Adam the Amazing (@AdamtheAmazing)

This is the collections I made of Brickstar and his animations for a game animation. You can see his animations including facial animations

Finally! Brickstar, his animations and his unused model can be view on your device in 3D!! Now you can get a closer look at his handsome face and animations!

Feel free to look here on sketchfab.

[adamtheamazing5]

Postmortem for Maniacs (Adams version)

Type: public product.   Genre: First person shooter and action-horror. Engine: Unity.   Key Roles: Animation, programming, lighting, and game design. Released: 29th May 2026 Last updated: 3rd June 2026.  Learned from: Make a horror survival game in Unity from Pepe Jepson on Udemy. Made by: Only myself (however borrowed some third-party assets and shared from the instructor).  

After a few busy years of development hell, my next game: Maniacs (Adams version) is finally here!! 

I was originally going to complete it back in 2023, but I had some difficulties polishing the game, but now I have enough Unity game engine and programming experience to finish it once and for all and release it to the public.

I started this course on Udemy since it had some important things to learn about like Melee combat, using the torch, saving items and weapons you have and loading the game, post processing, and etc. On the downside it is targeted as a “beginner-friendly course” which what I taught was mostly simplistic, but still good to learn. So, by the time I completed all the tutorials, the game was still buggy and unfair to play, so I fixed as many bugs as I could and polished the game. Am I satisfied with what I learned? Read below According to the games description: On this unlucky night, you have been kidnapped and scheduled to be tortured to death soon by a psychotic group of Maniacs, you eventually escaped with your life before a knife touched you.

You find out you are on a deserted abandoned island filled with other Maniacs guarding the island.

With no contact to the outside world and no easy way to escape the island, you decided the only way to escape safely was to take matters in your own hands by finding and killing their leader: General Carcus, who is believed to be reasonable for multiple kidnappings, tortures and murders.

You hear that General Carcus does not like to be disturbed, and will shoot at anyone who disturbs him, so stock up and prepare for the fight.... of your life. Will you be able to survive the night of the Maniacs? or perish forever? 

WHAT WENT WELL?:

Made certain trigger box one-shot that responds to Player collision to play one-shot sound once than destroy itself else it will play again in a certain amount of time once the Player reaches its trigger box again with only 2 public variables.

Made enemies open doors themselves by simply walking towards them.

Made 3 different melee weapons that have different cooldown timers and damage that the Player can experiment with when fighting enemies to see which weapon works for the Player.

I made a script where it determines how many enemies have spotted the Player and are currently attacking the Player. If the counter is greater than 0, the action music plays until its set to 0. To set it to 0, The Player must kill all the enemies that spotted the Player or lose their sight by running away from them. This mechanic generally works but does need to be refined and tested more in future. 

Made an “enemy flashlight” that aligns with the Players flashlight to light through enemies to be easily seen by the Player.

I made the enemies chase Player if they found him/her but give up and look around before going back to patrol when they lost sight of the Player.

I did the absolute best I could to polish the game on my own with barely any help.

I used Occlusion culling to really ease the framerates and only display what the Player sees, making it a smoother experience.

WHAT I LEARNED:

For the first time I learned to use the Timeline editor to… -  Make the cutscene play and then turn it off at a certain time or just skip with a press of a button. - Animated a logo scene and then a cutscene with music, character animations with positions, and camera movement. - Toggle between 2 game objects of the Player breathing depending how much stamina he/she has left. --Save and Load Inventory with PlayerPrefs--

Save Players progress in terms with items in inventory collected like weapons, apples, batteries, keys, and ammo,

Current health, battery usage, and certain amount of ammo loaded into weapons, etc.

Bools for each if Health, battery, arrows is filled.

Bools to check if it's a new game or saved game. New game erases all of Player's data and begins with no saved inventory. If it's a saved game, it will load up Players Inventory data and begin where they left off.

For the first time: I have made an inventory screen showcasing all items, weapons, keys and ammo the Player has in their inventory, The Player can select items and equip weapons as long as they find and collect them first.

For the first time, I have made a mechanic that can work around with the Players Inventory with Player preferences such as. - Save game from options menu, load the saved game or start a new game which will erase the Players existing save date in main menu. -  Weapons, keys, flashlight and night vision collected so their pickups don't spawn in the scene unless the Player has not collected them. - Current light power, current health, current clips in ranged weapons. - Amount of Ammunition each for gun bullets, arrows and Flare gunrounds, Apples, batteries. -   Which precise pickups have already been collected and will be destroyed the next time the Player loads the game. These precise pickups are batteries, bullets, arrows, flaregun rounds, and apples. -   These Player prefs use parameters for ints, floats and bools to store any pickups the Player has already collected. These numbers turn to 0 if the Player starts a new game. -   gather all of the transform targets and assigns to the enemies so when they spawn, they know where to patrol. -   To track how many Apples, ammo clips, batteries, arrows, and flaregun rounds in the current saved scene. These numbers rest to their default values when Player starts a new game. -  Make sure Players lights, options menu and inventory menu are off when the Player starts the game - stores and loads other misc data like Player hurt screen, stab sound, Player character and audio, etc to enemies.

For the first time. I have made an inventory menu where the Players weapons, keys and other pickups can be selected and used once he/she has collected them in the first place, rather than just using button inputs or scrolling the mouse to select them. The save script and Inventory work with each other to see which weapons and pickups the Player has. For e.g, if Player picks up the bat, the Inventory and save script communicate with each other that the Player now has this the bat and can select it to use it as a weapon. Though if the Player clicks on “new game”, they will lose the bat, keys, other weapons and pickups they collected in the game and start over. The Player can still refill health, power and ammo with apples, batteries, gun ammo and arrows respectively which will deplete 1 of the chosen pickup amounts from the inventory. --Enemies--

Made enemies patrol between 10 transform target positions around the map, these can be random, not round robin to add unpredictability in the game.

Made a stop distance value from which determines how far they stop before they reach their target.

Once they reach their target, they wait for a given amount of time and look around before going to their next target and repeating the process again, unless they detect the Player. If the Enemy's next target is the same as the one before, it adds +1 to go to its next target making sure it doesn't repeat going to the same in a row. If The enemy reaches its 10th target, it goes back to 1st target.

Made an avoidance Priority of the navmesh for each enemy that randomizes in between 2 values to prevent enemies from pushing into each other, especially while chasing the Player.

Used an AnimatorStateInfo to determine its base layer to perform certain actions when its animation state is called by code. For e.g, if the Bosses animation is tagged “chase” it chases after the Player and if its animation is tagged “shoot” it will stop, will look directly at the player and shoot him/her. If the Player runs away from Boss, the boss chases him/her repeating the process again.

For Enemy nav.acceleration: The greater the acceleration, the quicker the enemy will stop. The lower the acceleration, the slower it will stop like sliding on ice.

Allows to fire rays from its position from the nav mesh to see if the Player is nearby no matter where the enemy is facing, if its ray hits the Player, it will chase and then attack the Player when close, if it loses sight of the Player, he will look around before going back to patrolling the island.

Animated blend shapes on some enemy faces giving them different facial expression such as run towards the Player and getting attacked by the Player. --Other--

Added an alternative way to rotate a game object (lighthouse light) in world coordinates (LHObject.transform.Rotate(0.0f, Speed, 0.0f, Space.World); - Which reminds me that World space makes it move with the world, which with local space would move differently.

Learned to change a rigidbodys mass from code

Enumerators can be good to give code a second to check for something before being destroyed so it will not cause errors such as... -  Checking which pickups have already been collected, if it is collected by Player than it will destroy the game object the next time he/she loads the game. -  Making sure the Bosses bullets have access to The Player script so it will flash the UI screen if Player is hit by the bullet. -    They assign the spawned enemies targets so they can patrol them unless they spot the Player. -    Randomizes the Enemies check time so when they reach their targets, some will look around longer or shorter than other patrolling enemies before they go to their next target. - Make sure to get references of the Player character and its hurt screen before moving. 

Made the flashlight not only have a cookie light, but also undisturbed by other objects in front of the Player so he/she can view objects up close to objects without the flashlight being blocked by the mesh.

The layer “Ignore raycast" allows raycats to pass through triggers and collisions without blocking the players shots. Good to have if your scene has triggers set up in the scene.

For the first time since 2019, I have enabled code that Allows Player to change post processing in the scene into night vision view which allows the Player to see in the dark like real night vision goggles.

For the first time I have made Ui showing how battery the Player has before the battery runs out turning the flashlight and night vision off.

For the first time, I learned to bake lights on Players arms, scene objects, and enemies.

I learnt more of making an options menu since I did Punk-Ass 3000, I have listed in toggle and control options for visuals lie fog, brightness, AntiOff, AntiFXAA, AntiSMAA ,AntiTAA, ambient and sfx volume with audio mixers, difficulty (enemy amount only), back to menu, control list, and save button.

WHAT WENT WRONG, COULD I HAVE DONE BETTER?: 

I made too many scripts; I need to reduce how many scripts I make so it's nice and tidy. So, for e.g instead of the pickups each with their own script with similar code, all pickups should have the same script but customizable parameters to tell which pickup the Player gets when picked up by him/her,

The already-found pickups don't always destroy themselves accurately when the Player loads the game, I will need to find a better way to make it work better so the mechanic doesn't look broken and leave the Player at an unfair advantage.

I could have saved the Players current transform position, but I decided to let it go since it wasn't in the course and would have been tricky to program.

Sometimes the Enemy will jerk around while moving to its next target, I need to make sure it doesn't happen next time.

The enemies find the Player too easily even if not looking at the Player, next time I will need to add a cone of vision from the enemies' eyes to not only add realism, but to give the Player a fair chance of being hidden, unless seen by the enemy.

I could have got the Player raycast to check for pickups to work better, there's a possible chance I may fix it in a patch in future.

For the options menu, it is bare bones and lacking some important options like customizing inputs, more noticeable differences with difficulty, multiple saves, W&H resolution and several other visual and graphic options. When I start making commercial games, I will need to put in more accessible options in the options menu to suit different gamer needs. I also need to make sure the options are set in stone so the Player can see the changes made next time they log into the game

The Inventory menu could be a little better. For e.g not so many apples listed, only one apple button displaying its amount, same goes with batteries and gun clip bullets.

I could reduce the amount of trigger boxes the enemies carry for seeing and detecting Player attacks to reduce bugs from happening.

Most of the code I wrote is very spaghetti-ish, I will need to get in the habit of making cleaner and easier code to read next time. 

Next time; if any of the enemies has a gun or any other ranged weapon, I will need to use IK to get them to aim whenever the Player is in the air or below the enemy.

OVERALL: It was a very challenging project to do. Normally I'm not keen on making horror games, but this project gave me more knowledge of what I need to make in fps games like flashlight, Player melee combat, options, making cutscenes and saving Player inventory and progress.

What first became easy to pick up and hard to master, was a long project, but it was worth. every min of it.

I will be more prepared next time I make a horror game like Resident evil or Silent hill. 

At the end of the day, I am getting better and better with making games on my own.

click here to play the game: Maniacs (Adams Version) by Adam House

[adamtheamazing5]

Now my Brickstar character is complete, I have finally received yet another certificate of completion! If you haven't checked out one of my latest posts, The link is right here of what I learnt and achieved: https://lnkd.in/gECcsgTR

[adamtheamazing5]

This is the video I made in 2023 showcasing cut content that is not in the final game of Maniacs (Adam's version). These cut features are what I was taught from the online course, but I decided to cut them for reasons listed below. These cut features are...

- Silent hill post processing style: another way to emulate horror for the game, but not as scary when it takes place at night and does not work with baked lights in the scene.

- Tug boat sinking cutscene: didn't really mean anything to the games story or environment.

- Automatic climbing ladder: You don't really "climb" ladders, it's more like an open elevator. It's not implemented well and makes avoiding enemies too easy. Want to play the game?

Link is right here: https://adamtheamazing.itch.io/maniacsadamsversion

[adamtheamazing5]

After a few busy years of development hell, my next game: Maniacs (Adams version) is finally here!!

Download and play the game here!!: adamtheamazing.itch.io/maniacsadamsversion

On this unlucky night, you have been kidnapped and scheduled to been tortured to death soon by a psychotic group of Maniacs, you eventually escaped with your life before a knife touched you.

You find out you are on a deserted abandoned island filled with other Maniacs guarding the island.

With no contact to the outside world and no easy way to escape the island, you decided the only way to escape safely was to take matters in your own hands by finding and killing their leader: General Carcus, who is believed to be reasonable for multiple kidnappings, tortures and murders.

You hear that General Carcus does not like to be disturbed, and will lash out at anyone who disturbs him, so stock up and prepare for the fight.... of your life. Will you be able to survive the night of the Maniacs? or perish forever?

Post mortem and cut content video coming soon!

[adamtheamazing5]

Brickstar character animations

Brickstar character animations

Type: Practise project.  Genre: NAEngine: Unity.  Key Roles: Animation, rigging, programming character control mechanics Learned from: Blend

Type: Practise project.   Genre: NA Engine: Unity.   Key Roles: Animation, rigging, programming character control mechanics  Released:| 19/5/2026 Last updated: 19/5/2026 Learned from: Blender 2.8 Game Character Creation. Made by: Only myself. 

Meet Brick "Brickster" Stirling, a little Lego minifigure and Aussie legend. He survived in the outback inhabited by giant Lego creatures (especially big bugs) for weeks. He is fearless, he is handsome, and so strong he can shatter a giant Lego spider in pieces with only one punch. Don't underestimate him.

One of the simple and unique tutorials I learned at the start of the year. I wanted to learn how to animate my future characters' faces in 2D style for my future games to give a simple and expressive look without spending so much time making 3D realistic animated expressions like in modern games which could be stressful and time consuming.

While the tutorial covers making a Lego character, I decided to use my creative freedom to create a Crocodile Dundee inspired character named “Brickstar”.

Not only I animated the characters' facial expressions with sprites in blender, but I also combined the sprites into a sprite sheet each for Idle, run, and jump in a Texture packer app.

After I completed the character mesh, animations and sprites, I then tested it out on the Unity game engine with a custom movement script and a Unity third party Camera prefab, I also made a duplicate of my character testing the “Ethan” third party animations to see how accurately it works with Brickstar. The results were fascinating.

I made a “bonus animation” of Brickstar posing heroically at the end, I decided to animate without help except what I learnt from experience from the tutorial.

WHAT WENT WELL?: •  With animations, I manage to animate them smoothly as possible, including the bonus animation: Pose.

WHAT I LEARNED: •  The Texture packer program makes sprite sheets for each of characters facial animations in seconds rather than mins.  –Blender– •  K key: opens keyframe menu. •  I learned to use a Grease pencil tool for the first time drawing facial expressions and animating them for my character. •  / numpad allows you to zoom in and show only the 3D mesh you selected.  •  When modelling your character… - Shift + C: sets the camera perspective to view everything in the scene back to default position. - You can press E or F to re-straighten cuts during edge loops. - The bevel tool is affected by the geometry's scale. Be sure to reset the geometry to 1,1,1 scale which tells Blender it's a default scaled object. - You can press ctrl + M to mirror objects. - Alt+z allows you to see a transparent mesh without using the standard z-hold selection key. •  When making UVs for your character…       - Make sure you reset the scale on the mesh (1,1,1) before you unwrap UV maps. - You want to reduce stretching UV texture maps and hide seems as best you can. - Shift + H Only shows selected faces. - Alt + H to redo Shift + H.  - UV> Average Island scale: unwraps all UV maps to its approx 3D mesh size. - UV> Pack islands> Unwraps all UV maps and places them apart. •  When rigging your character… - It's always good to check on the role of the bone to see where the limb will rotate. Roll seems to be the angle the bone rotates. - Blender will take a look at the mesh vertices around each of the bone and set its position around them when selected "with automatic weights" with ctrl +P. - Shift + right click to select bone while weight painting.   - The foot roll is the most complicated of the rig. This is important since it adds believability to walking animations.  - When using the Inverse kinematics for the rig such as the foot bone, it needs to be curved to make the IK work easily with other bones. - When rigging, don't forget to duplicate the bone to make an IK bone of the, it should be parented with Alt-P. - With weight panting the character rig, remember red is the strongest influence. Blue has no influence at all. - Make pivot shapes to easily control the rig while animating. - Make foot rolls with several bones to easily control leg movements. - Alt+R clears rotation for bones and resets to default T-pose in pose mode. •  When texturing your character… - Shift + S turns on/off stroke. - F to change brush size. F+Shift to change brush strength.   •  When animating your character… - Shift+ left arrow: reset keyframe back to 1st frame. - 24 frames per seconds is usually "fine" for animation. –Animation control in Unity– •  If you get "loop match" in Animation import settings, you will get the animation to loop perfectly. •  For setting up your character in Unity, it's always good to test non-generic and humanoid skeletons with Ethan the third person controller before testing with other animations. •  Using anim set integer by value to play one animation at a time when the character either runs, walks, or idle. •  Generic type animation is for not quite humanoid specifically (e.g dragon with a tail or dragon with 2 heads, or even a Lego character with claw-like hands). Once selected, there are no green lights because it did not try to figure out if it's a cycling animation loop or not. •  Using a third party script from Unity to animate sprites in a material.

WHAT WENT WRONG, COULD I HAVE DONE BETTER?:  •  In Unity, I could have made the controls for the character easier to control like in Super Mario Sunshine or Galaxy rather than use tank controls, but I decided to let it go since it's not an important mechanic I want to use for my future fps games. •  The bonus animation “Pose” is still a bit stiff and rigid; I may need to rig the character and practise animating by hand better to make the animation more flexible and bouncier. •  With animating keyframes in Blender, I will need to make sure they are consistent, snapped together, and lined up properly to reduce animation mistakes of them happening.   •  I could have made the character move faster in Unity, but I decided not too since it wasn't that important, but I need to keep in mind that for commercial games movement needs to be faster.  •  I had the pose animation at 101 frames in Blender, but when exported to Unity, it was shortened down to 100 frames, I should probably stick to 100 frames or less for each animation. It might explain why the facial animations were not in sync with the pose physical animation, I'm letting it go for now since it's not an important animation to make, but a bonus one instead. This is something to keep in mind for next time. •  For the pose animation, I got the characters hands clipping through his torso, I didn't realise it before, next time I will need to animate with textures on instead of a generic grey material so I can see errors easily and fix them before they go in a game engine. •  Unfortunately, I couldn't upload the character to Sketchfab because I did not prepare in advance for the character to be viewed there properly, next time I need to plan ahead.

OVERALL: It was a fun and exciting lesson; this has helped me to give my game characters more dynamic expressions and animating experience for Blender. I may not be animating dragons, characters, zombies, or cyborgs yet, but I'm getting there!

I could just animate face sprites in Unity by hand to be consistent with the character animations. Especially when I was working on the pose animation which the sprites were not consistent with the animation.    

[adamtheamazing5]

Introducing Maniacs! (Adam's version) This project was in development hell for a while, but finally I'm finishing it for good. It is a survival horror action game and is 98% complete. Here is a short cutscene of the game. voices done by Pete Jepson, my online instructor from creative media tutorials. Stay tuned!

[adamtheamazing5]

Dragonscape postmortem

Type: Public prototype Genre: Platformer and Rocketship game. Engine: Unity. Key Roles: Game designer, Level design, and programming. Released: 3rd March 2026. Last updated: 8th March 2026. Learned from: Complete C# Unity Game Developer 3D from Gamedev.tv. Made by: Only myself, though few assets were provided to me by the instructor. Here is the link to the game: Dragonscape by Adam House

You are a lost dragon soul who was mercilessly killed by those puny, blood thirsty humans. You currently reside in the Underworld, suffering for eternity; you are sick of the torment and are willing to escape to the land of the living to get revenge on humanity, while avoiding traps and other collisions along the way. Do not lose your head....

Will you be able to pass through nine dungeons to escape the cruel and unforgiving Underworld? Step into their gates and find out or suffer forever in the Underworld!!!

Originally going to be a Rocketship game, I decided to make it more interesting by flexing my creative muscles and using assets from Synty to create dungeons within the underworld instead of Space and a flaming lost dragon skull instead of a rocket.

Some new tricks I learnt from the course while others I learned from research on Youtube.

This was a short exercise to increase my level design, game design and programming toolbelt for much more complex projects in future. 

Fun fact: the game was originally going to be called “Dragon escape”, but was shortened to Dragonscape instead, pretty cool huh?

WHAT WENT WELL? •  I used my experience to make creative level designs and made some assets share the same code to perform similar actions, some e.gs are   - Used swinging trap script on pendulums and hanging chains.   - Used rotate script on not just saws, grinders but also on a gameobject parent pivot to rotate saws and flame bricks clockwise around the level making it challenging for the Player to get through the last level. - Stone slaps and grinder parents share the Oscillator script. •  Made prefab presets of walls, floors, and ceilings, ground, and other assets to make level design less time consuming. •  Used some code that I learnt from the Super Mario Clone a while back to make the Spear trap trigger only activate when the Player is in its trigger. •  Managed to make the lava geysers and fire traps to be deadly to the Player. They also share the same code.

WHAT I LEARNED: •  From researching on Youtube, I made a mechanic where a pendulum swings back and forth repeatedly by using three variables controlling its rotation speed, angle direction to change, and position to start. This same script is used for the chains. - In further detail, it rotates from its current position in a new vector3 using LocalRularAngles and Mathf.PingPong with Time.time. •  public variables are also known as member variables. •  Another thing I learned from Youtube was making text slowly appear on screen rather than all at once. This is done with Textmeshpro with an IEnumerator, yield return Waitforseconds with an for-each loop and int variable to determine how many letters appear per second. •  Rb.Relative force is used to make the Player thrust forward which adds force to the rigidbody relative to its coordinate system, meaning no matter the current rotation of the Player, it will always go forward in local space. Vectors are both directions and magnitudes.  •  Able to make Player thrust sounds loop seemingly without glitching hurting the Players ears using an if statement with a property. e.g if (!audioSource.isPlaying). •  Made the Player freeze and then unfreeze rigidbody rotation while manually rotating by its transform so it does not cause a bug to make the Player jitter when colliding with obstacles. We don't want physics and collision to fight each other the whole game. --Oscillator-- •  Created an Oscillator that starts from Point A to point B and back again in a loop from transforms. •  Prevented the Oscillator to have errors by comparing its given period/speed (float) to Mathf. Epsilion. •  The Oscillator measures how much time has passed with period multiplied with Time.time. - Time measures how much time has elapsed. - Period controls how much time for the cycle to be. - Cycles will divide with the period to complete 1 cycle. e.g 2 secs to divide with time is to complete 1 cycle. - Time will keep on updating every amount period makes. - It is calculated by Tau which is multiplied with PI which gives it a wine movement equation. - It than uses a Math.Sin to multiply the tau with the cycles to give it a +1 to -1 in direction, though it moves from 0 to 2. - than we assign the movementFactor with rawSinWave which we add 1 which equals 0, we add it to 2 and then we divide them with 2 = 1. - This will offset within its vector creating a smooth movement from point A to Point B with clean code as a result. •  Created a debug feature that turns collisions on or off for prototyping purposes, this allows the Player to collide with obstacles without dying when hit. •  State machines are like if and else statements. This is used when Players collide with certain objects. - It only executes true if the Player collides with certain tagged objects (e.g finish, untagged, and friendly), and does not go further down code unless it is false. - Break: do nothing more and don't go to the other cases - default, also known as else. This is used for untagged objects that kill the Player character when collided with it unless the debug collision is on.

WHAT WENT WRONG, COULD I HAVE DONE BETTER? •  I could have used the Mathf.Round to make sure that the Spear trap exactly goes to the accurate calculated distance by floats forward once activated. I will keep that in mind for next time when I make similar traps in dungeon crawlers. •  I should have the prefab set sharing 1 whole collider on the parent gameobject rather than its child gameobjects to make tweaking colliders or turning them off easier when collision is not needed. •  Next time, I will need to program more variables to better control how long the fire shoots for, wait before shooting again and test a bit more before developing levels. Sometimes the Player can pass through the fire without being killed, it could be the amount of particles is small or collider placement issues since they don't use 2d colliders. •  The Players soul fire particles have a delayed response except for the sound, I don't know if it's a code issue or particle issue, but I will let it go this time. •  I haven't figured out how to reset the Oscillator every time the Player dies and restarts the scene, If I want it to be consistent with the scene, I should research how to restart positions of the Oscillators with every scene load. • Next time, I should have removed the debug keys, so Players don't figure it out and cheat their way through the game. Good thing I will remove them next update.

OVERALL •  It was a nice fun little project, some things I could have done better, but still made me more confident of making games on my own. •  I definitely want to stick to making fps games, though the preset prefabs I made can be useful to making dungeon crawlers in less time. •  The mechanics can be good for making spacecraft minigames if it was for a fps sci-fi game.

[adamtheamazing5]

The gates of the Underworld are now open!! Are you ready to escape? Play game here: Dragonscape by Adam House You are a lost dragon soul who was mercilessly killed by those puny, blood thirsty humans. You currently reside in the Underworld, suffering for eternity; you are sick of the torment and are willing to escape to the land of the living to get revenge on humanity, while avoiding traps and other collisions along the way. Do not lose your head.... Will you be able to pass through nine dungeons to escape the cruel and unforgiving Underworld? Step into their gates and find out or suffer forever in the Underworld!!!

[adamtheamazing5]

Coming soon: Dragonscape, where you play as a lost dragon soul with only its skull left escaping from the dark dungeons of the underground. Can you escape the underworld? Stay tuned for this free game when released on itch.io.

[adamtheamazing5]

Return to Game dev

Back again from holidays starting my game dev journey! Starting at this year is 3 of my projects that are almost complete 1 unique 3D character and 2 free games to play. Especially for Maniacs (Adam's version) which has been in development hell for years which finally will release this year! Brickstar the Lego man: 57% complete. Approx to be completed between early-mid 2026. DragonScape: about 78% complete. Approx to be completed early 2026. Maniacs (Adam's version): about 90% complete. Approx to be completed early 2026. Stay tuned!!

[adamtheamazing5]

Fps multiplayer

Type: Practise project.  Genre: First person shooter and Multiplayer. Engine: Unity.  Key Roles: Programming and some Game design. Released:  20/12/2025. Last updated: 20/12/2025. Learned from: Create Your First RPG And FPS Multiplayer Game in Unity by Awesometuts (Fahir) from Udemy. Made by: Only myself, though the assets were provided to me by the instructor.

Finishing of this busy year is a Multiplayer practice project I was originally going to do first before the Battle Royale Prototype, but the instructor did not have the available videos to help me finish this project myself. I than decided to learn the Battle Royale prototype and use what I learned to finish this project once and for all. Am I satisfied with the multiplayer mechanics that I learned? Found out below….

Some Fps mechanics are similar or just about the same I learned before, so I will only cover new skills and techniques I learned to keep this post mortem short. Should you want to see what I learned from my earlier projects like “Survival shooter”, ”Punk-ass 3000”, ”Into the Darkness”, “Humanoid animation control”, and last but not least “Battle Royale Prototype”, you can see what I learned from them on my portfolio site.

I originally started this project to research how different fps mechanics are made. I decided to warm up my game design skills by assigning each gun different fire rates and damage. More info on WHAT WENT WELL?

The rules of the game are simple, the two Players must find and kill each other, the last one alive wins the game. Players have 3 guns they can select at a time ready at their disposal each with its strengths and weaknesses. There is no respawns or rounds since it would be complex for me for this prototype.

WHAT WENT WELL?: •   As mentioned above, I used what I learned from Battle Royale Prototype.     -   Determined which type of weapon the Player holds can be a Pistol (Deagle) or rifle (machine guns) in the Animator controller and show the weapon the Player is currently using.     -   Made each gun have a different fire rate and damage to work through the network when the Player fires the equipped weapon. Deagle Pistol: slow fire rate, but high damage. AK-47 Machine gun: medium(ish) fire rate, but medium damageM4A1 Pistol: high fire rate, but low damage -   I made the Player that died to switch cameras showing the entire map before destroying the Player itself by setting active on the game object (camera) without affecting the other Player by using a Command. -  Used Commands and RPCs to instantiate the muzzle flash for all 3 Player's guns and set it as a child object under each Player's gun parent. -  Made the wall (Player shot at building) and blood particles (Shot at Player) instantiate in the server so all Players can see. -  Made the local Player see the text of which gun their currently equipped displaying their ammo, and magazine size of each gun. -  Player can reload gun to a full magazine only if the clip is less than the Magazine. -  Made almost all the networking mechanics in one script, some do have their own network scripts. - Made sure the Character animations don't play twice. -  Made gun shots heard by all Players through commands and RPCs, though the reload sounds only can be heard by the local Player, not in the server so all Players can hear it. -  I did the best I can to make sure each of the Player's guns fit in their characters hands so clients can see. •   Made the shooting controls as tight as I can so they reduce the chances of being broken by using some if statements, bools, methods, and enums.

WHAT I LEARNED: –Player– •  Used an if statement to determine if the Player moves forward or backward by either the W or S inputs, the same is done for Left(A) or Right (D) for a separate if statement. •  Made the Player lerp with Inputs with X and Y from values 0-2 with Time.deltatime which is similar to the Get axis raw. If 0, The Player does not move at all. •  Used an advanced if statement to make the Player not speed up when going diagonally while smoothing its movement. •  Used CollisionFlags to check if the Player is grounded.     -   CollisionFlags.Below means it's grounded. - If not equal to 0, it is true which means we are grounded. - If it is equal to 1, it is false and we are midair. -   Collisionflags  gives you a broad overview of where your character collided with any other objects, for e.g did your character controller collide by the side? above ceiling, or below ground?     •  Used a float which is the antibump factor to smooth Player landing while assigning them with new X and Y values when grounded. •   Used bools to determine which keys the Player is pressing: inputX and inputY. •   Used one script “FPSMouseLook” that also controls the Players fps camera on two child gameobjects with each an enum. - Mouse X on Player parent: Allows the Player to rotate the Player character and camera horizontally within its clamped values. It rotates the Player character model on the Y axis using x rotation while using a Quaternion with local rotation. - Mouse Y: Allows the camera to be rotated vertically and horizontally within the clamped values.  It also rotates using a Quaternion with local rotation. •   Uses TransformDirection for the Players vector3 movement times with speed from local space to world space. •  To make character model and Players arms in the first-person view animate at the same time for StandShoot, crouchShoot, and reloading guns in state machines. •  Used Vector3.lerp for smooth rotation of the Player camera while also using LocalEulerAngles. •  Set a mouse sensitivity default setting in an if statement to make sure the Mouse X and Y does not have the same value as a precaution. •  Adjusts the Ray distance and gets of half the height of character controller and radius in Start function to prepare it for Player crouching. •  Auto sets the default height of the character controller and default camera position. •  Can Change Player Colours RGB within an array each with 4 int values. •  Able to change Player's character model equipped weapon and FPS hands equipped weapon at the same time from 2 separate arrays. It also clears the selection first before changing to the next equipped weapon so 2 Players hands and 2 character model guns don't appear at the same time. Only keys 1,2,3 are activated to select one equipped weapon at a time. –Multiplayer– •   Made an if statement each for Local and Client Player that will execute depending on which out of these two is the Player.

LocalPLayer gets...     -    Players character model with its child gameobjects is tagged “Player” in a foreach loop which means Local Player won't see his/her character model, but other clients will. -    Changes the Local Players guns from his/her character model to “Player” while using a for loop so clients can see what gun the Local Player is using while he/she can't see it. -    Changes the FPS guns and its child components tag to “Enemy” so the Local Player can see his/her hands carrying the selected equipped gun while the clients won't see it. !LocalPLayer (Client) gets... -     Client Players character model with its child gameobjects is tagged “Enemy” in a foreach loop which means the Client Player won't see his/her character model, but other clients will. -    Changes the Client Players guns from his/her character model to “Enemy” while using a for loop so other clients can see what gun the Client Player is using while he/she cant see it. -    Changes the FPS guns and its child components tag to “Player” so the Client Player can see his/her hands carrying the selected equipped gun, but the other clients won't see it. •  Able to override on Start for Local player for their tag to be changed as “Player”. •  A little more detail of using Commands     -    Command is an attribute that can be put on methods for network behaviour class's that can be invoked on the server by sending a command from a client. -    These functions need to have Cmd short for command in front of the function. -    Commands are called on the server to send info to all clients. -    Cmd is a suffix.

–Other– •  Rigidbodys apply gravity straight away, unlike character controllers which need to be programmed. •  Update is one of those functions that doesn't return a value. WHAT WENT WRONG, COULD I HAVE DONE BETTER? •  The bullet holes from gun shots don't always face where they were shot. The map is complicated when almost all of its mesh is one game object, I decided not to worry about it for now since I want to focus on mostly the Multiplayer mechanics. I will look on my notes on how to normalise bullet holes on objects properly for next time. •   I could have made the Player reload automatically once their clip reaches 0, but I wanted to focus on the complex Multiplayer mechanics and not accidentally break code, so there's always a next time to implement that reload mechanic.  •  I could have given a health bar or text and damage screen UI to each of the Players, so they know their health and if damaged by another Player, but it ended up being a little tricky for a Multiplayer. I have decided that making Multiplayer games isn't my first type of product for the market, so I only focused on mechanics that not only I can easily implement, but also to make the game playable and to keep the gameplay loop going until one of the Player characters die. • I get an error whenever one of the Player characters die due something to do with executing a code that does not exist, possibly referring to the code of the Player gameobject that's destroyed, normally I don't like errors in my games, but I decided to let it go since it is a mild error, not a game-breaking bug and only a prototype, not a commercial game. •   Syncing the Player character crouch shooting from both shooting guns may not be what I expected since the machine gun goes straight down after each shot, next time I will make sure the character points the gun towards its target rather than aiming down. •   Like I mentioned in Battle Royale Prototype, I wish the Players characters hands move to where he/she is aiming that we can see. But unfortunately, I haven't been taught to do that yet. •   Next time I should not have OBS shown while screen recording.

OVERALL Despite all this trouble, I still have decided that I won't make multiplayer games early in my game dev journey, I will be sticking to making fps single player games instead.

Though this project really demonstrated my skills to finish the project on my own which I am very proud of.

I am happy to not only finish this project, but also learned to make similar fps mechanics for my future games, as much as I learned some similar multiplayer mechanics, I am still not satisfied with what I learned and may learn more of these complex mechanics when the time comes or hire a programmer to develop those mechanics for me.

My skills will be ready when the time comes to include multiplayer.

[adamtheamazing5]

This is the whole level of the 2nd map "Desert" without fog.

Unlike Tropic base, the maps art style is low poly, shorter map, shares different biomes, and more objects in scene.

There are empty buildings that Players can go inside to find weapons; however, they are guarded by enemies. Good hunting!

More info on these pics on my portfolio under "Level Designs", here: Battle Royale prototype Desert: Portfolio

[adamtheamazing5]

Finally, the pics of my Battle Royale prototype are here!

This is the entire level of "Tropic base" map. Players can pick where they can land in hopes to find powerful weapons to defend themselves from enemies and kill the other Players to win the game.

The map is styled with prototype prefabs and photorealism textures to make it very simple base-like and village-like.

More info on these pics on my portfolio under "Level Designs", here: https://adamhousegd.wixsite.com/myportfolio?pgid=mimvibuy-74dec236-1d98-4f48-b5ab-0696df75b5ec

[adamtheamazing5]

part 6 and final of the Battle Royale prototype. Our battles are nearly complete for the Desert and the Battle Royale prototype series. two of the Players must face the last two battles to see who controls the Desert and its connecting land. Let the final battles, BEGIN!

To see the previous parts of the Battle Royale prototype series: https://www.youtube.com/watch?v=jpyR7sZNTjA&list=PLcon1Zt8ssEQbU87sR2wWXgGCKNCi48Zj&index=4

Find out more in Post Mortem link: https://www.tumblr.com/adamtheamazing5/800534472053440512/battle-royale-prototype?source=share

[adamtheamazing5]

Part 5 of the Battle Royale prototype.

Now we begin our battle in the Desert. Player 1 gets a head start going to the corner of the map where powerful weapons are guarded by enemies at the corner of the desert where the deadly Storm begins swallowing. Player 2 starts small, but will Player 1 defeat Player 2 with his superior guns? Find out here, right now!

To see the previous parts of the Battle Royale prototype series: https://www.youtube.com/watch?v=jpyR7sZNTjA&list=PLcon1Zt8ssEQbU87sR2wWXgGCKNCi48Zj&index=4

Find out more in Post Mortem link: https://www.tumblr.com/adamtheamazing5/800534472053440512/battle-royale-prototype?source=share

[adamtheamazing5]

Part 4 of the Battle Royale prototype. In this short final video of the Tropic base, we get to see how to Players interact on 2 different screens.

1st video and postmortem right here: https://www.tumblr.com/adamtheamazing5/800534472053440512/battle-royale-prototype?source=share