-
Notifications
You must be signed in to change notification settings - Fork 8
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
Adjustments (maybe) needed for engine PR 3456 #30
Comments
Note: This is now tied to MovingBlocks/Terasology#3490 instead - see it for details |
@Cervator I just pushed a commit to MovingBlocks/Terasology#3535 which seems to have fixed the problem for me. Can you test and confirm please? |
@Cervator did you test this by any chance? Is this still required? Not promising anything, but maybe @jdrueckert or me can see whether GooeyDefence works without this fix with the serialization overhaul... |
@skaldarnar Don't recall: did we try this out? 🤔 |
No idea, but it sounds like there's a newer typehandling issue now, have noted it myself for the last couple play tests. Seems to trigger after you've got one or two waves going. |
Merging MovingBlocks/Terasology#3456 causes an error on auto save in this module, although exactly what causes it eludes me. First time I believe I hit it nearly immediately after having activated the shrine (
e
clicking it). Second time a fast enemy wave I placed three towers on the paths and triggered the wave (regular enemies that time). On the auto-save following that the game crashed with the error below.To place the towers open the inventory (with
i
) and buy a core + a single targeter + a plain damage effector. Place one set on each path then go activate the wave and watch the fireworks.Sending this @eviltak's way as the author of the engine PR and/or to @jellysnake if interested :-)
Log snippet on crash (which locked the game entirely):
The text was updated successfully, but these errors were encountered: