Author Topic: No Observers (Read 4606 times)

Brickmaster · March 10, 2014, 03:23:17 PM

Back to being the NSA.

Ad Bot · Advertisement

blueblur121 · March 10, 2014, 03:34:49 PM

package NoObserversPackage
{
  function SimObject::onCameraEnterOrbit(%obj, %camera) {}
  function SimObject::onCameraLeaveOrbit(%obj, %camera) {}
};

activatePackage("NoObserversPackage");

This could potentially break other addons.

Port · March 10, 2014, 03:36:31 PM

If your add-on depends on that function then you should use another function. By default, all it's used for is the observers message.

Electrk. · March 10, 2014, 04:11:06 PM

what functions do you recommend instead?

Cr�wn · March 10, 2014, 05:09:09 PM

Cool someone finally made this.

TheNoob · March 10, 2014, 05:50:33 PM

Wow thanks!
But i wanted this client-sided sooo....
Great.

-Jetz- · March 10, 2014, 06:31:46 PM

Quote from: Port on March 10, 2014, 11:36:44 AM

What exactly is the point of that other than making admin abuse on stealthy servers easier?

Uhh, make it easier to catch people in the process of doing things they shouldn't be? I thought that was the whole point of "spying" in the first place.

Why not just overwrite the functions outside a package? That way you don't risk breaking other mods that package it.

McZealot · March 10, 2014, 06:42:42 PM

Quote from: Port on March 10, 2014, 11:36:44 AM

What exactly is the point of that other than making admin abuse on stealthy servers easier?

The point of spying on users is to watch them without being noticed. If I suspect a user is breaking a rule or something and I want to spy on them, it's not helpful when they know I'm doing so.

Chrono · March 10, 2014, 07:10:06 PM

Quote from: blueblur121 on March 10, 2014, 03:34:49 PM

Code: [Select]
package NoObserversPackage { function SimObject::onCameraEnterOrbit(%obj, %camera) {} function SimObject::onCameraLeaveOrbit(%obj, %camera) {} }; activatePackage("NoObserversPackage");
This could potentially break other addons.

No, because other add-ons should be using a parent.

Port · March 11, 2014, 03:03:04 AM

Quote from: -Jetz- on March 10, 2014, 06:31:46 PM

Why not just overwrite the functions outside a package? That way you don't risk breaking other mods that package it.

Overwriting them outside of a package would be even worse because you couldn't turn it off if needed.

-Jetz- · March 11, 2014, 10:49:46 AM

Quote from: Port on March 11, 2014, 03:03:04 AM

Overwriting them outside of a package would be even worse because you couldn't turn it off if needed.

Your add-on doesn't appear to have a way to turn it off anyway. Perhaps the best results would come from reconstructing the functions entirely but introducing a preference to toggle it.

Quote from: Chrono on March 10, 2014, 07:10:06 PM

No, because other add-ons should be using a parent.

Wait, what? If another add-on modified these functions, the load order would determine if that one worked as it should.

Port · March 11, 2014, 12:09:12 PM

Quote from: -Jetz- on March 11, 2014, 10:49:46 AM

Your add-on doesn't appear to have a way to turn it off anyway.

Does deactivatePackage not count? :(

Quote from: -Jetz- on March 11, 2014, 10:49:46 AM

Perhaps the best results would come from reconstructing the functions entirely but introducing a preference to toggle it.

That would still overwrite other add-ons using it regardless depending on the name of the add-on. The default function doesn't return anything, so there's not really any gain to functions that package it and call the parent either.

Chrono · March 11, 2014, 12:48:43 PM

Oh, I didn't realize Port was using packages in this.