Deprecated Darkstar fourms

Chocobo model is part of animation 5, which means you cannot set a "look" value to change it as such. It is probably a sub-animation value that currently isn't being used on dsp. Feel free to tinker with it.

I would honestly recommend trying to manually apply the patch first. If you find that too difficult to do, then the patch has probably been made irrelevant by more recent changes and will require some consideration to re-implement.

HKEY_LOCAL_MACHINE\SOFTWARE\[Wow6432Node\]PlayOnline[US|EU]\InstallFolder "0001" has your install path for FFXI. Wow6432Node is only for users of 64-bit windows You should find ONE of PlayOnline PlayOnlineUS or PlayOnlineEU depending on what version of the client you installed. If you have more than...

You can also configure your mysql server to be more forgiving about timeouts to try to prevent the connection loss in the first place (at some significant performance penalty when the server is used by many programs).

Home/Workgroup makes zero difference. 1)What you need to do is close your server, go back to the zoneip section in the setup guide, and set it to your LAN IP address instead of localhost. That will allow people on your internal network to connect. If you then need to run a client on the SAME system ...

Changing the item name in the database does NOT do what you think it does. Item names are totally 100% client-side. Changing the name in the database changes the name of the script the server tries to execute when an item is equipped or used.

You cannot add an arbitrary item. The client will not know how to handle it. You must use an existing item id and you cannot change things like whether something is equippable without creating more problems. You can find an itemid with polutils or using ffxiah.com.

I could look it up, but i seem to recall the amount being reduced differently than other MDT items when it was implemented specifically to avoid the cap altogether.

If everyone playing is on the LAN then you are better off using the LAN IP. Otherwise you will have to hairpin everyone in unless your router supports hairpinning on its own (98% don't because of how NAT routers work).

Would also recommend you only "get" the var once per trigger action and store it in a local variable. The way you have it right now the DB can be queried 4 times to do the exact same thing, and generally will be when someone triggers the NPC with none of the quest requirements active. DB transaction...