{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
9/9/2010 3:52:52 AM
571
Forge Lessons - Lesson 49-51 (1/19/12)
[url=http://www.reachingperfection.com/p/forge-lessons.html]Download PDF w/ Lessons 1-51[/url] [LAST UPDATED: 11/22/11]
[i]Join like minded level designers on my game/level design blog @ [url=http://www.reachingperfection.com]ReachingPerfection.com[/url] where I fill you in on many things in the level design world. You can also join [url=http://www.reachingperfection.com/p/forum.html]our forums[/url] to meet other people that enjoy game/level design just as much as you do. ;)[/i]
[b][u]Forge Lesson Index[/u][/b]
[url=http://www.reachingperfection.com/2010/08/lesson-1-first-impressions.html]Lesson 1: First Impressions[/url]
[url=http://www.reachingperfection.com/2010/08/lesson-2-knowledge-is-power.html]Lesson 2: Knowledge is Power[/url]
[url=http://www.reachingperfection.com/2010/08/lesson-3-path-manipulation.html]Lesson 3: Path Manipulation[/url]
[url=http://www.reachingperfection.com/2010/08/lesson-4-perspectives.html]Lesson 4: Perspectives[/url]
[url=http://www.reachingperfection.com/2010/08/lesson-5-deterrents.html]Lesson 5: Deterrents[/url]
[url=http://www.reachingperfection.com/2010/08/lesson-6-incentives.html]Lesson 6: Incentives[/url]
[url=http://www.reachingperfection.com/2010/08/lesson-7-combat-congestion-and-traffic.html]Lesson 7: Combat Congestion and Traffic[/url]
[url=http://www.reachingperfection.com/2010/08/lesson-8-eye-catching.html]Lesson 8: Eye Catching[/url]
[url=http://www.reachingperfection.com/2010/08/lesson-9-perspective-variance.html]Lesson 9: Perspective Variance[/url]
[url=http://www.reachingperfection.com/2010/08/lesson-10-spawn-perspectives.html]Lesson 10: Spawn Perspectives[/url]
[url=http://www.reachingperfection.com/2010/08/lesson-11-smooth-spawning.html]Lesson 11: Smooth Spawning[/url]
[url=http://www.reachingperfection.com/2010/08/lesson-12-path-maps.html]Lesson 12: Path Maps[/url]
[url=http://www.reachingperfection.com/2010/08/lesson-13-area-introduction.html]Lesson 13: Area Introduction[/url]
[url=http://www.reachingperfection.com/2010/08/lesson-14-essence.html]Lesson 14: Essence[/url]
[url=http://www.reachingperfection.com/2010/08/lesson-15-purpose.html]Lesson 15: Purpose[/url]
[url=http://www.reachingperfection.com/2010/08/lesson-16-innovation.html]Lesson 16: Innovation[/url]
[url=http://www.reachingperfection.com/2010/09/lesson-17-color-contrast.html]Lesson 17: Color Contrast[/url]
[url=http://www.reachingperfection.com/2010/09/lesson-18-patience.html]Lesson 18: Patience[/url]
[url=http://www.reachingperfection.com/2010/09/lesson-19-threat-zones.html]Lesson 19: Threat Zones[/url]
[url=http://www.reachingperfection.com/2010/09/lesson-20-safe-spawning.html]Lesson 20: Safe Spawning[/url]
[url=http://www.reachingperfection.com/2010/09/lesson-21-incentive-weighting.html]Lesson 21: Incentive Weighting[/url]
[url=http://www.reachingperfection.com/2010/09/lesson-22-rule-of-thirds.html]Lesson 22: Rule of Thirds[/url]
[url=http://www.reachingperfection.com/2010/09/lesson-23-static-perspectives.html]Lesson 23: Static Perspectives[/url]
[url=http://www.reachingperfection.com/2010/09/lesson-24-advertising.html]Lesson 24: Advertising[/url]
[url=http://www.reachingperfection.com/2010/09/lesson-25-investment.html]Lesson 25: Investment[/url]
[url=http://www.reachingperfection.com/2010/09/lesson-26-nurturing.html]Lesson 26: Nurturing[/url]
[url=http://www.reachingperfection.com/2010/10/lesson-27-reputation.html]Lesson 27: Reputation[/url]
[url=http://www.reachingperfection.com/2010/10/lesson-28-perspective-direction.html]Lesson 28: Perspective Direction[/url]
[url=http://www.reachingperfection.com/2010/10/lesson-29-degree-of-focus.html]Lesson 29: Degree of Focus[/url]
[url=http://www.reachingperfection.com/2010/10/lesson-30-application.html]Lesson 30: Application[/url]
[url=http://www.reachingperfection.com/2010/10/lesson-31-immersion.html]Lesson 31: Immersion[/url]
[url=http://www.reachingperfection.com/2010/10/lesson-32-cohesion.html]Lesson 32: Cohesion[/url]
[url=http://www.reachingperfection.com/2010/10/lesson-33-continuity.html]Lesson 33: Continuity[/url]
[url=http://www.reachingperfection.com/2010/10/lesson-34-peer-review.html]Lesson 34: Peer Review[/url]
[url=http://www.reachingperfection.com/2010/10/lesson-35-failure.html]Lesson 35: Failure[/url]
[url=http://www.reachingperfection.com/2010/11/lesson-36-simplicity.html]Lesson 36: Simplicity[/url]
[url=http://www.reachingperfection.com/2010/11/lesson-37-orientation.html]Lesson 37: Orientation[/url]
[url=http://www.reachingperfection.com/2010/11/lesson-38-dance-floor.html]Lesson 38: Dance Floor[/url]
[url=http://www.reachingperfection.com/2010/12/lesson-39-dedication.html]Lesson 39: Dedication[/url]
[url=http://www.reachingperfection.com/2011/01/lesson-40-foreshadowing.html]Lesson 40: Foreshadowing[/url]
[url=http://www.reachingperfection.com/2011/01/lesson-41-consistency.html]Lesson 41: Consistency[/url]
[url=http://www.reachingperfection.com/2011/01/lesson-42-polish.html]Lesson 42: Polish[/url]
[url=http://www.reachingperfection.com/2011/01/lesson-43-lasting-impression.html]Lesson 43: Lasting Impression[/url]
[url=http://www.reachingperfection.com/2011/02/lesson-44-aesthetic-noise.html]Lesson 44: Aesthetic Noise[/url]
[url=http://www.reachingperfection.com/2011/03/lesson-45-pacing.html]Lesson 45: Pacing[/url]
[url=http://www.reachingperfection.com/2011/04/lesson-46-active-engagement.html]Lesson 46: Active Engagement[/url]
[url=http://www.reachingperfection.com/2011/04/lesson-47-kleenex-testing.html]Lesson 47: Kleenex Testing[/url]
[url=http://www.reachingperfection.com/2011/05/lesson-48-veteran-testing.html]Lesson 48: Veteran Testing[/url]
[url=http://www.reachingperfection.com/2011/10/lesson-49-exposure.html]Lesson 49: Exposure[/url]
[url=http://www.reachingperfection.com/2011/11/lesson-50-navigation.html]Lesson 50: Navigation[/url]
[url=http://www.reachingperfection.com/2011/11/lesson-51-audience.html]Lesson 51: Audience[/url]
[b][u]The Short Version... for us lazy folk ;)[/u][/b]
The short and skinny of it is that all of the above lessons are level design theories that are used by level designers in order to make their maps play better. Sure anyone can make a map now in Reach, but can you make a map that will get into matchmaking and be better than everyone else's? These lessons cover advanced design techniques that aren't your normal forging tutorials. They will actually improve your map's spawns (Smooth Spawning and Spawn Perspectives), weapon placement (Incentives), and gameplay. I will be updating as I release each of the BNet threads. Use this one as a reference and save it somewhere.
[url=http://www.reachingperfection.com/p/forge-lessons.html]Original Source[/url]
[b][u]The Longer Version for more info[/u][/b]
Are you ready to jump into the powerful tool that is Forge 2.0 to start making maps for you and your friends? Did Halo 3's system frustrate you too much to even try it? Do you aspire to get your map into matchmaking? This will get you prepared for all of those.
Let's all admit that with the new Forge system anyone can build a map. No more geomerging, no more interlocking, or any other painful methods. But just because anyone can make a map easily now doesn't mean that the map is going to play well and people are going to enjoy it. I want to help all of you make your maps and gametypes better. I want to help make your maps play well enough to get into matchmaking. You can't even find this much quality map design help at Forgehub, I guarantee it.
I write this series of level design theory lessons called "Forge Lessons" to help all designers make their maps play the best that they can. They will teach you about how to make your spawns smooth, how to place your weapons (and other incentives), how to get your map noticed, how to fully control every step that your player takes, etc. I cover advanced level design topics used by professional level designers in all games... though I may name the techniques differently ;). Eye catching, perspectives, incentives, deterrents, path manipulation, color contrast, innovation, and area introduction are just some of the topics I cover. I write a new lesson about once a week, sometimes slower.
Some of you may need to ensure that I am actually qualified to teach people. My old GT was AZN FTW. I was one of the original 6 members of Forgehub that turned it from a wordpress blog to a vbulletin forum. I created one of the most popular and iconic gametypes in Halo 3, Conquest. I am one of the two designers of Ravinia, one of the 50+ community maps that got into matchmaking. I am also the designer of Affinity in Halo: Reach's matchmaking system. I have taught many forgers and aspiring designers.
These lessons have been used by teachers to teach high school and college game design classes. Several of them have been featured on Gamasutra and various other game/level design sites. But I'm not going to tell you how good they are. I'll let those who support these lessons tell you. Keep an eye on this thread for testimonials of the lessons from all that read them. Many well known figures amongst the Halo community will take their time to stop by here to let you know what they think about these lessons. If you don't want to trust me, then trust what others have to say for them.
I will update the top of this thread with a link to all of the lessons as I post them and reply to this thread when I post a new one, so save this thread somewhere. You can find all of the original postings with summaries of the lessons on my blog @ [url=http://www.reachingperfection.com/]ReachingPerfection.com[/url]:
[url=http://www.reachingperfection.com/p/forge-lessons.html]Forge Lessons[/url]
I hope these lessons help you as much as they have helped everyone who has read them. Enjoy my fellow Halo fans!
[Edited on 01.19.2012 11:02 AM PST]
-
Really brilliant post OP, keep up the updates
-
I love to forge all day all the time but have no one to forge with and show ally awesome inventions tricks and glitches I've learned over the past couple months halo reach has been out... Anyone ever wants to forge just send me a message my gamer tag is duckjr94
-
If any one wants some one to build forge maps with, hit me up GT= MotoBreath send me a message first
-
Hey Godly, glad to see the thread is still up and running. I'v been away from Halo for a while, but I might have to read-up and get back into it. EDIT: Oh, and you're ego still block out the sun :) [Edited on 03.10.2011 6:03 PM PST]
-
wingin it!
-
Well, I've gotten five friends reading these lessons and they can't believe someone put so much time and effort into it. Ah... what do you expect?
-
critique this. [url]http://www.bungie.net/Stats/Reach/FileDetails.aspx?fid=13482768&player=TripN%20KniveZ[/url] map i made for big team battle. tell me if thats not big team battle material. [Edited on 02.03.2011 1:00 PM PST]
-
[quote][b]Posted by:[/b] SkyTag Jumpmstr[/quote]Good read, I especially agree with the fact that when novices break the standards of the trade the results are disappointing--very true statement.
-
[quote][b]Posted by:[/b] EpIc God 41[/quote][quote][b]Posted by:[/b] Godly_Perfection[/quote]HOLY -blam!-!
-
-
thanks, these lessons helped me a lot, im not very good at forge but these made me a lot better, im about to attempt to make an amazing map [url=http://www.mtgfanatic.com/?ForumReferrerID=108952]Click this for Magic :)[/url]
-
Above discussion was a tasty snack ;) I definitely wouldn't say the lessons are bad, considering they're the primary influences on how far I've come since August 3rd, but, well... 'Reaching Perfection.' I said this a while ago on RP, and I still think it's true to an extent. I agree with Jumpmstr (great name, BTW, jumping was my favorite non-conventional H3 activity) that specific examples could greatly help you out, if done correctly. I know these are general design theories, but even you call them [b]Forge[/b] Lessons. You know your main audience. And I think if you do them right, they could still be effective. For example, in the lesson on smooth spawning, something like, "A lot of people aren't fans of the spawns on Pinnacle. Why? [Note: I do disagree with Jumpmstr on the comments about questions, I think the more the merrier. The more questions Godly asks, the more the reader thinks. If the reader is thinking more, the reader is learniing more, in the same size lesson.] Because a lot of them have no cover around them, and in a lot of cases you can barely spawn without having fire rained down upon you immediately." You could go on to expand this, and it could be one of your paragraphs. It's clearly a very specific example from Reach (whose players are your target audience) but the way it's presented means that it makes perfect sense out of context. PS: Thanks to Jumpmstr for starting this discussion, it led to me looking at the earliest lessons for reference, and I saw some of my comments back when I had maybe an hour's worth of design experience. They made me smile.
-
[quote][b]Posted by:[/b] SkyTag Jumpmstr I found the Forge Lessons PDF to not be very helpful. There are several useful tips, but they're buried in 42 pages of stuff, most of which I didn't find helpful (my perspective) for a number of reasons. ... Anyway, that's just my $0.02. Or maybe $0.03. I'm not good at building maps or even a very good player, but my observations seem to apply to a lot of other areas in life and I see no reason they wouldn't apply here as well.[/quote] First of all let me thank you for the well thought out response Jumpmstr. You bring up some very valid points. I can definitely see where you are coming from. These lessons were not written only for Halo's forge system they were written with level design in all games in mind, not just halo. The sniper rifle and rocket launcher are used as a reference multiple times because those are very standard weaponry in a majority of games and they hold pretty much the same function in all games. The reason why I never go into specific instances is because these articles are not there for a specific game, they are their to cover the general sense of things. Also these lessons are written for the true beginner. Each lesson considers that the reader has NO previous knowledge on the subject. These lessons are meant to take a simple tip and break it down into something that you overly think about so you take the time to analyze the why and how rather than the what. If you cover things too specifically a designer will never learn. If I tell people to always do something they will know that they need to do it, but they won't know exactly why in the greater sense of things and won't be able to build off of that knowledge. My goal with these lessons is not to set you into a standard practice. It is to show you the pieces and teach you how to put them together in your own way and rediscover things for yourself. Learning is much greater when you do something wrong and then learn from it rather than when someone tells you that a certain way is the right way to do it. Basically I want you to start from the bottom and work your way up learning everything as you go for yourself. Why? Because everyone experiences things differently. That is part of that lesson you mentioned. You never know until you try. One thing that works for you may not work for someone else. If I give you specific instructions and tell you that it is the best way to do things, you may accidentally stumble upon a situation where it isn't the best way to do things and you won't know why what I told you didn't work. What I'm doing is teaching you the concept behind fishing. I'm teaching you the purpose of bait, I'm teaching you the importance of patience, I'm teaching you the importance of picking your location. I'm not going to spoon feed you, I'm going to tell you what you are looking for and allow you to make your own decisions. These lessons are also to open your mind and make you aware of things that seem like common sense. Sure being patient and dedication seems like common sense, but not many people consider this a part of level design and thus this is an area they could improve in. If I make them aware they can take the time to focus and improve on that area now that they are aware that it is just as important as weapon placement. You are right, level design is an art form and in art you can beat specific. You have to teach people why and how art is done, not what to make. When teaching people to make music teachers don't only tell you to use exactly these notes together because they sound good. They teach you the concept of synchronizing and feeling. If people only taught specific styles, new styles would rarely be born. My goal is to teach to encourage progress and learning because with that we can take the time to improve the level design field as a whole and learn new things as a group rather than be stuck in one particular set of standards. I hope you get what I am getting at and understand why I wrote the lessons in the way that I did.
-
I love you.
-
-
I found the Forge Lessons PDF to not be very helpful. There are several useful tips, but they're buried in 42 pages of stuff, most of which I didn't find helpful (my perspective) for a number of reasons. - There are 275 questions in the document. I understand the value of getting the reader to think through his map design, but being inundated with an average of 6.5 questions per page seems a bit much. - It feels as if too much of the document is spent convincing the reader that what you're trying to teach him is worth learning. Maybe that's reasonable given how many of your readers are at ages where people are known for knowing everything. ;-) For me that stuff just gets in the way. I go into a document like this with the assumption you have good reasons for taking the time to explain something, and that you have some experience and credentials. In any case, when you think it's worth explaining why something is important, just explain it. I wouldn't preface an explanation with "Why is X important?" (<-- Note: punctuation goes inside quotation marks.) - Some of it just doesn't feel helpful at all, such as Chapter 30. Nothing in the chapter is wrong, but nothing in it seemed overly helpful either. The fact that you don't know for sure if something will work well on a map until you try it is hardly a revelation worthy of four paragraphs. This lesson contains the following: "Sometimes you never know that something is going to work until you try it." "You never know exactly what is going to happen until you try something yourself." "Sometimes you never know until you try." And then there are several examples of things you can't know until you try them. Okay, I think I got the message, but I got it the first time you said it. Chapter 42 is Polish. If you're going to invest the time and effort (which you obviously have) to produce a document you're going to publish for public consumption, you should have someone edit it for grammar and writing practices. (That's how you polish written works. ;-) Now, as someone who feels inadequate as a map designer (that's why I read your lessons ;-), but as someone who has looked at a fair number of maps and has a fair bit of life experience (I'm 55), I offer the following food for thought: You talk about experimenting and trying things that are different, but you also rightly point out that it's important to understand the reasons standard practices are standard. I've looked at a fair number of maps, and a common problem with a lot of them is that they're just weird. In an effort to be distinctive and cool, the designer has gotten "creative" and created a map I can't imagine wanting to use for any type of game. If being distinctive becomes the main goal, a designer can lose sight of the real goal of creating a great map that's fun to play. For example, Grifball is a fairly popular game, and Grifball maps are about as simple as any map could be. There are no paths, no weapons on the map, and few spawn points. But it's really fun. It's a fun game facilitated by the simplest of all possible maps. I've always thought that while the rules can be broken to great effect sometimes, that's best left to people who understand them well and are experienced and talented enough to know when they can break them and get away with it. When novices break them, the results are usually disappointing, and usually end up showing why the rules are there. Different is not always better. Sometimes it's just weird or uncomfortable. My point here, in case it isn't obvious, is that people starting out in map design should start out building a good, solid, fun map or two using fairly standard practices. If you can't get the basics of traffic flow, spawning, path manipulation, immersion and so on working on a fairly simple, normal map, deviating from standard practices is only likely to add to the problems, not solve them. If your map isn't fun, putting it under water isn't going to help. In my experience it's best to give beginners (and I have to assume you're talking to beginners if you feel the need to present your audience with ten variations of "you never know until you try" ;-) pretty clear guidance and encourage people to experiment more after they've had some successes with the basics. If you teach people to walk, they'll figure out how to run on their own. It's for this reason I think your lessons would be more useful if they included more specific guidelines people could use to build good, relatively simple, straightforward maps to help them learn the principles. Once they have that conceptual knowledge under their belts they'll be better prepared to go off the beaten path. An example of something specific would be what kinds of weapons are better for what kinds of maps and game types. You mention the sniper rifle 20 times, but sniper rifles are pretty much useless in FFA Krazy King, Oddball and Headhunter. In fact, it shouldn't even be on maps for those games in my opinion because in my experience the people most likely to use it are jerks who want to camp somewhere boosting their K/D ratio instead of playing the game everyone they're killing is playing. After weapon suggestions, how densely should they be placed be on a map? Should there be weapons every ten feet so you effectively have infinite ammo, or should they be spaced out far enough that people with preferred weapons run out of ammo and can only use them for a short time? What's a good rule for deciding how many sniper rifles to put on a map? Is there a good rule of thumb for deciding when weapons should be put out in the open where they can't possibly be missed, such as in the middle of a main path, or in a more obscure location? For example, in Reach's Powerhouse map, some weapons are placed right in your path, while others, such as the rocket launcher, and even more so, the grenade launcher, are not in obvious places. Now, you can correctly say this is all up the map designer and that you don't want to limit his creativity, but guidelines don't limit creativity. Nothing you say can prevent someone from putting a fuel rod gun every ten feet on his map. But based on what I've seen, a lot of "creativity" in forged maps is really just the result of not understanding good design principles and the result is a lot of bad maps where people tried something that wasn't a good idea. Map design is an art, a form of creativity. In involves skill, but it also requires talent, and like pretty much every art form, most people won't have the necessary talent to create great maps. It's just a sad reality of life that the overwhelming majority of us will never be great composers, authors, sculptors, or game map designers. But with the proper guidance in the basics, a lot of people who can never be great can be good, or at least decent, and create maps that can be played and enjoyed. Anyway, that's just my $0.02. Or maybe $0.03. I'm not good at building maps or even a very good player, but my observations seem to apply to a lot of other areas in life and I see no reason they wouldn't apply here as well.
-
[quote][b]Posted by:[/b] CaptKrunch 96 Godly, in the game night we had, when we played Helix, I really enjoyed it. The map was looked nice, which is a plus, but the map also played well. The spawns were also well made. With a good balance of vehicle and infantry combat. The weapons balanced out the map and didn't make the vehicles impossible to kill which is a plus. My only complaint was when we played that capture the flag match on Helix. The Blue base had much more cover for people to hide and come out to take the flag. While the Red base was (where the flag was at least) kind of open and if you took the flag there waa barely any cover to go behind. And you could get easily team shot. Though maybe I'm uspet my team lost. <.< Good map though. 9.5/10[/quote] Yeah I have found a couple of issues with Helix in long term testing. Mainly that the bases are a little too easy to defend making it a little hard to pull the flag. I plan on re-designing it in the future.
-
Actually nvm, it would be better to post this after I was done. [Edited on 01.21.2011 7:42 AM PST]
-
Godly, in the game night we had, when we played Helix, I really enjoyed it. The map was looked nice, which is a plus, but the map also played well. The spawns were also well made. With a good balance of vehicle and infantry combat. The weapons balanced out the map and didn't make the vehicles impossible to kill which is a plus. My only complaint was when we played that capture the flag match on Helix. The Blue base had much more cover for people to hide and come out to take the flag. While the Red base was (where the flag was at least) kind of open and if you took the flag there waa barely any cover to go behind. And you could get easily team shot. Though maybe I'm uspet my team lost. <.< Good map though. 9.5/10 [Edited on 01.20.2011 2:47 PM PST]
-
[quote][b]Posted by:[/b] Godly_Perfection [quote][b]Posted by:[/b] KageZ Thank you. This lessons are absolutely awesome and I can't wait to actually make a halfway decent map! :)[/quote] Your quite welcome sir. I'm glad these lessons help. Remember that practice makes perfect, and you can't expect to create a masterpiece right away.[/quote] You [i]can[/i] make a masterpiece right away [i]if[/i] you put a lot of thought into it. I made a very decent drawing of glaciers the other day in class. My original idea was to make magma crashing into the glaciers like waves but I just made it simpler without the magma. It took five minutes and ten extra minutes to finish the details. Fifteen minutes in total, then.
-
[quote][b]Posted by:[/b] KageZ Thank you. This lessons are absolutely awesome and I can't wait to actually make a halfway decent map! :)[/quote] Your quite welcome sir. I'm glad these lessons help. Remember that practice makes perfect, and you can't expect to create a masterpiece right away.
-
Thank you. This lessons are absolutely awesome and I can't wait to actually make a halfway decent map! :)
-
[quote][b]Posted by:[/b] gomollypop I'm not a forger myself, but a lot of times I get random ideas for map names. I started a thread in the main Reach forum with a list of name ideas for forgers that like to build but have a harder time naming their maps. I hope it's ok for me to link it here. I thought it might be more helpful and people that are forgers might actually see it when it gets buried in an hour. [url=http://www.bungie.net/Forums/posts.aspx?postID=55465572&viewreplies=true]Map Name Ideas [/url][/quote] That list seems interesting... not sure if it will be of any help to anyone however.
-
I'm not a forger myself, but a lot of times I get random ideas for map names. I started a thread in the main Reach forum with a list of name ideas for forgers that like to build but have a harder time naming their maps. I hope it's ok for me to link it here. I thought it might be more helpful and people that are forgers might actually see it when it gets buried in an hour. [url=http://www.bungie.net/Forums/posts.aspx?postID=55465572&viewreplies=true]Map Name Ideas [/url]
-
[b]********** NEW LESSON **********[/b] Things are getting insteresting around the community folks. The community cartographers are out and hunting for great maps to put into matchmaking. They are out and about. Who could they be? ;) lol... anyways, I just posted this lesson today. Also if you hadn't noticed I posted my final version of my new map Affinity as well. Link is in the OP and it is in my fileshare. Like it, DL ed, love it, share it, tag it, recommend it, copy to your fileshare, etc. Enjoy folks! [url=http://www.reachingperfection.com/2011/01/lesson-42-polish.html]Lesson 40: Foreshadowing[/url] ------- ([url=http://www.bungie.net/Forums/posts.aspx?postID=55458320]BNet Version[/url]) * Applying polish to a map requires you to pay attention to minor details that most players don't notice * Sometimes you have to think outside the box to find how you can polish your map further * Polish doesn't refer to just aesthetics, it can refer to a lot of gameplay factors as well
-
O hai, I'm just droppin' in on this thread to say you guys write alot, and you do it alot.
