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.

Messages - Wifido

Pages: 1 2 3 ... 6
Thanks.  I understand how to use List/Array objects in the code and I have that all coded up.  However thanks for taking the time to provide the pseudo code.  I am just not describing the problem I want to solve effectively.

Let's say I wanted to put this behavior up on Stencyl Forge for everyone to use and have it be generic such that they would not have to add custom code to add enemies and friends to Lists inside the code.  I would want them to be able to pick from a list of Actor Types and add N number of Actor Types to the "Friends" and/or "Enemies" list. 

I want them to be able to select their enemies and friends inside the behavior's user configurable area  (The Behavior Tab of the Actor where the Behavior was added)...which only shows the "public" attributes.

Ask a Question / Re: How to not add Self to the region I created
« on: August 30, 2013, 09:14:46 pm »

Ask a Question / How to not add Self to the region I created
« on: August 30, 2013, 05:40:35 pm »
My actor creates a circular region when he is instantiated.
I have a When Actor Enters Region event for Actor Types like this actor.
And so it is adding him to his own region.

Is there a logic block for detecting if that Actor you are working with is "Self"?

Let's say I have 3 actors, A, B, and C

Each actor creates a circular region and knows when any of the other actors enter and exit that region.  He can face the first actor that is in the region...etc...

However, I want some actors to have priority...because they are enemies.

A is friends with B but C is A's enemy.  So B may be closer to A than C...but A has to look at C rather than B.

My goal is to create a behavior that I could stick on each actor and then allow each actor to set which are friends. 

I tried creating a List attribute.  This does let you add items when you attach the behavior to an actor.  However it only allows you to attach a Number or Text item.

What I really want is an Array of Actor Types that the user of the behavior can designate in the designer.  Is that possible?

Shared Resources / Re: Actor Stretch!
« on: August 23, 2013, 11:51:26 pm »

I got to the older API through the Stencyl 3.0 Help->View API menu.

It appears the B2Vec2 class was moved



HOWEVER, I have not verified that they are the same API yet...

Shared Resources / Re: Actor Stretch!
« on: August 23, 2013, 10:47:48 pm »
Hi SadiQ,

Looks good.  I am trying to port it to 3.0 to play with there.
It is complaining about the Box2DAS.Common.b2Vec2 import.
Not sure why's in the API...

Was DigiMax's example using Tweening? 

DigiMax...I tried your demo...  I saw the same problem.

I disabled the Simple Physics as the default setting of the game but left simple physics on for each actor. 

I'll dig into it more later today.  Have to do the day job thing ;-)

Game Ideas / Re: Community Projects
« on: August 06, 2013, 07:39:25 am »
You are great at drawing graphics.  That is an awesome truck image!

I often press the Test Game button but meant to press the Test Scene button and I have to pay the penalty and wait for the game to completely build when what i want to do is cancel the build immediately.

Ask a Question / Are Polygon Terrains supported for IOS in 3.0 yet?
« on: August 02, 2013, 09:48:53 am »
I see Polygon Terrain showing it was added in 2012 in the Change Update posts...

However there are a lot of 2012 posts saying it does not work.

Another post suggests that you can build your scene outside with the Polygon Terrain and then import it into the Mobile App and it *might* work. 


Hi, I know the post is old...but i am wondering if you ever solved this problem for IOS?

Suggestion Archives / Re: Can You Provide a Code Block Refactoring Tool?
« on: August 02, 2013, 09:36:34 am »
Thanks Capt.

That will certainly help.

I was adding a lot of code blocks with a lot of parameters and I kept making stupid mistakes like picking the wrong return type or having a typo in the parameter name.

Messing up the return type or parameter type was the more painful issue because i didn't find out until I was trying to code or compile.

So I just have to slow down and be more patient.  I am so used to writing C# code in Visual Studio that I've gotten a bit lazy I think.  They make it so easy to refactor little mistakes like that.

Thanks for the heads up on changing the name and description.

Ask a Question / Re: Background size versus scene size
« on: July 30, 2013, 05:24:37 pm »
Hi Rob,

You may have figured this out by now...however you can use the "Camera Follow Actor" behavior.
This will move the scene to where your actor is.  Just add this behavior to your actor.  You can find it in StencylForge.

If you put your actor in the bottom left portion of the world then the camera will follow him there and  that's where the scene will be located.

Thanks Rob.

Pages: 1 2 3 ... 6