View Single Post
  #39  
Old 01-30-2023, 04:29 PM
DeathsSilkyMist DeathsSilkyMist is offline
Planar Protector

DeathsSilkyMist's Avatar

Join Date: Jan 2014
Posts: 8,176
Default

Quote:
Originally Posted by ya.dingus [You must be logged in to view images. Log in or Register.]
Is that C or C++ it's hideous looking.
It's C++, but I agree I am not a fan of the coding style lol.

Quote:
Originally Posted by Jimjam [You must be logged in to view images. Log in or Register.]
 


Even eq emu isn’t classic. Classic eq was janky!

The way bypassing stun checks in classic would work often returned an autointerrupt.

I think the best known one is landing a bash on a giant with a rune would auto interrupt it (because no stun check and no damage done bypassed all the checks so eq went ‘herp derp no checks passed so spell casting is interrupted).

FSI on a sk that would use rune for aggro/damage absorb was actually a draw back!
Of course EQEMU isn't classic. But that is what we have to work with, and that is the codebase P99 is based off of. I don't think we will ever get the actual server-side codebase for a build of Everquest in the Classic-Velious era. EQEMU is basically rebuilt from the ground up using packet sniffers as far as I am aware.

I am simply pointing out that the EQEMU codebase doesn't have special spell interrupt code for stuns specifically resisted by FSI. Occam's razor is currently on my side, since the assumption should be the code hasn't changed significantly. Until P99 releases the source code we will never know for sure, but if someone wants to assert the code works differently, they will need to provide some evidence as to why they think that. As I said, a thread discussing FSI where a developer responded would show they were at least thinking about changing the code. Or perhaps patch notes discussing FSI.
Reply With Quote