Dancer Archive
Thread: Denyservice and covercharge not perminant?
Message Edited by --Qilue-UCW-- on 06-06-2005 08:07 PM
--Qilue-UCW-- wrote:
I keep reading that these things are noperminant. Has a Dev or someone else high up said why thise are not Perminanat?
I mean if somone pisses me off so badly that I /deny them... I'm not ever going to want to buff/heal them... Heck I have people on my ignore list from my second day playing..
Message Edited by --Qilue-UCW-- on 06-06-2005 08:07 PM
The devs have not (to my knowledge)offered any reasons why they are not permanent. I can think of practical reasons why they are not.If they are permanent (ie: persistfromone log in to the next), they will requiredatabase storage, a UI interface and code linking the two. This would mean dedicating dev hourstoimplement these features.Dancers ask for this soI include it in our issues, however, I would rather they spend the dev hours ($$) onus forthings that will make our gamemore fun.
Esharra wrote:
I can think of practical reasons why they are not.If they are permanent (ie: persistfromone log in to the next), they will requiredatabase storage, a UI interface and code linking the two. This would mean dedicating dev hourstoimplement these features.Dancers ask for this soI include it in our issues, however, I would rather they spend the dev hours ($$) onus forthings that will make our gamemore fun.
These aren't required for ignore so why would they be needed for deny? A text file on our client, a command line interface, and done. The code for both exist in the ignore feature. As for "privatising" entertainers I can deny people access to a public house or an entire town why the heck can't I deny them access to ME. What a bunch of hooey. The Devs really have no clue whatto do with usentertainers and will say anything to get off the hook. It really is sad.
2. Deny service. The devs said it *should* carry over and doesn't, so they need to look into that technically. They stated they prefer that if someone is harrassing you, you report the harrassment. This is a good thing. Abusive people *should* get banned.
There was a lot of talk about not denying access to the general population, which is where I think this stupid "privitization" keeps coming from. This one guy was whining that he wanted to /deny a whole guild because he didn't like them and the devs said that was not going to happen. Also, he demanded the devs create a /deny list that works exactly like the /addignore list.
Btw...they have a new team specificially to work on the UI so we might see some changes with that, too.
I've seen a couple of threads using that wording.I don't know if that is the terminology the devs used.Myself, I've never had a communication with a dev who used that term in reference to anything dancer.
Shaizann wrote:
Several of the fanfest feedback threads mentioned that they did not care to make a /denyservice list permanant because it would "privatise entertainers"
Solution to this for now is to do what I do i made a Macro that I run every time I log on with the list in it and I refesh or update that macro with the names of the users I choose to Deny. It works like a charm
ie:
/deny John Doe;
/deny Jonathon Doe;
Isiera wrote:
Solution to this for now is to do what I do i made a Macro that I run every time I log on with the list in it and I refesh or update that macro with the names of the users I choose to Deny. It works like a charm
To the analogy to the ignore list: No its not the same and not that easly. Why?
- Ignore works perfectly in the client. The server sends you a tell, spartial chat or whatever, and if your client sees its from one on the ignore list it will simply not shown to the user. But its still send. If someone on your ignore list sends you a /tell or stands beside you and talks in spartial, while you're still logging in, then you'll see that, since the client is not yet filtering it (trust me, i've seen that happening).
- Healing/Buffing etc are actions that take place on the server, not the client (otherwise it would perhaps be easy to manipulate it). Therefor either the server has to ask the client each tick (or at least every /watch or /listen) "Hey XY wants to be healed, he's on your deny list?" (can end with a lot of traffic) or the server needs to store that data persistantly in the server database (what would be the better solution).
Exactly.
Coreena wrote:
- Healing/Buffing etc are actions that take place on the server, not the client (otherwise it would perhaps be easy to manipulate it). Therefor either the server has to ask the client each tick (or at least every /watch or /listen) "Hey XY wants to be healed, he's on your deny list?" (can end with a lot of traffic) or the server needs to store that data persistantly in the server database (what would be the better solution).