Dude, I took the time to try and help you and give advice.
If you do not want to take it, what ever, but there is no reason to tell me "If you are not going to reply a relevant post it might not be best to post at all"
You are asking for help and you are going to treat people like that? So me taking my time, and trying to give advice on how to go about starting a project and getting used with the editor, and trying to explain that if you had a small project under your belt it would be MUCH easier to get people interested in helping you as they can see you actually are and can do something instead of all ideas and no show is not relevant to this thread, then I do not know what is.
The way you said that it seems like you feel I wasted my time posting in your thread. Again, I don't care if you don't take the advice, but don't shit on me for trying to help
- Make a very small project, and work on that first to learn the editor, what it can do, what it is capable of. Ideas are all good an all, but without experience with the editor it is extremely hard to get in depth conversation with you about they systems, and the fine details of the project.
- Great first project is just a normal map with custom units. Try making a normal map and add / change a bunch of units.
- Make a text document to go with your project. This editor has a lot of variables and it is nice to have a document you write all your stats, ideas and what not into that you can have open on the side while you work.
- Worry about terrain editing last. Figure out the system, triggers, and everything about the gameplay before making the lay outs for the levels.
- When making a project, try to get the whole project written into a document and planned out first. If you create a project and just do everything on a whim it is very easy to forget and miss stuff, or the project turns out different than what you had envisioned. This is the same with all level design. Never just go at it, always have a plan and a concept first.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Dude, I took the time to try and help you and give advice.
If you do not want to take it, what ever, but there is no reason to tell me "If you are not going to reply a relevant post it might not be best to post at all"
You are asking for help and you are going to treat people like that? So me taking my time, and trying to give advice on how to go about starting a project and getting used with the editor, and trying to explain that if you had a small project under your belt it would be MUCH easier to get people interested in helping you as they can see you actually are and can do something instead of all ideas and no show is not relevant to this thread, then I do not know what is.
The way you said that it seems like you feel I wasted my time posting in your thread. Again, I don't care if you don't take the advice, but don't shit on me for trying to help
Take this advice.
- Make a very small project, and work on that first to learn the editor, what it can do, what it is capable of. Ideas are all good an all, but without experience with the editor it is extremely hard to get in depth conversation with you about they systems, and the fine details of the project.
- Great first project is just a normal map with custom units. Try making a normal map and add / change a bunch of units.
- Make a text document to go with your project. This editor has a lot of variables and it is nice to have a document you write all your stats, ideas and what not into that you can have open on the side while you work.
- Worry about terrain editing last. Figure out the system, triggers, and everything about the gameplay before making the lay outs for the levels.
- When making a project, try to get the whole project written into a document and planned out first. If you create a project and just do everything on a whim it is very easy to forget and miss stuff, or the project turns out different than what you had envisioned. This is the same with all level design. Never just go at it, always have a plan and a concept first.