User:Sewil/issues

Report your Mega Extractorerrors 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