Here is some Test Footage of my level so far. After a few weeks, I finally got the main platform types (Green on a timer, Blue and orange switching) working, as such I rushed to make a the first level as a test level of sorts to see how well platforming actually performs now I have it coded in. Rather than being part of the level, the platforms are separate objects that exist contained outside of the level as an actor as its own "object" so they all must be moved simultaneously if being adjusted in the level. Adjusting 1 Platform of the collection of 60+ must be done within the object itself.
This is the blueprint actor that contains every single Blue/ Orange Platform within the level. First, the 3 connected separately at the beginning enable the 'E' Key to be pressed in the context of the Blueprint, which then activates a "Looping Multigate" Node which causes the sets of platforms to infinitely be able to switch states when the 'E' is pressed. These two states are Collision and Visibility available for Blue and not for Orange Platforms and then Vice-versa for the other state so one can only be enabled if the other is disabled. (For testing purposes both are currently enabled on level start.)
The two green nodes above and below the main Multigate Sequence are 'Make Array' Nodes and basically in its simplest terms this node serves the purpose of collecting the data of every separate platform in either Blue or Orange and making it into one variable, so they're affected by the code in the Blueprint. If they're not connected they won't reappear or disappear.
Here is the Blueprint for the Green Tiles which disappear on a Timer. I have much less of an understanding as I do with the switching as I relied on the help of the Tutor, Jay, to make this blueprint in this way, I would have done it through timers and loops, which is much less memory efficient but the effect is the same but I digress. The Blueprint works by having its own timer logic, where when it hits the "max time" (3.0 seconds) it sets the Timer back to 0 and when it is at 0, it causes the platform to appear in the collision and visual sense, which then sets the maximum time that the timer can go up to to the same as the max time (3.0 seconds) it can appear for and after this it sets the variable that decides that it should appear to false so it does the "disappear" sequence and the max time the object stays disappeared is also its own separate variable. After this, the platform uses the "Decide" Boolean logic in a way where it defines it as Deciding it is NOT Untrue as a variable (Which is different to being set to True for the purposes of this Blueprint)
With the completion of my game, I believe it is now appropriate to explore the development of my game in regards to my plan, how I feel I succeeded, how I perhaps failed and what I would do differently in the future, on future projects. First of all, in regards to my project and the scale of it, I think that once again I stretched myself too far. In terms of levels, I have 6 mostly linear levels to go through with some alternating paths and different level shortcuts and exits. Level 1 - The Proving Ground: This is a fairly blank level with white walls and an open sky where the player goes down fairly straight-forward corridors, familiarising themself with the mains mechanics of the Game such as Hemi-Switching, Checkpoints and the different types of platforms such as those that heal, damage, or disappear/ reappear without player control. Level 1.5 - Interlude 1: This is the first of the Red room levels, it involves the player climbing a tower to escape the level. The platfor...
Before beginning the Project it's good to find out how I would work with my Team. I found out I was an INTJ, which is likened to a tactician or a strategist or a planner. We all did the Myers-Briggs test and found out we all fell into the introvert category, which means we may struggle voicing our opinions and coordinating as a pitfall for our group. This is important to recognise early on so we can eliminate possible roadblocks early on. We had a short discussion after entering our group, Me, Jimmy, Nyssa and Mo. We concluded that we wanted to do a First-Person horror game based around a monster who freezes when flashed by a light in the Unreal Engine, this suits our previous Game Experience as we all made first person games and 3 of us have used Unreal previously. We also have experience with enemy pathing too which is really important for making the game scary and the main challenge effective.
Today and over the past weeks since late September I have been setting up the essentials of my game - whatever that may be so movement/ camera control and a sprint that will be needed for any direction I take the game in. These are the inputs and the logic for these features used by the gamemode base for the character the player controls used in every game I have made. Input Data in content browser. Most of these are booleans, except the mouse movement in which it is essentrially a check for whether a key is pressed or not. these inputs don't determine what the button does, rather is it being pressed or not. Input data mapped to different keys/ Mouse movement. This is how the yes/ no Boolean, checked for when a button which it is assinged to, is pressed This is the Blueprint which links the Player to Controller Inputs it assigns the keyboard as a controller to the player and casts the mapping of inputs to the character you control. These are the Input responses for Jumping, lookin...
Comments
Post a Comment