DSP Server Control application
Posted: Sun Feb 22, 2015 6:02 am
Pulling this, as I have not been maintaining. Sorry if you hoped to use. I can pass the source code if you would like if you wish to update for your own uses.
Go to LandSandBoat
http://forums.dspt.info:80/
I dont know who you are but will you have my server babiesDelaide wrote:Here is the Github link to my DSP server control application.
This application is written in VB.net, and is very rough and early at the current time.
You can access the full source code here, as well as help me build it if you are really interested.
Github link: https://github.com/helixhamin/DSP-Control
IDE: Microsoft Studio Express (Unsure if other IDE's will work, and I apologize, but I cannot help you if you have problems building with other IDE's or on other OSes.)
Features:
Start Server
Restart server
Stop Server
Can map DSP and Ashita file folder to anywhere on your computer (Need to do this before you can launch the server) (Partially fixed. First time you exit, use the x at the upper right corner, not the menu exit. It seems the form does not save when using the File->Exit command. Possibly it exits a different way between the upper right x and the End command I programmed into the ExitToolStripMenuItem? I will need to figure that out in the future. Just select your file paths, then hit the x to exit. It will keep them after that point.)
Launch Ashita
Hide/Show server windows
Future features:
Modify Server Settings (lua and config files)
Back up and restore character databases
Build/rebuild server
Check for updates and pull latest git (So, turn it into something like a 'Check for update' system)
Whatever I find interesting (Like maybe even being able to create customized content, set up and update a DSPWEB, whatever I will do with it later, or whatever others might like to help incorporate)
Eventually, I hope to have this so you can just click a button, download and build an entire server, or update a server. But, one step at a time.
I understand this is a very amateurish app, this is the first app I have released (And the first app I have made since 1999), so it is more of something for me to learn with, but hopefully others can find my vision of how I want this to run appealing and useful.
I will update this thread as more features are released.
Code: Select all
mysql_host: 127.0.0.1
mysql_port: 3306
mysql_login: root
mysql_password: root
mysql_database: dspdb
Code: Select all
msg_server_ip: 127.0.0.1
Code: Select all
#Central message server settings (ensure these are the same on both all map servers and the central (lobby) server
msg_server_port: 54003
msg_server_ip: 127.0.0.1
Code: Select all
#Expansion Icons - 2 Bytes
#
#Byte 1 - Zilart to A Shantotto Ascension
#00000000 Bit0 - Not Used - Original FFXI bit
#00000010 Bit1 - Enables Rise of Zilart Icon
#00000100 Bit2 - Enables Chains of Promathia Icon
#00001000 Bit3 - Enables Treasures of Aht Urhgan Icon
#00010000 Bit4 - Enables Wings of The Goddess
#00100000 Bit5 - Enables A Crystalline Prophecy Icon
#01000000 Bit6 - Enables A Moogle Kupod'Etat Icon
#10000000 Bit7 - Enables A Shantotto Ascension Icon
#
#Byte 2 - Vision of Abyssea to Seekers of Adoulin
#00000001 Bit0 - Enables Vision of Abyssea
#00000010 Bit1 - Enables Scars of Abyssea
#00000100 Bit2 - Enables Heroes of Abyssea
#00001000 Bit3 - Enables Seekers of Adoulin
#00010000 Bit4 - Not Used - Future expansion
#00100000 Bit5 - Not Used - Future expansion
#01000000 Bit6 - Not Used - Future expansion
#10000000 Bit7 - Not Used - Future expansion
Code: Select all
expansions: 4094
Code: Select all
expansions:
Okay, got it, so it is the hex converted to binary. So it is the binary number that is used. Thanks.kjLotus wrote:0xFFE and 4094 are the same number, not sure what you're asking?
Okay, so I just need to make sure the IP for the message server is bound to the lobby IP. I will need to add in different IP configurations for those who use multiple IPs for the different servers.kjLotus wrote:and the message server IP for game servers should point to your login server (which is where the message server is), and the message server IP in the lobby server is just the IP to bind to. so you can bind to LAN only, or localhost only, etc