How to make a cannon only spawn 1 actor per scene

whycaliwhycali Member, PRO Posts: 87
edited June 2012 in Working with GS (Mac)
I am currently building and app with a cannon that shoots actors at another actor. the problem that i am having is i only want the cannon to shoot 1 actor (bullet) and after it is shot if you dont kill the main actor i want it to be game over. One shot one kill type idea.

Thanks for your help in advanced

Best Answer

  • whycaliwhycali Posts: 87
    Accepted Answer
    @gyroscope

    My bad i miss read a part that you had written. I just wanted to let you know that it worked perfectly and thank you for your time on a Saturday to answer my question.

Answers

  • gyroscopegyroscope I am here.Member, Sous Chef, PRO Posts: 6,598

    Hi @whycali

    That straightforward enough: make a scene boolean attribute and called it ShotDone.

    So in your existing cannon rules for firing the shot, add a Rule:

    When ShotDone is false
    ---then your firing shot rules
    change attribute ShotDone to true

    -------------

    I'm sure you know that games need to have - ideally - that "can't put it down" factor; I'm wondering how many users of your final game will have the patience to keep going, when the complete game is over if the shot misses.... just a thought worth thinking about...

    ""You are in a maze of twisty passages, all alike." - Zork        temp domain http://spidergriffin.wix.com/alphaghostapps

  • whycaliwhycali Member, PRO Posts: 87

    Hi @whycali

    That straightforward enough: make a scene boolean attribute and called it ShotDone.

    So in your existing cannon rules for firing the shot, add a Rule:

    When ShotDone is false
    ---then your firing shot rules
    change attribute ShotDone to true

    -------------

    I'm sure you know that games need to have - ideally - that "can't put it down" factor; I'm wondering how many users of your final game will have the patience to keep going, when the complete game is over if the shot misses.... just a thought worth thinking about...
    I think i might be doing something wrong. I kinda understand what you have put but when i go to implement it i cant seem to make it work. by any chance can you show me a visual or screen shot maybe.

    Thanks for all your help

    Oh and i know what you mean with the "cant put it down" Factor. Oh trust me when this is completed it will have just that haha. Thanks again.
  • tenrdrmertenrdrmer Member, Sous Chef, Senior Sous-Chef Posts: 9,934
    @whycali This is a perfect example of why you should not be rejecting answers when you simply don't understand them. You have rejected the correct answer and in the future a user could browse through and completely dismiss the possibility @gyroscope answer could work because you rejected a perfectly good answer.

    Bottom Line. Don't reject things unless they are spam or absolutely completely 100% worthless to your thread.
  • whycaliwhycali Member, PRO Posts: 87
    @whycali This is a perfect example of why you should not be rejecting answers when you simply don't understand them. You have rejected the correct answer and in the future a user could browse through and completely dismiss the possibility @gyroscope answer could work because you rejected a perfectly good answer.

    Bottom Line. Don't reject things unless they are spam or absolutely completely 100% worthless to your thread.
    It was a simple mistake no need to light me up over it.
Sign In or Register to comment.