First of all let's get started.
REMEMBER, THAT TUTORIAL IS FOR THAT FILES
FOR FUTURE FILES LIKE GUARDIAN VERSION, YOU WILL NEED JUST CHANGE THE IPV4, DON'T CHANGE THE PORTS OR ANY OTHER CONFIGS
Local tutorial / LAN (Setup)
Let's start, first of all, download your files together with your client.You cannot use a different version client on your server.
Step 1 - Database
Extract your files.
And here we finish the database configuration.
This tutorial is based on the files of the Open Desert Online Remastered version.Some files may be different, but in the end it is all the same way to configure.
Let's start with the folder called database.You will open it, and inside it you will have this set of other folders and files:
It didn't fit all the files in the photo, but it is an example.
You delete the "data" folder if it exists and create another "data" folder
If it does not exist, you simply create one.
And here we finish the database configuration.
Now open the "loginserver" folder.
Inside of loginserver folder you will see two folders.
"BIN"and "LIB"
Open the "BIN" folder
Inside the "BIN" folder you will see these files.
Now, open the "Configs" folder
Open the "configs" folder and inside it you will see a bunch of files with the ending ".properties".Be calm, you can open these files with any text editor, from standard notepad to sublimetext and notepad ++.
But you will only focus on these three (Now that you're starting, of course)
Let's start with the file called database.
If you want to change the database password (I do not recommend it, as you are using the local configuration, not online)
You can edit the database.properties and it will look for the lines:
# The database Account.
database.account = EXAMPLE
# The database Password.
database.password = EXAMPLE321
# The database's host address.
database.host = localhost
Now, let's go to the "login.properties" file
Place this setting in login.properties.This configuration is for you to register your account automatically, basically put a login or email in the launcher, a password and when you click "play" it will automatically register in the database.
# Automatic registration for accounts.
# Default: false
login.autoregistration.accounts = true
# Enable auth by token from web.
# Default: true
login.server.token.auth.enabled = true
# Enable auth by email database field.
# Default: false
login.server.auth.by.email = true
Now, let's go to the "network.properties" file
You will follow the following configuration below.
# Rmi connection host.
network.rmi.host = 127.0.0.1
# Rmi connection port.
network.rmi.port = 9000
# Host for server binding.
# Default: 0.0.0.0
network.host = 0.0.0.0
# Port for server binding. EVERY SERVICE HAS HIS/HER OWN PORT
# Default: 8888
network.port = 8888
I'll explain it very simple.The ip "127.0.0.1" is a local ip, so you don't need to put your ipv4 on.
Regarding ports 9000 and 8888, you do not need to open them on the firewall, as you are playing locally, so there is no need to open them.
In relation also to the "0.0.0.0" ip you do not need to change, as it is an ip that redirects, so it will automatically redirect the ip to your ip.
And here we finish the loginserver configuration.
Let's go back to the root and open the gameserver folder.
What are these below
We will again be in order of the image.Let's open the rate.properties fileYou can open them with any text editor
I'm sorry for not explaining much about the item drop rate and others. I will explain it better in another tutorial.
Let's go to the next file.The network.properties.
Here will be the same network settings as the loginserver. However, with a difference in ports, from 8888 to 8889.
You will follow the following configuration below.
I'll explain it very simple.The ip "127.0.0.1" is a local ip, so you don't need to put your ipv4 on.
Regarding ports 9000 and 8889, you do not need to open them on the firewall, as you are playing locally, so there is no need to open them.
In relation also to the "0.0.0.0" ip you do not need to change, as it is an ip that redirects, so it will automatically redirect the ip to your ip.
Here it will be very quick. Just follow the short explanation below
Now let's configure the debug.properties file
Here we will configure to disable server logs, and avoid using high memory and high cpu.Just follow the settings below and the explanation of what each one is.
"debug.collections.spawn.disable" if you set "true" to this setting, it will disable collections from your server, this is a way to further optimize the game. And any form of collection, by mining, collecting trees, etc. will be disabled.
"debug.region.dataload.disable" This setting if you put "True" it will disable the background landscapes when walking the map, when you walk, you can see landscapes very deep, it consumes a little RAM and CPU of your server, but, if you put " true "these landscapes can disappear.
"debug.actions.enable" This setting if you set it to "true" it will show each step of each player, each action he does, with each NPC he speaks, and all of that will show on gameserver.batso it will consume a lot, but, a lot of cpu and ram.
"debug.aiscriptloader.enable" This one applies the same as above, the difference is that it applies to monsters and npcs.
Well, basically this file is an event file, here you can configure the daily rewards (just activate and deactivate)and also the rewards for time online (Yes, you can put pearls for time online and any other item)I will be very brief, because it is not that important, but it is also not useless.
Follow the settings below if you wish to have rewards for logged in time.
Let's go to the explanations.
"events.auto.reward.enable" It is basically if you want to activate this reward for logged time or not, "true" in case you want to leave it activated and "false" in case you don't want to.
"events.auto.reward.time" Basically here you set the time when each reward will come.30 Minutes is the default, so every 30 minutes online the player will earn this reward.
"events.auto.reward.mail.name" Here is basically the name of the email that will come in the "B" tab.You can rename the message to whatever you want.
"events.auto.reward.mail.subject" Here is the name of the subject who sent the email. For example: Staff or Admin.
"events.auto.reward.mail.message" Here is the message you will send via this email, thanking you for playing or anything else.
"events.auto.reward.items" Here basically will be the items that you will send.
The example of 6; 0; 1000It works like this:
6 is the pearl (pearl id = 6)
0 is the enchantment level, you cannot send a pearl in the PEN, right.
1000 is the amount of pearls to be sent.
When you open the gameserver folder, you will see the "bin" and "lib" folders againOpen the bin
When opening the "bin" folder, you will see this bunch of files and folders.But, let's focus on the "configs" folder again.Then open the configs folder.
When opening the configs folder, you will see many ".properties" filesI think you’ll see about 27 or 28.We will focus on only five of them.
What are these below
We will again be in order of the image.Let's open the rate.properties fileYou can open them with any text editor
The rate.properties file is responsible for setting the item drop rate, enchantment rate and others.
I will give a brief explanation, not very detailed.You can edit the drop rates (the enchantment rates are different)through settings.
Example:
1% = 1000
10% = 10000
100% = 100000
I'm sorry for not explaining much about the item drop rate and others. I will explain it better in another tutorial.
Let's go to the next file.The network.properties.
Here will be the same network settings as the loginserver. However, with a difference in ports, from 8888 to 8889.
You will follow the following configuration below.
# Rmi connection host.
network.rmi.host = 127.0.0.1
# Rmi connection port.
network.rmi.port = 9000
# Host for server binding.
# Default: 0.0.0.0
network.host = 0.0.0.0
# Port for server binding. EVERY SERVICE HAS HIS/HER OWN PORT
# Default: 8889
network.port = 8889
I'll explain it very simple.The ip "127.0.0.1" is a local ip, so you don't need to put your ipv4 on.
Regarding ports 9000 and 8889, you do not need to open them on the firewall, as you are playing locally, so there is no need to open them.
In relation also to the "0.0.0.0" ip you do not need to change, as it is an ip that redirects, so it will automatically redirect the ip to your ip.
Now let's go to the next file.The server.properties
Here it will be very quick. Just follow the short explanation below
# External server IP for client connections.
# If localhost use 127.0.0.1
# If docker & localhost use host.docker.internal
# If external - use real ip
server.ip = 127.0.0.1
Now let's configure the debug.properties file
Here we will configure to disable server logs, and avoid using high memory and high cpu.Just follow the settings below and the explanation of what each one is.
# Disable collections spawn
# Default: false
debug.collections.spawn.disable = false
# Disable loading huge region images (for memory economy while tests)
# Default: false
debug.region.dataload.disable = false
# Enable actions debug
# Default: false
debug.actions.enable = false
# Enables AIScriptloader debug
# Default: false
debug.aiscriptloader.enable = false
"debug.collections.spawn.disable" if you set "true" to this setting, it will disable collections from your server, this is a way to further optimize the game. And any form of collection, by mining, collecting trees, etc. will be disabled.
"debug.region.dataload.disable" This setting if you put "True" it will disable the background landscapes when walking the map, when you walk, you can see landscapes very deep, it consumes a little RAM and CPU of your server, but, if you put " true "these landscapes can disappear.
"debug.actions.enable" This setting if you set it to "true" it will show each step of each player, each action he does, with each NPC he speaks, and all of that will show on gameserver.batso it will consume a lot, but, a lot of cpu and ram.
"debug.aiscriptloader.enable" This one applies the same as above, the difference is that it applies to monsters and npcs.
Now let's go to the last file and not least.
Events.properties
Well, basically this file is an event file, here you can configure the daily rewards (just activate and deactivate)and also the rewards for time online (Yes, you can put pearls for time online and any other item)I will be very brief, because it is not that important, but it is also not useless.
Follow the settings below if you wish to have rewards for logged in time.
# Enable Auto reward event.
# Default: true
events.auto.reward.enable = true
# Auto reward each 30 min.
# Default: 30
events.auto.reward.time = 30
# Auto reward mail name.
events.auto.reward.mail.name = Reward!
# Auto reward mail subject.
events.auto.reward.mail.subject = Staff, or other poop
# Auto reward mail message.
events.auto.reward.mail.message = Thanks for play!
# Auto reward ItemId;EnchantLevel;Count
events.auto.reward.items = 6;0;1000
Let's go to the explanations.
"events.auto.reward.enable" It is basically if you want to activate this reward for logged time or not, "true" in case you want to leave it activated and "false" in case you don't want to.
"events.auto.reward.time" Basically here you set the time when each reward will come.30 Minutes is the default, so every 30 minutes online the player will earn this reward.
"events.auto.reward.mail.name" Here is basically the name of the email that will come in the "B" tab.You can rename the message to whatever you want.
"events.auto.reward.mail.subject" Here is the name of the subject who sent the email. For example: Staff or Admin.
"events.auto.reward.mail.message" Here is the message you will send via this email, thanking you for playing or anything else.
"events.auto.reward.items" Here basically will be the items that you will send.
The example of 6; 0; 1000It works like this:
6 is the pearl (pearl id = 6)
0 is the enchantment level, you cannot send a pearl in the PEN, right.
1000 is the amount of pearls to be sent.
Online tutorial (Setup)
Step 1 - Database
Step 2 - Loginserver
Let's start with the file called database.
Now, let's go to the "login.properties" file
Place this setting in login.properties. This configuration is for you to register your account automatically, basically put a login or email in the launcher, a password and when you click "play" it will automatically register in the database.
Now, let's go to the "network.properties" file
You will follow the following configuration below.
"network.rmi.host" I'll explain, basically you need to put your ipv4 here, as the players will connect to it..
Regarding port 9000 you don't need to open it.But as I said at the beginning, you need to open ports 8888 and 8889. Never open port 27017, it is the location of your database, if you intend to open an online server for everyone to enter, never open port 27017, because if you open , some people like me, will connect to your port 27017 and I will place my account as an administrator account.
In relation also to the "0.0.0.0" ip you do not need to change, as it is an ip that redirects, so it will automatically redirect the ip to your ip.
Step 3 - Gameserver
Extract your files.
And here we finish the database configuration.
This tutorial is based on the files of the Open Desert Online Remastered version.Some files may be different, but in the end it is all the same way to configure.
Let's start with the folder called database.You will open it, and inside it you will have this set of other folders and files:
It didn't fit all the files in the photo, but it is an example.
You delete the "data" folder if it exists and create another "data" folder
If it does not exist, you simply create one.
And here we finish the database configuration.
Step 2 - Loginserver
First of all, let's open the doors.8888 and 8889 on the firewall.
Open your firewall and create a new inbound rule, select the option "port" then select "TCP" and then enter the port.You can put it like this: 8888-8889That will already create an entry rule for both ports.
Now open the "loginserver" folder.
Inside of loginserver folder you will see two folders.
"BIN"and "LIB"
Open the "BIN" folder
Inside the "BIN" folder you will see these files.
Now, open the "Configs" folder
Open the "configs" folder and inside it you will see a bunch of files with the ending ".properties".Be calm, you can open these files with any text editor, from standard notepad to sublimetext and notepad ++.
But you will only focus on these three (Now that you're starting, of course)
Let's start with the file called database.
I recommend that you change the database connection password and login. It will be an online server and all servers have a login pattern like "admin" and password like "12345".So it turns out that it is easy for someone to break into your database and screw with your server.
You can edit the database.properties and it will look for the lines:
# The database Account.
database.account = EXAMPLE
# The database Password.
database.password = EXAMPLE321
# The database's host address.
database.host = localhost
Now, let's go to the "login.properties" file
Place this setting in login.properties. This configuration is for you to register your account automatically, basically put a login or email in the launcher, a password and when you click "play" it will automatically register in the database.
# Automatic registration for accounts.
# Default: false
login.autoregistration.accounts = true
# Enable auth by token from web.
# Default: true
login.server.token.auth.enabled = true
# Enable auth by email database field.
# Default: false
login.server.auth.by.email = true
Now, let's go to the "network.properties" file
You will follow the following configuration below.
# Rmi connection host.
network.rmi.host = (Here you will put the ipv4 of your virtual machine or your own computer.)
# Rmi connection port.
network.rmi.port = 9000
# Host for server binding.
# Default: 0.0.0.0
network.host = 0.0.0.0
# Port for server binding. EVERY SERVICE HAS HIS/HER OWN PORT
# Default: 8888
network.port = 8888
"network.rmi.host" I'll explain, basically you need to put your ipv4 here, as the players will connect to it..
Regarding port 9000 you don't need to open it.But as I said at the beginning, you need to open ports 8888 and 8889. Never open port 27017, it is the location of your database, if you intend to open an online server for everyone to enter, never open port 27017, because if you open , some people like me, will connect to your port 27017 and I will place my account as an administrator account.
In relation also to the "0.0.0.0" ip you do not need to change, as it is an ip that redirects, so it will automatically redirect the ip to your ip.
And here we finish the loginserver configuration.
Step 3 - Gameserver
Let's go back to the root and open the gameserver folder.
What are these below
We will again be in order of the image.Let's open the rate.properties fileYou can open them with any text editor
I'm sorry for not explaining much about the item drop rate and others. I will explain it better in another tutorial.
Let's go to the next file.The network.properties.
Here as you already opened ports 8888 and 8889 as TCP ports on the firewall, now we can just configure and place IPV4, as we did on the loginserver.
Follow the tutorial below.
"network.rmi.host" I'll explain, basically you need to put your ipv4 here, as the players will connect to it..
Regarding port 9000 you don't need to open it.But as I said at the beginning, you need to open ports 8888 and 8889. Never open port 27017, it is the location of your database, if you intend to open an online server for everyone to enter, never open port 27017, because if you open , some people like me, will connect to your port 27017 and I will place my account as an administrator account.
In relation also to the "0.0.0.0" ip you do not need to change, as it is an ip that redirects, so it will automatically redirect the ip to your ip.
Here again you will place your IPV4
Now let's configure the debug.properties file
Here we will configure to disable server logs, and avoid using high memory and high cpu.Just follow the settings below and the explanation of what each one is.
"debug.collections.spawn.disable" if you set "true" to this setting, it will disable collections from your server, this is a way to further optimize the game. And any form of collection, by mining, collecting trees, etc. will be disabled.
"debug.region.dataload.disable" This setting if you put "True" it will disable the background landscapes when walking the map, when you walk, you can see landscapes very deep, it consumes a little RAM and CPU of your server, but, if you put " true "these landscapes can disappear.
"debug.actions.enable" This setting if you set it to "true" it will show each step of each player, each action he does, with each NPC he speaks, and all of that will show on gameserver.batso it will consume a lot, but, a lot of cpu and ram.
"debug.aiscriptloader.enable" This one applies the same as above, the difference is that it applies to monsters and npcs.
Well, basically this file is an event file, here you can configure the daily rewards (just activate and deactivate)and also the rewards for time online (Yes, you can put pearls for time online and any other item)I will be very brief, because it is not that important, but it is also not useless.
Follow the settings below if you wish to have rewards for logged in time.
Let's go to the explanations.
"events.auto.reward.enable" It is basically if you want to activate this reward for logged time or not, "true" in case you want to leave it activated and "false" in case you don't want to.
"events.auto.reward.time" Basically here you set the time when each reward will come.30 Minutes is the default, so every 30 minutes online the player will earn this reward.
"events.auto.reward.mail.name" Here is basically the name of the email that will come in the "B" tab.You can rename the message to whatever you want.
"events.auto.reward.mail.subject" Here is the name of the subject who sent the email. For example: Staff or Admin.
"events.auto.reward.mail.message" Here is the message you will send via this email, thanking you for playing or anything else.
"events.auto.reward.items" Here basically will be the items that you will send.
The example of 6; 0; 1000It works like this:
6 is the pearl (pearl id = 6)
0 is the enchantment level, you cannot send a pearl in the PEN, right.
1000 is the amount of pearls to be sent.
Here we finish the tutorial, if I forgot something, let me know.
When you open the gameserver folder, you will see the "bin" and "lib" folders againOpen the bin
When opening the "bin" folder, you will see this bunch of files and folders.But, let's focus on the "configs" folder again.Then open the configs folder.
When opening the configs folder, you will see many ".properties" filesI think you’ll see about 27 or 28.We will focus on only five of them.
What are these below
We will again be in order of the image.Let's open the rate.properties fileYou can open them with any text editor
The rate.properties file is responsible for setting the item drop rate, enchantment rate and others.
I will give a brief explanation, not very detailed.You can edit the drop rates (the enchantment rates are different)through settings.
Example:
1% = 1000
10% = 10000
100% = 100000
I'm sorry for not explaining much about the item drop rate and others. I will explain it better in another tutorial.
Let's go to the next file.The network.properties.
Here as you already opened ports 8888 and 8889 as TCP ports on the firewall, now we can just configure and place IPV4, as we did on the loginserver.
Follow the tutorial below.
# Rmi connection host.
network.rmi.host = (The IPV4 of your virtual machine or your personal computer.)
# Rmi connection port.
network.rmi.port = 9000
# Host for server binding.
# Default: 0.0.0.0
network.host = 0.0.0.0
# Port for server binding. EVERY SERVICE HAS HIS/HER OWN PORT
# Default: 8889
network.port = 8889
"network.rmi.host" I'll explain, basically you need to put your ipv4 here, as the players will connect to it..
Regarding port 9000 you don't need to open it.But as I said at the beginning, you need to open ports 8888 and 8889. Never open port 27017, it is the location of your database, if you intend to open an online server for everyone to enter, never open port 27017, because if you open , some people like me, will connect to your port 27017 and I will place my account as an administrator account.
In relation also to the "0.0.0.0" ip you do not need to change, as it is an ip that redirects, so it will automatically redirect the ip to your ip.
Now let's go to the next file.The server.properties
Here again you will place your IPV4
# External server IP for client connections.
# If localhost use 127.0.0.1
# If docker & localhost use host.docker.internal
# If external - use real ip
server.ip = (The IPV4 of your virtual machine or your personal computer.)
Now let's configure the debug.properties file
Here we will configure to disable server logs, and avoid using high memory and high cpu.Just follow the settings below and the explanation of what each one is.
# Disable collections spawn
# Default: false
debug.collections.spawn.disable = false
# Disable loading huge region images (for memory economy while tests)
# Default: false
debug.region.dataload.disable = false
# Enable actions debug
# Default: false
debug.actions.enable = false
# Enables AIScriptloader debug
# Default: false
debug.aiscriptloader.enable = false
"debug.collections.spawn.disable" if you set "true" to this setting, it will disable collections from your server, this is a way to further optimize the game. And any form of collection, by mining, collecting trees, etc. will be disabled.
"debug.region.dataload.disable" This setting if you put "True" it will disable the background landscapes when walking the map, when you walk, you can see landscapes very deep, it consumes a little RAM and CPU of your server, but, if you put " true "these landscapes can disappear.
"debug.actions.enable" This setting if you set it to "true" it will show each step of each player, each action he does, with each NPC he speaks, and all of that will show on gameserver.batso it will consume a lot, but, a lot of cpu and ram.
"debug.aiscriptloader.enable" This one applies the same as above, the difference is that it applies to monsters and npcs.
Now let's go to the last file and not least.
Events.properties
Well, basically this file is an event file, here you can configure the daily rewards (just activate and deactivate)and also the rewards for time online (Yes, you can put pearls for time online and any other item)I will be very brief, because it is not that important, but it is also not useless.
Follow the settings below if you wish to have rewards for logged in time.
# Enable Auto reward event.
# Default: true
events.auto.reward.enable = true
# Auto reward each 30 min.
# Default: 30
events.auto.reward.time = 30
# Auto reward mail name.
events.auto.reward.mail.name = Reward!
# Auto reward mail subject.
events.auto.reward.mail.subject = Staff, or other poop
# Auto reward mail message.
events.auto.reward.mail.message = Thanks for play!
# Auto reward ItemId;EnchantLevel;Count
events.auto.reward.items = 6;0;1000
Let's go to the explanations.
"events.auto.reward.enable" It is basically if you want to activate this reward for logged time or not, "true" in case you want to leave it activated and "false" in case you don't want to.
"events.auto.reward.time" Basically here you set the time when each reward will come.30 Minutes is the default, so every 30 minutes online the player will earn this reward.
"events.auto.reward.mail.name" Here is basically the name of the email that will come in the "B" tab.You can rename the message to whatever you want.
"events.auto.reward.mail.subject" Here is the name of the subject who sent the email. For example: Staff or Admin.
"events.auto.reward.mail.message" Here is the message you will send via this email, thanking you for playing or anything else.
"events.auto.reward.items" Here basically will be the items that you will send.
The example of 6; 0; 1000It works like this:
6 is the pearl (pearl id = 6)
0 is the enchantment level, you cannot send a pearl in the PEN, right.
1000 is the amount of pearls to be sent.
Here we finish the tutorial, if I forgot something, let me know.
If you want a video tutorial, comment below.It may take a while to make the video, but I will.
Attachments
You must be registered for see attachments list
Last edited: