Spawn actor: LetterTile (at self.pos.x&y, in front of actor)

Essentially, each Redaction is a black actor. It has a unique ID. It then saves its X + Y Positions to a table.

Hey just looking for someone to make this trivia game prototype spawn each question 1 time only. $10 via PayPal for the help. Thank you.

I tried to watch some tutorials on how to spawn from tables without repeating and it seems quite convoluted since there are apparently a gazillion approaches/scenarios to spawning randomly from table

-- Save & Retrieve Unique Game Tables.

(Quote)

I mostly use the networking behaviours to allow games to track the progress of students and upload that progress to a server. A student will log in with a unique 7 digit code, which will retrieve thei

Explore Dungeon, which has changed endlessly with the power of the Cube, collect unique weapons, shoot up monster while avoiding bullets!

ah yep, i think i get where you’re coming from. it’d be very complex to get it going, and not possible using what i described, if you are using the spawn behaviour to build turrets.

I have used spawn actor as well, but if you can avoid it is better.

Make an integer attribute called game.spawnCount. Leave its value at zero.

I have an actor that spawns 1x and is then collected with playable actor. Actor spawns a 2nd time right after. After this second time I need the actor to not spawn any more and a new game level attrib

I got it working by moving the buttons on / off screen. I think its the spawn/destroy that was causing unexpected issues - the logic I think was sound, but it seems destroying actors probably caused

First, when my actor is touched, spawn the two buttons off to the side. The challenges I see are if I click on one of the two buttons, how does the button not touched get destroyed (think one button

* Unique paths every time

GS creator is very powerful and putting everything online will be troublesome for us. We do not want another construct 3 or stensyl. GS is unique in its own way.

(Quote)

One thing I can think of -- and it's not terribly efficient -- is to destroy the actor and spawn an actor with the next frame's image. And repeat as needed for the full animation. Each actor (frame) w

Next thing I'd do would be throw a display text or spawn into the timer along with the consume, and check that that timer is actually being run. Could still be lots of things though.

I'm curious why you wouldn't just show & hide or spawn and destroy each piece of the maze in a single scene though.