currently, if the current number of seeds generating is equals to max generating seeds (wall), seedqueue waits for one of them to be paused before unpausing a locked instance. instead, instance priorities should be immediately re-evaluated, so the locked instance can be given its correct priority from SeedQueueThread#unpauseSeedQueueEntry. this affects the implementation of #8, because locked entries will almost always be held up longer on entries which are doing the stretch after the max world generation %.
currently, if the current number of seeds generating is equals to max generating seeds (wall), seedqueue waits for one of them to be paused before unpausing a locked instance. instead, instance priorities should be immediately re-evaluated, so the locked instance can be given its correct priority from SeedQueueThread#unpauseSeedQueueEntry. this affects the implementation of #8, because locked entries will almost always be held up longer on entries which are doing the stretch after the max world generation %.
mentioned in discord here: https://discord.com/channels/1262887973154848828/1272158999298707488/1272693673418686557