Making A Level

Making A Level

By Pedro Colon

Oh God, Where Do I Begin?!

As of currently, our base scene build is using a pre-made track for us to test our Karts on it. However, for the final build, it would be best for us to have our own track level. Why? Simple, to make it fit better with the mechanics we have in mind. While the tracks from the (free) asset pack we have been using is working well for us, eventually we have to move from the base track to making our own track that would better suit the game we are trying to make. We will still use the base scene since it has work for us to testing out our mechanics but in terms of it being apart of the build, it will not. With that preamble out of the way, the biggest question still remains...

OH GOD WHERE DO I BEGIN WITH DESIGNING A LEVEL?!

Small Steps Leads To Victory!

Turns out, it was actually a little easier than I thought. Well at least the process was. What do I mean? What I mean is that instead of trying to do it in one go, get an idea on paper (in this case digital) and work from there. Here is this as an example:

While this isn't the most detailed drawing in existence, it does provide a good groundwork on what I envision the track to be and how I can work from there to make it a good length for fun factor. Lets go over what some of the colors mean.

Green is our Checkpoint/Lap, this will serve as a place where we will count the amount of times that our Kart Drivers have passed over it. The purple lines is where the Kart Drivers will spawn. The grey rectangles are the Turbo Pads, the yellow lines are our bumps and the blue circles are where the powerups will be located. With this general layout completed, I can actually have a reference to start making a level to and with it change as needed without having to worry about the general structure.

The moral? Start with the small steps and draw that idea/overview onto paper or digital. It doesn't have to be the prettiest but something to reference on for later work. It can go a long way!


Comments

Post a Comment

Popular posts from this blog

The Pitfalls of Crafting a Position Placement and Lap Counter for Kart Racing Games

Kart racing games have always been a favorite among gamers, offering thrilling experiences of speed and strategy. Behind the scenes, however, game developers face numerous challenges in creating a seamless Position Placement and Lap Counter system. In this article, we'll explore the intricate web of issues encountered when striving to implement these essential features in kart racing games. 1. Real-time Position Tracking: Creating a Position Placement system that accurately reflects the real-time positions of players on the track is a daunting task. Traditional methods, such as grid-based placement, fail to capture the dynamic nature of kart racing, where players can change positions rapidly. Developers often resort to complex algorithms that require intensive computation to track player movements accurately. 2. Lap Counting Accuracy: Lap counting seems straightforward, but ensuring precise lap detection can be surprisingly intricate. Developers must consider factors like collisio...
Read more

Troubleshooting Unity GameManager Input Handling

Navigating Unity's complex ecosystem of scripts, input handling, and camera management can be challenging. This guide sheds light on the issues faced while implementing input actions in a Unity GameManager script and demonstrates a concise solution. Issue 1: Unresponsive Input Actions At first, the GameManager script wasn't responding to the LocalMultiplayerStart input action. The issue was traced to incorrect syntax usage. By replacing inputActions.Player.LocalMultiplayerStart.actionMap.enabled with inputActions.Player.LocalMultiplayerStart.triggered, the input action was correctly detected and acted upon. Issue 2: Inactive Update Calls Another roadblock was the GameManager's Update method not being called. This led to confusion and halted gameplay mechanics. The issue was mitigated by ensuring that the GameManager script was properly attached to an active GameObject within the scene. Furthermore, script execution order settings were adjusted to ensure proper function call...
Read more

Only one line of code

Image
 Only one line of code      For a while I was having trouble with a part of the drifting where the kart would completely stop at the drift zone. I made sure the trigger for the box collider was on so I was confused on why it would completely stop. I checked and messed with the drifting part of the code that maybe it was a way I made it but it still didn't work. I was working on it so much I reworked the drifting 3 times and even added a second boolean and I had no clue. Then after looking at how I'm calling the Drift method I thought about maybe moving it out of it's own if statement and it worked.     I didn't realize that it stopped moving rather than getting stuck. It was picking one over the other and after changing that it finally worked. I'm not sure if my previous code would have worked but now I'm making it so that the kart would drift after turning into a certain angle. I still can't believe that I overlooked the fixedupdate again.
Read more