If your mod has something that truly needs to happened after se post processes, there's no issue with having it as a dependency. It's only an issue to do so if there's no need for it, so that SE can properly verify the needed data.

I acknowledge that,and that is totally fine,but when it combined threat/risk to totally nullfy your work? no.
and the fact that k2 just put about a small mod amount of content in postprocess just become the final straw to crack me up.

If he start to process every issue in github,then you can start blame me.

If your mod in particular needs to change something post processes sets, you can simply have a dependency on post.
It just not supposed to be done if not needed.

so does this mod,this mod is work just the way you said.

It looks like some sort of tool for other mods to use. Which is basically unnecessary.

It looks like some sort of tool for other mods to use. Which is basically unnecessary.

or I will have to make postprocess mod everytime I want to make a mod with se-k2 compatiblity.
with these 2 mod,I will have no need to do that,so it is kinda necessary.

If you have steps you need to do both before and after post processes, I guess you would need two mods. Didn't consider that bit.