The server is running in l2house.com.ar with C4 mode and in L2Tekila within the same login you can also test it in C5, if you want me to raise another chronicle to test, just let me know.
I have a system where Accounts are saved on login screen for fast login. I am playing a server where this feature is not on the logic screen. How I can try to add this feature to the system?
I don't know what files I would have to touch.
Thanks!!
Question
terrys77
re paida exo problima me to pack pos tha to kano online
an einai sosta otan kapoios pai na mpi den ton afini kolai sto login mipos prepi na prostheso kai afta AllowedProtocolRevisions?
# Enter here (ip) address of your game server, or use the symbol *
GameserverHostname = 0.0.0.0
GameserverPort = 7777
# Configure your external ip
ExternalHostname = ................edo ip tou no-ip ?
# Configure your internal ip
InternalHostname = ................edo tou lan mou?
# Bunch ID and game server. It is better not to change.
LoginPort = 9014
LoginHost = 127.0.0.1
# Database Pool Type
# Possible Values: c3p0 or BoneCP
# c3p0: more stable
# BoneCP: more performance
DatabasePoolType=c3p0
# Parameters Databases - MYSQL
Driver = com.mysql.jdbc.Driver
URL = jdbc:mysql://localhost/l2jdb
# Login - Mysql's user
Login = root
# Password - Mysql's Password
Password = root
# Attention: lazy init connections disabled!
# Please, set only real values for your database
# Default: 100
MaximumDbConnections = 200
# Default: 0
MaximumDbIdleTime = 0
# The timeout before a new connection to the database (in ms)
# 0 - to remove restrictions
TimeOutConDb = 0
# The timeout before the single connection must be closed (in ms)
# if a connection life is more then this timeout, a Runtime Exception
# is rised up. Post the exception on forum (www.l2jfrozen.com) to solve
# it.
SingleConnectionTimeOutDb=0
# Sets number of partitions to use.- BoneCP
# In order to reduce lock contention and thus improve performance,
# each incoming connection request picks off a connection from a pool that has thread-affinity,
# i.e. pool[threadId % partition_count]. The higher this number, the better your performance will be for the case
# when you have plenty of short-lived threads. Beyond a certain threshold, maintenance of these pools will start
# to have a negative effect on performance (and only for the case when connections on a partition start running out).
PartitionCount = 200000
# Setting emulation off the kernel (package SendStatus)
RemoteWhoLog = True
RemoteWhoSendTrash = True
RemoteWhoMaxOnline = 329
RemoteOnlineIncrement = 50
RemoteWhoForceInc = 50
RemotePrivStoreFactor = 12
# Datapack folder
# DatapackRoot = C:/Work/tmp/DataPack
1 answer to this question
Recommended Posts