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

Mobs no longer spawning #9

Open
xNocki opened this issue Feb 18, 2023 · 2 comments
Open

Mobs no longer spawning #9

xNocki opened this issue Feb 18, 2023 · 2 comments

Comments

@xNocki
Copy link

xNocki commented Feb 18, 2023

It is technically possible that they are either spawning in a different scene, but the challenge prompt still shows up on the left side of the screen.

Situation: I was fighting a Bathysmal_Vishap and I was unsure how to kill it, as I don't play the regular game anymore and had never encountered this mob. It was swimming through the ground in a circle around me and I tried many things to kill it, to no avail. So I decided to /killall and remove it, hoping it would just continue spawning the next round of things. I got the notification that 14 things were killed in scene 3, despite only seeing the one. This had occured after I did /mw wave5 x3 lv120 t2 and it was on (I think) the 5th wave. I tried logging out to see if that would reset it, but it did not.

Here's what my server log looks like:

16:42:17 <INFO:MobSpawner> Set custom wave: elite
16:42:17 <INFO:MobSpawner> Set custom wave: elite
16:42:17 <INFO:MobSpawner> Set custom wave: elite
16:43:04 <INFO:MobSpawner> Set custom wave: elite
16:43:04 <INFO:MobSpawner> Set custom wave: elite
16:43:04 <INFO:MobSpawner> Set custom wave: elite
16:43:23 <INFO:MobSpawner> Set custom wave: elite
16:43:23 <INFO:MobSpawner> Set custom wave: elite
16:43:23 <INFO:MobSpawner> Set custom wave: elite
16:43:59 <INFO:MobSpawner> Set custom wave: elite
16:43:59 <INFO:MobSpawner> Set custom wave: elite
16:43:59 <INFO:MobSpawner> Set custom wave: elite
16:50:00 <INFO:DungeonSystem> Nocki(10001) is trying to enter tower dungeon 3310
16:50:00 <INFO:Scene> Scene 33100 loaded 4 group(s)
16:50:00 <INFO:Scene> Scene 33100 Block 33100 loaded.
16:50:33 <INFO:DungeonSystem> Nocki(10001) is trying to enter tower dungeon 3410
16:50:33 <INFO:Scene> Scene 34100 loaded 4 group(s)
16:50:33 <INFO:Scene> Scene 34100 Block 34100 loaded.
16:51:07 <INFO:DungeonSystem> Nocki(10001) is trying to enter tower dungeon 3510
16:51:08 <INFO:Scene> Scene 35100 loaded 4 group(s)
16:51:08 <INFO:Scene> Scene 35100 Block 35100 loaded.
16:53:31 <INFO:DungeonSystem> Nocki(10001) is trying to enter tower dungeon 3402
16:53:32 <INFO:Scene> Scene 33732 loaded 5 group(s)
16:53:32 <INFO:Scene> Scene 33732 Block 33732 loaded.
16:55:27 <INFO:GameSession> Client disconnected from
16:55:27 <INFO:MobSpawner> [MobWave] Player logged out so challenge ended.

Now this occured for the following wave after I logged back in:
image

@xNocki
Copy link
Author

xNocki commented Feb 18, 2023

There are also times where the waves can get caught on glitched mobs, for example this guy:
image

And the skip command didn't do anything to make it stop or go away, and I'm afraid if I /killall again it will get stuck. This is effectively what happened in my previous note, as the electro vishap was stuck at 1hp without me able to hit/interact with him.

@NotThorny
Copy link
Owner

This has the affected mobs removed for those facing this same issue, as a temporary solution until the next update.
MobWave.zip

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

No branches or pull requests

2 participants