TFS 1.X+ New runes with unpatterned area

[Trevys]

Hi guys, I'm trying to make runes with different areas, and I came across this difficulty.


When I use the rune in one direction, the area goes one way, and when I use it in another direction, the area goes out in another.
It's like some system forces you to invert the area according to the direction the rune is thrown, and I didn't want that, I'd like a fixed area on all sides. I even tested it with other areas to prove this, follow the images.

https://i.gyazo.com/691116d82edf69a8a5c13b0ac7af67ef.gif

combate local = Combate()
combat:setParameter(COMBAT_PARAM_TYPE, COMBAT_FIREDAMAGE)
combat:setParameter(COMBAT_PARAM_EFFECT, 7)


AREA_KUNAI = {
    {1, 1, 1},
    {1, 3, 0},
    {1, 1, 1}
}

combat:setArea(createCombatArea(AREA_KUNAI))



função onGetFormulaValues(player, level, maglevel)
    local min = (nível / 4,5) + (maglevel * 6) + 25
    local max = (nível / 4,5) + (maglevel * 8) + 45
    return -min, -max
fim

combat:setCallback(CALLBACK_PARAM_LEVELMAGICVALUE, "onGetFormulaValues")

função onCastSpell(criatura, variante)
    return combat:execute(criatura, variante)
fim

Does anyone know how I can solve this problem? I know that in normal spells direction="0" solves it, but in runes it's not working

 

[wizzy1231]

Hi guys, I'm trying to make runes with different areas, and I came across this difficulty.
View attachment 69550View attachment 69551

When I use the rune in one direction, the area goes one way, and when I use it in another direction, the area goes out in another.
It's like some system forces you to invert the area according to the direction the rune is thrown, and I didn't want that, I'd like a fixed area on all sides. I even tested it with other areas to prove this, follow the images.

https://i.gyazo.com/691116d82edf69a8a5c13b0ac7af67ef.gif

combate local = Combate()
combat:setParameter(COMBAT_PARAM_TYPE, COMBAT_FIREDAMAGE)
combat:setParameter(COMBAT_PARAM_EFFECT, 7)


AREA_KUNAI = {
    {1, 1, 1},
    {1, 3, 0},
    {1, 1, 1}
}

combat:setArea(createCombatArea(AREA_KUNAI))



função onGetFormulaValues(player, level, maglevel)
    local min = (nível / 4,5) + (maglevel * 6) + 25
    local max = (nível / 4,5) + (maglevel * 8) + 45
    return -min, -max
fim

combat:setCallback(CALLBACK_PARAM_LEVELMAGICVALUE, "onGetFormulaValues")

função onCastSpell(criatura, variante)
    return combat:execute(criatura, variante)
fim

Does anyone know how I can solve this problem? I know that in normal spells direction="0" solves it, but in runes it's not working

Maybe you can try to swap the "
AREA_KUNAI = {
{1, 1, 1},
{1, 3, 0},
{1, 1, 1}
}
" with
local area = createCombatArea(AREA_SQUARE1X1)
setCombatArea(combat, area)

 

[Gesior.pl]

Does anyone know how I can solve this problem? I know that in normal spells direction="0" solves it, but in runes it's not working

direction = 0 - sets spell target position on player, so there is no direction between player and target position - it uses 'NORTH' spell orientation (not rotated)
direction = 1 - sets spell target position 1 tile in front of player, so there is some direction between these 2 positions
but that config is ignored for spells that have target (all runes). For them it takes target position from tile on which player clicked using rune.
Then it goes to 'combat area' calculation that returns 1 of 4 areas generated when you declared new area (rotated 0, 90, 180, 270 degree)

forgottenserver/src/combat.cpp at master · otland/forgottenserver

A free and open-source MMORPG server emulator written in C++ - otland/forgottenserver

github.com

If you don't want to rewrite engine, create 4 combats, each with rotated area and in onCastSpell check direction between player and target. Then select combat that will look as you want after C++ rotate it.

 

[Trevys]

direction = 0 - sets spell target position on player, so there is no direction between player and target position - it uses 'NORTH' spell orientation (not rotated)
direction = 1 - sets spell target position 1 tile in front of player, so there is some direction between these 2 positions
but that config is ignored for spells that have target (all runes). For them it takes target position from tile on which player clicked using rune.
Then it goes to 'combat area' calculation that returns 1 of 4 areas generated when you declared new area (rotated 0, 90, 180, 270 degree)

forgottenserver/src/combat.cpp at master · otland/forgottenserver

A free and open-source MMORPG server emulator written in C++ - otland/forgottenserver

github.com

If you don't want to rewrite engine, create 4 combats, each with rotated area and in onCastSpell check direction between player and target. Then select combat that will look as you want after C++ rotate it.

I understand, so the only way to fix this without creating the 4 areas, would be to change the sources? What if I did post action? Would the area still be inverted?

Maybe you can try to swap the "
AREA_KUNAI = {
{1, 1, 1},
{1, 3, 0},
{1, 1, 1}
}
" with
local area = createCombatArea(AREA_SQUARE1X1)
setCombatArea(combat, area)

Did not work :\

 

[Gesior.pl]

I understand, so the only way to fix this without creating the 4 areas, would be to change the sources? What if I did post action? Would the area still be inverted?

It does not matter where (spells, actions, some addEvent) and how you cast this spell. If it's combat, it has area and it's shot from distance, it will invert area.

 

[Trevys]

It does not matter where (spells, actions, some addEvent) and how you cast this spell. If it's combat, it has area and it's shot from distance, it will invert area.

I understand, so I'll try to create an area for each direction, thank you very much for your attention