"The current method is not called by any events..."

[x2495iiii]

I get what you mean, and I agree it's kind of annoying, but it such a simple fix I never really thought much of it. In fact, one of the first things I used to do when I started a world was delete the pre-made start event. I didn't always want one, so I figured it was better to delete it immediately and re-make it if I needed it.

[Funnybone]

Dude, you just repeated a portion of what I just said. *sigh.* Every time, this always happens to me. Why me?

[x2495iiii]

You seem to take a lot of simple, innocuous things personally.

My post had nothing to do with you, just the original question and how I dealt with it in the past.

You really should calm down and stop being so defensive.

[Funnybone]

And since when were GIFs not allowed here? Jeez, you banned me from using them, but everybody else can?

It's not like that's hypocritical or anything.

[x2495iiii]

If they're disruptive and off-topic, I can remove them.

This isn't the lounge.

[Funnybone]

Now you're just thinking I'm stupid.

Let's take this somewhere else or just burn it so we can end it.

[fourbros]

Hey Funnybone, who's that in your avatar? I was wondering if you're just posting in a particular style because you're trying to emulate that particular character.

[RavenOfCode]

Originally Posted by DensetsuNoKaboom

I'm gonna try explaining this again, since I don't think I was clear enough at first.

When you play an Alice world, if the method you're currently editing isn't called by any other methods or events, Alice gives a warning telling you that this method isn't going to be used at all in the world.

However, in the example world, Alice gives this warning when "world.my first method" is the currently opened method, even though there is an event which calls the method. That's not supposed to happen.

Again, it's not a very important bug at all. You can work around it just by making sure to close the methods before playing the world. However, having to close the method or click through the warning every time you play the world gets a little annoying.

Yep... I get that error... Kinda annoying... but a simple fix...

[MrMoke]

Hey! Lighten Up!
At the risk of repeating myself, and in defense of FBone, when you click Play you are running a world, not an object.

In the attached program you can open all of the separate "my first method" methods for each object in the editing pane, select any one you wish, and play the World with no errors.

Notes:
1) The World event references all "my first methods".
2) The "world.my first method" contains no actual code.
3) The print statements in the Object.my first methods are executed twice indicating that the object-based events are unnecessary, and can be removed.

[Funnybone]

Originally Posted by MrMoke

Hey! Lighten Up!
At the risk of repeating myself, and in defense of FBone, when you click Play you are running a world, not an object.

In the attached program you can open all of the separate "my first method" methods for each object in the editing pane, select any one you wish, and play the World with no errors.

Notes:
1) The World event references all "my first methods".
2) The "world.my first method" contains no actual code.
3) The print statements in the Object.my first methods are executed twice indicating that the object-based events are unnecessary, and can be removed.

This is a good example. For once

But sometimes it has to do with the "world.myfirstmethod" method, so if no other methods are considered useable, just use "world.myfirstmethod"