.SoNiiC.

no

yes

here you have the parts for the collect quests from the official usa locale translate.lua

https://mega.co.nz/#!GdVxgbJJ!HBQNvfTWDUcDs_FFP16EU45kgrO3daTzE5okyYAiZQQ

this is bullshit i got my own src

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

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

with all new affects & skillflags

activate ingame the this eventflag ..

mob_gold 200 and mob_gold_buyer 200

mob_exp 1000 and mob_exp_buyer 1000

Novaline = modified version of mainline_sg made by nova.

does it work on the new mob_proto structure from the beta server ?

upload all your config files and syslog on every gamecore

on which level is the problem ?

run update_limit_time.py with python or delete #define GLOBAL_LIMIT_TIME on limit_time.h

i need them to

Thats all the libs compiled from mainline on freebsd. You have only chance some stuffs on makefile to compile the source without problem.

The quest isnt buggy ! The devilscatacombe quest have the same funktion for check on 2 levels. And now tell me why that quest still work ?

try this

https://mega.co.nz/#!qU8RFJqZ!QRGzUynufidoWIqSgposr3YiYYhBrKCeabYQmsoSvh0

you disabled killed_a_2 that means your quest checks only one time on level 1 or level 3 if monster exist. but this is not the bug.

Apr  7 16:45:49 :: QUEST loading locale/germany/quest/object/killed_A_1/server_timer/flame_dungeon.run : flame_dungeon [sTATE] run
Apr  7 16:45:49 :: XXX AddServerTimer killed_A_1 3510000 0x510cdb40

Apr  7 16:46:00 :: QUEST clear timer 0
Apr  7 16:46:00 :: QUEST clear timer 0

this is the bug. if any server_timer will starts at the same time all running server_timer on that quest will be cleared.

let me give you example.

the firtst QUEST clear timer 0 is for that

Apr  7 16:41:20 :: QUEST loading locale/germany/quest/object/flame_dungeon_45m_left_timer/server_timer/flame_dungeon.run : flame_dungeon [sTATE] run

and the otherone is for

Apr  7 16:45:49 :: QUEST loading locale/germany/quest/object/killed_A_1/server_timer/flame_dungeon.run : flame_dungeon [sTATE] run

if any server_timer will be startet all server_timer on that quest will be canceled and this is the real bug. i dont think that the quest will have a bug. i think its on the gamefile. because its a gamefile before the beta server started.

that cant be work because you disable the check for monsters on level 1 and 3. and this is not the problem. the problem is that any server_timer works on that quest. when a server_timer starts all server_timer will be cleared and this is the problem.

Apr  4 01:09:57 :: XXX AddServerTimer killed_A_1 3510000 0x507fa580
Apr  4 01:10:09 :: QUEST clear timer 0
Apr  4 01:10:09 :: QUEST clear timer 0

thats the problem

i dont know why but it look like that something stops the servertimer.

here is the the official locale ymir.. its not the latest but it can help

why you need it to unpack when everything is unpacked ?

https://mega.co.nz/#!uEFBFAwB!Oml28i0y8Ix3zLLGDiKB-zixpYIUxpo0VO89Oy947eo

All Official Packs with official archiver to creat your own key and packs