SweeTs

Changeset 331 Quests rework (part 2), Misc Quest rework - Ty roko91. - Addition of Q417, Q420. - Recode of Q605, Q606. - Fix the invalid reward id on Q405. - previous commit got all details about what is added, removed, edited on existing quests. This commit is effective from Q401 up to latest quest. Compared to roko91 patch : - Drop useless exitQuest(true) on STATE_STARTED. - Q403 : fix onKill for npcId 27038. Extract getItemEquipped( checks to avoid code repetition. - Q405 : fix onKill (could infinitely drop the qItem), revert hasAtLeastOneQuestItem use (wrong logic, it's && and not ||). - Q415 : addition of a missing Gantaki HTM, cond 9. - Q417 : move cond 2 obtention (to avoid permanent setInt/sound). - Q419 : improve Martin's STATE_STARTED case. - Q420 : Wrap Mimyu talk in a cond 4 check (avoid an exploit). Fix an if/else in Maria. Fix a permanent setInt/sound on Byron, when "deluxestone" occurs. Drop useless items checks on dragons cond 6/7. - Q421 : cleanup STATE_CREATED. - Q508, Q509, Q510, Q601, Q602 : general cleanup. - Q617 : revert npcId 31271 01 and 02 HTMs to handle STATE_CREATED easily. - Q618 : cleanup cond/items checks on onAdvEvent( - Q644, Q645, Q646, Q647, Q649 : general cleanup. - Q651, Q652, Q653 : use Location[] instead of int[][] to hold positions. Misc - rename getIsSpoiledBy() to getSpoilerId(). Same for setter and _variable. - fix the Class Master and simplify the code using ItemHolder, ty Hasha. - create a dedicated Class Master, npcId 50006. Revert L2Class of 31228 to L2Npc. - revert to initial buffer visuals. The amount of text generated by skill names is too big in few cases, leading to client crash. - fix and cleanup Ketra/Varka buff system (the last buff was out of index check).

That's hilarious .. There is even no info about the way you want them to become a noble. Anyway, I won't bother :P

Locked then .. :D

Locked then.

Locked.

The walk ? Check npcwalkers_routes :) Like spawn mob -> go from point a to b -> if inside range -> attack

Kinda wrong section, but well.. Good luck :D

You could get a GM position, but for sure you won't be able to create items, set enchant, edit chars and so on. Just basic stuff, like announcements and blabla :) At least normal / serious project would do like that.

Probably GM position @ server.

The structure of frozen is other than l2j's so its not gonna be "like that" - thats my point why its "not working". Pure c/p wont work :P

lol, seriously .. ? That would cost like .. hmm 5 euro ? Even its not worth 5 :D

I have posted them (some months ago) their fix, and ppl claim 'it's not working'.. So, I doubt he can 'adapt' their fix. Well ..

:troll: I did not know about that. I "never" played chronicle above interlude, I do not rly like them.. Thanks for the info, may be handy ;)

Indeed, there is no hope for brainless ppl. They only come here when THEY need help, when they get it, bb. "What you take is what you give" - but in this case, he get all the cookies and he let us shiet. You ruined everything.. Topics w/o answer should not be locked, else junked. My 50 cent before I go to sleep.

You could at least say the solution, its a community, you know.

Looks like solved, then I will lock it. :> If not or you have further question related to the topic, then pm for unlock.

Have you tried to reinstall your L2 ? Maybe it's some kind of client issue. Is your server online for public so other ppl can test it ? So, you will know if it's your client problem or files. Also, don't bump your topic after 3min of your last post, lol.

It's not that bad, but sometimes it simply may be too dark, at least for some other ppl :)

Yeah, but you can see shit :troll: Render is too dark and dat triangle .. well, it's somethin 'different'. You and your traingles :)

I dont, too dark :P

So, it's on sql table - weapons -> duration row :) Also, you have to edit client side in order the "remaining time" will be displayed. So, while testing put low value like 1 (it's gonna disappear when you equip) or 2 (it's gonna disappear after 1min and you will get a msg about that).

If you are talking about "shadow item" like, then add this to your xml (depends of the pack you use) <set name="duration" val="60" /> val in minutes.

If someone still would like to know the asnwer. Turn off "low details" :D