Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 08/15/17 in all areas

  1. M2 Download Center Download Here ( Internal ) LINK
    1 point
  2. Story: Over time I learned that the SetEvent function can cause weird problems in Metin2, maybe you have this bug or maybe not, I actually encountered this problem and found the fix. How to trigger the bug: 1. Use this quest for a test: quest test begin state start begin when 9003.chat."quest test" begin say("Hey we are doing a test here") local o = select("option 1","option 2") if o == 1 then return elseif o == 2 then return end end end end 2. Now you click on the NPC, choose "quest test" option and don't click on any option(1,2) 3. /transfer your_character with another GM account 4. The character who clicked on "quest test" option and didn't choose any of the sub-options (1 or 2 ) will now have an invisible stucked window on the center and can't click on the ground or click the area in the center of the screen(where the quest ui was before teleportation) How to fix it: 1. Go to uiQuest.py 2. In def MakeQuestion find the SetEvent functions and edit them as below: def MakeQuestion(self, n): global entire_questbutton_number global entire_questpage_number global cur_questpage_number entire_questpage_number = ((n-2)/7)+1 entire_questbutton_number = n if not self.board: return self.btnAnswer = [self.MakeEachButton(i) for i in xrange (n)] import localeInfo self.prevbutton = self.MakeNextPrevPageButton() self.prevbutton.SetPosition(self.sx+self.board.GetWidth()/2-164, self.board.GetHeight()/2-16) self.prevbutton.SetText(localeInfo.UI_PREVPAGE) #self.prevbutton.SetEvent(self.PrevQuestPageEvent, 1, n) # buggy self.prevbutton.SAFE_SetEvent(self.PrevQuestPageEvent, 1, n) # unbuggy self.nextbutton = self.MakeNextPrevPageButton() self.nextbutton.SetPosition(self.sx+self.board.GetWidth()/2+112, self.board.GetHeight()/2-16) self.nextbutton.SetText(localeInfo.UI_NEXTPAGE) #self.nextbutton.SetEvent(self.NextQuestPageEvent, 1, n) # buggy self.nextbutton.SAFE_SetEvent(self.NextQuestPageEvent, 1, n) # unbuggy if cur_questpage_number != 1: cur_questpage_number = 1 Note: After that you should check for other SetEvent functions (comment them and see if the bug still happens) Info: The bug has something to do with the function arguments Other locations where this bug caused problems: intrologin.py - can cause the arrow keys,enter,esc to not work in the select character phase
    1 point
  3. May be specular on i.p? I think its 100 lower it to 50 and check
    1 point
  4. I just stopped replying on such topics because 89% of the members are "devs-like" and try to be smart and the other 10% are not even in the dev scene "leechers". I don't like the way this topic is going but Mali61 what you did is a great job no one had the guts to do the same. "hours of coding -> releasing" I have seen even code that can be lower than this code being sold so it's pretty decent for someone if it's not for you. So bottom line is a release means "say thank you or get the hell out of the topic". The same attacks has happened in another forum in 2009-2012 until those who release has left the scene or gone inactive and that forum is now dead weeks without any releases. This forum's members are going down the same path. The rule is "If I'm not going to release anything, at least I'm not going to criticize anyone that releases anything." Thanks for releasing that system.
    1 point
  5. Does not need tabs in my opinion. Does it open a window when clicking on the npc?
    1 point
  6. If it works on an other npc then its ok. Just send me a screen of your quest and the cube.txt and if possible search on ch1core1 the sysser for possible errors.
    1 point
  7. The system is already been posted here on the forum, as long as you don't know what a well code does why you ask for it? The system that Mali made is the same with the official. As long as there are sh** eaters replying his topic without knowing a word they say is normal that they trigger people not to use it. If you don't know what coding is you don't need to care about the code as long as the final result is the same... They are just "Dev's" spreding around sh** here.
    1 point
  8. 1 point
  9. you have minmax for that, you can just: i didnt dig into the problem tho, so this is to intent as a correction to him and not to a fix for the bug you have. Btw what you did is checking if getmaxhp its minor or equal to 0, then assign 0 again so the = statement even lose his effectivness. If you want to have something more than 0 on p.bHPPercent as min you have to do: p.bHPPercent = MINMAX(1, (GetHP() * 100 / GetMaxHP(), 100); And since you doing the same thing on both checks, you can also if (IsPC() || GetMaxHP() < 0) p.bHPPercent = 0;
    1 point
×
×
  • Create New...

Important Information

Terms of Use / Privacy Policy / Guidelines / We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.