Closed NewSoupVi closed 1 month ago
@Alchav (Can't request review)
no deprecated sweep_for_events
to not break apworlds?
no deprecated
sweep_for_events
to not break apworlds?
My bad, I had that, and then I accidentally removed it again lol
Approval from Espeon is implicit as per https://discord.com/channels/731205301247803413/1214608557077700720/1253206955879694336
@Alchav (Can't request review)
What, do you really need my approval to rename a core function just because I use it?
Alchav (Can't request review)
What, do you really need my approval to rename a core function just because I use it?
That is the current procedure, yes - If something touches a world, the world maintainer has to approve.
We have discussed changing this in the (recent) past, some ppl argued that we shouldn't need to do this, but some world maintainers have said they want to continue to be required to sign off on anything touching their world.
Happy to discuss solutions in the Discord.
Oh thanks for the reapproval Alchav, did I accidentally ping you again? If so, I didn't mean to :D
Oh Violet, extremely smart and beautiful world maintainer of the highly acclaimed The Witness Randomizer for AP, are you willing to acquiesce to this most recent change?
Yes, esteemed and prolific core maintainer NewSoupVi, this change is beautiful and you should be proud of yourself, hats off to you my friend
Thank you lovely Violet, please continue on with your day, may it be an awesome one like you deserve!
Seems like we're going with the "advancement" naming now, and I have recent evidence that people think this function is referring to
address = None
. So let's try to get away from the old "event" naming and be consistent about "event" meaningaddress = None
and "advancement" meaning "will be picked up by sweep_for_events / etc."I wasn't sure about the
event
parameter oncollect
. I feel like that one might be used slightly differently? Lmk what you think about that one.