Stuff being requested.
Description
I'm fairly certain that the in the used to repop without the dying, similar to
Since at least last year it doesn't seem to be the case. Now once someone requests the , they're no longer available outside of killing the and waiting for a repop. That means the area can only be explored once per reboot for a lot of classes since the mobs are generally .
Carrion Fields on 2024-01-13 19:20 UTC
Automatically imported from the legacy bug board forum.
Ishuli on 2024-01-14 00:15 UTC
Subject: Working as intended
Working as intended
Java on 2024-01-14 22:32 UTC
Subject: I really don't think this is intended though
Right now any non-limited WORN item that is requested will eventually repop on that mob, even if that mob is never killed.
The bug is that items carried in inventory do not behave in the same way as items that are worn. They never repop (until the mob is killed or the game reboots). This is most obvious in a certain explore area with a bunch of goodie mobs that carry keys in their inventory.
Again - the code exists so that all non-limited worn items WILL repop. That seems to be the design. This is an (accidental?) exception to that design, with no real rationale on why it would be intentional.
We don't see this in most other areas, because most other areas have worn keys (such as Eil Shaeria, other explore areas).
Fix would be to either make inventory items repop with the exact same frequency as worn items. Alternatively, just make all of those suspect keys become worn items, rather than just in inventory.
Ishuli on 2024-01-15 00:44 UTC
Subject: RE: I really don't think this is intended though
It isn't an accident. It is working as intended.
Dallevian on 2024-01-15 02:46 UTC
Subject: Ok. But why did it change?
It is now literally impossible to explore unless you're first one there after a reboot. I don't understand that. The keys used to repop.
Ishuli on 2024-01-15 03:09 UTC
Subject: It didn't change.
Working as intended.
Dallevian on 2024-01-15 03:32 UTC
Subject: Ok! Sorry for bugging. nt
nt
Ishuli on 2024-01-15 13:35 UTC
Subject: It's fine to bug.
I don't mind a bugboard when someone THINKS there is a bug.
This is just an easy non-debatable one because the code notes are super clear both in function and intent. Everything is working exactly as it has been, exactly as intended, and no bug is present.
If the argument is "I want it changed" then you're up against a hefty series of code notes that make it really clear that this was a purposeful goal. In which case you CAN argue it, but not on the bugboard because I really only glance here at posts to fix stuff and it isn't really a discussion-friendly-location.
Dallevian on 2024-01-15 17:24 UTC
Subject: Word! I meant sorry for bugging you.
I was 99% certain it worked differently in the past. But I'm good with being wrong and admitting it if that's the case, and you went above and beyond stating that it is the case.
I can also understand with how the last room functions with the thing that is opened and how it is only able to be opened once per reboot that it lends even more credibility to me being wrong.
Done brigadiering the original person's bug post. All good and thanks.