[dev1008] Make Fish HP Server-sided, not only client-side.

[Raxiaz]

In my many years of FFXI I've come to understand that the fish's HP is client-sided information only, where the server has no monitor on it until it's 0%, wherein it can accept the user's input to reel in the fish/item/monster/whatever.

Because of this many bots simply just alter the fish's HP value to 0, without actually fighting the fish. This straight 100% -> 0% should be a huge indicator that a bot is being used. So, SE, to help cut back on abuse, making the HP server-sided is a step in the right direction. All of these bots can, presumably, simply fight the fish after the fix. But I'm sure it will throw many of them off.

Thanks for reading.

[Freebytes]

I really like this suggestion. The implementation may be difficult, but it would dramatically decrease the bots that rely on this exploit.

[Nidhogg]

Nidhogg likes this post.

[Myrrh]

But then how will Urat fish? D:

[Alukat]

i really like the idea. only issue might be ping & lags which can mess up fishing.

[Arcon]

In my many years of FFXI I've come to understand that the fish's HP is client-sided information only, where the server has no monitor on it until it's 0%, wherein it can accept the user's input to reel in the fish/item/monster/whatever.

Because of this many bots simply just alter the fish's HP value to 0, without actually fighting the fish. This straight 100% -> 0% should be a huge indicator that a bot is being used. So, SE, to help cut back on abuse, making the HP server-sided is a step in the right direction. All of these bots can, presumably, simply fight the fish after the fix. But I'm sure it will throw many of them off.

Does it really work that way? I find this a bit hard to believe. I thought the current system already uses server-side information, the client only allows some unchecked interaction, which it corrects if it disagrees with the server (which is why sometimes fish magically come back to life, the client thinks the player caught it, but the server says POIDH and transmits the fish's actual HP), which is why fishers always wait a second at 0%, before reeling the fish in.

I fully agree though, that it should be server sided only. Lag would be an issue, as it is with everything else in this game as well, but the server could make some adjustments, like give the user a flat 0.1s time to react. It would be better than right now, where the server does its own thing and can occasionally result in lost fish, broken lines and broken rods, when the client clearly said the fish was at 0%.

[Raxiaz]

The server only reads the fish's HP, honestly, when you press the enter button to send the information. If the server was monitoring the fish's HP and saw that it went from a solid 80-100% to 0% in less than 3 seconds, something is up. Many fishing bots will act like they're fighting the fish, but most just have a wait variable of when to reel in. So it acts legit in the wait time, but when it wants to reel in the fish all it does is modify its HP to 0, and reels it in. The server has no idea what just happened either, because it seriously thinks the character was legitimately fighting the fish. It wasn't monitoring the fish's HP.

I know this will not have a permanent fix on fishing bots. But I do know that it throw a lot of them off. SE will probably see a lot of bot fishers if they made this adjustment, if they can make it. I know with the way the game was coded there's a lot that SE wishes they could do, but can't due to the development process.

[Byrth]

This is how it works and how it has always worked. The client used to also choose what fish/item was on the line.

[Malamasala]

Are you sure the client chooses that? Makes it sound like you could just send him "khroma ore" as information in that case. Though SE could have some check that it at least was a fish.

[Arcon]

Are you sure the client chooses that? Makes it sound like you could just send him "khroma ore" as information in that case. Though SE could have some check that it at least was a fish.

He said "used to choose", so I'm guessing it's fixed. I still find this a bit hard to believe though. How come fish sometimes come back from the dead? I can't really explain it with this client-side model. At least I always thought it was calculated server-side, precisely because of this glitch.