Keeping track of xp/hour while paused would probably be fairly difficult given the way the plugin is designed. It calculates your incoming XP/Hour and totals based on the time the plugin has been running. When you hit pause, the timers stop, and the calculations stop too since the time isn't moving.


I cannot disable parts of the plugin based on "unfriendly" plugin detection, nor can I detect what scripts Skunkworks currently has loaded, nor can I tell what actions that script is doing. In this case, it's either the whole plugin or not at all.


---


Not true. Hit 'Pause', and the timer keeps going. The plugin stops targeting and killing and buffing and taking any "actions" but it still counts down the rebuff timer and increments the running timer. I believe the damage over time stats keep working to although I'm not 100% on that right now.


I wasn't referring to detecting specifically which plugins were working. You already block on Skunkwords being detected. My thought was instead of blocking totally, wrap the functions that call the action of targeting and killing into the authorization check. That way people could still use lifetank for other purposes other than actual combat and still be able to run skunkworks. You still get to hold the "high ground" and keep lifetank from being used for UCM.


It's a non-issue though, really. I'm impressed you've remained calm through these changes and have still been willing to consider opposing points of view. Thanks for that.

you can't "ban" your original sources, you still have to give them credit.


---


Not necessarily true. Writing software is different than writing an essay in that the important factor is what type of license the original software was released under. Software can be released under a myriad of different licenses and some of them do not require attribution to an original source/author. I personally write lots of software that gets used across the world and keep stuff like your water treatment systems running. The companies I sell the software to are under no obligation to give me credit for the original code if they modify it, even for a re-sale, but are prohibited from duplicating the code for multiple projects. The end user of my product has no clue who I am, and probably believes the company they purchased it from is the author -- but this is not the case.

Thank you for giving me "choice", I appreciate it Crelic' of MT!

Thanks C' your work is greatly appreciated!!!

 

-----signature-----

you can't "ban" your original sources, you still have to give them credit.


-----------------------------------


Ummm.. yes you can. He did it already.


Also, he can still give "credit" in the documentation.. but that doesn't mean that he has to allow the program to run in conjunction with his.

 

-----signature-----

Just a FYI/bump.. version 7 will be disabled tomorrow (Saturday). Be sure to get the new version to prevent any interruptions in your gameplay =P


C

 

-----signature-----

Seems a little strange to me that on one hand you help ucming by adding log out on death/ unfriendly players, things that would only be used by the player when they are AFK while disabling skunkworks/log out on low components and all irc functions to try to deter UCMing.


Could you please explain that?

 

-----signature-----

[MOD-Edit]

 

-----signature-----

k3ny:

I've explained myself about a million times now.


I'm trying to make the plugin more unfriendly to UCM, but it's not going to happen overnight. It's clear I don't want the plugin used for UCM and I've reserved the right to disable the plugin based on other plugins you are running, or if I feel you have abused the plugin itself too much.


However, I'm not an idiot. I know people will still UCM with it, and will use some plugin or write their own script to bypass some of the measures I've put in place. The way I see it, the log out options get the users OUT of the game and not necessarily help them keep playing. It's hard to UCM when you're logged out.


C

 

-----signature-----