Monday, December 29, 2008
Happy Christmas from FiveDevTeam!
He will be helping us move the maps and level assets to a specialized codebase for Five with a few little changes. We look forward greatly to working with Dan and getting progress made on this little mod, which turns one year old... yesterday! Wow!
Before you play the game, RTFM. (XD) It helped me for the controls.
As for Five's progress, terrain stuff for the mod has been downright tedious but once it's done the island's beaches should look quite nifty. I'll probably post a little video eventually so you can see what I've been doing this whole time.
Friday, December 5, 2008
Going into Test Maps
This is the carnage that followed.
I tried waiting longer the second time I did it and I crashed Source by using an smg1 grenade in the middle of about 100 metrocops and at least 40 airborne manhacks. I bet my older computer would have wound up in rigamortis by that point...
Either way it's nice to know what Source can do for you!
EDIT: New carnage pic in 1440x900 glory!
I wonder if anyone's nuts enough to try making that into a desktop...
Tuesday, November 11, 2008
Still Alive!!! Five @ Five! Part Fi- I mean Four
Yes I am Still Alive and so is this mod.
Everyone hum with me!
While you're dying I am still alive
And when you're dead I will be still alive
The rest of the images- well, not talking about those yet. In any case, more is to come with five's development, though we have been pretty slow lately we are chugging along.
Sunday, September 7, 2008
Biological Downtime
Don't you just love it when I'm on time with my updates? Well, once again sorry for all the delays everyone but I was unable to operate the computer for a while because a severe illness hit me. Thankfully I'm back on my feet now to tell you that I did some research while I had the time. And two cookies for who can guess what's behind this door.
Rest assured, the FiveDev team remains committed (and not insane!) to bringing you the best mod we can possibly make. And progress is getting underway.
Friday, August 22, 2008
Data Stream Currently Unstable
http://www.cyberpunkreview.com/images/minority_report30.jpg)
It even supports motion blur. Excellent. Also, I'd like to take a moment to thank Death Spektor in particular, he is now the second unofficial member of the development team, for a total of five members.
(I just had to point that out. That number keeps popping up too much!)
Anyway, he's been slaving away at a near final build of one of my blacklisted levels, and I thank him most gratefully for his assistance. I suck at optimization and he makes my work a lot easier to deal with. So props to him big time for helping us.
As for that visual content? Still forthcoming. I might just post it in the Windows Media format I accidentally recorded it in. We'll see.
Thursday, August 14, 2008
Sorry we've been neglecting you all...
Monday, July 21, 2008
Friday, July 18, 2008
Monday, July 14, 2008
TaSk InTeRcEpT @480 10/7/2013
Subject 02. Program Summary- Sniper 1 terminated by candidate after prolonged inactivity period @30. Subject 02 reconnoitered the island for 50 additional beats. All remaining snipers reported contact with the subject. Sniper 3 was mortally wounded via shrapnel @127. Sniper 2 at the dockyard position terminated Subject 02's candidacy @150. Subject 02's corpse was retrieved @153. Ammunition was restored to rebalance the test. Restocking crew reported the subject had moved fuel supplies intended only to encourage tactics involving explosives to a storage area near the dockyards. The supplies were returned to the coordinates specified in the testing area's original design.
Subject 03- Program Summary- Sniper 1 eliminated @45. Unpredictable acquisition of new combat tactics by the Subjects warrants the construction of a training area for future recruits. Furthermore, the Fairness Committee suggests repositioning of personnel in Section 1 to enhance the reality of the challenge. Sniper 2 terminated at the dockyards @102. [Post-test note: Body location has not been identified. Collection teams suspect obliteration of Sniper 2.]
Sniper 3 dispatched Subject 03 with two headshots, negligibly six pot shots were also fired. Subject 03 evaded the Sniper for 20 beats, but was forced out by necessity when ground teams approached his position. Consider notifying Administration of effectiveness of the Main Island for training Snipers in live fire exercises as well as training Elite operatives. Ammunition resupplied in increased quantities to improve subject survivability.
Subject 04- Program Summary- New sniping teams were rotated to the island, replacing all previously deployed units. Subject 04 performed with unusual perspicacity. He eliminated all four targets slightly under 200 beats. To his credit he explored much of the island and frequently outpaced the Subject tracking equipment. He is the first graduate of the program. Subject 04 displays an unfortunate penchant for creativity. The Promotion Committee recommends delaying his Elite respecifications until cyborgization technologies advance.
Subject 05- Candidate selected from Inglewood Dissident Holding Facility. Testing area now in preparations for the new candidate.
The staff would like to pass a candidate for Elite training in the near future.
Tuesday, July 1, 2008
Wednesday, June 25, 2008
tRaNs-OpT rEc1e\/3I] @318 25/06/2013
I: I am at peace with my this shithole. I've got every spot marked. This is going to be easy.
II: This is going to be easy. This is gooooooingggggg to be easy provided I can survive the minutes between firing my beloved plasma pulse rifle. (A drawing of the plasma pulse rifle)
VII: I Blew his head clean off. Fun, but creepy. Not normally trained to shoot at Combine uniformed. Except in special circumstances like this one. Discrimination is not an option.
I (or VIII): They released a new target. I saw him run past, had a different pace to his gait. Should be fun in the future to note differences in running speed. Differences in head explosions are always interesting.
II part II: My inability to destroy the target made me realize that there are several design flaws in how the employers refurbished the island for training. I will exhaustively enumerate these throughout the room.
Not enough explosive barrels. There are no explosive barrels here, and I imagine few are on the island at all. Makes it tough for us to miss.
Too many buildings. Should have been demolished so we can get a clear shot. There are no locks in my nest outside the inner door. I imagine this would be true for the rest of the island.
Too much ammo. They should do a better job of cleaning up the ammo. Each successive game stacks the odds against us. (Third at the time of this writing)
Went to the employer's island after the third target's demise. They need to check the vulnerability of ventilation shafts. Need to clean up the older areas, they pose a security risk.
Tuesday, June 10, 2008
5 At 5, Part 3
An early shot from what I have been working on in the latest tidbit to the blacklisted map.
The newer, prettier version, with lots more going on in it. Gameplay for this segment is mostly complete.
Big plans.
Wednesday, June 4, 2008
Thursday, May 29, 2008
Aw, crap,
A bunch of work on the mod and now I'm running on Valve time. Fantastic.
Tuesday, May 13, 2008
How (not?) to Develop A Mod, Part Four
The main idea with "5" was to create a fresh, non linear take on standard Half Life 2 weaponry with a limited weapon set. Since the levels were nonlinear we had to use the Episode Two tech to keep render detail at longer distances. The benefits to AI and graphics improvements were just on the side, because we needed the longer render distance to enable us to make larger areas the player could move through. The first area for example is a large area with several entry points for buildings, combining interior and exterior spaces for a small military base and a power plant. The second section will be much larger and rely more heavily on the long distance draw- a forest, dockyard, waste treatment plant, substation, and a shanty town are planned for the second section which work has commenced upon (below). The current shots below are not representative of the final project, so each area will be expanded.
The main idea for each map is to keep the choice of multiple routes fresh. The entrance to the military base and power plant area has no less than four separate entry points with varying levels of risk. Gaps in a fence, a minor exploration physics puzzle to get over a fence, a more direct route, and a fortuitously placed dumpster all provide different approaches from distinctly different angles and of varying visibility to the first target. Keeping in touch with the alternate way to beat the game (which involves more avoidance, observation, and exploration than direct conflict), two of those routes avoid the sniper in places. The other two are somewhat more direct. This is only the beginning as well. The third segment of the island happens to be even more taxing than the second area, as it requires a HUGE area of open space. I'll reveal more later when the map is under construction.
Remember, your comments fuel progress!
(In other news, I tried the demo for "The Bourne Conspiracy-" fun but infuriating often. I predict that it will get 7s and 8s from the media.)
Monday, May 12, 2008
5 at 5, Part Two
Images, away!!!
Monday, April 28, 2008
5 at 5, Part One
Wednesday, April 2, 2008
Aw damn, I missed a golden oppertunity...
Friday, March 21, 2008
How (not?) To Develop A Mod, Part Three
Many mods often either try too hard to be innovateive and become cumbersome or not try hard enough and end up being unoriginal. I won't pretend to be an expert (being as this is my first mod project) but I will opine on the subject.
The first thing you need to do is study. Look at other mods, even at professional games, not for ideas necessarily but for what they did right and what they did wrong. For example I'll cite Half Life 2. I loved so much about that game (part of the reason why I'm going to the trouble of modding it), but I saw pros and cons. For one, many sections of the game felt like excess in places. Entanglement was a particuarly annoying chapter for me. Even though a major story point is made midway through the chapter, I felt the chapter itself (particuarly one huge gunfight where you must set up three turrets) was often overly difficult. However, I looked around in the level and began to think strategically on my next playthroughs and got better as I replayed HL2. (I've gone through the game on hard more than five times. I know somewhat what I'm talking about.) Valve's inner theory is telling a story but keeping it firmly within the player's control. So we really don't begin to learn all about the combine until Black Mesa East when Eli explains the newspaper clippings on the wall. The beauty of that sequence was that it was *completely optional.* I love it when a story can get the gist of it across to a casual player, yet still have huge amounts of story in the backweb for the more serious crowd (since I've been on both sides of the fence it's even more apparent to me.). Excellent examples of this point are also in Episode One's Kleiner cast, which again is completely optional and pops up at several points so the player can make the choice themselves to listen or not.
When I first brainstormed "5," I first thought of the AI in HL2 as compared to a game like F.E.A.R. Fear's AI is excellent- they dive for cover, they can go everywhere the player goes (climbing ladders, jumping through windows) and even some places that the player can't (climbing under pipes), and doing more intelligent things like moving things around to make their own cover (see the 18 minute "Project Origin" trailer to get a hands on look at this idea.). HL2's AI often felt mindless in places (rappeling in front of a water boat just to be run down is funny once, but after awhile it feels stupid, not to mention some of the more fortiuitously placed explosives in some setpieces).
Another gripe I had with both HL2 and F.E.A.R. is that sometimes the experience felt overly linear. MINERVA: Metastasis's opening level for example feels extremely non-linear. (And once you open the service doors to the center of the island, it can be approached from multiple entery points, earning non-linear points from me.) Parts of HL2's "Ravenholm" chapter were similarly non linear, because you had a nice set of rooftops and streets and back alleys to explore and shoot zombies in.
So taking notes from the above games, I attempted to craft a mod. My first attempt was a never-to-be-released attempt at nonlinearity that I tenatively called "Wasted."
The idea was that the player had been tasked with taking a small team of rebels aboard a combine transport over the Sahara desert and retrieve a specified cargo- the HEV Mark V. Ultimately everything went to hell, the player accidentally managed to strap himself in the suit, most of his team is killed, and he manages to port out of the transport as it begins to crash (the very beginning of the game). Under the direction of his Neural Interface (NI) named "Delator" (Roman for "informant"), he was to scout a huge desert locale for pieces of the transport, rip as much data as he could from these scattered terminals, avoid roving patrols of Combine soldiers looking for him, and attempt to track down any survivors from his crew. I ultimately abandoned the mod when the maps hit a huge technical hurdle and the map data was corrupted. In any case, "Wasted" died a quiet drunken death (A little humor!). Out of the ashes of Wasted came "5." Originally called "The Hunt" (name changed because of a mod by that name already existed), it has grown into the in progress mod you see on this blog.
Moral of the lesson: Revisiting old ideas with fresh eyes can give you some excellent refinements you might not have seen back in the day. Remember that hindsight is 20/20, and if you didn't release an old project than feel free to rip yourself off. (Just like I did!)
Progress ticker: Section 1 in progress. Naturally I wouldn't want to spoil what I mean by that.
Wednesday, February 27, 2008
How (not?) To Develop A Mod, Part Two
Be careful with Displacements.
The level (like the mod) will be quite displacement intensive but to a lesser extent than the main island. You have to plan carefully with displacement textures because
-They're a bitch to manipulate when you need to do fine detail work
-It's difficult to fix a displacement when you screw up
-It's difficult to make a displacement look realistic when you're working on large terrain with lower numbers of displacement verticies
-Texture contineuity (making the ground appear natural) is also difficult to achieve
-Sew can be detrimental to map progress if you sew too early, because it will link the displacements improperly and you will see big seams in the displacements on compile
A few positive things:
-Combine scanner units are incredibly easy to put in a level- just place a few info_node_airs in logical sweep patterns around the area you want patrolled and the scanners will sweep the area automatically and take pictures of the player and other npcs.
-trigger_waterydeath is also relatively easy to implement and will help you block off waterways or oceans when necessary.
-Soundscapes do a lot to add to atmosphere when implemented appropriately.
More updates as development progresses.
Friday, February 15, 2008
How (not?) To Develop A Mod, Part One
When you decide to work on a mod, planning is key. Planning is key for just about anything, from asking out a girl to laying the framework for a mod.
The team must start with a clear plan in mind for the mod. Don't even touch Hammer or Photoshop or Maya or whatever else you use before you know exactly what you want to do, but make sure your initial plan is flexible. For all you know, it could be completely impossible.
The initial concept for "5" was the player being dropped into a large forest being assigned to track down a kill a single target, and the target was supposed to have flawless A.I. to the point where he could change position to engage the player dynamically. The sniper would take a shot, we kill the sniper in the nest and spawn a combine soldier behind the nest, then he would assault to a different point as fast as he could, we kill the runner and activate a sniper in the nest, then he would wait until the player was within a radius, then take another shot. The player was to begin with nothing but a melee weapon, and then track down a single shot rifle to engage the sniper with. The map would have been very large, including a rail yard, a small shantytown, and huge expanses of dark forest, complete with constant rainfall and fog to limit the player's ability to engage the target. But we just decided it wasn't feasible to make because of the huge emphasis on the A.I. The combine aren't designed to run away from the player, and since we have no coders on hand, just mappers and texture artists, we decided to abandon this model and turn to the current one. The player is dropped in much the same, except he will likely have a hatchet and find a crossbow shortly in his quest giving him more ammunition. We upped the target count to four and forced the player to figure out a new way of combat, similar to the game "Shadow of the Colossus." The player will need to exploit his environment and flush the sniper. There will be several methods of either flushing or killing the target, adding replay value, plus additional "scout" units actively scouring the island attempting to find and kill the player. Scanner units will also act as informants, and the player has the option of avoiding combat entirely and attempting to unravel the greater motives of the people who dropped him on the island, and interfere with their endgame.
In one way, you could consider the new version more ambitious than the original one, but at least with an island we have a more finite landscape to work with, plus less work with trees and displacements (Forests look bland when you have a bunch of cloned trees). And the new setup also allows for an alternate ending that will be difficult to unravel but well worth the effort.
Another important part of modding is to love your job. This may sound corny, but I genuinely enjoy slaving away at a keyboard working in Hammer because it lets me take my brain and smear it all over a screen for other people to play. (I bet this mod will have far less users now that I've used this analogy.) You and your mod team need to have a unified vision, so having a small amount of people with a large skill set is good. Depending on the scope of your mod, you may need more people. I won't pretend to know about modding with a large team, as this is the first mod I've ever worked on. One of our team has worked on previous mods, but for the most part we are first time modders.
Third part: Don't be afraid to change things when technical issues arise. The current island workload might even change for all we know. Early in the development of a mod, things are very volatile. Things can explode several times over before you nail down a correct concept. Let them explode on occasion. You might find out something better than you had.
Monday, February 4, 2008
The Very First Post!
FOR GOD'S SAKE, BACK UP YOUR MAPS. You have to be absolutely paranoid about your data. Over the course of making an internal demo of "5," I have lost map data at least four times, even though I currently have ten seperate versions of the same map.
COMPILE EARLY, COMPILE OFTEN. Hammer will croak more if you do a large amount of new geometry and not test at frequent intervals. I suggest one compile for every man-hour of work on your maps, and save a new file for alll the new stuff.
WHEN ADDING LARGE AREAS TO YOUR LEVEL, PREFAB THE ROOM IN QUESTION BEFORE COMPILING. This particular instruction also comes from my "5" demo experiences- I lost the underground portion of the map twice, so I prefabed the whole darn underground upon each map revision, so in the event of losing my data, I would be able to stick the entire area back into the map in one operation without having to rebuild from scratch. Entities, brushes, npcs, the works. Prefab it all.
And now a teaser screenshot from the mod:
Perhaps more screens to come. Definitely more rants.