MonsterSpawn 304, like the previous versions, spawns ScriptedPawns (SPs) in maps at random from lists which can contain up to 60 SPs - 304, unlike the previous versions, has 100 lists (the previous versions had 20 lists).
I have recently started to fill out the lists and currently have around 38 lists full or partly full. I've been using MonsterSpawn for several years but have not used more than 5 or 6 lists, mostly concentrating on one list adding or removing SPs as I tried them out.
My issue is that 304 will only use the first 20 lists (numbered 0 to 19) - trying to spawn SPs from any list beyond number 19 generates a non-specific error message* for each SP which should be spawned.
Has anyone else come across this issue? Does anyone else use MonsterSpawn and successfully spawn SPs from a list with a number greater than 19?
► Show Spoiler
* Normally if a SP can not be spawned, the message will indicate the package/class name, the number of the list from which the SP should be spawned and the number of that SP in the list
The issue happens in 469d and in 436; is not map-specific; is not related to any other mutator I am running as far as I can tell, having run MonsterSpawn without any other mutator; and is not caused by any gaps in list 19, typos etc. I have set MonsterSpawn to use 30 lists and thus far it has attempted to 'use' most lists between 20 and 29.
The code for MonsterSpawn is obfuscated - UTPT will decompile it to some degree and there does seem to be reference to 100 lists - certainly every list and every SP in each shows up when looking at the mutator in the Advanced Preferences.