User:Sewil/issues

Report your Mega Extractor errors here.

Reports:

Major formatting error
Error message: ID used (leave blank if null): 2710

Version used: 11.1.16

Further information:
 * Job requirements printing every job instead of one class. Very messy.
 * Procedure - hunting monsters will result in e.g. Eliminate 20 . \n Obtain Orange Mushrooms.
 * nextQuest - it does not mean that this quest is unlocked, it just means that after completing the quest, the option to accept or decline the next quest is available right away, instead of closing the dialog UI after completing quest.

Richmond2010 (Talk)  09:32,10/7/2012 (UTC) MapleStory


 * 1) It prints out every possible job ID because sometimes not the full class may be available, for example, in some cases, maybe just Cleric + Priest is available, and in other cases, only Aran II, III, IV is available (Which is later manually rewritten to II-IV), while this system may be messy, it's very detailed, and makes it so that only the jobs that actually are available, are printed out.
 * 2) I don't know what you mean. Do you mean that it says '#Obtain' when it should say '#Eliminate'? I just tried it and it doesn't say '#Obtain' when I should be eliminating something.
 * 3) Should I just remove it then since it doesn't really do any difference?

If there's only one monster eliminated, then it will print If there's 2 monsters eliminated, it prints
 * 1) Eliminate monster.
 * 1) Eliminate 2.
 * 2) Obtain monsters

As for nextQuest, just remove it. Quests will only be unlocked if you meet all of the prerequisites, not a quest that triggers nextQuest. Act.img is actually what will happen if you talk to an NPC, so nextQuest means the quest will be started immediately after the previous quest has completed. 0 is upon accepting the quest, 1 is upon completing the quest.

Richmond2010 (Talk)  05:21,10/8/2012 (UTC) MapleStory

Printing
Error message: NIL

ID used (leave blank if null):

Version used: 12.1.0

Further information: Not really an error, but it is an error with terms. That's all for now. Thank you.
 * 1) 'Level' should be capitalized, because it is a title, similar to 'Charm', 'Ambition', 'Diligence', etc.
 * 2) 'Equipment' should be spelled in full, because the short form equip, formally, is a verb. Although 'equip' is technically correct in informal communication, the wiki should be kept formal.
 * 3) There is this printing error while doing Leafre maps, where the notes print 'This map is only available to Maplers level 15 at least.' It should print 'This map is only available to Maplers at least Level 15.'

Richmond2010 (Talk)  10:16,10/9/2012 (UTC) MapleStory

Thanks for the report.
 * 1) Fixed.
 * 2) Fixed.
 * 3) It was never actually an error, I had just formatted it that way, and since map levels doesn't pop up that much you didn't notice it until now, anyways, fixed.

NPC location error and crash (quest)
Version used: 12.2.1

The quests print out (2850) This is incorrect, because the Dark Lords are different NPCs.
 * 1) Talk to Dark Lord (1052001) located at Hideout, Thief Hideout and Thief Hideout.
 * 2) Talk to Dark Lord (1052127) again.

NPCs with the same name are not the same.

The second line 'Talk to Dark Lord again.' is also incorrect, because the Dark Lord in the second line is different from the first line (I added NPC ID into the lines to show the difference).

EDIT: job = "16400", (if Thief)

EDIT: if Act/1 has 'pop', it means Fame.

charmEXP means 'Charm EXP', insightEXP means 'Insight EXP', willEXP means 'Willpower EXP', charismaEXP means 'Ambition EXP'.

EDIT2:

Error message: String index out of range: -145

ID used: 2859

Version used: 12.2.1

Um... what happened?

EDIT4: It's best to stick with the old format, to ensure the wiki is consistent. The previous format is        To have not started quest Talk to NPC in map. Talk to NPC by clicking on the light-bulb.

Richmond2010 (Talk)  02:01,10/15/2012 (UTC) MapleStory

The error was due to a mistake by Nexon, they forgot to close the map tag, and directly after a '#k' tag came along, made it looking like this: The method replaces the '#k' before it starts searching for '#m', so when it starts looking '#m', it looks like this: Subway #m103020200 and in #m103020300# As you see there is no close tag after the ID (a simple '#') So when it looks for a '#', it will keep going --> until it finds one. Right now that one was at the next '#m', as you see it starts with a '#'.
 * 1) rSubway #m103020200#k and in #r#m103020300##k

So when it's finished with that ID, it will think the ID is: 103020200 and in So when it try's to make it into an int (Integer, simply a number), it will go to the NumericValueException, which has the code catch(Exception e) { map_id = to_return.substring(index_m_start+2,to_return.indexOf(":#",index_m_start+1)); } Which basically means it should instead search for ':#' instead of '#', because some tags end with ':#' instead. Since there is no ':#' tag in the description, it will result in an index error, hence the problem.

And I'm not going to change that, because it's not my fault Nexon America can't code for sh*t. Unless you have some better idea on how to make the program find the ID's? This current system feels a little unbalanced to be honest. I mean it's not the first time Nexon forgets to close tags.

Anyway, I fixed the rest you said, thanks a lot for the bug reports.

EDIT: What you can do is to close the tags manually in the files if you experience any of these errors in the future, unless the error is due to something else, but you can always check and see if all the tags are closed. This error was from the description in "1" from QuestInfo.xml, that's where the method called "prefix_replacer" reacted and sent an error.

EDIT 2: I now made it print out a slightly more descriptive error (what actually comes up in my console). It might look a little advanced but to know it's an error from "prefix_replacer", just look at the new error explanation at the top of the page.

So that's why. Well, I logged in today and the quest says "... Subway Transfer Areak and in Line 1 Area 1. " So Maple's replacing IDs first before replacing font color. Anyway, if the program identifies '#m103020200' but no '#' at the back, it will print '#m103020200' in game.

Richmond2010 (Talk)  15:09,10/16/2012 (UTC) MapleStory

That's odd, because in the other ID, the tag is closed; opposed to the un-closed one;
 * 1) r#m103020300##k
 * 1) rSubway #m103020200#k

Hm... after looking at it closely, see how it says; Subway Transfer Areak, with a 'k' in the end? It means it first took the Map ID, and left out the 'k' after '#', and never closed the first red font tag. So that means it's not closed in game either, they just add stuff in a different order. So either way if you want unclosed font tags or errors, you still have to close that tag manually if Nexon already hasn't (I think like less than 1% is unclosed, not that much)

Incorrect quest print
Version used: 13.0.3

In Investigating the Dark Lord (2613), the extractor prints Quests/14/Helping Nella with Her Problem|Helping Nella with Her Problem in the In Progress section.

For Procedure, the extractor missed out the quests needed to be not started/in progress/complete.

EDIT: In Stealing the Goods, Dark Lord's Delivery is without 'x 0'. In rewards section, there is a missing 'x 1'.

EDIT2: In Yun's Worry 1, the procedure prints Talk to Yun again., but the first step was the light bulb one. The 3rd step should show the map the NPC is located in, because it is not specified in the first step. The extractor also do not recognize Ins items, and printed.

Richmond2010 (Talk)  10:48,10/19/2012 (UTC) MapleStory

Ok I fixed it now, also added Ins for rewards and req items.

Items - rewarded from
Well, from what I saw from Orange, it is weird that Orange is actually "rewarded" in quests that takes them away after completion. What it should be is that
 * 1) Have the extractor look at the 'count' variable.
 * 2) If count < 0, then place quest under "Used in".
 * 3) If count > 0, then place quest under "Rewarded from".
 * 4) If count = 0, ignore quest.

There's no need for "and" in lists.

EDIT: For gender in equip, 0 is Male, 1 is Female. |sex=

EDIT2: There are quests with start dates and end dates. For Event quests (see the one you just did), under Check/0, there is an end variable. This determines whether the quest is accessible or not.

Richmond2010 (Talk)  15:58,10/19/2012 (UTC) MapleStory

Yeah I did that count thing a while after I submitted Orange, though this is how I did it;


 * 1) If Check/0 -> "Used in"
 * 2) If Check/1 -> "Used in"
 * 3) If Check/0 or Check/1 and count = 0, ignore
 * 4) If Act/1 AND count > 0 -> "Reward"

No need to put it in "used in" if it's less than 0 in act/1, because it's going to be in check/0 or check/1 anyway.

And as for equips, I've never seen a page with the variable "sex" in it. I will add the date things for quests too.

No point doing a quest that's expired, no? I'm pretty sure I saw a gender variable somewhere. Let me go find it.

EDIT: The variable is no longer there. When I looked into ThaiMS's files (the discontinued version), the variable is there. I believe that after the Chaos patch, the reqGender variable shifted from the files to the server.

Richmond2010 (Talk)  16:18,10/19/2012 (UTC) MapleStory

I guess we'll have to do it manually then. EDIT: Is there a difference between <string name="end" and <string name="end_t" ? They both seem to have the same value.

They are the same, except that "end_t" is a copy. The extractor should find "end". There's really no point doing expired quests, since the info that was provided cannot be used in-game.

Richmond2010 (Talk)  00:38,10/20/2012 (UTC) MapleStory

Yeah I agree we can delete the expired ones. I did it so that if there is no "end" it looks for "end_t", like a back-up.

Crash
Error message: java.lang.ArrayIndexOutOfBoundsException: 999 ID used: NPC 9010000 Version used: 13.1.3 Crashed with Maple Administrator. Guess the Admin really does her job, not letting the extractor "extract her". Haha…

Other: The locations print for Dark Lord should have two  Thief Hideout s, but only prints out one (different maps with same name).

On another note: NPCs with different IDs normally have different involving Quests and locations, so merging them together in one template may confuse readers.

EDIT: Error message: String index out of range: -1 ID used: QUEST 2047, 2048, 2119 (most likely all quests) Version used: 13.1.3

EDIT2: Jobs I figured out: 2099202 (if Warrior), -2145384446 (if Warrior), -2132740034 (if Warrior), 4198404 (if Magician), 8200 (if Bowman), 8388608 (if Bowman), 32800 (if Pirate), and 32 (if Pirate). There might be more, but these are the more common ones.

For gender, capitalize 'M' and 'F', because it is a title, and do not capitalize 'if', because it is one of the special words that do not need to be capitalized (just like 'and' and 'the').

EDIT3: Error message: String index out of range: -89 ID used: 2813, 2822 Version used: 13.1.2 It is caused by a '#m 102020400#' in the desc. Stupid NexonNA. 2822 - Stupid Nexon put #tIron Hog's Metal Hooves#s. They should replace their translation team soon.

Richmond2010 (Talk)  08:04,10/20/2012 (UTC) MapleStory

Wow, did you know that maple administrator has around 1000 quests? That's why you got an ArrayOutOfBoundsException, because it overrides the array size, which was 999 slots, anyway, I raised the size to 4999 slots. That should be enough. Every other bug is also fixed. Check the readme.txt to see the changes.

Error message: java.lang.ArrayIndexOutOfBoundsException: 1000 ID used: NPC 9010000 Version used: 14.0.0 Wow. Sc*** the Admin.

Richmond2010 (Talk)  03:17,10/21/2012 (UTC) MapleStory

Formatting error
Version used: 14.0.0 Description: Bold text

Bold text should be , for #b, and  for #n.

This is not related to bold text, but the first step in procedure is reverted back to
 * 1) Talk to npc by clicking on the light-bulb.
 * 1) Click on the light-bulb to talk to npc.

EDIT1: The # nodes are removed if the extractor cannot find the string. If the string is not available, then it should be left and not removed.

Richmond2010 (Talk)  06:47,10/21/2012 (UTC) MapleStory

I thought #b was for and #n for and #e for while #k closes ANY tag? That's how I've always formatted it. In that case, what is ?

Oh wait, my bad. It was #e. My fault. But is not a valid wiki code, so it skips it. Same for 'normal'.

Richmond2010 (Talk)  01:03,10/22/2012 (UTC) MapleStory

The problem is then that I have that #k replaces with and not , so I'll have to figure out a way to make it bold with a font tag.

There. Fixed.

Just found out that there are some quests with a dayByDay tag, if it is 1, it is repeatable. This is another kind of repeatable quests.

Richmond2010 (Talk)  05:43,10/22/2012 (UTC) MapleStory

Repetitive locations
Version used: 14.1.1 Description: Repetitive locations (mobs)

The extractor somehow prints multiple same maps for mobs. The extractor should check for one occurrence in a map, and then move on to the next one.

Richmond2010 (Talk)  14:40,10/22/2012 (UTC) MapleStory

Fail, it didn't break the loop when it found an occurrence, it just kept going through the entire "life". Anyway, fixed. Also fixed the dayByDay variable.

Max Level
Version used: 14.1.2

Description: Master level doesn't print for Hardcore mode.

Richmond2010 (Talk)  14:25,10/24/2012 (UTC) MapleStory

Fixed.

Decoded job rewards
Not an error, but I can boldly say that I have decoded the meaning of those random numbers in the job rewards.

If the first digit is 1, then it is Thief. If the first digit is 2, then it is Warrior. If the first digit is 3, then it is Pirate. If the first digit is 4, then it is Magician. If the first digit is 8, then it is Bowman.

On a side note, when a quest is autoStart, the first step "Talk to ... by clicking on the light bulb." has two periods printed.

Richmond2010 (Talk)  13:26,10/25/2012 (UTC) MapleStory

Quest rewards
Well, I figured that the rewards for quests may not necessary be at 1, it can also be at 0. If Act/1 has nothing, and Check/0 has an npc but Check/1 has none, then the rewards will be at Act/0. Also make the extractor to disable printing when both Check/0 and Check/1 has no npc.

I think there is something you may want to look into here. It has got to do with pets and stuff.

EDIT: Well, apparently the job rewards have a different first number for Pirate (9), and there is also Common (10).

Richmond2010 (Talk)  01:59,10/28/2012 (UTC) MapleStory 　　　　　　　　　　　　　　　　 　　　　　　　　　　　　　　　　↑

Very weird.

Sorry for have being so inactive lately. Have been trying to figure out how to do the previous thing with act/0 and act/1. Still working on it. I also did the so called Swedish Scholastic Aptitude Test yesterday, took 8 hours, so I was a little exhausted after that. Anyway, I think I've kind of figured out how to solve the problem. I'll then start on the "weird" job problem.

EDIT: Wait... so both 3 and 9 is pirate? Also, no need to print that it's common. Just means it's available for everyone.

I think you misunderstood the 'Common' part, it just means that the player is rewarded if he is neither of the 5 main jobs.

Richmond2010 (Talk)  13:10,10/28/2012 (UTC) MapleStory

How is that even possible?

It is when the player decides to remain a Beginner.

EDIT: Yes, both 3 and 9 is Pirate. It somehow got knocked in 14.3.5. EDIT2: I'm probably wrong, the Nautilus quests that has job lock -- have multiple starting digits.

Richmond2010 (Talk)  06:17,10/29/2012 (UTC) MapleStory

Realization on quests
This has got to do with
 * 1) Act/1/item, when count is missing
 * 2) Description, e.g. #t4031175:#
 * 3) Job rewards


 * 1) For Act/1/item, when count is missing, it deducts the number of items at Check/1.
 * 2) Description, for #t4031175:#, ignore the colon(s) that are there. There are sometimes more than one colon at the end (I saw that somewhere in ) and if it happens and if it is legit (open tag with proper close tag), then ignore the colon(s) and print as normal.
 * 3) Job rewards have to be done manually. Auto is currently not possible. Job rewards for has been very random. Bloody hell with my "Jobs decoded".

Richmond2010 (Talk)  12:21,10/30/2012 (UTC) MapleStory

Fixed. I'll try to figure out how jobs work, maybe they have multiple ID's in one string. Anyway, when it's jobEx, it's much easier, it's like the equipment job id's.

Quest chains, option to print blocked quests
I&apos;m just wondering if the extractor can print out quest chains, since some chains are long (Book of Ancient), and some, ridiculously long (JP version Silent Crusade, 32 quests). JP has the quests gender locked, 0 Male, 1 Female. If it is not possible or is too hard, then never mind about it.

Is it possible to place an option to be able to print blocked/expired quests? GMS locked JP&apos;s Silent Crusade, so it will have to be done manually unless an option is placed.

Richmond2010 (Talk)  11:00,11/1/2012 (UTC) MapleStory

You do know there's a template now for QuestGauge right? And yes, I can make the extractor print the entire chain, but that would not ease anything for you since it would take the same amount of time as to do it manually, since what takes time is really only when it searches for the locations of the NPCs (It must scan through every file in Map.wz which is 11113 files). What you can do is use the search parameter "-chain" and search for the chain, and then just have that window open and extract the quests one by one. And about the expired/blocked quests, I can make it print out with a notification that pops up just to notify that this is indeed blocked/expired.

Failed tags
Error message: String index out of range: -19

ID used: 3558

Version used: 14.3.2

Suggestion: ignore '#' tags if the ID is invalid.

Other minor: When a quest is selfStart enabled, the first procedure should be "Click on the light-bulb above head." and not left blank. When a quest is selfComplete enabled, the last procedure should be "Click on the book above head.".

EDIT: I just found out what happened to NPC's 'quest involved' The extractor should look for one occurrence in a quest, if the NPC is in Check/0, then go to the next quest. If not, look into Check/1. What the extractor did was it searches both Check/0 and Check/1, so if a quest has the same starting and completing NPC, the quest in the 'quests involved' space will duplicate.

Richmond2010 (Talk)  12:11,11/2/2012 (UTC) MapleStory

selfStart and selfComplete was already added. Though I changed the text to what you said.

Missing quest procedures
Version used: 20720 Description: Whenever the first step is to click on the light bulb, the last step to talk to an NPC is missing, if there is no delivery.

Richmond2010 (Talk)  05:04,11/3/2012 (UTC) MapleStory

Quest rewards (again)
Version used: 14.3.5 Description: If Check/1 does not have an NPC but Check/0 has one, then look into both Act/0 and Act/1 for rewards. (Little White Lie)

EDIT: Map extractor no longer prints script names. Script names should be printed so it is easy to find which portal leads to where.

EDIT2: Put in an extra variable for monster summons, if skill id is 200, then identify 'level'. Look for the summoned id in Skill.wz/MobSkill.img/200/ / (0, 1, 2,...).

Add an extra "|summon= " in the format.

An example is Astaroth (9400633).

Richmond2010 (Talk)  14:52,11/4/2012 (UTC) MapleStory