Allow Metatable hooks on ROBLOX Services or Instances (Sorta...)

[NodeSupport (Node)]

@metatablecatmaid

also whoops just broke every CoreScript by removing a core method it relies on,

This is clearly mentioned within the post. I don’t really get why people are responding if they aren’t reading the thread.

My suggestion isn’t to allow users to override or hook in to pre-existing roblox functionalities. My suggestion is to create a registry of additional methods you can incorporate on to a base Instance class.

@metatablecatmaid

This is a performance tarpit. Good luck getting Roblox to add it. Don’t see why its so hard to just make a prototype that references the Instance.

The performance tarpit would be completely dependent on a developer to developer use case. Implementations of poor code will obviously result in poor performance. It would be no more or no less efficient then say an index call.

Also, I mention the draw backs of needing to create wrappers that reference instances. Please read the post (x2)

[HexadecimalLiker (Liker)]

CoreGui:TakeScreenshot does NOT utilize cookies, or HTTP. It simply, stores a screenshot. Also this “security risk” is not even one considering one could not hook CoreGui:TakeScreenshot if that feature was implemented. The hooks could also be inherited from required scripts or shared environments, which would make it harmless.

[icymanred (gengar)]

that wasnt my point at all bud but okay

[HexadecimalLiker (Liker)]

Yes it clearly was your point as everyone appears to have the same idea as me

…or you just can’t speak english

[icymanred (gengar)]

no it wasn’t and wdym take screenshot doesnt have access to http ofc i know that but ik where it gets run which is a CORE SCRIPT

[SomeScripter3]

You only be breaking your own game.

[VSCPlays]

I don’t know why two people didn’t read the thread before replying. It’s not a security risk unless you use too much toolbox models. Is reading skills decreased? Are people being blind? is attention span ruined?

@NodeSupport

one in which does not allow you to override or hook functionalities, rather allow you to add your own methods to a pre-existing ROBLOX class / instance.

@NodeSupport

They could always reference back to the original function, regardless of what you may declare within your hooks.

@NodeSupport

Certain methods that are could potentially be a security risk to override (ie core features, etc…)- could be immutable.

---

anyways I agree with this, Imagine I need to add some function to some instances that would make it more useful, I can even modify certain function to make it better.

[TimBob2471 (wally)]

@metatablecatmaid

also whoops just broke every CoreScript by removing a core method it relies on, whoops just broke every admin script by removing the Kick method.

fwiw CoreScripts run on a separate Lua state anyway so hooks like this wouldn’t affect them (the same behavior applies to script executors)