I was mining that node

dear blizzard,

i was mining a rich bismuth node, eagerly awaiting the 4 rank 1 ores that would be deposited into my bank, when suddenly it despawned! it’s a miracle, because my bismuth mining cast is less than a second long, but apparently that’s just enough time for you to take away my hopes and dreams.

i gotta tell you something, blizzard. every time a node despawns while i’m trying to rip out all the shiny rocks from it, i cry and i throw up. i’m serious! full-on ugly crying, and i’m a very ugly crier. and the vomit? always has carrots. this, this is what you’re doing to me.

so please, do me a favor. make it such that if a node would despawn while a person is mining it, instead it doesn’t. i’m tired of crying, and i’m tired of cleaning up after my hysterics.

20 Likes

better then what it used to be but your suggestion is a fair one that could be done potentially with a simple conditional statement. Still having it vanish in mid air feels way better then fighting a pack of mobs just to have someone swoop down and mine it right infront of you and it be gone.

3 Likes

Even Palia does this. lol

Also: I very much enjoyed how you wrote your post. :grin::two_hearts:

2 Likes

I stole it. And you can’t have it back.

In seriousness though, they shouldn’t de spawn once you start trying to farm them. But I suspect there might not be a non trivial solution that doesn’t present some exploit risks. You would need to let untrusted clients tell the server not to de-spawn things.

1 Like

Stunning imagery. But I don’t care for the carrot vomit very much. You can have some of my (non-despawned) bismuth if you don’t do it again.

This would be really nice. If you start it, you get it. I don’t see why not.

There was node in a cave in the ohara plains that despawned everytime it was touched

I was mining one of those exploding nodes. I had to move twice to avoid the damage and by the time I got to the end of the cast the third time it despawned…

3 Likes

Need to be careful with that request.

Two bots, that keep alternating/cancelling mining. What’s stopping them from holding the node for as many accounts as they control?

Edit: I do sympathize with the situation.

Almost wonder if maybe small countdown timers above the node, only visible to those are close might be more useful. Let those swooping down know that the node is on its way out.

2 Likes

if botters are just alternating and canceling a mine (or herb, i suppose), then they’re not actually going out and gathering the stuff. the opportunity cost is way high for virtually no benefit to them. i mean, does it really matter if a node stays up indefinitely?

thanks for that memory lol

1 Like

I legit think they must have it in the code to despawn WHILE your mining it as it never despawns before I mine it, always right before I finish mining it

So there I was on Argus, about to open yet another cache

when, it despawned

like seriously. seriously

:crab: :izakaya_lantern: :crab: :izakaya_lantern:

The issue might be, you fly into an area with a node that has 2 seconds left, client is told this and spawns it into the world. 10 seconds later you get to it and click, then your client is told it’s despawned. Most likely de-spawns aren’t even broadcast. If it’s still there when you fly into the area it’s spawned on your client. And it stays there until you click it or leave.

If that’s the case the solution might be to not even let clients spawn a node that’s been tapped.

Just call it a “fickle” node with “shy” ore in it.

1 Like

They need to just make mining and herb nodes client side.

Or maybe once you start the mining “cast”, even if the node despawns before the cast is complete, the cast still completes and gives you the ore.

That way the despawning of the ore node doesn’t change, but the players don’t feel robbed.

/moo :cow:

2 Likes

this is kinda how it was back in the day, where every node was single-tap. nowadays with timer-based despawns, your client still needs to know if a node has been tapped since it’s possible you could also get the node before the despawn timer runs out. if you want it to be a little more responsive, a better solution is to look at the despawn timer of a node as well as the max speed at which your character could gather that node, and if there’s no way you can complete the gather before the node despawns, your client doesn’t render it.

1 Like

Or your character hallucinated it

1 Like

Ya, sending time left to the client and putting that over the node would probably help with the bad experience this currently creates.

Something else that might help is having two timers, a 30 second notice timer and a 1 minute hard despawn. After the 30 second notice timer the server wouldn’t notify clients entering an area there’s a node there.