#61
|
|||
|
I've been going through the Enlightened Dark guild news page and cataloging all their drops.
I'm only up to May 2001 in parsing the drops so this will take some time but their page is very comprehensive and they almost always listed every drop. Examples: https://web.archive.org/web/20020602...s.html?month=2 Once there are some hard numbers then objective decisions can be made. | ||
Last edited by Dolalin; 01-05-2022 at 05:41 PM..
|
#62
|
||||
|
Quote:
| |||
#63
|
||||
|
Quote:
| |||
#64
|
||||
|
Quote:
That said, I did clear ST quite a bit after the changes, and it was indeed very easy. I had no issue tanking the trash on a ranger. We'd have like 6-12 people typically. I never noticed a disparity in 1h vs 2h to be honest, but I didn't pay very close attention. (Also, I loaned Nazlug like a million plat worth of stuff on p99 a few years ago and he disappeared one day :[ )
__________________
alksley <rampage> / <awakened> / <TSS>
| |||
#65
|
||||||
|
Quote:
https://www.project1999.com/forums/s...d.php?t=395711 As I've mentioned creating a new staff member position like "Lorekeeper" who filters bug reports and updates a visible status would be exceptionally helpful for those who want to contribute research and more on this forum. This group of people can be responsible for filtering out garbage, bringing you the bug reports that are worth review, and then updating their status based on your feedback. Potential status: 1. Open, no one has reviewed it. 2. Lorekeeper has reviewed it, garbage, not a bug, duplicate, previously discussed, etc. 2. Lorekeeper has reviewed it, needs more research. 3. Nilbog has reviewed it, needs more research. 4. Nilbog has accepted the bug as legitimate and it is part of the backlog to fix. 5. Fixed. There seems to be a lot of effort here being wasted when people keep researching things that are on the "short list" already or get disgruntled when they can't get any response about their efforts so they just stop contributing. I would reverse engineer the client to figure out the classic Charm code but I feel it's wasted effort until channeling gets fixed because it seems likely that such an effort might never materialize into any changes. Also what if you already have the classic Charm code figured out on your short list and I don't know? That would be a lot of wasted effort on my part. Without adequate communication on posts and visibility into this "short list" of confirmed issues and the work needing to be done on them we have a very disjointed volunteer contribution process that leaves a lot of people feeling rejected. The indication provided here by staff is that volunteer efforts are encouraged and desired but you have to balance this with the reality of the experience of trying to contribute which gives the opposite impression that the staff would rather we didn't bother them or that we can "try" to contribute and the staff "may" bother to look at something. This disconnect is the source of a lot of those feelings. It would be better if the messaging was more clear up front that you can't expect any kind of response or follow up but if you want to post go ahead OR if the staff would implement better management of the issues so that each contributor felt their efforts were being acknowledged. I would again encourage you to read this sticky, "Please read before posting" on the bug forum. https://www.project1999.com/forums/showthread.php?t=19 Quote:
Quote:
If you're still wasting time reading posts with inadequate research or links, and this thread must be another example since you commented it needs more research, then consider the Lorekeeper idea I mentioned above. Volunteers like Dolalin or others could filter these bug reports so you don't waste your time and can spend your time responding and reviewing the things that probably should get a review/response because people put in the effort to contribute something worthwhile. It would likely be a lot easier for you and better for volunteers if there was a go between who brought you a list of a dozen threads that were solid and you could ignore the rest and those people who made those dozen threads actually get a response and follow up in a timely matter about if they should keep researching or can consider the matter tracked and "done" on their part. One final note on this particular change is you mention it is more difficult than others to implement. Is it possible the work could be broken down into sub tasks and into two groups where one is possible to do with the EQEmu code and the other requires access to P99 source? This would allow you to say, "Ok this is an acknowledged bug, the research is good, we (staff) have some changes we need to make but in the mean time someone should be able to adjust X, Y, and Z using EQEmu open source code please contribute those changes here if you want this to get done sooner." This would also require the staff inform people though if they decide to do X, Y, and Z themselves to avoid that duplicated effort. That could also be a matter of doing all the private source work first and then dropping a note, "We completed our changes and are working on X, Y, and Z ourselves now." | |||||
Last edited by azxten; 02-25-2022 at 02:25 PM..
|
#66
|
|||
|
Oh and a separate note about the trolling.
Trolling in the bug report forum should probably warrant an immediate suspension/ban. Like I said, it upsets contributors, who in turn get frustrated and post things that upset the staff, and so on. Strict rules about posts here would probably also help things. For example, maybe no one here should even be questioning if proof is sufficient or not except staff. All posts and comments here should require research or they should be deleted. I doubt there is any value in the "please fix this!" or "Yes, this would be awesome!" or "I don't remember it being like that on live" and so on comments. Every single comment here should have research either confirming or denying a specific bug. If the staff needs feedback on which bugs players want fixed the most there would be more effective means to get that information than random people commenting about how much a certain bug bothers them or they wish it would be fixed. I do all of these things I'm complaining about by the way because it's the way things are here. I post things I think were bugs with zero research and let others tell me I'm wrong and so on. It's like why not? That's the easiest way to vet a bug initially, start a discussion and see what others contribute. That kind of thing is probably better suited to the general forums though if people want to just gather feedback, memories, and so on. It's still a valuable function though just not so useful cluttering up these forums. Lorekeeper staff member with forum mod permissions over the bug forums and an established process for updating status and communicating between volunteers/staff seems like a huge win in my opinion. | ||
#67
|
||||
|
Quote:
Thank you for continuing to maintain this project.
__________________
Wulfgur <Vanquish>
| |||
#68
|
|||||||
|
Quote:
Looked into this a bit to get a scope of changes. Will start with the easiest* tasks first before getting into difficulty changes of npcs and loot table % adjustments. Quote:
Quote:
a newly created sentry an aged caretaker a tireless servitor If I understand this correctly, those ^ should see invis prior to sleeper awakening. After sleeper wakes, nothing in the zone should see invis? Quote:
Also, I noticed newly created sentries, and tireless servitors have no loottable. Is this correct? | ||||||
Last edited by nilbog; 05-18-2022 at 09:40 AM..
|
#69
|
||||||
|
I think the tl;dr is (1) post awakening Sleeper's Tomb mobs should be easier (less flurry, no see invis and sneak/hide); (2)Prog/MOTG/FA should drop Primal weapons more often than current; and (3)primal drop rate should be more even across weapon types.
Some citations from prior posts /external sources - https://web.archive.org/web/20011030...c&f=4&t=000292 Quote:
Quote:
Quote:
A number of quality posts from Dolalin as always. | |||||
Last edited by Tigerstyle Wutangfist; 05-17-2022 at 10:36 PM..
|
#70
|
||||||||||
|
Quote:
According to the research posted in this thread, they should not drop primal at 100%, pre or post sleeper. This suggests 20%. Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
| |||||||||
Last edited by nilbog; 05-18-2022 at 09:41 AM..
|
Thread Tools | |
Display Modes | |
|
|