TheMonument_Screenshot_01
TheMonument_Screenshot_02
TheMonument_Screenshot_03
The Monument
TheMonument_Screenshot_05
TheMonument_Screenshot_06
TheMonument_Screenshot_07
TheMonument_Screenshot_09
TheMonument_Screenshot_10
TheMonument_Screenshot_11
TheMonument_Screenshot_12
TheMonument_Screenshot_13
TheMonument_Screenshot_14

Unannounced Title - Developed by Raven Software and Activision Blizzard

What Did I Work On For Unannounced Title?

I worked as a Junior Mission Designer for the level design department of Raven Software. My duties were focused on the ownership of two major locations in the mission as well as many smaller locations that I was supposed to iterate on and maintain. I worked on the building the environment, setting up the encounters, and scripting additional behaviors or setting related to those encounters. I worked alongside the art and lighting departments to bring the area up to expectations.

  • Designed, built, and populated high-quality environments and gameplay for two major locations and many smaller locations of a larger map using a proprietary toolset.
  • Owned the design and production of two major locations and various other minor locations of the map.
  • Setup the environment, collision, encounters, and enemies for each of the areas I owned in engine and in script.
  • Scripted examples of multiple features in a test map for testing UI-related features for the project.

What Did I Learn From The Monument?

  1. AAA WORK FLOW – Unannounced Title was my first professional work in the industry as well as my first AAA work in the industry. I learned a lot about how games are made at the AAA level, how level designers are supposed to operate and work with the other disciplines like Art, Lighting, Sound, and Tech. Since I had full ownership of multiple sections of a larger map I had to figure out where to iterate and build upon the levels on my own, while still getting feedback from my peers.
  2. GSC SCRIPTING – Learning new scripting languages and skills is always good. Most of my experience up to this point was in C# and GSC isn’t all that much different, but it was still a learning process to figure out a new language and I believe it will help me going forward when learning other proprietary scripting languages.
  3. RADIANT ENGINE – Similar to learning a new language, learning new engines and tools are also very important.  I learn tools fairly quickly, however I did spend a bit of time at the beginning of the project learning more about Radiant.  I had used the older versions of the engine for making maps and mods for games like Call of Duty: World at War, but learning new versions of engines whether used in the same or a different way can be strange and a process.  I learned this when returning to Unreal Engine from Unreal Engine 3 to 4 and 5.  The process of learning a new engine is a fun and interesting task, it allowed me to learn new techniques for solving certain level design problems based on the tools I had available to me; sometimes that is an extra tool and sometimes it is a lack of a tool, both scenarios bring new challenges that helped me grow as a level designer.
  4. PROPER BUG TRACKING / JIRA – When working on the title we used JIRA and Confluence to monitor and track tasks, bugs and document various elements of the project. I had never used these tools nor had any proper experience learning to monitor and track bugs. Learning these tools not only helped me in terms of learning new tools, but also improving skills that I was lacking in going into the project.