Construct 2 Large Event Tree Bug

0 favourites
  • 5 posts
From the Asset Store
Casino? money? who knows? but the target is the same!
  • Link to .capx file (required!):

    Steps to reproduce:

    No idea.

    Observed result:

    Pressing "troll" until you get a banned response does not increase the banned variable.

    Expected result:

    The banned variable should increase, thus causing the player to be banned.

    Browsers affected:

    Chrome: yes

    Firefox: yes

    Internet Explorer: didn't test

    Operating system & service pack:

    Windows 7, latest version I think.

    Construct 2 version:


  • Closing, no clear evidence this is a C2 bug and not just a mistake in your events. Please try to reproduce with as few events/objects as possible, specific steps to reproduce, and an identification with the particular event or feature that you do not believe is working correctly.

  • No. Not really.

    It's not possible.

    I'm not sure which portion is bugged.

    All I know is that every event-ending with banned does not work. It'll display text saying "You are banned." but never increment the banned feature. Logically, the entire setup should work. It has worked on a smaller scale in the past.

    I suspect that Construct 2 cannot handle long event chains, and cannot increment variables up at the end of a long event chain.

    If I were to give you an even smaller event file, you'd probably say the problem cannot be pinpointed down further.

    Honestly, I don't get paid enough to do QA testing.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • Your bug report does not really contain enough information to warrant investigation. I need to know things like the exact variables in question (did you mean "banlength"? The "banned variable" seems an ambiguous thing to say compared to just saying "banlength"); the specific event that you believe to be working incorrectly; precise steps to reproduce (which buttons to press how many times exactly in which sequence and then the expected event result vs. observed event result/variable values/etc), and so on. A large fraction of bug reports are simply mistakes in events, or users misunderstanding how the execution flow works when it is working correctly. The event engine is pretty mature and well tested at this point, so it would also surprise me if a simple tree of events like this did not work properly. So on that basis the report was closed as not sufficient evidence to prove there is a Construct 2 bug. Please feel free to repost with significantly more information if you think there really is a bug.

  • I know, it's surprising myself. I would expect better from such an expensive engine.

    Aha. Found the bug. All the actions after Set banlegnth are not carried out. Moving set banlength to the penultimate action seems to fix it completely.


Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)