[DiscordArchive] Hello, I need some help. I am looking for how script a spell, and noticed that we have the table in
[DiscordArchive] Hello, I need some help. I am looking for how script a spell, and noticed that we have the table in
Original source
Hello, I need some help. I am looking for how script a spell, and noticed that we have the table in sqldb - "spell_proc"
That spell_proc contains duplicates about procs , that we already have in db2 data about spells.
Why should I duplicate proc info in spell_proc? Just because scripting?
rektbyfaith
03-19-2025, 06:17 AM #1Archived author: Boka • Posted: 2025-03-19T06:17:49.692000+00:00
Original source
Hello, I need some help. I am looking for how script a spell, and noticed that we have the table in sqldb - "spell_proc"
That spell_proc contains duplicates about procs , that we already have in db2 data about spells.
Why should I duplicate proc info in spell_proc? Just because scripting?
Original source
spell_proc is for the in-depth details about a proc. when exactly to proc, which spells allow it. also spell_proc uses the same pattern as spell_script_names which means -[spellId] = all ranks, otherwise per rank
rektbyfaith
03-19-2025, 06:18 AM #2Archived author: Northstrider • Posted: 2025-03-19T06:18:45.527000+00:00
Original source
spell_proc is for the in-depth details about a proc. when exactly to proc, which spells allow it. also spell_proc uses the same pattern as spell_script_names which means -[spellId] = all ranks, otherwise per rank
Original source
I see that, but, i thought if data is missing in spell_proc - it is ok, just is not overrided, core looks in db2.
But in real life it seems to be "you should provide this info if you want script to work"
I would like to know: Must I provide proc data and put it in spell_proc every time I make a script? or Core takes this data in db2 when it's missed
rektbyfaith
03-19-2025, 06:21 AM #3Archived author: Boka • Posted: 2025-03-19T06:21:44.505000+00:00
Original source
I see that, but, i thought if data is missing in spell_proc - it is ok, just is not overrided, core looks in db2.
But in real life it seems to be "you should provide this info if you want script to work"
I would like to know: Must I provide proc data and put it in spell_proc every time I make a script? or Core takes this data in db2 when it's missed
Original source
db2 only contains proc flags and cooldowns. the rest is missing
rektbyfaith
03-19-2025, 06:25 AM #4Archived author: Northstrider • Posted: 2025-03-19T06:25:03.222000+00:00
Original source
db2 only contains proc flags and cooldowns. the rest is missing
Original source
spell_proc is only needed when you need to apply extra conditions to a proc. also no, it's not mandatory for spell scripts. spell scripts even have their on checkProc/checkeffectproc hook
rektbyfaith
03-19-2025, 06:25 AM #5Archived author: Northstrider • Posted: 2025-03-19T06:25:48.521000+00:00
Original source
spell_proc is only needed when you need to apply extra conditions to a proc. also no, it's not mandatory for spell scripts. spell scripts even have their on checkProc/checkeffectproc hook
Original source
thanks) I need to eat it
rektbyfaith
03-19-2025, 06:26 AM #6Archived author: Boka • Posted: 2025-03-19T06:26:31.989000+00:00
Original source
thanks) I need to eat it
Original source
the procflag and cooldown columns should be left at 0 when not needed to make the core use the db2 values
rektbyfaith
03-19-2025, 06:26 AM #7Archived author: Northstrider • Posted: 2025-03-19T06:26:46.855000+00:00
Original source
the procflag and cooldown columns should be left at 0 when not needed to make the core use the db2 values
Original source
It’s just interesting if Blizard does not provide more information in dB2 about procking, does this mean that spell does not work like a near Blizard and requires code-refactory?
Just if I were a developer near Blizard and decided to make a spell system, I would keep the information locally for the server, or stored in dB2, but I would keep it in one place without duplication. After all, duplication = possible error.
rektbyfaith
03-19-2025, 06:37 AM #8Archived author: Boka • Posted: 2025-03-19T06:37:27.373000+00:00
Original source
It’s just interesting if Blizard does not provide more information in dB2 about procking, does this mean that spell does not work like a near Blizard and requires code-refactory?
Just if I were a developer near Blizard and decided to make a spell system, I would keep the information locally for the server, or stored in dB2, but I would keep it in one place without duplication. After all, duplication = possible error.
Original source
they only ship data in db2 that's somehow used within the client. This is not an actual representation of their own database
rektbyfaith
03-19-2025, 06:56 AM #9Archived author: Northstrider • Posted: 2025-03-19T06:56:16.096000+00:00
Original source
they only ship data in db2 that's somehow used within the client. This is not an actual representation of their own database
Original source
they have WAY more fields on their own end
rektbyfaith
03-19-2025, 06:56 AM #10Archived author: Northstrider • Posted: 2025-03-19T06:56:27.654000+00:00
Original source
they have WAY more fields on their own end
1 Guest(s)
1 Guest(s)