logic to create a constant shoot [SOLVED]

[blackant]

hi,

I'm trying to Make a constant shoot by olding the space bar
but i don't see what i must use  to keep this key used

as anyone could help me ?

[jonathangersam]

Hi,
You may want to try the following below. Suppose you would be shooting a laser beam that starts by pressing space, and ends when releasing the space bar:


Setup:

State 1: "Idle" (This is the start state)
State 2: "Shoot Laser"
Event 1: "Start Shooting"
Event 2: "Stop Shooting"


Graph Logic:
State 1: "Idle"
  Action 1: Get Key Down
    Key: Space
    Send Event: "Start Shooting"
  Transition: "Start Shooting" -> State 2


State 2: "Shoot Laser"
  Action 1: <do your shooting logic here>
  Action 2: Get Key Up
    Key: Space
    Send Event: "Stop Shooting"
  Transition: "Stop Shooting" -> State 1




Hope this helps,

[Red]

Good call Jonathangersam.

Another approach could be a cycling loop system (with a wait or next frame event to prevent an infinite loop warning)

I've got a system set up like this for a shooter system. i have a monitor fsm (yes, i like monitor fsms. ) monitoring the button i want to map to the firing mechanism.

then another fsm has a state (idle) that has a get fsm bool that'll fetch the boolean value of the button pressed (set to every frame since it will sometimes sit in this state.)

once there, if it registers the boolean as being changed (by using a bool test set to always on) then it goes to the "shoot" state (where i tell it what to shoot, how fast, the usual bullet/projectile systems.) once that's done, it'll cycle back (i use a single state with a wait for .01 seconds real time since the next frame event action can produce variable times dependant on the computer running the game) and once it loops back to the idle state, the button still being pressed will still result in it being triggered so it'll loop through the shoot system.

this is more for a "bullet" kind of mechanism though so it might be different if you're looking for a "beam" kind of mechanism. if you wanted a "beam" system, i'd probably set it up with a collider and an "on/off" sort of setup in that to toggle when it's on and off and what to do from there.... or maybe a raycasting system... though since raycasts can become expensive for the CPU i do try and limit how often raycasts are performed to free up CPU power... but, maybe a raycast would be more ideal for a beam weapon... dunno... you know the phrase, there's more than one way to skin a cat? (i know, it's barbaric... but it gets the point across.)

[hide]

I have the same problem, i can't make my player to shoot continuously like in most shmup. If I put an event for shooting my player will stop moving during it.

Here's what i have :

And in the shoot laser event there's a simple create object(missile).

This way i can shoot each time the Fire1 button is pressed but not continuously :/

Any help ?

[blackant]

thanks for answers,

@Jonathangersam: i did this way but i use create object as bullet and it only create one and stop.

@Red: i tested something like that too but not worked.
will try it more following your description.

[blackant]

I have the same problem, i can't make my player to shoot continuously like in most shmup. If I put an event for shooting my player will stop moving during it.

Here's what i have :

And in the shoot laser event there's a simple create object(missile).


This way i can shoot each time the Fire1 button is pressed but not continuously :/

Any help ?

you should separate your actions on differents fsm:
fsm 1 move
fsm 2 shoot
etc...

[hide]

Thanks blackant i will try this.

[Lane]

An FSM can only be in one state at any given time, so you have to decide to make it shoot or move. If you want the player to be able to do BOTH at the same time then you need two FSM's.

One for Shooting, the other for Moving - like mentioned above.

If you want continuous shooting then setup a Fire state and do all your projectile creating or whatever in there, also use a Get Key Up event to see if the player has released the fire button in conjunction with a Wait event to define the time between shots which just loops back in a circle into itself. You make a loop between two states for "firing" with the exit condition being when the player releases the button.

If this is a separate FSM from your Moving FSM then it will be independent and you can do both at the same time.

[blackant]

thanks lane. i solved by adding a wait action beetween two create object action.