it is on DT

 

-----signature-----

On a side note, someone please post a pic of 20 people on a white server all tipping the same cows for me

 

-----signature-----

Ftuoil: does the Log on Death only work while the plugin is in "tipping" mode, and/or only on DarkTide?

The plugin template started from the Quack plugin so I just left it the log option in.

If it is on, and you die then it will log you no matter where you are or what you are doing.

 

-----signature-----

I'm just nervous about log on death and how it affects UCM.


I've always been a strong advocate of Log on Death being options on Buffbots and stuff, but the functionality only working while in "buffbot" mode ... (or tradebot, or whatever).


that prevents the plugin from being used for UCM purposes unless you have the plugin actively in Buffbot or Tradebot mode.


that's all I was getting at. It should only Log on Death while in "tipping" mode as to prevent UCMs from using the plugin as a "log on death" for the macros that don't already offer that feature.

/\


We have something for that already, don't gotta use the Khao Tipper prog :-p

just because the functionality can be found somewhere else, doesn't mean the plugin shouldn't take personal responsibility for it's own usage. If all the plugins did this, then they could only be used for their intended purpose meaning that the macro would either have to have "log on death" built in, or someone would have to create another plugin specifically for the sole purpose of log on death.


my point being that just because something else does it, doesn't mean a developer should not take the responsibility of making their plugin secure.


This is not a slight toward anyone (especially Ftuoil). Just a general statement to developers that they should think about things like this while developing their plugins. When it comes to development, stuff like this comes up in the real world and has to be considered. It's like all those people who used the house buyer plugin to bypass eltank security. It is up to the house buyer developer to ensure (or attempt to ensure to the best of their ability) that their plugin cannot do that.

im nervous that ac dual client is used by more macroers than not.

 

-----signature-----

and I've done everything within my power to make sure ACDualClient cannot be used directly in terms of macroing. This was done while making sure it didn't Impact real players. Unfortunately there isn't a whole lot I can do about the acclient once it's been launched as that is when the realm of ACDualClient ends. So your point is off topic and moot. I've taken every precaution I can. Without totally impacting all other real players, there really isn't much more I can do. If you have a suggestion, I'm more than willing to listen to it and consider implementing it. Unfortunately, no one yet has come up with a good solution that doesn't totally kill the main usage of ACDualClient.


What I have suggested for the Log on Death only working while in "tipping" mode doesn't interfere with the plugin's purpose or functionality. Same with the house buying plugin. If the developer of the House buying plugin did everything he could to try to stop it being used to bypass ELTank security, and just couldn't get it, I wouldn't blame him. It might not be possible. But I would expect that he'd at least attempt to take precaution and attempt to do something to limit the unintended usage.

Has Turbine ruled if UCtM programs are against the CoC?


(Unattended Cow tipping Macro)