personally i don't really think the title reflects what half of the guide is even about, and secondly, it really should be re-worded to include the phrase 'in my opinion' as you come off sounding pretty condescending and as if every sentence you write is a fact, which frankly, it isn't =)
in regards to the guide not reflecting the title i do mean that in a positive way though, it has many good points for someone starting out map creating. e.g. trying to not get bogged down in creating terrain when really it's more about the mechanics and gameplay etc and i do generally agree with the point about only bringing ideas to the table. however, it does heavily depend on the situation. i think the poster above me (obliviron) has missed the point in all fairness, you are talking more about a team of like-minded _unpaid_ individuals coming together, he is talking more about a paid situation, for example, saying level design matters, he clearly hasn't seen a few of the high pop maps haha :D
to make this guide a little more rounded i would probably include:
good tips for starting out in general, team or no team!
try to start small
plan some ideas out before loading the editor
points to re-word
the rest that 'dont really count' are actually a great place to start, but once you have a basic concept, leave it at that, once you've then completed a beta version of your game through triggers and data you can come back and 'polish' the map by looking at these points, because, they do count!
too many cooks dont spoil the broth necessarily, but the more you have, the more you DO need someone purely to lead, and in general, this person doesn't need data/trigger experience. he/she just needs to be very organised, which is why i don't always agree with your big two point. i do however think it is generally true as teams start out best smaller, and grow. so initially the project leader will need some skills in triggers or data editing
commitment is almost irrelevant in terms of hours per day. everyone is different, your main commitment is to how long it takes overall. if you dont think the hours needed divided by how many hours a week works out then try something smaller or tone down the idea into something more manageable - again, this is more a point about general game making as opposed to making a team.
on a more negative note though, you really must tone down some of the stuff you say as it does just come off with you sounding like an ass. i mean the part where you compare you and your mates 'skills', it sounds like one of those cv's i sometimes get on my desk and almost die laughing at the utter bollocks people write on them to try and sound good. 'advanced' scripting, 'advanced' data editing, 10+ years experience - you really need to learn what modesty is.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
personally i don't really think the title reflects what half of the guide is even about, and secondly, it really should be re-worded to include the phrase 'in my opinion' as you come off sounding pretty condescending and as if every sentence you write is a fact, which frankly, it isn't =)
in regards to the guide not reflecting the title i do mean that in a positive way though, it has many good points for someone starting out map creating. e.g. trying to not get bogged down in creating terrain when really it's more about the mechanics and gameplay etc and i do generally agree with the point about only bringing ideas to the table. however, it does heavily depend on the situation. i think the poster above me (obliviron) has missed the point in all fairness, you are talking more about a team of like-minded _unpaid_ individuals coming together, he is talking more about a paid situation, for example, saying level design matters, he clearly hasn't seen a few of the high pop maps haha :D
to make this guide a little more rounded i would probably include:
good tips for starting out in general, team or no team!
points to re-word
on a more negative note though, you really must tone down some of the stuff you say as it does just come off with you sounding like an ass. i mean the part where you compare you and your mates 'skills', it sounds like one of those cv's i sometimes get on my desk and almost die laughing at the utter bollocks people write on them to try and sound good. 'advanced' scripting, 'advanced' data editing, 10+ years experience - you really need to learn what modesty is.