If you use 'pin'. You have to pin it in an action. A specific instance to another specific instance.

With 1 boat you just do it in the 'on start of layout.

But i suppose you will have more boats. Then you have to do it on creation. Preferable combined with the use of containers.

Logic:

Create the boat. (when using a container it will auto create the turret)

Place the turret (it will be automaticaly in a picked state, so no additional picking needed)

Pin the turret to the boat. (due the container the right boat and the right turret wil be picked)

Ah !

ty

Okay, if its not 'that' what should the camera-movement that you have in mind look like ?

Ofcours you need an example once in a while.

When you say thinks like: 4- when you set a sprite variable in layout 1 you can not access to that in other layout

Then i just have to prove you wrong.

https://drive.google.com/open?id=0B1SSu ... kFtbWtzeHM

Still dont want help ?

mahdi71 (better adres you, else GamesCorpStudio shoots at me)

About your point 2-sheets. Yes you have to pick them. But picking one, combined with the use of a container is so easy.

https://drive.google.com/open?id=0B1SSu ... XlJV2V5akU

— is said "I did't. Why ? Lets talk."

Dont sound to me like i have a problem. Assuming that is English, maybe it should be "i did not".

Sound to me as an invitation to talk about concrete solutions to concrete problems. To get arround one thing involved the 9patch?

Yeah i know you cant set imagepoints on it. Yet. It is a nice object to scale backgrounds behind a simple ui.

And thank you cinserely for that compliment. (calling it perfect) Very appreciated.

About point1, the ui.

I wonderd if would build some ui from start, would i encouter the same problems ....

https://drive.google.com/open?id=0B1SSu ... HNZWUtXSjg

I did't. Why ? Lets talk.

I dont know the cordova plugin. But if it works as all read/write plugins do, then time is your problem.

'on start of layout' runs its actions just once. After it ran once, it keeps its actions and sub conditions out of the following ticks.

So, first of, that 'trigger once while true' (unless its embeddded in a loop) has no meaning. After one time working, it will not see one tick again.

Secondly. I suppose the 'cordova-plugin-game___login, tag "log"' will log in the user. When you tested this at home, it probaly took almost no time to complete. So the 'c-p-g is logged in' got triggerd in time and picked it up. But this does take time. Also 'get user image' takes time.

Every time you use a 'store' or 'read' condition. That reading and storing will take time. Thats why they all have a 'on completed' or a 'on succes' condition. But if you keep those in the 'on start of layout' they will not be checked in the following ticks.

Just bring them out of the 'on start of layout'. Make them root events. Then they check every tick if there is a succes story to tell. And if so, they run there actions.

Make an instance variable on that armor. Subtract from it when it gets hit.

I see you teach.

How about an article on students who ask the forum to make theire project, to meet the deadline ?

I have question, if that is ok.

I read 'fps style'. fp.. stands for first person ....

Meaning the camera should (since its 2D) be on the players position and look in the direction that the player is looking ?

Because the tower is probaly 'unreferenced'.

https://www.scirra.com/manual/75/how-events-work

Functions start picking from scratch. Meaning, the tower is not picked. When no tower is picked, the actions run on all towers.

2 solutions.

1/ If the tower has a turret behaviour, then use the 'on shoot' trigger. It is meant for this.

2/ More generaly. If you picked an object and want to call a function with actions that work for that object. Then add the expression object.UID as a parameter to the function call. And in the 'on function' you use the condition 'pick by UID' with UID= object.function.param(n).