|
Post by Acaos on Jul 9, 2010 14:48:14 GMT
Correct, it's for building and hosting modules.
Acaos
|
|
|
Post by CataclysmicDeath on Jul 9, 2010 14:55:31 GMT
Ok thanks, I'm probably not going to be of much use then. I don't host any modules and can't build to save my life, much as I might wish I could Cata
|
|
|
Post by Werehound Silverfang on Jul 10, 2010 7:45:53 GMT
So...
I have HGLL along with SIMTools set up within the server (onenter, onexit, onload, x2_def_activate, levelup, onchat is empty, etc) and the nwnx.ini points to fky_chat a dn fky_chat_srv.
When loaded with NWNx (outside of NWNIAB), HGLL works, but trying to send a tell crashes thee server (usual behavior for me at this point, so I haven't been using SIMTools), However, when using NWNIAB, it tells me LETO is registered and CHAT is registered, but HGLL wont work (player gets booted, no changes made), but tells don't crash the server (however, absolutely no chat is logged regardless of my settings). Are Leto and nwnxchat setup to work with NWNIAB. Also, how do I access the NWNeXalt tools and commands. =)
A lot I know, but I'm eager to use the full extent of this nice tool.
|
|
|
Post by Acaos on Jul 10, 2010 7:50:27 GMT
Did you edit the NWNX configuration inside the VM? You can do that by pressing LEFTCTRL+A 0 to get to a terminal, then 'nano nwn/nwnx2.ini'.
Acaos
|
|
|
Post by Werehound Silverfang on Jul 11, 2010 3:53:38 GMT
Chat is working once I changed it, but Leto is still having issues.
Also, how would I sue the function int SetAbilityScore (object oCreature, int nAbility, int nValue);
Script won't compile as it doesn't recognize the command.
|
|
|
Post by Acaos on Jul 11, 2010 4:25:54 GMT
|
|
|
Post by Werehound Silverfang on Jul 11, 2010 5:06:41 GMT
I'll double and triple check and get back to you. Thanks!
|
|
|
Post by Werehound Silverfang on Jul 11, 2010 8:57:43 GMT
Ah ha!
My issue was Shayan's subrace system conflicting with Leto (I had made another change).
Now that nwnx_funcs is working, I no longer need Shayan's system.
Everything is working wonderfully except...
The server isn't showing in the GameSpy list. I'm currently forwarding ports to the machine hosting the server. Do I need to forward it to the IP that NWNIAB gives me?
I can play with it tomorrow and figure it out, I'm sure. I'll double check all the settings from the instructions and such as well.
Amazing program.
|
|
|
Post by Acaos on Jul 11, 2010 9:43:19 GMT
You'll need to edit your ~/nwn/nwnplayer.ini file and set 'GameSpy Enabled=1'. You'll also need to either add local port forwarding on your PC or switch to bridged networking for the VM. To add local port forwarding through VirtualBox NAT, open a DOS prompt on your host computer in the VirtualBox program directory (often C:\Program Files\Oracle\VirtualBox) and enter: VBoxManage setextradata "NWNIAB" "VBoxInternal/Devices/pcnet/0/LUN#0/Config/nwn/HostPort" 5121 VBoxManage setextradata "NWNIAB" "VBoxInternal/Devices/pcnet/0/LUN#0/Config/nwn/GuestPort" 5121 VBoxManage setextradata "NWNIAB" "VBoxInternal/Devices/pcnet/0/LUN#0/Config/nwn/Protocol" UDP (There are three commands above, each on their own line, in case your browser line-wraps them, as mine seems to do on my laptop) You'll need to do that with the VM shut down. If you're running Windows Firewall, you'll likely get an Unblock request when starting up the VM again (at least, I did on XP and Server 2003). I did just test this and it worked - I forwarded UDP port 5121 on my router to my PC, then used the internal VirtualBox NAT forwarding to forward port 5121 on my PC into the VM proper, using the above three commands entered at the DOS prompt. Acaos
|
|
|
Post by Werehound Silverfang on Jul 11, 2010 20:16:57 GMT
So... ipconfig from the DOS prompt on my computer tells me my local IP is 192.168.1.101...
Running the server I can only see it in the LAN network, and it tells me my IP is 192.168.1.109.
The VM tells me the IP is 192.168.1.103
Forwardign ports to 192.168.1.109 made the server appear on the list.
;D ;D ;D
|
|
|
Post by Acaos on Jul 11, 2010 20:24:09 GMT
So... ipconfig from the DOS prompt on my computer tells me my local IP is 192.168.1.101... Running the server I can only see it in the LAN network, and it tells me my IP is 192.168.1.109. The VM tells me the IP is 192.168.1.103 Forwardign ports to 192.168.1.109 made the server appear on the list. ;D ;D ;D I presume then that you switched to Bridged instead of using the VirtualBox NAT forwarding trick from above? Make sure you are only forwarding UDP port 5121 if that's the case - don't forward everything, because the VM has no real security by default (for example, the root and mysql passwords are published). Only forwarding the NWN port means people can't access the secure services from outside your LAN (and using VirtualBox NAT port forwarding means the 'LAN' is limited to being on your PC only). Acaos
|
|
|
Post by Werehound Silverfang on Jul 11, 2010 21:19:08 GMT
Hmm. Never realized it, but the server when running through the VM isn't seeing my previous databases (which I use for item/gp bank and guild statuses).
|
|
|
Post by Acaos on Jul 11, 2010 22:07:34 GMT
What kind of databases were you using before? The Bioware campaign databases, or a MySQL database?
Acaos
|
|
|
Post by Werehound Silverfang on Jul 11, 2010 22:09:50 GMT
Bioware Campaign.
|
|
|
Post by Acaos on Jul 11, 2010 22:56:29 GMT
You can copy that into the VM by doing (in a shell window): cp /nwn/database/* ~/nwn/database Acaos
|
|