News:

SMFNew Installed

+-+-

User+-

Welcome, Guest.
Please login or register.
 
 
 

Login with your social network

Forgot your password?

Site Stats+-

Members
Total Members: 728
Latest: Cho
New This Month: 0
New This Week: 0
New Today: 0
Stats
Total Posts: 10932
Total Topics: 795
Most Online Today: 389
Most Online Ever: 854
(September 18, 2024, 07:49:37 am)
Users Online
Members: 0
Guests: 191
Total: 191

Author Topic: Triggerable annoyance  (Read 1701 times)

0 Members and 48 Guests are viewing this topic.

Triggerable annoyance
« on: »
As gytfunke implied in this thread  http://forums.runicgames.com/discussion/58093/walkthrough-triggerables-for-playerskills

Quote
The triggerable has a cooldown of 950ms on Fire Brand. I believe what this means is that the triggerable is only going to attempt to cast the skill every 950ms, whether or not the target is burning. If the target isn't burning, the proc won't cast, but you'll still have to wait the 950ms for another chance for the triggerable to activate. It's not a huge issue, but certainly bears consideration for your own skills.

Has anyone got any idea how to keep the triggerable from triggering without its statwatcher?

I got a skill that procs hp regen at low health when attacked and its suppose to be an emergency skill with a fairly long cooldown. Now I had to resort to lowering the proc cooldown so that the skill procs can proc often or else, it'll goes cooldown at the wrong time. 

And another question : Does anyone have the list of things that can be used for the SUBTYPE?

Share on Bluesky Share on Facebook


Re: Triggerable annoyance
« Reply #1 on: »
Sorry @Viz im having trouble imagining how the code might look, but my first reaction is "just reduce the cool-down even more".

If okay with you, can you copy-paste the code you're looking at into this thread?


Re: Triggerable annoyance
« Reply #2 on: »
Yea sure @Phanjam


Seems like reducing the skill's cooldown is the only way to go. Oh well.

Re: Triggerable annoyance
« Reply #3 on: »
I did not fully understood the problem... can't you set the triggerable to trigger as often as possible but the proc skill's cooldown as high as you want it to be?

What conditions you want for that skill

here's the dropdown list from inside GUTS:
Spoiler: SUBTYPE (hover to show)
some projects in progress

Re: Triggerable annoyance
« Reply #4 on: »
I did not fully understood the problem... can't you set the triggerable to trigger as often as possible but the proc skill's cooldown as high as you want it to be?

What conditions you want for that skill

here's the dropdown list from inside GUTS:
Spoiler: SUBTYPE (hover to show)
Oh yea, that might work too. I forgot that proc can have a cooldown, silly me. Thanks for the SUBTYPE list.

EDIT: I tried setting the proc cooldown to 15 sec and the triggerable to 100 ms.. the skill still procs often so I guess it didn't worked.
« Last Edit: September 17, 2017, 09:05:59 pm by Viz »

Re: Triggerable annoyance
« Reply #5 on: »
Unrelated but anyone knows list of things that can be used for STATNAME/STATMODIFYNAME  inside affixes?

I've seen some rare ones like PLAYER AVG ITEM LEVEL and "character max damage righthand"
and they work.
« Last Edit: October 04, 2017, 01:25:42 am by Viz »

Re: Triggerable annoyance
« Reply #6 on: »
Hey Viz, here's a list of all pre-existing static stats that can be used in those fields:

docs.runicgames.com


You can also use any dynamic stats that you declare in the Stat Editor.



It's odd that your cooldown isn't working on the procced skill.  Setting the cooldowns the way you have should work correctly.  When the triggerable condition is met it should try to fire the proc skill every 100ms.  The proc skill should cast only as often as its cooldown.

Maybe double-check your syntax, spelling, etc.  Posting the text for your files might allow someone else to notice something you've missed.

Re: Triggerable annoyance
« Reply #7 on: »
Oh.. there's already a list of them. I should've read Runic Wiki more often. Thanks gyt!  :P

About the triggerable, I'll check it again sometime later.

 

Recent Topics+-