Re: A thread not about casting
Posted: June 14th, 2019, 12:09 am
Good to see you anyway.
A Mondain's Legacy era Ultima Online freeshard.
https://uogdemise.com/community/
I came back for the "Airing Of The Grievances"The Silvertiger wrote:Good to see you anyway.
Yes!marm wrote:GO DAWGS!
You and those mutts..........The Silvertiger wrote:GO DAWGS!
The delayed spell damage is indeed a little off. We are planning some timing changes that should go in effect next server wars to fix this.Loler wrote:Dg nailed it. But there's more wrong with the casting then just that. Delayed spell damage is still off. Overcasting penalty is still to aggressive. (Time to cast after finishing a spell is to long)
We have noticed the participation of new accounts in the poll and will account for this when the poll is closed.Anthony File wrote:Seems like we’re going to lose OSI casting to a 14 year old with a mass amount of spam accounts?..
Chivalry still has a 250ms delay between spells when you have 6 FCR equipped, so Chivalry cannot go into overcasting. (Much like Magery with 5 FCR equipped.) This is the case on OSI as well. Holding down a Chivalry spell button I cannot seem to trigger overcasting with 6 FCR there. It would require 7 FCR.royal kapero2 wrote:And chiv spells needs a serious fix, chiv spells weren't taken into account when they half fixed the casting. I killed some "Alone man", he was just holding a chiv heal and saying huahua, then I threw fukiya and that broke his pvp plan, so he died. Later I killed him 3 other times and he started trash talking because his exploit didn't work.
Archers do need to stop moving to shoot normally. Our 500ms delay seems accurate, though brief testing on OSI shows the value to be more random and sometimes higher (perhaps similar to spell casting). We will need to look into this!royal kapero2 wrote:PS: Can you confirm or deny If archers need to stop moving for a longer time to shot?
That is an interesting find. Regardless of the delay in your macro, you are targeting yourself with a magic arrow and casting a spell right after with the same delay on both the damage and spell cast. Since you target the damage first, it will tick first on Demise, and disrupt yourself right before your spell completes casting. This behavior makes sense.Loler wrote:Just used this macro starting the pause line at 25 then raising by 25 every 10 attempts till i got to 250
I got interrupted casting gheal every time. The way you said you wrote the delay it should have worked at one of the intervals but never worked at any.
cast 'magic arrow'
waitfortarget 1500
pause 250
target! self
cast 'greater heal'
The same exact macro on OSI will work 100x out of 100.
Any chance you can look more into monster and pet AI?Eos wrote:That is an interesting find. Regardless of the delay in your macro, you are targeting yourself with a magic arrow and casting a spell right after with the same delay on both the damage and spell cast. Since you target the damage first, it will tick first on Demise, and disrupt yourself right before your spell completes casting. This behavior makes sense.Loler wrote:Just used this macro starting the pause line at 25 then raising by 25 every 10 attempts till i got to 250
I got interrupted casting gheal every time. The way you said you wrote the delay it should have worked at one of the intervals but never worked at any.
cast 'magic arrow'
waitfortarget 1500
pause 250
target! self
cast 'greater heal'
The same exact macro on OSI will work 100x out of 100.
You are right, however, that on OSI the spell will cast fine. Perhaps spell disruption checks if the spell is done casting, even if it hasn't ticked yet. This will not be fixed by the update planned for tonight as designed currently, but we will look into it.
So much for not caring anymore, eh?Loler wrote:Yeah I posted similar information in the bug section with video proof of both but it makes sense to answer it in a general discussion thread months later.
https://www.uogdemise.com/community/vie ... 14&t=29049
I think you posted it when eos was on her vacation. The other staff can’t be bothered to interact with the community soooLoler wrote:Yeah I posted similar information in the bug section with video proof of both but it makes sense to answer it in a general discussion thread months later.
https://www.uogdemise.com/community/vie ... 14&t=29049