It is working, just like retail, you have the highest chance to climb onto the horse within the 40-60 second time frame after getting to the horse and opening your bag, there is also a config somewhere to make it easier to catch horses. The config is within your config folders, servant.properties, line 11 taming_rate = xxxxx
No problem glad to help, is there anythign else you need help with?
and the leveling thing, but we will try to complete the buglist... or at least trying.)
[B]database.properties:
[/B]# Use database logging.
allowDatabaseLogging = false
# Do mongodump while server starting.backupAtStart = false
[B]
debug.properties:
[/B]# Disable collections spawn# Default: falseDisableCollectionsSpawn = true #enable for fishing/gathering# Disable loading huge region images (for memory economy while tests)# Default: falseDisableRegionDataLoad = true #true to save loading time# Enable actions debug# Default: falseEnableActionsDebug = false
[B]network.properties: (i don't remember what i changed so i linked the entire file)
[/B]# Rmi connection host.network.rmi.host = 192.168.50.85# Rmi connection port.network.rmi.port = 9000# Rmi connection password.network.rmi.password = 1234# Server version supported# NA-EU: 4635network.server.version = 4635# Client support european.network.encrypt.packets = true# Host for server binding.# Default: 0.0.0.0network.host = 192.168.50.85# Port for server binding.# Default: 8888network.port = 8889# Show debug messages.# Default: falsenetwork.debug = false# Packet executing mode.# DIRECT - The worst. Income packets are directly executed after receiving and decrypting. As packets here implemented terribly, it not only increases latency, but decrease overall performance significant.# OFFLOAD - Offloads execution to a ThreadPool. Good option with POOLED IOExec mode. Increases throughput but also may increase context switch count.# Default: OFFLOADnetwork.packet.exec.mode = OFFLOAD# Receive buffer size.# Default: 32768network.recv.buffer.size = 32768# Send buffer size.# Default: 65536network.send.buffer.size = 65536# NetworkThread socket backlog size.# See: http://www.linuxjournal.com/files/linuxjournal.com/linuxjournal/articles/023/2333/2333s2.html# Default: 50network.server.socket.backlog = 50# Client socket options.# SO_SNDBUF - the size of the socket's send buffer. On most systems this the size of a kernel buffer so be careful! See RFC1323.# SO_RCVBUF - the size of the socket's receive buffer. On most systems this the size of a kernel buffer so be careful! See RFC1323.# TCP_NODELAY - The Nagle algorithm. Enabling it increases throughput but also increases latency. See RFC1122.# Default: SO_SNDBUF(8192);SO_RCVBUF(8192);TCP_NODELAY(true)network.client.socket.options = SO_SNDBUF(8192);SO_RCVBUF(8192);TCP_NODELAY(true)# NetworkThread socket options.# SO_REUSEADDR - if true, prevents socket from usage until all opened sockets are really closed. See RFC793.# Default: SO_REUSEADDR(true);SO_RCVBUF(4096)network.server.socket.options = SO_REUSEADDR(false);SO_RCVBUF(4096)# IO Network thread execution mode.# POOLED - All IO operations are executed in a special thread IO execution pool# FIXED - All IO operations execution is spread across fixed number of treads# Default: POOLEDnetwork.io.execution.mode = POOLED# Number of IO Network threads.# Default: -1 (Processor count)network.io.execution.thread.num = -1# Income packet header size.# Default: 3network.income.packet.header.size = 3# Max income packet size.# Default: 16384network.max.income.packet.size = 16384# Outcome packet header size.# Default: 3network.outcome.packet.header.size = 3# Max outcome packet size.# Default: 16384network.max.outcome.packet.size = 16384You might of fucked up a config somewhere, P2P trading works fineYea XD Marketplace works however fine i guess...
Right, open Gameserver.jar with winrar then go to, \com\bdoemu\gamserver\model. Then replace your trade folder with this one, should fix the issueI mostly use configs as-it-is.(Exept the few what needed to work better lagfree-ish npc's and in configs what DNC said before to do to increase thread pools, and horse taming. Nothing else...) So i dont meddled with player config or similar, but it might be something related the configs but "I" did not f*cked up anything
Thats because siege/node wars was never finished
