-
Account Upgraded | Title Enabled!
problem 999 ping.
hey i have a problem 999 ping .
i use Gunz 1.5 Repack By jur13n #1 .
my server.ini
[DB]
;DNS="gunzq"
;USERNAME="sa"
;PASSWORD="a"
DNS="gunzq"
USERNAME="sa"
PASSWORD="a"
[SERVER]
MAXUSER=1500
SERVERID=1
SERVERNAME="Debug Server"
SERVERPORT=6000
SERVERUDPPORT=7777
FREELOGINIP="127.0.0.1"
KEEPERIP="127.0.0.1"
DEBUGIP="127.0.0.1"
MONITORIP="127.0.0.1"
MONITORPORT=9000
DEBUG="1"
MODE=Quest
COUNTRY="KOR"
LANGUAGE="KOR"
USETICKET="0"
GAMEGUARD="1"
;Survival Mode : 1 for enable, 0 for disable (works only when MODE=test)
SURVIVALENABLE="1"
;Daily request time for survival ranking list(hour:0~23, minute:0~59)
SURVIVALRANKING_DAILY_REQUEST_HOUR="5"
SURVIVALRANKING_DAILY_REQUEST_MINUTE="0"
;DuelTournament Mode : 1 for enable
DUELTOURNAMENT_ENABLE="1"
;DuelTournament MatchMaker run every this time interval (in positive millisec)
DUELTOURNAMENT_MATCHMAKING_INTERVAL = 1000
;DuelTournament MatchMaker match users have TP diffenrence less than this value. (must be positive)
DUELTOURNAMENT_MATCHMAKING_ACCEPTABLE_TP_GAP = 30
;DuelTournament MatchMaker match a user waiting over this time with users have the most nearest TP (ignore TP GAP, value in positive millisec)
DUELTOURNAMENT_MATCHMAKING_WAIT_LIMIT = 15000
;DuelTournament Service Time
;CAUTION! if END_TIME is n then this mode will opened until n:59.
;ex) all day open -> 0, 23
;ex) from 3 to 6 o'clock -> 3, 5
;ex) from 22 to next day 3 o'clock -> 22, 2
DUELTOURNAMENT_SERVICE_START_TIME = 0
DUELTOURNAMENT_SERVICE_END_TIME = 23
SEND_LOGINUSER_TO_DUELTOURNAMENT_CHANNEL ="0"
[BATTLETIMEREWARD]
BATTLETIMEREWARD_REFRESH_INTERVAL="1"
[FILTER]
;0:»ח¿כֱַֿצ ¾ְֺ½. 1:»ח¿כ.
USE="0"
;0:ַד¿כֱַֿצ ¾ְֺ½. 1:ַד¿כ.
ACCEPT_INVALID_IP="1"
[ENVIRONMENT]
;0:»ח¿כֱַֿצ ¾ְֺ½. 1:»ח¿כ.
USE_HSHIELD="0"
;0:»ח¿כֱַֿצ ¾ְֺ½. 1:»ח¿כ.
USE_XTRAP="0"
;0:»ח¿כֱַֿצ ¾ְֺ½. 1:»ח¿כ.
USE_EVENT="0"
;0:»ח¿כֱַֿצ ¾ְֺ½. 1:»ח¿כ.
USE_FILECRC="0"
;0:»ח¿כֱַֿצ ¾ְֺ½. 1:»ח¿כ.
USE_MD5="0"
USE_RESOURCECRC32CACHECKECK="0"
;Flooding°ר° µנ÷ס¿¡ ¼³ֱ₪ ְ¯¹«.
BLOCK_FLOODING="1"
;ְ§ ¸ס·ֿ¿¡ °ֳֻגµָ ְ¯ְת¸¦ ÷ם·¯ֵ· ְ¯¹«.
USE_BLOCKHACKING="1"
USE_ITEM_CONSISTENCY="0"
[KILLTRACKER]
;÷׀´ְ§
;0:»ח¿כֱַֿצ ¾ְֺ½. 1:»ח¿כ.
USE_KILLTRACKER="1"
MAXKILLCOUNT_ON_TRACETIME="30"
KILLCOUNT_TRACETIME="5"
[POWERLEVELING]
USE_POWERLEVELING_DB_BLOCK="1"
POWERLEVELING_DB_BLOCKTIME="1"
[LOOPLOG]
;0:»ח¿כֱַֿצ ¾ְֺ½. 1:»ח¿כ.
USE_LOOPLOG="0"
;1ֳֺ(sec)¸¦ 1000 ְ¸·־ ַ¥±ג
MAX_LOOP_TIME_GAP=100
My Locator:
[DB]
DNS="gunzq"
USERNAME="sa"
PASSWORD="a"
[NETWORK]
IP="127.0.0.1"
PORT="8900"
[ENV]
ID="1"
LOCATOR_UID_HIGH="5"
LOCATOR_UID_LOW="0"
MAX_ELAPSED_UPDATE_SERVER_STATUS_TIME="1000"
UDP_LIVE_TIME="10000000"
MAX_FREE_RECV_COUNT_PER_LIVE_TIME="9"
BLOCK_TIME="0"
UPDATE_UDP_MANAGER_ELAPSED_TIME="3"
MARGIN_OF_ERROR_MIN="500000"
USE_COUNTRY_CODE_FILTER="no"
ELAPSED_TIME_UPDATE_LOCATOR_LOG="3600000"
ACCEPT_INVALID_IP="1"
TEST_SERVER="0"
my MatchAgent
<?xml version="1.0" encoding="euc-kr"?>
<XML>
<AGENTCONFIG>
<NAME>Debug Server</NAME>
<MAXCLIENT>1500</MAXCLIENT>
<ADDRESS ip="127.0.0.1" tcpport="5100" udpport="7778"/>
<MATCHSERVERADDRESS ip="127.0.0.1" tcpport="6000"/>
</AGENTCONFIG>
</XML>
Help please :(
-
-
In Progress... FFXIV...
Re: problem 999 ping.
You're doing it locally that's why?
-
Account Upgraded | Title Enabled!
Re: problem 999 ping.
if i change to my own ip its will be work?
-
Valued Member
Re: problem 999 ping.
Change to your Dynamic IP address Don't run things locally.
-
Account Upgraded | Title Enabled!
Re: problem 999 ping.
dont work , anyone help ?
-
Valued Member
Re: problem 999 ping.
My friend Alex fixed this issue with his client, it turned out it was something with his client and not the server. It had to do with his local network connection and ports. He was up late last night helping with server related issues, so he probably won't be on for another few hours. I can ask him then. But you can google the issue of NAT configuration error, this is what causes 999 or 0 ping and it's the green error you get when trying to connect to another client. Another thing you should note is that with GunZ two clients logging in from the same IP Address sometimes causes conflict in the server. So if you're testing with two clients from the same house, this could be your issue.