Issue Information
-
#006354
-
4 - High
-
Fixed
Issue Confirmations
-
Yes (0)No (0)
0
Originally posted by Kenpachi
r16522
r16522
[Warning]: npc_parsename: Name 'Job Change Location Change Notice#hugel' is too long (len=39) in file 'npc/pre-re/jobs/2-1/hunter.txt', line'34'. Truncating to 24 characters.<br />[Error]: Loading NPC file: npc/pre-re/jobs/2-1/wizard.txt<br />script error on npc/pre-re/jobs/2-1/wizard.txt line 68<br /> parse_simpleexpr: unmatch ')'<br /> 63 : next;<br /> 64 : mes "[Wizard Guildsman]";<br /> 65 : mes "Ok, then. Farewell.";<br /> 66 : close;<br /> 67 : }<br />* 68 : if (WZRD_Q',' == 0) {<br /> 69 : mes "[Wizard Guildsman]";<br /> 70 : mes "Huh? What are you doing way up here...?";<br /> 71 : mes "So what brings you here?";<br /> 72 : next;<br /> 73 : switch (select("I want to become a Wizard.:...nothing.")<br />) {<br />[Error]: script error on npc/pre-re/jobs/2-1/wizard.txt line 506<br /> parse_simpleexpr: unmatch ')'<br /> 501 : next;<br /> 502 : mes "[Raulel]";<br /> 503 : mes "What do you want? Jeez...just get lost, won't you?";<br /> 504 : close;<br /> 505 : }<br />* 506 : if (WZRD_Q',' == 0) {<br /> 507 : mes "[Raulel]";<br /> 508 : mes "*cough* *cough* *sneeze* I don't know who you are and what you do, but I don't have any business with you.";<br /> 509 : next;<br /> 510 : mes "[Raulel]";<br /> 511 : mes "Go away! Get lost!";<br />[Warning]: npc_parsename: Name 'Room of Water#Door Keeper' is too long (len=25) in file 'npc/pre-re/jobs/2-1/wizard.txt', line'1964'. Truncating to 24 characters.<br />[Warning]: npc_parsename: Name 'Room of Earth#Door Keeper' is too long (len=25) in file 'npc/pre-re/jobs/2-1/wizard.txt', line'2149'. Truncating to 24 characters.<br />[Error]: script error on npc/pre-re/jobs/2-1/wizard.txt line 2525<br /> parse_simpleexpr: unmatch ')'<br /> 2520 : mes "I don't have time for people like you!";<br /> 2521 : close2;<br /> 2522 : cutin "",255;<br /> 2523 : end;<br /> 2524 : }<br />* 2525 : if (WZRD_Q',' == 0) {<br /> 2526 : cutin "job_wizard_maria01",2;<br /> 2527 : mes "[Dog]";<br /> 2528 : mes "Ah...I know what you're about to say. You want to change jobs to a Wizard, right?";<br /> 2529 : next;<br /> 2530 : mes "[Dog]";<br />[Error]: npc_enable: Attempted to hide a non-existing NPC 'Room of Water#Door Keeper' (flag=4).<br />[Error]: npc_enable: Attempted to hide a non-existing NPC 'Room of Earth#Door Keeper' (flag=4).
Originally posted by Masao
Fixed in [rev=16525]
Fixed in [rev=16525]
Originally posted by EvilPuncker
also you forgot to add a sql update file to change old permanent char variables to the new ones, since you broke any server that got any player in the middle of the quest
also you forgot to add a sql update file to change old permanent char variables to the new ones, since you broke any server that got any player in the middle of the quest
Edited by EvilPuncker, 28 July 2012 - 08:48 PM.
Originally posted by Kenpachi
Yeah that's right EvilPuncker. Thanks.
Yeah that's right EvilPuncker. Thanks.
Originally posted by Kenpachi
What's wrong with you Masao? EvilPunker is absolutely right. So either fix it or leave it for someone else to fix, but don't set it to "Fixed" when it's not fixed!
What's wrong with you Masao? EvilPunker is absolutely right. So either fix it or leave it for someone else to fix, but don't set it to "Fixed" when it's not fixed!
Originally posted by Masao
Dude, check out the changelog and you'll see that I completly reverted all changes made to the jobchange files 2 or 3 days ago, so everything is back to where it was and working as it should, so wtf is wrong with you dude changing it always back from "Fixed" to "Confirmed".... ?!
Dude, check out the changelog and you'll see that I completly reverted all changes made to the jobchange files 2 or 3 days ago, so everything is back to where it was and working as it should, so wtf is wrong with you dude changing it always back from "Fixed" to "Confirmed".... ?!
Originally posted by Kenpachi
Maybe you should just leave a note instead of simply changing the status. It's not my or any other developers duty to check every commit...
Maybe you should just leave a note instead of simply changing the status. It's not my or any other developers duty to check every commit...
Originally posted by EvilPuncker
my point still persist even with latest update, perm variables changed.
my point still persist even with latest update, perm variables changed.
Originally posted by Masao
Which did change? They should all have stayed the same since I used the original ones from the files before.
Which did change? They should all have stayed the same since I used the original ones from the files before.
Originally posted by EvilPuncker
I really didn't looked into all files, but you may check acolyte.txt
old: job_acolyte_q
new: ACO_Q
I really didn't looked into all files, but you may check acolyte.txt
old: job_acolyte_q
new: ACO_Q
Originally posted by Euphy
Yes, a lot of the variables still have changed and some variable values, as well. This is being discussed, and we'll do something about it shortly.
Yes, a lot of the variables still have changed and some variable values, as well. This is being discussed, and we'll do something about it shortly.
Originally posted by Masao
Well sorry about that, but I care absolutly not at all about 1st class job change variables
It would be an huuuuuge incident if someone is currently on any of the very very few servers out there which uses the official job change quests instead of an job changer NPC and is currently doing the 1st class job change quest and that such an server is immediatly updating their server to the new scripts so that those players wouldn't be able to continue the quests.
This is like a one in a million chance.
Well sorry about that, but I care absolutly not at all about 1st class job change variables
It would be an huuuuuge incident if someone is currently on any of the very very few servers out there which uses the official job change quests instead of an job changer NPC and is currently doing the 1st class job change quest and that such an server is immediatly updating their server to the new scripts so that those players wouldn't be able to continue the quests.This is like a one in a million chance.
