Friday, December 11, 2015

ET 49 - Assignment 16 - Code Name Donkey Kong - Basic Key Events

Due to design choices I made no effort to be apart of that probably didn't foresee having to shoehorn in random tutorials, I couldn't quite implement the key events the way Nick Tuso outlined.  However, level three already had items that fit the bill; It was just that it didn't make sense to have to "Pick up" said items.  Still, the basic concept is the same: Set off multiple triggers separately for one final event.  In this case, winning the game.

Skipping the parts that didn't work and had to be removed, first I created an integer variable in the third person game mode called "Points Captured" to track said capture points.


Then in the capture points' blueprint, it accesses the third person game mode to add one to the Points Captured variable upon its own destruction.  It also adds fifty points to your score and prints out how many points you've captured to the screen.


Finally, the level blueprint checks the number of Points Captured against the number of capture points.  Since there are seven control points, it checks to see if you've captured more than six of them.  Once done, it ends the level.


Check it out in action below.  Normally there are enemies on this stage, but I disabled them before recording this video.

Friday, December 4, 2015

ET 49 - Code Name Donkey Kong - Time Bonus and Score Keeping

This week, I added blueprints to convert time remaining in the level to bonus points, and fixed and issue where the score wasn't transferring between levels.




Friday, November 20, 2015

ET 49 - Code Name Donkey Kong - Timer and Air Control

So this week, I was reassigned from Marble Magic to Code Name Donkey Kong.  I made a scoreboard, a timer system, and enhanced the jump maneuverability.

Here's some screenshots of my blueprints.  The first enhances jump maneuverability.


Here's some of the blueprint for the timer.  It's referenced by the scoreboard widget I also made, but I don't have a screen shot of it.




And now a video of me using these things in-game:

Friday, November 13, 2015

ET 49 - Checkpoint and Respawn Tutorial Remastered

I'm pretty sure I've been miscounting the weeks on this thing.

Anyway, despite getting my laptop back from having it's broken hard drive repaired, it's been a decidedly off-week for me.  Suffice it to say, remaking my tutorial took longer than I thought, and I didn't have time to do anything else.  Hopefully, I'll make up for it next week.

Friday, November 6, 2015

ET49 - Week 8 ... Stuff

My laptop is in the shop for repairs this week, but I managed to get some work done. Unfortunately, I did not get pictures our video of any of it. Most of it was refining what I had already made, so there wasn't much to look at anyway. The controls should be a little tighter now, and I managed to get jump pads to work better with the ball. That's pretty much it.

Friday, October 30, 2015

ET 49 Week Seven - Marble Magic Falling Damage

In our game, you have to get the ball to go downhill without falling and breaking.  I managed to find and refine a fall damage blueprint on-line and so far it works fine.

Below is the video demonstration.  After ramming into a wall to show it has to be falling to die, I use a keyboard command to teleport the ball to an aerial checkpoint.  From there, it falls to the ground, dies, respawns, falls, and dies again.



Friday, October 23, 2015

ET 49 Week Six - Auto-Zooming Camera

I'm continuing to look into fine-tuning the ball controls, but I'm not making much headway. I also can't get health to display on the HUD because the tutorial I'm following uses a widget with "Cast to Character" in it, which the ball isn't compatible with it and I have yet to find an analogous substitute.  HP can probably work without it, though.

This week, all I have that I can actually show is a camera that zooms into the ball when something gets in the way.  This sort of thing is the default in the third-person template, but in the rolling ball template it isn't.  All you have to do is go to the ball's blueprint, click on the spring arm component to view it's details and click "Do Collision Test."
You can see the results in the video below.  Those blocks have a low clearance, so the camera gets in pretty close.