As a service to our younger gamers, who, upon being asked, "what's your favorite CS map?" will respond incredulously with, "isn't CS that really old game?" then blow a large bubble gum bubble in your face and go back to texting a fellow bro -- here, you little shit, here's why The Bridge is great.
Many moons ago, I worked on a single player Half-Life 1 mod called "Nightwatch" with many of the the best and brightest minds of the mod community. Even with all our expertise, resources and manpower, we still overestimated ourselves and ended up not releasing a thing.
This weekend at MapCore, we're going to live vicariously through you and actually release some Nightwatch maps -- make a small Half-Life 1 deathmatch level in 72 hours using these awesome textures!
The Half-Life 1 version of Hammer is more or less identical to the current Source version, except the design process is so much faster. No worrying about cubemaps or water shaders or prop models. Just start mapping!
Confer the thread for instructions, what to download, and various tips and tricks for working with Half-Life 1.
I still make Source mods and I like it, don't get me wrong -- there's no harm in a little experimentation though, right? Now, if you make levels for Source Engine stuff then you already have the skills to start using Unity. Think of it as learning another language and being bilingual or multilingual. Here are some general concepts from Source, their translations in Unity, and some tips:
> In the Unity editor, hold right-click in 3D camera view to enable WASD / mouse-look / noclip-style navigation, just like in Hammer. Hold "Shift" to sprint. This is probably the single most important thing for you to remember that you might not've figured out immediately.
Against our better judgment, me and Eddie Cameron have made another Unity FPS for the Mini Ludum Dare #27, "All Talk." It's horribly unfinished because we spent most of the time playing LA Noire and going out to bars and eating amazing burgers, but hey, next time we'll know.
This game is based on the central setpiece of Francis Ford Coppola's classic espionage thriller, "The Conversation."
Here's how it works: you have three characters with microphones. Two have long-range parabolic "sniper" microphones in fixed positions, and one is on the ground to actively tail the target.
The target couple wanders into all kinds of obstacles (walls, trees, spheres, crowds) that prevents the snipers from getting a clear recording, so that's where the ground guy comes in -- he can tail them for a limited time, but then occasionally the target will turn around -- in which case he has to go run and hide.
Right now a lot of it is broken and the game doesn't work as well as it should. Specifically, it's either really hard or it's too easy if you find one particular exploit.
There's also a bunch of stuff we want to add: working gameplay, character animations, non-male character models, additional missions and scenarios, maybe a second "audio mixing" phase where you have to mix the 3 sources together before submitting to the client, etc.
Still... I think we're slowly getting better at this.
If you really want to play it, though I can only half-heartedly recommend it, the 7.1 mb Unity web player build is right here. Here are two important things you need to know before playing --
1) A yellow arrow hovers above your target for 30 seconds as an aid at the beginning of the game. After that, you're on your own.
2) Also, keep your briefcase guy out of the target couple's LoS, or else you'll lose! They have really far LoS! Just hide behind stuff to break LoS.
It's so refreshing to make Portal 2 levels -- you have an idea, you make it, you test it, you detail it, you test it, you fix it and then you have a rather playable map in the end.
I've worked on so many unfinished levels and half-baked concepts the past year... and then I just cranked (crunked?) out a few chambers in the last few weeks.
Making a map pack is suddenly so much more manageable. Never before has the function of video game architecture been so clear and elegant. In a weird reversal of architectural history, ornament has even transformed into something functional (it makes a surface unportalable) and slanted walls become more than just visually interesting.
The only thing I dislike is the lack of a decent custom map loader interface in the main menu. Right now you have to go into the console and type "map [mapname]" which the average player can't be bothered to do. I'm sure it'll get addressed in the next update (DLC #1?) but until then, profound sad-face.
If you've been working on the same old project for the last few months (or years) then take a break and spend a few days on a Portal 2 map.
Remember the designer you once were and enjoy the feeling of actually finishing things.
This is a series of posts that analyzes the immersive sim. It's a play on the excellent RPS feature, Dark Futures.
In past posts, I argued that (part 1) immersive sims were so cool we got overprotective of them and suffocated them, but (part 2) we can still extend the same design theory to contemporary single player design.
For part 3, I'd like to explore the limits of "immersive sim theory" and even criticize it in light of recent research. This devil's advocate stuff will help us in part 4.
Both system dynamics (sort of the science of systems) and Looking Glass Studios came out of MIT in the 70's or 80's or some time around there -- and for the convenience of my argument, let's assume it wasn't a coincidence...
