Random pieces i'm putting together in order to eventually make a game (hopefully)

[SkacikPL]

Most certainly this isn’t something that will impress anyone above beginner level, but oh well, everyone is sharing their work so why shouldn’t I?

Most recent video:

- YouTube

Link to the playlist: https://www.youtube.com/playlist?list=PLuUsBgTvSDeLOAPMHXYcZh5LkwZDYj-m5

What i’ve figured out so far:

• FPS “Dishonored style” ledge climbing system
• First person camera with full body awareness
• Main menu/settings menu using UMG
• Basic interactive objects
• Basic health and stamina implementation (along with HUD display for them)
• Basic “physical blood” particle which creates a splatter decal upon collision
• Fake mirror blueprint/material setup

**
What i’m working on:**

• Explosive barrels
• Player inventory (weapons/powers, etc)

Some details on my solutions(boy i could use a spoiler tag in here):
Vaulting/climbing mechanic:

Inside pawn blueprint, i’ve added a sphere without any collisions, which is attached to the player camera. This allows me to easily (lazyness ftw) get its location.
The sphere is placed just outside player collision capsue, at about “eye height”, which determines the maximum height at which i can possibly climb.

The vaulting/climbing itself is trace based.Each time player presses or holds the jump button, a trace will fire, the trace itself originates from the aforementioned sphere and simply goes several units straight down (i guess you want to match the length of the trace to match waist height of your character).
The “initial trace” simply looks objects that we can possibly climb onto (world static/dynamic/physics bodies). Additionally, i’ve implemented a check whether the hit actor does NOT have a tag called “ignoreclimb” so that certain objects are skipped during the checks.
IF the initial trace returns something we can possibly climb onto, then i fire another trace, from two units above the hit location of initial trace (to prevent hitting the first object). This time the trace goes upwards, its length is set to the slightly rounded up height of the player - this is the check whether there’s actually enough space for us to fit standing up, after we’ve potentially climbed up.
If the second check does NOT return a hit (aka, there’s nothing preventing us from standing up in proposed climb location), we fire a third (and last) trace.

The last trace is “needed” due to nature of the solution i’ve used for locomotion. We need to check, whether the way between player collision capsule and proposed climb point is clear.
Without this check, in cases of climbing onto tall objects with rounded ledge (as in not 90 degree wall to top angle) “move component to” blueprint function will falsely report that it succeeded moving player to his destination, whilst the capsule will collide with the object during the movement, effectively blocking player from reaching the destination and dropping the player back down right after he “finished” climbing.

Third trace originates from several units (depending on the height of the capsule, in case of classic 96 units it can be a range from 15 to infinity IIRC). above the hit location of the first trace and goes towards the collision capsule of the player.
If this trace does not return any hits on its way, then it means that we’re good to go and the climbing process will be 100% successful (at least it’s been so every time i tried).

If all the pre requirements are met, we can proceed to the actual climbing/movement itself:

1. Set pawn gravity scale to 0
2. Set pawn velocity to 0
3. Use “move component to” function on pawn capsule(root) to move it to first trace hit location
4. When movement is finished, return gravity scale back to 1

Bear in mind that this is just barebones description and depending on your personal vision, it may require additional touch ups.
Personally, i also have a hefty set of booleans to control the climbing (to not fire additional traces if we’ve already found ideal one and/or are climbing, that we want to climb while holding jump key, etc.).

Also, some ending notes:

• If your player mesh is visible by any other players (or even owner), you’ll most likely want to restrict mouse yaw input during the climbing, to prevent player mesh from rotating during the climbing
• As i mentioned before, additional boolean(s)/gates may be required to fit the sytem to your needs (i know that i needed a few)
• There are some other surrounding features, mechanics you can implement, but that’s up to you and your imagination. For eg. my pawn won’t climb object if its stamina is equal to zero, or if pawn climbs a physics body, it’ll apply an impulse equal to it’s pre-climbing velocity to that body. Etc.

Object interactivity:

Simple box (or rather rectangle) attached to player first person camera in pawn blueprint.
Whenever it overlaps over anything, it checks whether it has a tag named “interactive”, if it does, then we call the hud to draw the “hand” icon to indicate to the player that given object is interactive.
When player presses the “interact” key, we try to cast to that object and fire an event. (this will work well if you have base blueprint class and then all other interactive objects are children blueprints).

On a side note, you may or may not want to use traces fired at each tick instead of box, which one is better or more efficient - i can’t really tell. I’ve already used the box and don’t feel dissatisfied with it.
Or if you don’t have any interactivity indication, the just fire the trace for each key press.