Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The hero should be able to trigger events while the main interpreter is running #331

Closed
Zegeri opened this issue Aug 19, 2014 · 3 comments
Closed

Comments

@Zegeri
Copy link
Member

Zegeri commented Aug 19, 2014

It's possible for the hero to trigger other touch/collision events while it's being moved by a list of event commands. In fact, the hero can trigger multiple events, but they won't start until the list has been completed. If more than one events have been triggered, they'll run in ascending order of IDs. This means it doesn't matter in which order these events are triggered by the hero. It looks like in this context, the touch/collision triggers are checked right after the hero's move route has been finished.

That might have been a bit confusing, so here's an example.
https://dl.dropboxusercontent.com/u/30277047/PendingCommands.zip

@fdelapena
Copy link
Contributor

fdelapena commented May 12, 2015

Added the test case example to emscripten for online testing:
Latest PR: https://easyrpg.org/play/index-pr.html?game=issue_331
Master: https://easyrpg.org/play/?game=issue_331

@fdelapena fdelapena modified the milestones: 0.3.1, 0.3 May 12, 2015
@Ghabry
Copy link
Member

Ghabry commented May 13, 2015

What do you think about some convention like test_name_of_test or issue_#number.

@fdelapena
Copy link
Contributor

Looks good the issue_# way for easier access if exist. Updated links for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

4 participants