Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Well, I had a few free days so I thought I'd check up on you. I'm gone again after tonight, but I still peruse Forge daily.
If you are spawning them at the screen width, it's probably beyond the coding bounds for them to accept coding, meaning that you will need to add "make self always active" (and possibly change your off screen bounds so they don't die upon creation).
EDIT: I guess Innes just mentioned those two things too.
Well, i don't really know how to do the "change screen bounds." i put in the when created event, "make self always active." nothing changed. The clouds are now spawning on the left side of the screen instead of entering on the right side. they are also not moving.
I'm so confused man.
Create cloud at screen width + camera x + offset (if you want one) and whatever y
When created:
Always active
set x-speed to #
Always:
If x of self + width of self < cam x
kill cloud
G.G.
EDIT:
Also, if you want random spawn times:
When created:
trigger event rando
when rando happens:
set number to random # between __ and __
do after number seconds
create cloud
trigger event rando
If you are spawning them at the screen width, it's probably beyond the coding bounds for them to accept coding, meaning that you will need to add "make self always active" (and possibly change your off screen bounds so they don't die upon creation).
EDIT: I guess Innes just mentioned those two things too
You can't use a time loop in an "always" statement without using booleans or something to turn them off. They probably are overloading your system (as you are trying to make a near-infinite number of them!) Try doing it in a "when created" statement instead.
T_T Impatient again, huh? Well, if you're using the code I gave you, you already have the attacking player's info. Originator! So you just need to use:
for Originator get _PlayerID from Player Behavior or whatever they are called. Make sense?
EDIT: You can also add in an attribute for the health behavior that gets the originator from the thrown snowball and you can use that for scoring.
Sorry to say, but everyone else is at a disadvantage when it comes to helping you on this game because I have intimate knowledge of all the code that you used.
Also, i tried doing it on my own. i tried doing it by assigning a different snowball to each character. But after i did that, when i tried writing the score code, it would just add points when ball collided with the other players. Overall, it doesnt work. I just want the players to gain points when they kill a player. not hit.haha.. ^^
I'm not sure in the "if health blah blah part" XP
Then create another actor, rename as "P1snowball" or something. ^^
if self hits P1snowball(or you can also use a group)
kill last collided actor
if health = 0
set P1score + 1
haha.. I'm not sure with this, don't have stencyl so I can try. ^^
How about name your snowball for each player? So that it would be easier to know who kill who? ^^
hmm..this brings another question. ^^
How can a player kill another player?
Making score is just like the "timer" code. You're just going to add points(increment or Add). ^^
ha alrighty! This is the second post of mine you commented on. You searching for my post?! O.O
haha..not really, just browsing the "New Posts" ^^
Making score is just like the "timer" code. You're just going to add points(increment or Add). ^^
Stencyl is the easiest way to create games for mobile, web and desktop without code.
Learn More Download
© 2021 Stencyl, LLC - Terms of Use - Privacy Policy - Proudly made in California & Japan 