How do YOU program?

The reason for this random poll will all come clear soon

if u vote please say what u voted for

Since you asked, I nearly always create my own behaviors, it's pretty rare for me to use something pre-made (even as great as they are, I'm usually doing something odd and experimental anyway).

How do u create a wall sliding behavior from scratch

How do u create a wall sliding behavior from scratch

Since you've already got a thread specific to that request, just check there for my response.

I wouldnt be averse to seeing how other people codes things, but ultimately i like to make my own code. It's the only way I truly learn and it gives you a level of confidence that encourages you going forwards.

Gruffman, plus I like to be able to troubleshoot my own code. It's always harder looking at something that someone else has done and trying to figure out what went wrong.

totally correct hectate..  same goes for me.. anyway if you know the answer to my thread please answer it.. i have wait for days and set up 2 threads about testing ios locally but still no progress.

totally correct hectate..  same goes for me.. anyway if you know the answer to my thread please answer it.. i have wait for days and set up 2 threads about testing ios locally but still no progress.

Sorry, I continually check all new threads but I have to skip over iOS specific problems because I don't develop for them. Good luck!

I have had a thing for "build from the ground up". I have made two games in Python using the Pygame library, essentially doing all other coding outside of the library myself.

On the other hand, that's part of why I gave Stencyl a try. Perhaps needless to say, starting from complete nothing makes for a long road; my two Python games were nothing overly huge. The interface of Stencyl and how it handles a lot of physics calculations (or housekeeping, if you will) for you really helps. Like any software, you have to play by the rules it sets up, but that's all part of manipulating the software's framework to work for you.

For my first game in Stencyl, I wanted to start simple and build. I used a lot of pre-shipped platformer behaviors and then proceeded to go on from there with my own code. I even modified some of the pre-shipped behaviors to better suit my needs.

It's nice to start from scratch and handle all the details youself. I like that. But sometimes ask yourself, "Do I really need to reinvent the wheel yet again?". It all depends on how crazy and complex you're getting with your game, no?

So yeah, I do a lot of coding myself, but I am not against using other people's code.

Ha, since the option was there, I chose "I MADE the stuff in the behavior library"
(but I was not the only one working on them)

I like to do stuff myself, but agree reinvent the wheel is not a good thing. If there is something tested and bug-free out there that does what you need, why waste time doing it again? Although this is is more important when you want to get something done and released. If you are just learning, doing everything from scratch is a good way.

The way I see the behavior library, it is good to get started and especially good to make quick prototypes. In the later stages of game development I guess you would always have to tweak the behaviors or make your own to make sure everything works the way you want.

'Occasionally I use stuff from the Stencyl Behavior, but I mostly program myself.' 

Ah, so CC, you're the other one. Only lately have I publicized more of my work in the Forge though (not quite the library, but it's the closest answer )

As a new stencyler I use current behaviors, learn what makes them do what they do, then make my own using the cut and paste technique of various parts of those other behaviors, then the behavior after that I generally make it on my own. Thats how its progressing at least.

Once I know how to do it i'll just do it myself. If there were easier to use premade behaviors I would probably use more of them. But as of now about 80% of my current game is original design.