02-26-2009, 04:58 PM
Recently, this forum has been flooded by elementary DCing problems. They're so easy that a link to the mainsite is enough. To be honest, I get sick of these idiotic askers. If you feel offended now, that's your problem, I didn't say your name. I'd just be pleased as punch if everybody could think BEFORE asking, it'd reduce the amount of redundant questions a lot. kthx.
Now, back to topic. You need an approach of how you can solve a problem. For unknown reasons, I'll just tell you how I do it (in case it is a harder problem). What you need:
# knowledge about DCing (duh!)
# pen and paper
# a comp to test your method out
First step: get off the computer. You don't need a comp to get the solution set up.
Second step: illustrate what your solution requires. Take advantage of these questions: How is the situation set up? What's the end result supposed to be? And most important: how do you get from the set up to the result? Many ways are possible.
Third step: Think of your way. Don't even try to express it in DCing-terms. Pseudo-code is something awesome. Write down your thinking steps. Think about it once again. Is your logic flawless?
Fourth step: After you got down your way of approaching the problem, it's time to think about the DCing matter. Imagine if you can realize these problems. Programmer's "if" can be realized with timers, itr/k: 8, or even mp. Think about it until you know THAT it is possible.
Fifth step: Now it is time to write down the code. The ultra-important steps are usually somewhere written down, the other parts are easy to imagine then. Depending on how much knowledge you have, you can omit more and more steps as they seem pretty obvious to you.
Sixth step: Smash the code into your computer. Actually, you just need to follow the guidelines you made in the previous steps and add a few things (for example a neat itr or something similar).
Seventh step: Testing. It's common that it won't work at the beginning. Is it a reason to desperate? No. Try to find the "corrupt" frame, think about your logic another time. Bug fixing etc.
Eighth step: Rejoice that the thingy is working, or, alternatively ask in the forum why it's not working.
That's it. Hopefully you'll follow these steps, especially if you're asking a lot without ever seeing a pattern in the solutions. Again, if you feel to be meant, that's your thing, I didn't say your name. And now stop asking dumb questions. kthxbye
Now, back to topic. You need an approach of how you can solve a problem. For unknown reasons, I'll just tell you how I do it (in case it is a harder problem). What you need:
# knowledge about DCing (duh!)
# pen and paper
# a comp to test your method out
First step: get off the computer. You don't need a comp to get the solution set up.
Second step: illustrate what your solution requires. Take advantage of these questions: How is the situation set up? What's the end result supposed to be? And most important: how do you get from the set up to the result? Many ways are possible.
Third step: Think of your way. Don't even try to express it in DCing-terms. Pseudo-code is something awesome. Write down your thinking steps. Think about it once again. Is your logic flawless?
Fourth step: After you got down your way of approaching the problem, it's time to think about the DCing matter. Imagine if you can realize these problems. Programmer's "if" can be realized with timers, itr/k: 8, or even mp. Think about it until you know THAT it is possible.
Fifth step: Now it is time to write down the code. The ultra-important steps are usually somewhere written down, the other parts are easy to imagine then. Depending on how much knowledge you have, you can omit more and more steps as they seem pretty obvious to you.
Sixth step: Smash the code into your computer. Actually, you just need to follow the guidelines you made in the previous steps and add a few things (for example a neat itr or something similar).
Seventh step: Testing. It's common that it won't work at the beginning. Is it a reason to desperate? No. Try to find the "corrupt" frame, think about your logic another time. Bug fixing etc.
Eighth step: Rejoice that the thingy is working, or, alternatively ask in the forum why it's not working.
That's it. Hopefully you'll follow these steps, especially if you're asking a lot without ever seeing a pattern in the solutions. Again, if you feel to be meant, that's your thing, I didn't say your name. And now stop asking dumb questions. kthxbye
Silverthorn / Blue Phoenix
~ Breaking LFE since 2008 ~
"Freeze, you're under vrest!" - Mark, probably.
» Gallery | » Sprites | » DeviantArt
~ Breaking LFE since 2008 ~
"Freeze, you're under vrest!" - Mark, probably.
» Gallery | » Sprites | » DeviantArt