[TIP] Taking Notes

Icarus

aa
Sep 10, 2008
2,245
1,210
I don't know how many of you guys do this, but I use this method that I learned from Fishbus.

Take screenshots: for those of you having problems remembering comments

let's say you compiled your map, and are walking around finding problems and new ideas all over the place. What can you do? make a note in chat and take a screenshot!

cp_observatory_b50032.jpg

cp_observatory_b3test0011.jpg

cp_observatory_b30007.jpg


Works during gamedays, too! When somebody makes a complaint or suggestion, type it out and screenshot it! Afterwords, open your screenshot folder and have a look through. You now have a specific comment and a visual aid!

Works better than relying on people to post in threads.
 
Last edited:

Ravidge

Grand Vizier
aa
May 14, 2008
1,544
2,818
I've done the same for quite some time, except I dont write in the chat. I just need the picture and I can remember what the issue was. I can see how writing a comment would help when you're not planning to fix it right away (lika at a gameday as you mentioned).

Everyone should run around their map until they can't find any more errors themselves before releasing another version. That's the point of public testing imo, this method really works (better than just pen and paper too, issues like wierd lightmaps are hard to explain in words)
 

Kronixx

L5: Dapper Member
Apr 17, 2009
205
38
yeah building oversea i probably took near 80 pictures i'd say of crap i missed and needed to move and forgot to fix and all that stuff, it's a great tool to remember the long list of things to fix
 

Nineaxis

Quack Doctor
aa
May 19, 2008
1,767
2,820
Such a simple thing, but a great idea. Thanks for posting it.
 

Mar

Banned
Feb 12, 2009
607
63
Icarus, You and Fishbus should have a baby. You guys would then keep on creating such high quality maps that your posed to overtake Valve's granary and badlands as the top maps in TF2. In an attempt to keep control of TF2 they would hire Gordan Freeman, through G-Man to kill you both.

Your son would then go on a pilgrim and find the original coder for the source engine high on mountain with his adobe being protected by a long tunnel with radioactive waste. He would then train your son all the in's and out's of the source engine in an epic montage. They would create the perfect TF2 map that satisfies both pubbers and the most critical comp players. the soundscape of the map would be embedded with subliminal messaging. They would brain wash all the smell nerds of TF2 and in a coup, your son would take over Valve and kill Gabe Newell and Robin Walker to avenge your death and all their shitty updates.

Your son would then produce TF3 and Half Life 2: Episode 3 in one year, and Half Life 3 and Portal 2 the next, proving to the world that Valve can make games in Real time and not Valve time.

PS. That was a very good tip you had their. Thanks for spreading the love. Your cool. :cool1:

PSS. I had 13 nerd refernces in that paragraph, can YOU find them all?

PSSS. I got herpes from your spreading of love. :angry:
 
Last edited:

Ninjilla

L420: High Member
Sep 13, 2008
445
116
PPS = post post script, or the script after a post script. Makes sense.

PSS = Post script script. Sounds like a spelling mistake, right click to correct repeated word.
 

UKCS-Alias

Mann vs Machine... or... Mapper vs Meta?
aa
Sep 8, 2008
1,264
816
I usualy make screens and write down the number of the screen on paper. often i also make screens that i use to show others. And by using paper i can also simply have some notes that dont need a screen.

Screens however are indeed usefull as they say more than text.

And even better is to make a demo during map tests. Not only you can use that demo to promote the map better. you also hear/see the comments in the way they say it.

Btw, both PSS and PPS are right.
PPS = post-postscript
PSS = post-subscript