Jump to content
  • 0

[HELP]Gameserver's console Error


Question

Posted

Geia Sas Paidia Tou MaxCheaters, Eimai Kainourgios Edw Kai Dokimasa Ta Guide Sas Gia Na Ftia3w Ton Diko Mou L2jServer....Ta Katafera O Server Douleve Empena Kanonika Alla....Thn Epomenh Mera Evala Kati Custom Items Ston Server Ton Ekana Restart Kai Ka8os Ton Ekana Me Evgale Thn Parakato Eikona...

1-1.jpg

 

Mporei Na Me Voithisei Kapoios?

 

Eyxaristo

10 answers to this question

Recommended Posts

  • 0
Posted

Prota Apola Euxaristo Gia Ton Endiaferon Sas...Oriste Ta Properties Tou Gameserver Kai Tou Login Server

 

Gameserver\Config\Server.properties

# This is the server configuration file. Here you can set up the connection for your server.

# Usually you have to change the ExternalHostname option to

# - 127.0.0.1 (if you want to play alone / testing purpose)

# - LAN IP* (if you want to play from another computer in the network)

# - WAN IP** (if you want to play with friends over internet)

# - Questions? => http://l2jfree.com

#

# * = If you want to get your LAN IP, simply choose "Start" => "Run..." then type "cmd" => "ipconfig"

# **= If you want to get you WAN IP, visit http://www.whatismyip.com

# ===================================================================================================

 

# ================================================================

# General server setting!!! REQUIRED to configure to everyone!!!

# ================================================================

 

# Bind ip of the gameserver, use 0.0.0.0 to bind on all available IPs

GameserverHostname = *

GameserverPort = 7777

 

# This is transmitted to the clients connecting from an external network, so it has to be a public IP or resolvable hostname

ExternalHostname = MyNo-ip.no-ip.biz

# This is transmitted to the client from the same network, so it has to be a local IP or resolvable hostname

InternalHostname = MyIp

# Note: You can define server hostname for each network in subnets.properties

 

# The Loginserver host and port

LoginPort = 9014

LoginHost = 0.0.0.0

 

# This is the server id that the gameserver will request (i.e. 1 is Bartz)

RequestServerID = 1

# If set to true, the login will give an other ID to the server if the requested ID is allready reserved

AcceptAlternateID = True

 

# Database info

Driver = com.mysql.jdbc.Driver

# Driver = org.hsqldb.jdbcDriver

# Driver = com.microsoft.sqlserver.jdbc.SQLServerDriver

URL = jdbc:mysql://localhost/l2jdb

# URL = jdbc:hsqldb:hsql://localhost/l2jdb

# URL = jdbc:sqlserver://localhost/database=l2jdb/user=sa/password=

Login = root

Password =

MaximumDbConnections = 50

 

# Datapack root directory, defaults to current directory from which the server is started

# DatapackRoot = H:/workEclipse/L2J Free/trunk/L2_DataPack_CT2

 

# Define character name template

# These ones are regular expressions, visit http://www.regular-expressions.info for details

# Note: Checking lengths are done server side, but keep it in pattern for future purposes

# Character name ( Default [A-Za-z0-9\-]{3,16} )

CnameTemplate = [A-Za-z0-9\-]{3,16}

# Pet name ( Default [A-Za-z0-9\-]{3,16} )

PetNameTemplate = [A-Za-z0-9\-]{3,16}

# Clan and ally name ( [A-Za-z0-9 \-]{3,16} )

ClanAllyNameTemplate = [A-Za-z0-9 \-]{3,16}

# Title ( [A-Za-z0-9 \-\\[\\]\<\>\(\)\!\|]{3,16} )

TitleTemplate = [A-Za-z0-9 \-\\[\\]\<\>\(\)\!\|]{3,16}

 

# Maximum number of chars per account - 0 = illimited - default = 7

CharMaxNumber = 1

 

# Define how many players are allowed to play simultaneously on your server.

MaximumOnlineUsers = 20

 

 

# Minimum and maximum protocol revision that server allow to connect.

# You must keep MinProtocolRevision <= MaxProtocolRevision.

MinProtocolRevision = 1

MaxProtocolRevision = 999

 

# ---------------------------------------------

# Safe Reboot configuration

# ---------------------------------------------

# This will prevent some exploit during restart/shutdown process

SafeReboot = True

# To use following options, SafeReboot must be set to True

# Time in seconds before server complete shutdown/reboot, when

# following striction take effect

SafeRebootTime = 10

# Disable item enchant

SafeRebootDisableEnchant = True

# Disable players teleportations

SafeRebootDisableTeleport = False

# Disable craft and crystallize

SafeRebootDisableCreateItem = False

# Disable trades and shops

SafeRebootDisableTransaction = False

# Disable actions between players

SafeRebootDisablePcIteraction = False

# Disable actions on NPC

SafeRebootDisableNpcIteraction = False

 

# Flood Protection

# If enabled players which send more then PACKETLIMIT packets in PACKETTIMELIMIT ms will get kicked

FloodProtection = False

PacketLimit = 500

PacketTimeLimit = 1100

 

# ================================================================

# CT1 Legacy

# ================================================================

CT1LegacyMode = False

 

 

 

Loginserver\config\loginserver.properties

 

# Bind ip of the loginserver, use 0.0.0.0 to bind on all available IPs

LoginServerHostname=0.0.0.0

LoginServerPort=2106

GMMinLevel=100

 

# The port, ip on which login will listen for GameServers

LoginHostname=*

LoginPort=9014

 

# If set to true any GameServer can register on your login's free slots

AcceptNewGameServer = False

 

# If false, the licence (after the login) will not be shown

ShowLicence = True

 

# Database info

Driver=com.mysql.jdbc.Driver

#Driver=org.hsqldb.jdbcDriver

#Driver=com.microsoft.sqlserver.jdbc.SQLServerDriver

URL=jdbc:mysql://localhost/l2jdb

#URL=jdbc:hsqldb:hsql://localhost/l2jdb

#URL=jdbc:sqlserver://localhost/database=l2jdb/user=sa/password=

Login=root

Password=

 

# Useable values: "True" - "False", use this option to choose whether accounts will be created

# automatically or not.

AutoCreateAccounts=True

 

# The delay in minutes after which the login updates the gameservers IP's (usefull when their ip is dynamic)

# (0 = disable)

IpUpdateTime=0

 

 

# ==============================================================

# Test server setting, shoudnt be touched in online game server

# ==============================================================

 

Debug = False

Assert = False

Developer = False

# Enforce GG Authorization from client

# Login server will kick client if client bypassed GameGuard authentication

ForceGGAuth=False

 

#FloodProtection. time in ms

EnableFloodProtection=True

FastConnectionLimit=15

NormalConnectionTime=700

FastConnectionTime=350

MaxConnectionPerIP=50

 

#Ban management

# number of attempt before a user is banned when he fails his login

LoginTryBeforeBan=10

# Time you won't be able to login back again after LoginTryBeforeBan tries to login. Provide a value in seconds. Default 10min. (600)

LoginBlockAfterBan=600

 

 

 

Episis O Server Kanei Login Kanonika Aplos To Ping Einai 9999  

 

 

  • 0
Posted

Ixa ena prob paromio.. Stantar otan evales ta Custom petaksan error se row. aftod ne einai prob aplos exi kolisi i db kai den diavasi to game server kapia pragmata apo tin db.. eimai sigouos pos stin arxi den mporousan na kanoun login i chars. :S

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Posts

    • And whats the reason posting this here? GoldMembership in 2026 in MAXC.
    • Added the protection module to the demo.   DDoS Guard Pro v2.0 is a system protection module for PlayMMO CMS designed to reduce the load on the website during HTTP floods, bot activity, suspicious frequent requests, and attacks on individual pages or API methods. Unlike simple global limiters, DDoS Guard Pro v2.0 supports flexible rules based on routes and HTTP methods. This allows you to block the entire site in a targeted manner, rather than blocking the entire site equally. You can set up protection for specific areas of the site, such as login, registration, APIs, administration, forms, and other sensitive areas. What is the purpose of the module? DDoS Guard Pro v2.0 helps protect your site from basic L7 attacks at the HTTP request level. The module is useful when your site receives: frequent requests from a single IP address; HTTP page floods; login or registration form flooding; automatic requests from bots; URL scanning; frequent API requests; suspicious activity spikes; load on individual CMS methods or pages. The module helps to reduce the load on PHP and CMS by limiting suspicious activity before it starts to create a serious load on the site. Main features Per-route and per-method Rate Limit In the new version, protection is configured not only globally, but also according to specific rules. You can set limits separately for: GET; POST; PUT; PATCH; DELETE; ALL. This allows you to flexibly protect different parts of your website. For example: for the login page, you can set a strict limit; for registration, you can set a separate limit; for the API, you can set a limit for reading and a limit for changing data; for regular website pages, you can set a soft limit or not set a limit at all. This approach reduces the risk of accidentally blocking regular users and makes the protection more accurate. Flexible rule system The module supports setting rules in the following format: METHODS|PATTERN|LIMIT|WINDOW|BURST_LIMIT|BURST_WINDOW|BLOCK_SECONDS|IDENTITY|NAME Example of rules: POST|*login*|10|60|5|10|600|ip|login_post POST|*register*|8|60|4|10|600|ip|register_post GET|*api*|300|60|80|10|120|ip|api_get PUT,PATCH,DELETE|*api*|80|60|20|10|300|ip|api_write This allows you to specify exactly: which HTTP methods to protect; which URLs or URL patterns to consider; how many requests are allowed; over what time period; what burst limit to use;  how many seconds to block the offender;  by which ID to count the limit;  what the rule is called. Burst protection against sharp spikes  In addition to the regular request limit, the module monitors sharp spikes of activity.  This is useful when a bot makes many requests in a few seconds. In this case, the protection can be activated faster, without waiting for the overall limit per minute.  Burst protection is especially useful for: authorization pages; registration; API; search; data submission forms; administrative sections. Support for different types of requests DDoS Guard Pro v2.0 works not only with POST requests. The module can control: GET — regular pages, API requests, search; POST — forms, login, registration, data submission; PUT — updating data via API; PATCH — partial data update; DELETE — data deletion; ALL — all methods at once. This makes the module suitable not only for regular sites, but also for CMS with API, personal accounts, game panels and administrative actions. Limit storage: Redis, APCu and file fallback In the new version, the module supports several options for storing temporary data. Available modes: Redis; APCu; file fallback. The auto mode tries to use the most suitable option: Redis; APCu; file storage as a fallback. Redis or APCu are suitable for more efficient operation, while the file storage is left as a fallback option for simple hosting environments that do not have additional extensions. JSONL logging The module records protection events in JSON Lines format. Logs are saved in the following file: storage/logs/ddos_guard.jsonl This format is more convenient than a regular text log, because each event is stored as a separate JSON record. The logs can record the following information: event time; IP address; HTTP method; URL; name of the triggered rule; reason for blocking; number of requests; action status; user-agent; protection mode. The JSONL format is convenient for analysis by external tools, log agents, and monitoring systems. Prometheus metrics DDoS Guard Pro v2.0 adds an endpoint for receiving metrics in Prometheus format. Endpoint: /?ddos_guard_metrics=TOKEN The token is set in the module settings. Metrics allow you to track: the number of processed requests; the number of rule activations; the number of blocks; activity by limits; protection events; module status. This allows you to connect monitoring and configure alerts so that the administrator can see when suspicious activity starts on the site. LOG ONLY mode The module has a LOG ONLY mode. In this mode, DDoS Guard Pro does not block users, but only records events and potential triggers in the log. This mode is recommended to be used after installation, in order to first see which rules are triggered, and only then to enable the real blocking.  This helps to avoid too strict limits and random blocking of regular users.  Support for Cloudflare and proxy  The module supports working behind Cloudflare or another reverse proxy.  With proper configuration, it is possible to take into account the real IP of the user, and not the IP of the proxy server.  This is important for sites that use:  Cloudflare; nginx reverse proxy; load balancers; CDN; hosting proxy protection. Nginx-recommendations DDoS Guard Pro v2.0 contains an example nginx-config: modules/ddos_guard/nginx-ddos-guard-example.conf This allows you to use the module as an additional application layer of protection, and to move the main coarse limits to the nginx level. Recommended protection scheme: Cloudflare / nginx / firewall → DDoS Guard Pro → PlayMMO CMS This approach is more correct than trying to solve all problems only at the PHP level.
  • Topics

×
×
  • Create New...

Important Information

This community uses essential cookies to function properly. Non-essential cookies and third-party services are used only with your consent. Read our Privacy Policy and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..