BigT

Thank you

Update npclist.txt in root with the last from gameforge client

 

 

 

Use this, it's already done.

This is the hidden content, please

• Sign In
• or
• Sign Up

&nbsp;Thank you very much <3

&nbsp;

Of course open normal_attack.msa &amp; normal_attack1.msa

and change

HittingType          1

by

HittingType          2

&nbsp;

Server-side or client-side?

Guys, calm down.

 

I'm gonna release a new hotfixed version (with invisibility bug etc. fixed), debugging is back and some optimizations are gone because they made some problems.

Still pending test.

 

And please, as I said before. Think before you're reporting a bug. Many of the things you state here are only made by misconfiguring your server and not the vanillacore itself.

Can you check assassins or skipia dungeon?

Where ninjas attack with dagger they log out to login screen, if the use bow is ok.

 

Thanks in advance

Please post syserr.

Hi all, I'm getting this error only in channel 99: 

SYSERR: Jun 20 17:49:58 :: Process: UNKNOWN HEADER: 136, LAST HEADER: 0(0), REMAIN BYTES: 4911, fd: 28
SYSERR: Jun 20 17:50:05 :: Process: UNKNOWN HEADER: 182, LAST HEADER: 0(0), REMAIN BYTES: 4922, fd: 28
SYSERR: Jun 20 17:50:11 :: Process: UNKNOWN HEADER: 223, LAST HEADER: 0(0), REMAIN BYTES: 4941, fd: 28
SYSERR: Jun 20 17:50:11 :: Process: UNKNOWN HEADER: 45, LAST HEADER: 0(0), REMAIN BYTES: 4960, fd: 28
SYSERR: Jun 20 17:50:11 :: Process: UNKNOWN HEADER: 84, LAST HEADER: 0(0), REMAIN BYTES: 4979, fd: 28
SYSERR: Jun 20 17:50:12 :: Process: UNKNOWN HEADER: 162, LAST HEADER: 0(0), REMAIN BYTES: 4998, fd: 28
SYSERR: Jun 20 17:50:12 :: Process: UNKNOWN HEADER: 118, LAST HEADER: 0(0), REMAIN BYTES: 5017, fd: 28
SYSERR: Jun 20 17:50:12 :: Process: UNKNOWN HEADER: 58, LAST HEADER: 0(0), REMAIN BYTES: 5036, fd: 28
SYSERR: Jun 20 17:50:12 :: Process: UNKNOWN HEADER: 36, LAST HEADER: 0(0), REMAIN BYTES: 5055, fd: 28
SYSERR: Jun 20 17:50:12 :: Process: UNKNOWN HEADER: 152, LAST HEADER: 0(0), REMAIN BYTES: 5074, fd: 28
SYSERR: Jun 20 17:50:13 :: Process: UNKNOWN HEADER: 84, LAST HEADER: 0(0), REMAIN BYTES: 5093, fd: 28
SYSERR: Jun 20 17:50:13 :: Process: UNKNOWN HEADER: 158, LAST HEADER: 0(0), REMAIN BYTES: 5112, fd: 28
SYSERR: Jun 20 17:50:13 :: Process: UNKNOWN HEADER: 194, LAST HEADER: 0(0), REMAIN BYTES: 5131, fd: 28
SYSERR: Jun 20 17:50:13 :: Process: UNKNOWN HEADER: 140, LAST HEADER: 0(0), REMAIN BYTES: 5150, fd: 28
SYSERR: Jun 20 17:50:13 :: Process: UNKNOWN HEADER: 47, LAST HEADER: 0(0), REMAIN BYTES: 5169, fd: 28

Client crash and go back to login screen.

Can someone help me, please?

Thanks in advance!

There is a bug with anti exp pc.block_exp(). If I use pc.block_exp() I can donate all the exp I want to my guild! Please fix it

The drop of the poly marbles is in common_drop_item.txt look for the vnums I said before

Now I drop the poly marbles, but when I right click nothing appens.

Thanks

&nbsp;

Because that won't work, do what i said

I set the polymorph item. Have I to edit common_drop_item or mob_drop_item is ok?

&nbsp;

That's not how it's done.

&nbsp;

In mob_proto you can find a field called poly_vnum where you enter the vnum of the polymorph he should drop (70104-70107)

&nbsp;

To adjust their drop rate use common_drop_item.txt

Added the vnum to drop_item, but the sphere doesn't polymorph my character It says "You can't read this book"

&nbsp;

Group	poly_2052{	Type	drop	mob	2052	1	70104	1	0.001}

Works for me

&nbsp;

Thank you :*

Hi guys, how do I set the drop of a Polymorph Sphere from a mob?

A command to reload drop would be really useful (:

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?

 

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

Thank you Vanilla, I really appreciate your work!

 

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

BUG REPORT!!!!

Trigger "kill" is bugged.

 

If you use this trigger in the following way, it will work.

quest test begin
     state start begin
          when kill begin
               chat("hello")
          end
     end
end

But if you use the trigger in this way, it won't work!!!

quest test begin
     state start begin
          when 101.kill begin
               chat("hello")
          end
     end
end

Please fix this bug!

Thanks in advance.

ITEM_FLOOR_TIME is bugged.

Hello.

There is a bug with empire chat (only Chunjo):

Link is dead :-(

 

EDIT: Solved

Hi all! The question is the same of the title.

Here we should say something about our hosting provider.

 

 

I'm currently hosting my server on eterhost and all is ok so far