First off, to Areibman: I noticed the same difference in my Stencil, but as I downloaded mine yesterday i think this might be an update where they have tried to simplify the program a little and also have renamed some buttons. Rest assured that I have completed both tutorial 1 and 2 without problems, so the program works and the tutorial is still valid, you just have to figure out some of the new names for things.
For Abigayl: I tried to make it so that my character died when leaving the screen, resulting in the same "Fade-out-reset-fade-out"process. This I did by giving him a trait that killed him when leaving the screen, and one that made the game fade when he died. However - this only works when he leaves the top of the screen, all other edges simply makes him disappear without coming back. Any tips? In advance, thanks for taking the time to help out with a problem that must seem ridiculously simply to you.
That's a common question, one that is answered in this tutorial set, part 5, and to a degree, set 2, part 2 (that one only covers the bottom, but you can adjust to to be in all directions). The basic idea is to check in "always" to see "if [x of self] < 0 OR [x of self - width of self] > [screen width] OR [y of self] < 0 OR [y of self - height of self] > [screen height]" (then do your coding, either killing self or pushing self back on to the screen). To make it work, in "when created" set self "make self always active" to make it still take in coding when beyond the screen. Hope that helps. :)
Also, I had never heard of the Stencyl program before, neither do I have any experience what so EVER with programming of any kind.
I browsed through your tutorial here and though to myself: "Shit, this person made me understand everything here without even having the software of my own to try it on." In other words, I just downloaded Stencyl. First tutorial on anything I have ever seen that makes it so understandable for us newbies. I mean - I'm just really impressed. You just gave me something do to in my rainy, Norwegian holidays. 6/5.
As far as I can see, this AbiGayl person appears to be one of the nicest persons out there. I mean, talk about contributing to helping people out! free tutorials for the programming program (I know, I know, sounds weird) and answers everybody who has a problem in the comments! There has to be a stake here - oh wait. He has a stream. He just wants people to become his viewers for money.
Oh, nevermind, all stream income goes to charity. Best internet person ever achievement unlocked, AbiGayl.
Two problems with what you said: 1. my stream is free (both to me and to viewers, I don't get any revenue from it (nor do I pay the insane amounts for my over-use of saved videos)), 2. I am a she, not a he. Besides that, you're pretty accurate, thanks :).
I like turtles because they're so chill. They don't hurt anyone. They're just like " Hey man, I want to swim, and maybe eat some lettuce. But I'm gonna take my time getting there, I'm in no rush. Because.....I'm a turtle."
@donbomb:
yes. the max AP increases as the character get experience. so does all of the skills, some more than other, based on the character. therefore, keeping your characters alive will sum up, and every character can become a little superhero even though you hired then for 200 $.
the story is correct, and i like that. to supply: the Normans were descendants of an earlier viking huscarl who got exciled, and the vikings did exist in sweden and denmark as well - but it was the norwegean ones who took England. for instance, the town York was actually named Jorvik by the vikings. and the king's name was Harald Hardråde, but i'm sure you couldn't get that in English.
could need a progress counter for the achievements, maybe? like a "sharpshooter - awarded when birdie hits 90 times with laser. current progress: x/90."
one button bob is epic stuff. i kinda feel my lifestory in this game. anyways, walkthrough: when you come to the gap, click. how to beat the bat: click. the spikes can be dogded by clicking. press the + to let other get this important help.
That's a common question, one that is answered in this tutorial set, part 5, and to a degree, set 2, part 2 (that one only covers the bottom, but you can adjust to to be in all directions). The basic idea is to check in "always" to see "if [x of self] < 0 OR [x of self - width of self] > [screen width] OR [y of self] < 0 OR [y of self - height of self] > [screen height]" (then do your coding, either killing self or pushing self back on to the screen). To make it work, in "when created" set self "make self always active" to make it still take in coding when beyond the screen. Hope that helps. :)