deth123 you need to do a check to make sure that touch 0 was on the object.

On start of layout:

For(start=0, end=100)

System->CreateObject->StarSprite (x=random(0,LayoutWidth), y=random(0, LayoutHeight), layer=random(0,2))

Start the animation using the object touched event, not the is touching. And use the on touch end to finish, not the 'x is touching'

if the numbers and letters are always separated by a '-', then that expression will always get the second part.

Taking the 123456-Name example, the 'Name' can be extracted using "tokenat('123456-Name', 1, '-')"

If you are making a game where the object has a built in behaviour, there should be a behaviour event which would suit the case better

Or you could use the on touch end functions.

If you have representations of the keys in game you can use a system like:

Not a problem

Check this out:

Please see this capx for a demonstration using a tilemap.

https://dl.dropboxusercontent.com/u/706 ... ample.capx

I'm also having the same problem.

Ashley Tilemap setting to draw tilemap outside of viewport?

Something like this?

Sending your gender:

Here when a peer connects, it first checks if the connecting peer is itself, then it sends a message to peer "", which defaults to the host, with the content of their gender id under the tag of genderMessage.

Then, the event is called when the host receives the message, it picks the instance of the player sprite which is linked to the peer, then broadcasts the same message to all clients. After that it assigns the gender variable to the peers sprite. (This is where you'll have to make it do something).

Finally, when the hosts broadcast reaches another peer, it checks whether the peer was the original sender and stops if it is (The original sender already knows their gender). Then for everyone else, sets the instance variable of that sprite to the gender of the original.

Getting everyone else's gender:

When a peer connects, the host must give it all the other connected peers' gender. The host loops through every instance of the player sprite and sends a message to the client for each player in the form "PlayerID:PlayerGender" (You could lower bandwidth by creating one string with two separators such as "Player1ID:Player1Gender,Player2ID:Player2Gender,..." but that would require a little more work on the event sheet), with the message tag "hGenderMessage".

When the connecting peer receives one of these messages, it picks the instance of the player sprite which has the ID given in the message, obtained using the tokenat expression. Then it sets the gender of that sprite with the value of the message using the same tokenat expression, just changing the index.