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

"Uncaught TypeError: Cannot read properties of undefined (reading 'steps')" #244

Open
cool-RR opened this issue Nov 4, 2022 · 2 comments
Assignees
Labels
bug Something isn't working GriddlyJS An issues specifically relating to GriddlyJS

Comments

@cool-RR
Copy link
Contributor

cool-RR commented Nov 4, 2022

I loaded a Sokoban game in griddly.ai and modified the rules a bit. I pressed "play" though I think the button was inactive. Nothing happened, but I got this in the error log:

HumanPlayerScene.js:594 Uncaught TypeError: Cannot read properties of undefined (reading 'steps')
    at t.processTrajectory (HumanPlayerScene.js:594:38)
    at t.update (HumanPlayerScene.js:734:16)
    at initialize.step (phaser.js:49068:26)
    at initialize.update (phaser.js:100289:21)
    at initialize.step (phaser.js:162805:20)
    at initialize.step (phaser.js:89366:14)
    at e (phaser.js:89613:19)
t.processTrajectory @ HumanPlayerScene.js:594
t.update @ HumanPlayerScene.js:734
step @ phaser.js:49068
update @ phaser.js:100289
step @ phaser.js:162805
step @ phaser.js:89366
e @ phaser.js:89613
requestAnimationFrame (async)

I cut off the traceback because it's long and repititive, find the full traceback in the log: https://gist.github.com/cool-RR/97a4d6043ef2c63fd119619dbb5ac568

@Bam4d
Copy link
Owner

Bam4d commented Nov 5, 2022

Thanks for this bug report! Its easy to reproduce so good catch :D

I'm currently in the process of separating the GriddlyJS components into NPM modules which can be used anywhere... These will be in a separate repository so I can track the bugs better.

@Bam4d Bam4d added bug Something isn't working GriddlyJS An issues specifically relating to GriddlyJS labels Nov 5, 2022
@Bam4d Bam4d self-assigned this Nov 5, 2022
@cool-RR
Copy link
Contributor Author

cool-RR commented Nov 5, 2022

Hmm, my two cents (with much less background than you about this project) is that it'll be better to keep them in the same repo. Modularity is less important than the dependency hell you could get yourself into by separating to two repos. But let's discuss that in video.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working GriddlyJS An issues specifically relating to GriddlyJS
Projects
None yet
Development

No branches or pull requests

2 participants