[ Dead Download Link ] Vanilla Core 2.4.1 [ We Need You ]

[BigT 5]

 

use

 

quest test begin

     state start begin
          when kill with npc.get_race() == 101 begin

               chat("hello")
          end
     end
end

This is normally a bug with multiple kill triggers which is in every core.

 

ATTR_CHANGE_LIMIT is still the same, nothing changed. It's in seconds, not minutes.

 

In 2.4 101.kill or 102.kill ecc... was working.

In 2.4.1 no

[SirGath 1]

Can someone help me?

[Vanilla 1451]

One reason is that 101.kill is deprecated long time ago. The reason behind this is that two 101.kill-trigger will intercept each other. Two kill with npc.get_race() == 101 will not intercept each other and work without any flaws.

Additionally the double count was fixed. That caused the old 101.kill to not work anymore, but it prevents you from not triggering it two times like it was before.

Actually, yes, it is a bug because it's not intended to break the old 101.kill. But I don't see any reason to fix it because it was buggy before and there's no reason in using 101.kill.

 

@SirGath: It's clearly not the vanilla core's fault. I also use vanilla core and I don't have this bug.

 

pet.is_mine() is approved to work. I'll have a further look on that.

[BigT 5]

Thank you Vanilla, I really appreciate your work!

[iExChange 1]

One reason is that 101.kill is deprecated long time ago. The reason behind this is that two 101.kill-trigger will intercept each other. Two kill with npc.get_race() == 101 will not intercept each other and work without any flaws.

Additionally the double count was fixed. That caused the old 101.kill to not work anymore, but it prevents you from not triggering it two times like it was before.

Actually, yes, it is a bug because it's not intended to break the old 101.kill. But I don't see any reason to fix it because it was buggy before and there's no reason in using 101.kill.

 

@SirGath: It's clearly not the vanilla core's fault. I also use vanilla core and I don't have this bug.

 

pet.is_mine() is approved to work. I'll have a further look on that.

 

Can you help me?

[BigT 5]

 

One reason is that 101.kill is deprecated long time ago. The reason behind this is that two 101.kill-trigger will intercept each other. Two kill with npc.get_race() == 101 will not intercept each other and work without any flaws.

Additionally the double count was fixed. That caused the old 101.kill to not work anymore, but it prevents you from not triggering it two times like it was before.

Actually, yes, it is a bug because it's not intended to break the old 101.kill. But I don't see any reason to fix it because it was buggy before and there's no reason in using 101.kill.

 

@SirGath: It's clearly not the vanilla core's fault. I also use vanilla core and I don't have this bug.

 

pet.is_mine() is approved to work. I'll have a further look on that.

 

Can you help me?

 

Replace when 101.kill with when kill with npc.get_race() == 101 in all your quests

[LadySelene 0]

Hey I cannot find the command for the config where i can set the rates. I need the command pls. Can somebody help ?

[Vanilla 1451]

Hey I cannot find the command for the config where i can set the rates. I need the command pls. Can somebody help ?

 

Which rates do you want to change? Actually there's no CONFIG-option to change the rates. You can adjust the exp-table or edit the mob_proto to set exp/gold rates. And dropp rates can be adjusted at the mob_drop_item.txt, etc...^^

[RatCatcher 77]

I know it's bad to ask here, but please, can you tell me how did you fix the command_log to work properly? What was bad? Can't find what's bad. Thanks

[luzzo 195]

One reason is that 101.kill is deprecated long time ago. The reason behind this is that two 101.kill-trigger will intercept each other. Two kill with npc.get_race() == 101 will not intercept each other and work without any flaws.

Additionally the double count was fixed. That caused the old 101.kill to not work anymore, but it prevents you from not triggering it two times like it was before.

Actually, yes, it is a bug because it's not intended to break the old 101.kill. But I don't see any reason to fix it because it was buggy before and there's no reason in using 101.kill.

 

@SirGath: It's clearly not the vanilla core's fault. I also use vanilla core and I don't have this bug.

 

pet.is_mine() is approved to work. I'll have a further look on that.

 

i think that isn't totally correct.

 

Double 101.kill of course intercept each other but  execute just the fist in alphabetical order.

I don't know if you manage npc.get_race() or it was managed already in the 40k rev but when i used 2089m rev with npc.get_race() there was a real problem with the execution of this function;indeed when you are killing a metin or a different kind of mobs all togheder, it didn't count every time the metin.

In a killing test , on 10 metin just 2 was counted.

 

Finally, I want to congratulate you ,even if i don't use vanilla core ( i have my own one), for your grat job.

 

Reguards Luzzo

[Vanilla 1451]

 

One reason is that 101.kill is deprecated long time ago. The reason behind this is that two 101.kill-trigger will intercept each other. Two kill with npc.get_race() == 101 will not intercept each other and work without any flaws.

Additionally the double count was fixed. That caused the old 101.kill to not work anymore, but it prevents you from not triggering it two times like it was before.

Actually, yes, it is a bug because it's not intended to break the old 101.kill. But I don't see any reason to fix it because it was buggy before and there's no reason in using 101.kill.

 

@SirGath: It's clearly not the vanilla core's fault. I also use vanilla core and I don't have this bug.

 

pet.is_mine() is approved to work. I'll have a further look on that.

 

i think that isn't totally correct.

 

Double 101.kill of course intercept each other but  execute just the fist in alphabetical order.

I don't know if you manage npc.get_race() or it was managed already in the 40k rev but when i used 2089m rev with npc.get_race() there was a real problem with the execution of this function;indeed when you are killing a metin or a different kind of mobs all togheder, it didn't count every time the metin.

In a killing test , on 10 metin just 2 was counted.

 

Finally, I want to congratulate you ,even if i don't use vanilla core ( i have my own one), for your grat job.

 

Reguards Luzzo

 

 

I never had any problems with the npc.get_race() maybe it's already fixed in 40k, but as far as I know there are plenty servers running with 2089 and they also use the new way with npc.get_race().

And yeah, I know that one gets executed, but people want both to be executed.

Let's say you have a quest that's triggering when you kill the lv40 metinstone. And then you go to dt. Only one of both can be used and if the newer quest is first in the order (as you said alphabetical) you can't use the dungeon anymore.

That's just for example.

 

[luzzo 195]

 

 

One reason is that 101.kill is deprecated long time ago. The reason behind this is that two 101.kill-trigger will intercept each other. Two kill with npc.get_race() == 101 will not intercept each other and work without any flaws.

Additionally the double count was fixed. That caused the old 101.kill to not work anymore, but it prevents you from not triggering it two times like it was before.

Actually, yes, it is a bug because it's not intended to break the old 101.kill. But I don't see any reason to fix it because it was buggy before and there's no reason in using 101.kill.

 

@SirGath: It's clearly not the vanilla core's fault. I also use vanilla core and I don't have this bug.

 

pet.is_mine() is approved to work. I'll have a further look on that.

 

i think that isn't totally correct.

 

Double 101.kill of course intercept each other but  execute just the fist in alphabetical order.

I don't know if you manage npc.get_race() or it was managed already in the 40k rev but when i used 2089m rev with npc.get_race() there was a real problem with the execution of this function;indeed when you are killing a metin or a different kind of mobs all togheder, it didn't count every time the metin.

In a killing test , on 10 metin just 2 was counted.

 

Finally, I want to congratulate you ,even if i don't use vanilla core ( i have my own one), for your grat job.

 

Reguards Luzzo

 

 

I never had any problems with the npc.get_race() maybe it's already fixed in 40k, but as far as I know there are plenty servers running with 2089 and they also use the new way with npc.get_race().

And yeah, I know that one gets executed, but people want both to be executed.

Let's say you have a quest that's triggering when you kill the lv40 metinstone. And then you go to dt. Only one of both can be used and if the newer quest is first in the order (as you said alphabetical) you can't use the dungeon anymore.

That's just for example.

 

 

 

 

Yes , i'm totally according you but it's always better have both.

As you said:

"you have a quest that's triggering when you kill the lv40 metinstone. And then you go to dt. Only one of both can be used and if the newer quest is first in the order (as you said alphabetical) you can't use the dungeon anymore."

That's the reson of different vnum of tower's metin.

I hope that's a reason for 101.kill and npc.get_race() even if ymir's code never end to surprice me.

[Ev4ng3li0n 0]

@Vanilla How can i make global chat for all reign with vanilla_core 2.4. 

A thing like that: https://metin2.download/picture/mGBsUb6CqcHyDYqYeUjUvaRjgYg5yC82/.png

 

 

Edited August 29, 2022 by Metin2 Dev
Core X - External 2 Internal

[Vanilla 1451]

Use 2.4.1 there the global chat is fixed.

[Ev4ng3li0n 0]

Use 2.4.1 there the global chat is fixed.

Have i to change something in client side?

[LadySelene 0]

Hey Vanilla. Well my Problem is that when i turn on the rates it only shows 200.Doesnt matter what i type in it keeps on 200 rates.. 

[Life 13]

Edit: Found Soloution

[Minion 73]

Vanilla fix ext_table guild, guild level > 20

[Dev S. 1]

Hey, Vanilla

I created this account to say THANK YOU !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

FCK damn nice work

But i have the same problem with global chat, just red empire work ( by the way it looks nice ) and blue/yellow is still buggy ( u see the color code )

i use 2.4.1 and in my uichat.py is nothing, but why just red work ? i rly dont understand i think its because the core file

 

Edit 2:

 

v: rename syslog to ./log/20140612/syslog.00: No such file or directory

a some milliseconds lag occur if i see the message in putty, or my server is bad ?

 

EDIT 3 :

if u have auto attack on and if u die and respawn it still attack on metin stone without clicking something, its clientside or serverside ?

 

 

by the way nice work rly nice work

[deadman 31]

Vanilla i have a suggestion for the functions of pet:

 

When you use pet.summon(value, value, value)  the pet shows the name of the character who summon him.

 

Its posible do create other function for example: pet.summon_noname(value, value, value) and he dont show the name of character only the name of the pet?¿

 

 

[deadman 31]

Sorry double, post i do a missclick

[ThePanic 1]

How do I resolve?

https://metin2.download/picture/r3F9504x09DVmF8K988YXgTtGTP6KMUj/.gif

Edited August 15, 2022 by Metin2 Dev
Core X - External 2 Internal

[BigT 5]

How do I resolve?

https://metin2.download/picture/r3F9504x09DVmF8K988YXgTtGTP6KMUj/.gif

Same problem for me.

 

When your character reborn sometimes it remains invisible. It's only for me?

Edited August 15, 2022 by Metin2 Dev
Core X - External 2 Internal

[ThePanic 1]

 

Come posso risolvere?

https://metin2.download/picture/r3F9504x09DVmF8K988YXgTtGTP6KMUj/.gif

Stesso problema per me.

 

Quando il tuo personaggio rinasce a volte rimane invisibile. E 'solo per me?

 

No, I only have that problem.

Edited August 15, 2022 by Metin2 Dev
Core X - External 2 Internal

[iExChange 1]

How do I resolve?

https://metin2.download/picture/r3F9504x09DVmF8K988YXgTtGTP6KMUj/.gif

 

I have the same problem

Edited August 15, 2022 by Metin2 Dev
Core X - External 2 Internal