Hard no. Do not encourage the messing about with block related code. After all these years the vast majority of block bugs have finally been resolved. Lets not tempt fate.
Hard no. Do not encourage the messing about with block related code. After all these years the vast majority of block bugs have finally been resolved. Lets not tempt fate.
This would be a simple client-side rendering change. No need to touch any actual blocking logic, only some visual flourishes that trigger from the block event being received. It's a safe, one-way data transfer that can't affect the block logic. If you wanted to be even 'safer' about it then the 'safest' way would be something as easy as making the icon an invisible texture. Literally no logic changed anywhere with something like that.
sounds like and adventure for 5 patchesHard no. Do not encourage the messing about with block related code. After all these years the vast majority of block bugs have finally been resolved. Lets not tempt fate.
This would be a simple client-side rendering change. No need to touch any actual blocking logic, only some visual flourishes that trigger from the block event being received. It's a safe, one-way data transfer that can't affect the block logic. If you wanted to be even 'safer' about it then the 'safest' way would be something as easy as making the icon an invisible texture. Literally no logic changed anywhere with something like that.
Hard no. Do not encourage the messing about with block related code. After all these years the vast majority of block bugs have finally been resolved. Lets not tempt fate.
This would be a simple client-side rendering change. No need to touch any actual blocking logic, only some visual flourishes that trigger from the block event being received. It's a safe, one-way data transfer that can't affect the block logic. If you wanted to be even 'safer' about it then the 'safest' way would be something as easy as making the icon an invisible texture. Literally no logic changed anywhere with something like that.
It wouldn't be. Animation code is embedded in the action code, and that code is spaghetti - ZOS' word for it, not mine.
Hard no. Do not encourage the messing about with block related code. After all these years the vast majority of block bugs have finally been resolved. Lets not tempt fate.
This would be a simple client-side rendering change. No need to touch any actual blocking logic, only some visual flourishes that trigger from the block event being received. It's a safe, one-way data transfer that can't affect the block logic. If you wanted to be even 'safer' about it then the 'safest' way would be something as easy as making the icon an invisible texture. Literally no logic changed anywhere with something like that.
CameraBeardThePirate wrote: »The block indicator is necessary in PvP, where visual clutter makes it difficult to see if someone is holding their weapon at a slightly different angle. It provides an immediate and easy-to-recognize signal that your target is blocking
CatalinaWineMixer2 wrote: »Please do not change this. It is useful for many people and there are bigger issues that need more attention in combat.
CameraBeardThePirate wrote: »The block indicator is necessary in PvP, where visual clutter makes it difficult to see if someone is holding their weapon at a slightly different angle. It provides an immediate and easy-to-recognize signal that your target is blocking