Thanks for your detailed explanations !
So for the speedrun ...
There are many categories and many things to go over. Bear with me, i'll try to be as clear as possible.
First, when I was talking about caverns, I was talking about cavern entry, not the biome.
You see, those, are very important for speedruns. They lead to a lot of things >>>
First, exposed orbs :
Exposed orbs are crimson/corruption orbs that got crossed by one of those cavern generation like that (So we dont need things as bombs to get to them) :
In red you have the cavern path and in green the orbs positions.
So what we could use is some bool that goes "cavern entry generation overlap crimson/corruption generation"
Or more like "Cavern entry is in crimson/corruption biome".
The best would be something like "There are exposed orbs" but again, I don't think you could detect such things. But if you can, then knowing/checking their distance to spawn would be a huge deal.
Again, if you can't do anything above but detect cavern entry location, you could still let us
test the distance from corruption biome to cavern entry.
That would be enough I guess
(Im really sorry if my explanations are bad/hard to understand. I'm not a native english speaker)
Knowing how many hearts are down those cavern would be great too. (Corruption or not eh. But then it would be a nightmare to organize everything. Meeh)
I don't think you could detect things as heart or chests in those exact caverns generation, but if you actually can, I'll make another list of things (items in chest for example) we could need as close as possible to spawn.
(Especially Iron bars and
TP Potions)
______________
Now, about the jungle.
If you didn't know, the bee hives are very often used in speedruns.
Knowing how high is the highest one would be really usefull. (as well as testing how close it is to spawn)
Another thing is about jungle is the "jungle path" (as I call it). Getting the distance from spawn to it could be useful.
There's always a path that goes from the surface directly to the underworld.
Sometime, unfortunately, it get itself obstructed by many other things, especially the freaking temple and/or the crimson/corruption.
We can already clear out the corruption out of the jungle with your mod and that's really nice !
But do you think we could clear out that temple thing out of the way too ?
It's probably as tricky as detecting exposed orbs so I would not count on it but I'm only here with ideas, I've no idea how goes the world generation and what is actually "checkable"
_____________________________________
Other things
Testing if there are sunflowers near spawn. That's not as useful as all the other things above, but that could be helpful.
Testing if there are teleportation potions somewhere in world/somewhere relatively near spawn
_____________________________________
That's kinda everything I came up with so far about speedrunning.
And some other bug I found out :
- (Yes you were right, it's platinum
mybad)
- If you start generating world/checking seed right after opening any menu on the right you have the choices still up.
http://prntscr.com/jvnxvq
(Mod is generating the world but I still can select things in the menu. All the text will eventually get overwritten after a seed was checked)
- When selecting "world name" "seed" or "config name" you can have the "blinking bar" that says you have the focus on it on all 3 text.
You can't write in all 3 at the same time but it still blinks :
https://i.imgur.com/BQZnI1R.gif
- After using your mod, if I try to join any world afterwards, none of my input are working (even escape) so I need to crash the game to actually join the world.
I guess it has to do with the fact that after using the button "Stop" it gives me an error and something in the background somewhere is still up, blocking any classic ingame input when joining the world.
But it happens on rare situation : Im not sure, but I actually think it's linked to the bug right above. If any of the 3 textbox i was talking about (or whatever their name is) have still the focus after the crash, you won't be able to do anything but typing invisible things.
Clicking away from them should remove that focus
(Or at least when pressing the stop button)
Done !
(And I also think I forgot tons of things I wished to talk about. Welp, I'll come back to you if you're still up for the challenge !)
Thanks again !