mob repop locations.
Description
I don't know how to easily post a log of this one. Sorry!
It's not a huge deal but it does tilt the balance of the area some. It creates more empty rooms, and it can stack too many in other rooms that become more deathtrap-y
Carrion Fields on 2024-03-13 15:36 UTC
Automatically imported from the legacy bug board forum.
Ishuli on 2024-03-14 00:33 UTC
Subject: This is the whole MUD
The entire MUD works this way. This isn't area specific.
Dallevian on 2024-03-14 01:40 UTC
Subject: Probably. Butâ¦
If you had a unique mob for each room wouldnât it prevent it? It only happens when mobiles are reused? In this scenario and in this area and with the repop timer it seems needful.
Ishuli on 2024-03-14 14:06 UTC
Subject: RE: Probably. Butâ¦
That's true MUD-wide too. Nothing here is specific to the area.
Kalageadon on 2024-03-14 14:19 UTC
Subject: No idea the logged info but.
A few years back the IMM team asked that mobs that repop and don't go back to the same room they spawn in, but spawn in another mob's room of the same type, be noted so that they could be fixed or standardized.
As example, dark guards from old arial city were a great example. You have rooms in a row that are 9 wide, and you kill the ones on the east of center and when they repop, they don't go to the east rooms, they pile up in the west rooms. I don't recall which IMM but they wanted to be notified when this stuff happens so it can be fixed/standardized.
This was because of the way they were set was to repop them in specific room order, one after another, until the total number for that area was met rather than the intended rooms they were supposed to be in.
This made learning in certain places difficult or impossible if the process went on too long.
This could lead a person who found a situation like this to think it may be a bug or oversight.