-
Notifications
You must be signed in to change notification settings - Fork 242
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
Some cities which produce errors #19
Comments
A quick disclaimer, I am not a HAXE dev, I've got experience in Java, JS and Typescript primarily but thought I would have a quick dig. Just tested both use cases, and found that: First linkproduced Which appears with some further stepping through the code to suggest Now some digging into the compiled js indicates to me this appears to relate to a class That's about as deep as I can go, so hope it helped a little in respect to that issue. Second LinkI was unable to produce any error, included in this testing:
|
Here's another city link: It errors out with the following output on the console:
|
Someone on the Azgaar FMG discord was telling me that there's a problem with larger cities producing too much recursion for the browser (on Firefox and Chrome at the least). In practice it seems the examples they gave both produce errors for me as well, but sometimes different errors; probably because of different settings we have. For example, the second one only produce errors if Improved Lots are turned off.
In any case, the problematic cities:
https://watabou.github.io/city-generator/?size=60&seed=8414616970181&name=Test2&population=59782&hub=0&random=0&elevation=1&green=0&farms=1&citadel=1&urban_castle=0&plaza=1&temple=1&walls=1&shantytown=1&river=1&coast=0
https://watabou.github.io/city-generator/?size=61&seed=8414616970001&name=Test&population=60811&hub=0&random=0&elevation=1&green=0&farms=1&citadel=1&urban_castle=0&plaza=1&temple=1&walls=1&shantytown=1&river=1&coast=1&sea=0.3
The text was updated successfully, but these errors were encountered: