Announcement

Collapse
No announcement yet.

Mode Change event code!??????

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Mode Change event code!??????

    I just started making a game (my signature says why) and I made my city and my feild but when I testplay my game. A message pops up and says thie...

    An autorun event is cought in a loop. Please use a mode-change event code, ect to cancle the loop.

    What does that mean, I don't know how to fix it.

    Please help me of direct me a a thread with the answer.

    #2
    Re: Mode Change event code!??????

    Well I'm kinda new to the game to but it sounds like one of your events just keeps happening over and over so what you do is go to the charecter object whatever has the looping event (by going to layout and clicking on the object)
    from there go to the event page click on the + sign (this add's a new mode) the go to the event code page (blue button at the bottom of that screen doesn't matter if it's day or night) Then make the event you want to happen. After it is made make a new part to the event code list make it under "property control" then go to "modify mode" make it change from mode 1 (the currently edited mode) to mode 2 (the newly made mode) save. Then back at the charecter edit screen you can edit the new mode from there. Alsoif you want the object to do the same thing during the day/night asyou edited in the night/day section go to the opposite daytime as you edited the click on "copy data."


    Sorry this might be a bit confusing I'm pretty new to the game too but i hope this solves your problem
    Last edited by Zero Down; 07-05-2006, 01:53 PM.

    Comment


      #3
      Re: Mode Change event code!??????

      Here's a sample event.

      http://www.pavilionboards.com/forum/...ead.php?t=6826
      " I am the way, the truth, and the life. No one comes to the Father but by me. " - Jesus

      Comment


        #4
        Re: Mode Change event code!??????

        Two things cause what you are talking about.

        A) An event set to automatically happen (There's a field on page one of the event editor for changing the activation conditions, I also think the default for this field is auto) without either a add/subtract/modify mode event code in its script (You can find these codes in the property control code list) or the event transition code (Found in the control code list). An event set to activate automatically will continue to loop indefinitely.

        B) When the system detects 20 event transitions in a row (Unless if this is a really complex game you will most likely never have to contend with this).

        Zero Down's instructions are a good solution, but a little convoluted so I'll try to put them a little easier to read.

        1) Enter the event editor for the event in question.
        2) Go to page 2 of the editor.
        3) move the cursor to the "add mode" button (The plus sign) and press X. Select to add a new mode.
        4) You should be set to modify mode 2 of the event (The numbers next to the arrow buttons read "2/2", if not use the arrow buttons until it reads "2/2"). Go to page 1 of the editor and make sure the activate field says anything other than "Auto" (Your choice between "button" and "touch" depends on your use of the second mode, if at all).
        5) Go back to page 2 of the editor and use the arrow button to go to mode 1 of the event (The numbers next to the arrow buttons should read "1/2").
        6) Go to the event code editor screen and add a new code. Choose the code category titled "Propoerty Control". Then scroll down until you come to the code named "Add Mode".
        7) Choose the event you are presently modifying in the field on the new screen.

        Basically, you're creating a second mode for the event and changing the mode of the event. Auto events must ALWAYS be accompanied by a mode change, especially if you're using an event transition in its code, because that will cause a real infinite loop that the system will NOT detect and will not end until you reset or cut the power. Which equals wasted time if you didn't save your work before playtesting.

        Comment

        Working...
        X