Issues with Vanilla Expanded Storyteller - Winston Waves

When using Dubs Rimatomics and you have the TACS system active and summon the wave early you are givien the reward for the wave and the wave still haves a time limit before the wave starts. What has ended up happening is if you summon multiple waves early they can come in rapid succession.

Potential bug? https://i.imgur.com/CRkYQgh.png I can't put reward marker down. No error in log.

You can't have two rewards drop spot, that's all. This is telling any other reward drop spot has been removed

RimThemes causes the "Wave Box" to have a Opaque Black Background instead of a Transparent one

The alert appearing at the start of a raid continues coming in - hundreds of raid notifications came in before I was able to finally kill all the raiders

Im not sure if this problem is inherent to this mod, or is caused by the interaction of it, and other mods. But it has caused me to have to restart multiple games.

Theres thousands of notifications after the offending raid
and its impossible to get rid of all of them... Ive tried

I hope this can be adressed- this storyteller is hands-down, my favorite one
-
thank you for all your work! I wouldn't play this game were it not for your mods

An issue when starting a new map with a scenario that triggers a random threat, if the random event is a raid the map crashes back to the main menu unfortunately. It would also be GREAT if the wave interface (is nicely done btw) had a smaller width, it makes clicking the rightmost colonist impossible if you have a very big colony. Either that or allowing clicks through the window with a mod setting when draggable is turned off. Love this new game mode and THANKS!

https://gist.github.com/b15b52e00e55633b0c2cfad46bbccb3b

https://i.imgur.com/SyjCObX.png It seems that mechanoids, the sapper kind, prefer to crush every meteorite on the way to my base, making it very easy to pound them with mortars. No errors.

@Japa I cannot do anything about it.

@ASF If this happen again, you can try to use the debug option to reset the wave.

@M M Will take a look at this.

@Snues This mod doesn't change the IA in any ways, so it shouldn't be this mod doing it.

the wave doesnt start and the summon early button doesnt work, the timer goes to negatives


Screen shot of the bug: https://preview.redd.it/0n6snozrjug81.png?width=250&format=png&auto=webp&s=ac2d9cb1eaebc585edc02101f0efe1bd28de64bf

Screen shot of the debug console: https://preview.redd.it/sajf9kktf2h81.png?width=833&format=png&auto=webp&s=bac9cb8706c4cf946c52fb6c8ee57f59b27fc3dc

I tried restarting and there was no mods added mid-game, havent changed story tellers winston waves was the starting storyteller.

Screenshot don't help, full hugslib log do.

The "Increased Stats" buff from Winston Wave persists even after you switch to a different storyteller.

https://gist.github.com/fc05779aecb3aae6f0a55834bcef3e02

Also the research speed buff stacks with the global work buff, creating lighting fast research. Is it intentional?

I mean just look at this

https://www.reddit.com/r/RimWorld/comments/uncvw0/researching_stuff_at_the_speed_of_light/

I'll admit, this much was mainly due the "Work frenzy" inspiration, but should those two still stack?

bug encountered, not sure how to replicate... ANYWAY. wave had the "no retreat" modifier on it. I called in 3 helper squads. the wave destroyed them.... and killed one of my guys, so i quit to desktop out of rage. when i turned the game back on, it was mid wave, but despite having the no retreat buff, they retreated.... and then the wave didn't end, even when i killed all of them. so i turned off waves and turned them back on, but now the wave timer disappeared and no waves are spawning as if it's still off.

@Harmless Orange Will take a look

@Cookiesnm1lk Use the debug option to reset the wave

sooo... i forgot to check this, reloaded my save... back like 4 autosaves.... and everything was working again. it didn't send a no retreat wave at me.... and then wave mode disappeared completely anyway without me turning it off.

edit: turning wave mode off and on again fixed this.