Did Yula just say that Paraduck and Crelic UCM?

 

-----signature-----

So Yula... let me get this straight....


You're basically saying that you're going to blame the pharmaceutical makers of pseudoephedrine because it can be turned into methamphetamines and abused.. We're not going to blame the meth users, and we're going to put the meth cookers on the same level as the pharmaceutical companies, because their product is being improperly used? That doesn't sound right to me.


As for the comments toward hypocracy, what is it exactly you expect me to do? Not release memlocs next patch? Shut down Decal because people use it for UCM? I take responsibility for Decal as a plugin framework and system which allows multiple different types of plugins to be developed, but ultimately the blame for that lies on the end-users for not exercising self-control and not using the plugins, and the creators for publicly distributing these plugins to the end-users.

More like the pharmaceutical company is turbine and you're the meth cooker.


edit: no, your analogy is just horrible and can't be properly related to the situation.

 

-----signature-----

Before this turns into a hate fest - and feelings being hurt beyond repair - it should probably be locked.

 

-----signature-----

And since my name is being dragged through the mud every other post here, I want to make clear of something, which is very similar to Drakier's situation:


Myself nor Paraduck wrote Lifetank... We didn't write the code, we didn't put those features in, it wasn't our idea. It's been very clear we're against the act of being unattended, especially while running a program we're currently MAINTAINING now. There are alot of things I'd love to do to keep steering it to the not-UCM friendly side, but we can't just "turn the wheel" on a whim.


I would *LOVE* to remove the death alarm, or even the log out features. But it's not that easy, there's more to it than just deleting a few lines of code. When we removed the admin alarm, it completely disabled the whole program because it was tied in so much with the rest of the code. It took us months to remove it without harming anything else. During that phase, we had to use an "off" switch to disable it, but finally later was able to kill it... and if I remember, it crippled part of the IRC function too.


So, please stop comparing myself and Para to this. We're trying to do the exact opposite of what he's presented here. We're, slowly, but trying to remove these remaining "aid" features... not improve upon and promote them.


and Lord_Anton:

I invite you to tear apart and reverse engineer our code and find the admin alarm we're "hiding" from the general public. Go ahead, help yourself. I'd almost post the source myself.


C

 

-----signature-----

it was already posted a while ago, and last I heard you took it out after it was brought up, or somethng like that

 

-----signature-----

Looks good to me. Gj Eps =) I got faith in u lawl

Lookin forward to usin it. =P

so is there anyway this will be released or any of that good stuff?

 

-----signature-----

I didn't write much of any of the code in 'my' plugin either. I didn't even sure what scripting language it was in until somebody asked me and I had to go double check. I took a utility I enjoy using, took out all of the combat, looting, buffing, healing, movement, and little perks of the utility that not everbody would use, and made it into a an assisting utility to run coinciding with similarly based plugins like Lifetank XI. I've made it so that decal users can take advantage of what other plugins have to offer, and use it combined with what they currently do. I wasn't planning on keeping in the admin alert, because it wouldn't really be needed, but I kept it in just incase a user wants to use.


I think players should be able to decide how they want to play, or not play, the game for themselves. If they want to break the rules, I'm not going to hold them back, but they better be ready to accept the consequences from doing so, and they better be respectful of other people who are playing the game as it is meant to be. Log on player detection should always be in any combat plugin. A main reason people don't like UCMers is because they take away hunting spots that the person could be leveling themselves by hand in, and playing the game in a rule abiding manner, in. I do not like when people UCM and never respond or react to players around them. I don't care if you UCM and nobody is directly effected, as long as when somebody wants you attention, you are there to give it, or you leave.


Although Turbine doesn't say it, and will never admit it, you can tell that they don't really care if you UCM, unless somebody lets them know they don't want you doing it. This is shown by the amount of UCM checks they do. I haven't seen a "Envoys are sweeping EO and POTB" message on general chat in MONTHS. The chances of being UCM checked now adays are almost non existant, until somebody reports you. Yes there are extremists that go around reporting people UCMing in spots they don't even want to use, but almost always there won't be an issue unless somebody else wants to hunt where you're macroing.


If somebody is going to break the rules and UCM, they are going to do it whether or not they have the things that are in my plugin. Some of you say that my plugin is bad because you think it is made only for aiding UCM, well if that was true, look who else it would help in the process. Say somebody is macroing a quest dungeon that people generally don't go in. Somebody is running quests, and they go in the dungeon. Normally that UCMer would continue macroing and ruin the quester's experience. With the log on detection type features, that person will log out when a player runs near by. Yeah, it could log back in and start macroing again, once you're gone. As long as a player is nearby, they will not be bothered by any UCMer, and that's the real reason why anybody would report another person for UCMing, because they are taking up area that people who are following the rules want to use.


I myself may be pro UCM in whether it should be allowed or not allowed, but I respect other players if I ever do anything that I shouldn't be doing. Not once has anybody complained about me macroing in a dungeon and not responding. It doesn't happen. If I hunt where other people could be, I hunt. I don't think there has ever been a time when I have ran a macro and not used log on player detect if I could, not because I could be banned, but because if somebody else comes by and wants to use the spot while abiding by the rules set by Turbine, they definately deserve it before I do.


For this reason, I could FORCE log on player if you use my plugin and do not show that you are attended, similar to how el tank required you to press a key to show you are attended, you go into an auto log on detect mode, but I haven't decided on it yet.

 

-----signature-----

Wait... So now you are admitting to stealing all the code from some other plugin, ripping out the portions you don't care about, then repackaging it as your own?


You can't even tell us what language it is written in, not because you don't want to, but because you can't?


Wow.