Downtime Notice: Wednesday, October 15th 9:00 AM - 1:00 PM Eastern (-4 GMT)

wmmt81

Member
So people are finally going to play the game how it is supposed to be played! No more hireling cheezing and high difficulty finally becomes high difficulty again because of resource management. Isn't this what you all wanted? 🤣
I see your point, but that mechanic has been in the game since the inception of hirelings. The vast majority of the time I don't ever summon the hire for assistance. I use it as an insurance policy to avoid wasting my time in a long quest. Maybe if the hires' survivability scaled based on the summoner's reaper points one could just have the hire tag along. Soloing on mid reaper the hires simply get splattered.
I mostly solo while leveling a TR. Running R1 while leveling is just boring so I like to up the challenge even though it takes longer to run the quest. Again, I don't want to waste the time put into a quest so I use hires as an insurance policy. It's a lot cheaper than buying cakes. The challenge for me, at least, is to not use the hire, but I still do not want my time wasted. Parking hires never caused a noticeable issue on the old servers.
 

Mornyngstar

Ymerawdwr
I noticed in Sands that my hire parked at the front never went away. While my hire parked in Lamordia went POOF right on cue. I guess players will eventually figure out a list of which wildernesses are and aren't effected.

Edit: and now I've been in lamordia for 15+ minutes and my hires haven't despawned this time. So odd with the inconsistency
If the hire is placed near the entrance from where Body Snatchers dumps you it does not despawn. The same happened at Amber Temple teleport location. Just outside the wall going down hill hires despawn there. I think it has something to do with permamnently loaded locations for teleporting/DDoor. I am doing more testing.

Also: Korthos, Boarderlands, Sands of Menencharum, Twilight Vale and Cannith Manufactory no matter where you leave the hire they don't despawn. Further testing needed.
 

Dhalgren

Well-known member
My understanding of the work is that the game just now cares whether there is anyone in a wilderness landblock under certain conditions and will no longer retain spaces in a more performance heavy active state if it doesn't need to. So, if you haven't been to a far away place in the kind of space impacting this for a few minutes it will now no longer be loaded. As a result of that, objects in that space go along with the space. This change is being done in some but not all wilderness areas and in some but not all spaces within adjusted wilderness areas. So, in terms of player-facing you'll probably not have to worry about it, unless you are used to parking hirelings or objects in places far away that you don't go back to semi-regularly. If you do, you may see an impact of those objects losing their permanence, and may need to be resummoned/re-placed.
Fantastic, wonderful, etc.

Why couldn't the update notes have said as much? I mean, without all the developer speak which honestly most players don't get?

Just say the thing in the update notes and avoid all the forum drama. It's not hard.

"Hirelings left in certain wilderness areas and which are out of render distance for 2 minutes may despawn. Hirelings within quests are unaffected." Done. How hard would that have been?

Seriously, just put some more thought into writing the damned update notes and you could save yourself all this time having to put out fires on the forums.
 
Top