WS Quest

[Fwahm]

Linkshell leader of my Dynamis linkshell said he got it at 20 with 5250 points.

[Aikar]

Ill write a plugin to display the points for the people concerned with running third party programs.

Then we can make the people requesting a plugin for it finally shut up! lol

Plus this code will break on patch

[Omegademon]

Sholin, I tried downloading and using your Weapon Checker but I keep getting an error. Unhandled Exception or somesuch, it has a big list of issues but I have no idea what they mean. Have you ever ran into this issue? I am runing Windows Vista by the way if this has anything to do with it.

[neithan]

Sholin, I tried downloading and using your Weapon Checker but I keep getting an error. Unhandled Exception or somesuch, it has a big list of issues but I have no idea what they mean. Have you ever ran into this issue? I am runing Windows Vista by the way if this has anything to do with it.

Most likely you need the latest .NET framework to make it run.

and thank you Aikar for the work on a plugin! I checked over the code and there doesn't appear to be anything out of the unusual, in fact it doesn't even use any networking namespaces.

Also I call bullshit on 5250 points to unlock < POIDH

[Sholin]

Looks like UAC is canning it access to other processes, you have to right click > run as administator.

[Alistaire]

Ill write a plugin to display the points for the people concerned with running third party programs.

Then we can make the people requesting a plugin for it finally shut up! lol

Plus this code will break on patch

Something just a wee bit ironic about the people who run windower making a plugin for "preople concerned with running third party programs".

[rezo]

Sholin, I tried downloading and using your Weapon Checker but I keep getting an error. Unhandled Exception or somesuch, it has a big list of issues but I have no idea what they mean. Have you ever ran into this issue? I am runing Windows Vista by the way if this has anything to do with it.

first, make sure that you have Microsoft FrameWorks 2.0 installed on your PC
second, the program accesses the memory location of your current running ffxi to fatch information, therefore, system admin authority is needed.

always right click on the .exe and choose run as system admin

[Omegademon]

Ah okay, I think that might be it. Only issue is that UAC crashes POL when it brings up comirmation... Sometimes I just want to disable it... Is there a known way around that issue without disabling?


EDIT: I got it to work by starting the weapon checker then opening POL, Thank you very much for this, @273 Points on Killer Bow floor 15 cleared; Should have Floor 20 Cleared tonight.

[dejet]

i got that program. and i was close i said i had over 6000 ws well sorta wrong/

im at floor 10. this is what Weapon checker tells me
9/17/2008 9:00:18 PM
Windslicer : 5894 pts.

my guess is that there might be a glich because at this point why is it counting WS? so its one of two things
the WS quest is gliched at under floor 40(ish)
or it goes up by more then the rest after around floor 20

[dejet]

is there a time where this thing updates or something? because i just used my 2hr geko>yuk>geko>kash and thats 11 points did not go up.

[Fwahm]

Takes 15-20 minutes for it to register for some reason.

Don't worry, it'll show up in the correct numbers.

[Shufflesx]

dejet damn we close, i was off on mine, it said 6027, i logged on someone invited me to one run on nyzul island got to 10, that gave me my assault rank up quest, i went and found footprint first try, and now corporal , all i need is ws now to finsih off a good night

[Tahngarthor]

Here's a link to source (along with personal edit, made item names english) if you can't find it on 2ch. Feel free to pull it apart if you think I'm trying to jack your account, just trying to help out.

To use it, simply run 'WeaponChecker.exe' with FFXI running, it only scans your inventory, so all weapons you want to scan have to be on your person.

It -DOES NOT- update in real time, you have to hit scan again to see the new point value. It also looks like you need to zone to get it to update to the correct count in my testing.

http://img137.imageshack.us/img137/5158/wsjf9.png

http://www.megaupload.com/?d=RGWBTF1D
http://www.sholin.net/nyzul.zip
http://rapidshare.com/files/146155053/nyzul.zip.html

EDIT:
JUST SO IT'S CLEAR: I TAKE NO CREDIT FOR THIS APP, I SIMPLY TRANSLATED THE ITEM NAMES, AND BUTTON TEXT.
All credit goes to 'sage - ◆tUOfNukWcE' of 2ch BBS
http://changi.2ch.net/test/read.cgi/ogame/1221588213/

It appears this program may not be looking for the process correctly on x64.

I don't know very much about it but my understanding is that not much needs to be done to allow operation on an x64 system. Do you know how to make this change? (Given the source is included, it seems like it should be ok). Maybe just compiling it on an x64 system would do the trick? (is this working for anyone on a 64-bit OS?)

-edit- I had a thought, maybe you need to advance your nyzul progress at least once after starting the quest. (even if its not a multiple of 5) It could be a trigger, idk it's a long shot lol just throwing that out there.

-edit2- On my system, this for loop always fails to find the right process module:
foreach (ProcessModule pm in ps[0].Modules)
{
if (pm.ModuleName == "FFXiMain.dll")
It only finds ntdll.dll , wow64.dll , wow64cpu.dll and wow64.dll . wow64 = the emulation layer for running 32 bit applications (FFXI) on a 64 bit system. I could be wrong but it might be masking the actual ffximain.dll .

[Aselin]

This was posted in that 2ch thread: (http://changi.2ch.net/test/read.cgi/ogame/1221588213/)

100  250(95層×0.5) 
 95   500 
 90   625(95層×1.25) 
 85   750(95層×1.5) 
 80   875(95層×1.75) 
 75  1000(95層×2) 
 70  1250(75層×1.25) 
 65  1500(75層×1.5) 
 60  1750(75層×1.75) 
 55  2000(75層×2) 
 50  2500(55層×1.25) 
 45  3000(55層×1.5) 
 40  3500(55層×1.75) 
 35  4000(55層×2) 
 30  5000(35層×1.25) 
 25  6000(35層×1.5) 
 20  7000(35層×1.75) 
 15  8000(35層×2) 
 10 10000(15層×1.25)

I don't know if that is true or not, but that seems to be way too many WS points needed.

Another is this one:

80 875  
 75 1093(80層×1.75)  
 70 1312(80層×1.50)  
 65 2187(80層×1.25)  
 60 1750(80層×2)  
 55 2187(60層×1.75)  
 50 2625(以下同様)  
 45 3062  
 40 3500  
 35 4375  
 30 5250  
 20 7000  
 15 8750  
 10 10500  
 5 12250  
 0 14000

What do you guys think?

[Tahngarthor]

Something just a wee bit ironic about the people who run windower making a plugin for "preople concerned with running third party programs".

he means "third party programs not yet approved by the community" I think.

[neithan]

This was posted in that 2ch thread: (http://changi.2ch.net/test/read.cgi/ogame/1221588213/)
bunch of models from 2ch
What do you guys think?

Seems plausible, Ill let you know when I hit 7000 points for floor 20

[Fwahm]

We already have a confirmed 2800 for 40.

[Shufflesx]

and a couple people got ws at 5500 at floor 20

god, why do i feel like we are trying to solve an ancient riddle, geez se

[rezo]

is there a time where this thing updates or something? because i just used my 2hr geko>yuk>geko>kash and thats 11 points did not go up.

well, need not me to remind you guys, but the actual weapon data is stored on the sever, the one you have in the memory is merely a copy.

FFXI should update the client copy regularly, but not ALWAYS, cuz that will chuck up your network loading. One of the occassion where the FFXI MUST update its client information should be zoneing. so if you feel the number is not updated currectly and you're so despered to see the information, just relog or zone.

[Seraph]

well, need not me to remind you guys, but the actual weapon data is stored on the sever, the one you have in the memory is merely a copy.

FFXI should update the client copy regularly, but not ALWAYS, cuz that will chuck up your network loading. One of the occassion where the FFXI MUST update its client information should be zoneing. so if you feel the number is not updated currectly and you're so despered to see the information, just relog or zone.

Or reequip the weapon? This might explain much of the behavior we have seen so far...