Attempted Suicide

[Freddy]

Im currently making a game and it's almost complete. I've worked all the stuff and am almost done with the code. I just need the graphics.

Its called Attempted Suicide and the point is...

well I dont wanna say yet. u'll find out soon.
I cant give a release date yet because I have a lot of homework tomorow. I'll have more time to finish it on Fri and Sat. All I can say is that it will be out soon.

[eatmorchikin6464]

Woohooo! that sounds cool. Your idea is better than vegetable chips dipped in lemonade! Wow, your idea must suck then. But, it sounds good, just my comparison to another object was bad. Ok, I'm going to shut up now. Good day to you all.

[illrainman]

Attempted Suicide is a weird title. Maybe it has something to to with killing a character in an unusual way?

And veggie chips in lemonade?

[eatmorchikin6464]

Yup, just trying to be random!

[Freddy]

my my, some one is...
..spammy.

Update:
Came up with a story... well a purpose for your actions anyway.
Completely worked out how every thing will work in the planning stage.
Have four of the 'goodies' completed.(more on goddies later in development.)

Estimated Release: 2-4 days.

[Freddy]

pardon the double post, but I need some help.

a problem occured just as Im fininshing all of the code.

I have a dynamic text box named health. I need it so that if it turns to 0, it goes to a different frame in the timeline.
but,
when I put the usual code:
if(_root.health = 0){, _root.gotoAndStop("dead");,}
wierd stuff happens.
for some reason it automaticaly goes to frame("dead") with out health reaching 0.

wtf?

[arkhan]

just..

if(_root.health <= 0){
_root.gotoAndStop("dead");
}

you were actually seting health to 0 with the
health = 0
to test if health is equal 0 you gotta use double =
health == 0
or if health is 0 or below
health <= 0

[The Brown Cow]

Right.

health = 0 will set health's value to zero. Then the if statement looks at it and resolves it to true, so it goes ahead and runs the code, sending it to the dead frame. Not good.

So, as arkhan says, use the double equals (==) to test.

[MercuryLime]

I never understood why that was needed; Couldn't Flash just detect if it was an if statement?

[Liokae]

... because that would leave you with the inability to manufacture your program in certain ways that can be occasionaly useful.

[Freddy]

WOO HOO!

It worked. That was my only problem too(funny how it was so wasy to fix).

expect a small demo soon. maybe even today(dont get your hopes up) or tomorow.

[Fiz]

You've caught my interest...now I wait... ;)

[arkhan]

its usually somenthing as easy as that, if the logic is correct of course...

[Freddy]

wad 'up pimps,

here's that demo.

[flash width=550 height=400 loop=true:91196cf8e0]http://atlas.walagata.com/w/stalkerstudios/AttemptedSuicide_demo.swf[/flash:91196cf8e0]

the final version will have:
4 more ways to torture yourslef
more and better sounds
more art done(much more, this is nothing)
animations to the tortures
a whole new mode
and who knows what else...(I do :b)

[MercuryLime]

Pretty good... It get boring quick though.

[Freddy]

well mayby not when I put in the new mode.

[The_Fuzz]

Sweet, i got dat bike

[Bodadem]

Yes, me too! I solved this game mathematically!

One way to solve below (note, if you want to try to do this yourself first, just don't read it.)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
_______________________
|3x bleach, 2x shoot, 4x poke | <-- Spoiler.
| _____________________ |

[Mystic Gunman]

Pixx RPG has a lot of errors in it.

[Nexus]

I never understood why that was needed; Couldn't Flash just detect if it was an if statement?

This setup allows you to save yourself some time in certain instances.

Say for example you wanted to create a random number between 0 and 1, and output a result based on that. Rather than doing the conventional method of...

rNum = random(2);
if (rNum == 1) {
trace("You win!");
} else {
trace("You lose!");
}
trace(rNum);

You could do this...

if (rNum=random(2)) {
trace("You win!");
} else {
trace("You lose!");
}
trace(rNum);

This is because an assignment operation always returns the value on the right side of the assignment. So in this case if random() returned 1, the if statement would evaluate to true since 1 is the same as true. Meanwhile, if 0 was produced the if statement would evaluate to false since 0 is the same as false.

The difference is trivial, I know, but in the end it makes for a better language. True and false are simply defined constants, or read-only global variables if you want to get really technical.

trace(Number(true));
trace(Number(false));
//or
trace(int(true))
trace(int(false))

Since they are constants, they can also be used in expressions...
trace(10+true); //11
trace(10+false); //10

That's my really drawn out explanation. :)

[Bodadem]

Mystic, are you aware how irrelevent that is?

[denacioust]

I finished it, its pretty easy

[Freddy]

what are u guys screwing in my thread for?

this is attempted suicide only.

[The Brown Cow]

Hey, Flash knowledge was imparted by Nexus. Don't complain. :)

[Bodadem]

Crawl under your toenail and stop whining.

[The Brown Cow]

Crawl under your toenail and stop whining.

Hey, that's harsh.


Any progress, shadow?

(ahem, no grammar errors made. Nope)

[Bodadem]

Anything grammar, TBC? (You posted one minute after me. Very cool.)

[Freddy]

yeppers. The only thing thats taking forever is the animations.
and the fact that I only get about 2 hours on the comp a day.

balancing internet and flashwork is dificult.
I often times just pick one of them and stick with it for the day.

[Bodadem]

Only two hours? That's gotta suck big.