ok
the trank script is complete and i have a map
what im doing now is just making it look nice and remaking the terrain and all that stuff
i hope this is a good map!!!!!!
Soon i know, but i wana help out with the new project-Oxygen
-
Kentho Birne
- Rank 7
- Posts: 2315
- Joined: Sat Dec 06, 2003 9:10 pm
- Steam ID: mspencer86
- Location: DC area
-
Kentho Birne
- Rank 7
- Posts: 2315
- Joined: Sat Dec 06, 2003 9:10 pm
- Steam ID: mspencer86
- Location: DC area
Woo! Happy bday dude!Oxygen wrote:the map is on its way, honest
but its my birthday13, thats why i put just about 13 in my thingy incase u think i lied
The reason a dog has so many friends is that he wags his tail instead of his tongue.beni wrote:Hey, as they say, there's no place like 127.0.0.1!
-Anonymous
ok
relising the great want by some clans for the map and the fact i cant be arsed with this buggy junk anymore, im just gona round it off now and finish it with some old techniques rather than replacing the whole terrain, its a nightmare because of the way my m8 entar did the terrain into the buildings, meaning i have to get it exatcly right or its ruined and worthless
ill get it done
relising the great want by some clans for the map and the fact i cant be arsed with this buggy junk anymore, im just gona round it off now and finish it with some old techniques rather than replacing the whole terrain, its a nightmare because of the way my m8 entar did the terrain into the buildings, meaning i have to get it exatcly right or its ruined and worthless
ill get it done-
Java
- Rank 11
- Posts: 9046
- Joined: Thu Dec 26, 2002 7:53 pm
- Steam ID: java_lang
- Location: Newport News, Virginia
- Contact:
Graham, you are learning a lot of what I learned early on in mapping. As frustrating as it sounds, it's usually a good idea to just drop a project instead of trying to go back and "fix" everything.
You are continuing to get better as a mapper while you are working on such large projects as maps, by the time you near completion of one, the majority of work you started doing is absolete in comparison to your new skills.
I'd have to say my first two projects are laughably ridiculous compared to what everyone expects from me nowadays. Live and learn. But again, sometimes it's best just to start over dropping the old project.
You are continuing to get better as a mapper while you are working on such large projects as maps, by the time you near completion of one, the majority of work you started doing is absolete in comparison to your new skills.
I'd have to say my first two projects are laughably ridiculous compared to what everyone expects from me nowadays. Live and learn. But again, sometimes it's best just to start over dropping the old project.
-
Nordic
- Rank 9
- Posts: 5046
- Joined: Fri Dec 27, 2002 2:44 pm
- Steam ID: linus.lang
- Location: Stockholm, Sweden
"Kill you darlings" as they say in Hollwood.
I know, when I go back to maintain 2-3 year old (or even older) programs I've written I sometimes just redo them from scratch since it's just crap. (The alternative is to adapt to the crap and continue to write crappy code which I refuse. I have SOME pride man!)
Often there are some parts that you don't grasp at 100% and you get it done mainly from trial and error techniques. Then you understand how it really works and work out a method that suits you and gets the job done in the right way. After reaching that point you don't want to go back and do it "the old" way because it's a lot of work and it makes you embarrased and frustrated.
I would suggest that you create a small map with all the typical elements that you use in a map and structure your code so you clearly can see what part do what. It will work as a refference library. When you need someting you're not sure how you did it, just look at the ref map and pick what you need.
I don't have a ref program exactly but I have a few programs that I know do all the unusual stuff I sometimes need. Instead of inventing it again, I copy it from the program I know work.
Cut & Paste, my two best friends!
I know, when I go back to maintain 2-3 year old (or even older) programs I've written I sometimes just redo them from scratch since it's just crap. (The alternative is to adapt to the crap and continue to write crappy code which I refuse. I have SOME pride man!)
Often there are some parts that you don't grasp at 100% and you get it done mainly from trial and error techniques. Then you understand how it really works and work out a method that suits you and gets the job done in the right way. After reaching that point you don't want to go back and do it "the old" way because it's a lot of work and it makes you embarrased and frustrated.
I would suggest that you create a small map with all the typical elements that you use in a map and structure your code so you clearly can see what part do what. It will work as a refference library. When you need someting you're not sure how you did it, just look at the ref map and pick what you need.
I don't have a ref program exactly but I have a few programs that I know do all the unusual stuff I sometimes need. Instead of inventing it again, I copy it from the program I know work.
Cut & Paste, my two best friends!
Never interrupt your enemy when he is making a mistake.
Napoleon Bonaparte
Napoleon Bonaparte