Great job on this repack! I'm enjoying running around and checking things out. A strange issue though:
I have learned Tailoring, Leatherworking, and Skinning. With previous UCW1.3.0 build (and client 1.8.0) I had no issues.
I'm trying this server and whenever I go to a trainer or weapon master, I get no option to train for my characters and a dialog appears over the trainer's head saying I already know 2 professions and they can't help me.
Any idea how to fix this bug? I'm using client 1.11.0 and the 3.21 repack.
Thanks for any help!
-Ex
I know about the edit function, I just wanted to get this to the top of the list so that people knew what was going on.
With the AFGWarrioz 3.21 repack, make sure you make this change to both the MasterScript.tcl and the n_MasterScript.tcl files.
Update: OK, so I decided to spend the rest of the afternoon pouring over the MasterScript.tcl file and fixed this issue with a few lines of code. However, pet, weapon, and talent trainers are suffering from the same thing as the class training issue. I might just sit down and rewrite the entire function, but we'll have to see about that later. The fix, at least to allow 2 professions and class training to work:
Code:
set pclass [GetClass $player]
set npcjobs [join [GetScpValue "creatures.scp" $section "npcjobs"]]
set npcjobs [string tolower $npcjobs]
foreach npcjob $npcjobs {
if {$npcjob == "trainer$pclass"<closebrace> { return 1<closebrace>
<closebrace>
Put this in the "proc CanTrain { npc player<closebrace> {" function after this line:
Code:
set section "creature [GetEntry $npc]"
In my perusings of the creatures.scp file I have noticed that trainers for blacksmithing, leather working, alchemy, herbalism, tailoring, and engineering, for the most part, have a field called qtnpcflags. It's set equal to prof# where # is the number of the skill. It looks like the creatures were set up with it for the main skills shown, but fishing, first aid, and others were not. I might be able to put together a patched creatures.scp with an updated MasterScript.tcl that will fix this issue once and for all. I'm not sure yet, but we'll see.
If anyone has already done this, please step forward and provide the fix. There's no need for me to reinvent the wheel.