#Why was reflection removed?

16 messages · Page 1 of 1 (latest)

fringe monolith
#

Maybe this isn't the best place to ask this, but theres a lot of things I could do if reflection was available like in 1.20. I read that it was removed due to security, but a modpack creator could just include a custom mod in their pack that could do the exact same damage. It seems like more of an annoying limitation than anything.

dusk hareBOT
#

Once your ticket has been resolved, please close it with </ticket close:1054771505520717835> command!

fringe monolith
#

A mod could also just mixin into kubejs and skip the class filter. Which I might end up doing tbh

echo gorge
fringe monolith
#

Again you can do all of that in a mod

candid spear
#

Yeah, but that doesn't mean they should allow someone the easier access of doing the bad thing just because there's some other avenue.

fringe monolith
#

Imo it isn't easier, because if you know how to do that, then you probably know how to code and make mods anyway. It seems mainly like a nerf to kube

#

Mods and packs are vetted by curseforge and modrinth too

candid spear
#

Then do it through a mod instead of letting KubeJS do it. It's much easier to make a startup script then make a java mod. I install KubeJS put a js file in a folder, and that's it.

fringe monolith
#

Fair play, it just feels like it goes against the spirit of something like kube which is meant for scripting and mashing together features of mods. A lot of the time you'll need to access private things

#

Most usages of kube are covered by the api, so I do understand there not being a bigger demand for reflection

hollow steeple
#

they would have to know kubejs to vet each script individually

#

so all they do is check for is this mod in the approved list?

fringe monolith
#

I guess the filter could default allow all classes, and then java.net, sun, etc could be denied? That way, you can use reflection with all mods but make it more difficult to do harmful things

fringe monolith