Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
Also limit using carts only to cartoon players.
|
|
|
|
Variable: guild_emperium_check
We do not have the resources to support hundreds of guilds made
from snake eggs. NPCs that will only give the guild creation item
if certain conditions are met are needed.
|
|
|
|
This is sent along with char name replies to GMs able to recieve hack
notices. Unfortunately,it locks up clients that do not support this packet.
Must coordinate to get this added to TMW 0.5 release and mana. Until then,
code is commented out in clif.c(grep for MD5_ip)
Packet structure:
0x20C (len 2)
AccountID of character name was requested for (len 4)
IP address of requested char in network byte order (len 4)
Config option in battle_athena.conf:
gm_mask_ips (boolean) - When set to 1(default) GMs will only see a
hashed/masked IP address.
|
|
This is to be used for @ipcheck, sending GMs IP identifiers, and
clone blocking.
|
|
Also makes minor style adjustments and cleans up comments.
|
|
Also allow change guild positions to guild owner even without Guild Master position.
Signed-off-by: Chuck Miller <shadowmil@gmail.com>
|
|
Thanks to 4144 for reporting.
|
|
back into drop parties, as the former rate of 200ms made them fairly
lame.
|
|
Some of our maps are bigger.
|
|
Guess I forgot to remove them when the actual trade/sit spam
code was removed.
|
|
This eliminates part of the client's burden to manage the ID of the
player sending the invitation. This also introduces a new response
value (3) for the invitation acknowledgement packet (0x00fd) to
indicate the party is full.
Resolves: TMW Mantis #676
|
|
|
|
|
|
|
|
usage: ipcheck <char name>
This new command defaults to level 60 and displays all characters
currently online from the same IP address. It does not reveal the
actual IP address.
|
|
Sorry for the inconvenience
|
|
|
|
Signed-off-by: Chuck Miller <shadowmil@gmail.com>
|
|
Signed-off-by: Chuck Miller <shadowmil@gmail.com>
|
|
Signed-off-by: Chuck Miller <shadowmil@gmail.com>
|
|
|
|
|
|
This is so nobody gets too confused if a GM is doing @commands as
an alternate character. Since account ID is public to anyone on
the server anyway, it shouldn't be a security risk.
|
|
|
|
This reverts commit 07ac029ab049cd8fdec5f271a814c2459edeefb8.
|
|
It is acting funny and being mean to innocent users
|
|
.29.1 has a bug that spams ChangeDir packets like crazy and my checks
had some problems with this, causing players to be disconnected while
navigating through areas with large amounts of blocked tiles. Hopefully
someone remembers to re-enable this code when 1.0 is the officially
supported version.
|
|
|
|
Signed-off-by: Jared Adams <jaxad0127@gmail.com>
|
|
Oops :(
|
|
It's now possible to run 'make' in any of the src/ subdirs and
have it build properly. Moved some tools including eathena-monitor
to src/tools - run 'make tools' to build. CFLAGS, etc are now in
the 'make.defs' file. Requires GNU make.
|
|
The limits were interfering with repetative NPCs such as Agostine
|
|
Breakdancing is fun. Spinbotting isn't..
|
|
Pre-mana clients spam this packet while walking into blocked tiles
|
|
I had forgotten to do this when I removed the functions themselves.
|
|
map string using pc_setpos()
Noted (and solution suggested) by Freeyorp
|
|
|
|
This is unused and gave false alarms about rid not being attached when it didn't need one.
|
|
|
|
This takes one parameter, an entity, and returns the id of the class associated with a mob if it is a mob, and fails otherwise.
|
|
|
|
|
|
|
|
map.
This patch models its behavior partly on that of movenpc and the
atcommand npcmove.
|
|
|
|
|
|
The idea behind this is to keep abusive clients from flooding the
server. Everything from over-voracious auto pick-up to exploitation
of NPC vulnerabilities is mitigated by this. It will also eventually
reduce server traffic, load, and possibly lag.
Config options in battle_athena.conf:
packet_spam_flood (default 30)
packet_spam_threshold (default 2)
packet_spam_kick (default 1)
Each packet type has a specified allowed incoming rate in milliseconds,
if this rate is exceeded the packet is ignored. If over 'flood' overruns
in 'threshold' seconds are detected, a flood is logged and a kick may be
triggered depending on the 'kick' config boolean.
The packet rates and flood thresholds have been tested and tweaked
on a live server, this should only affect abusive clients. Only
extremely abusive clients will trigger a log/kick condition.
This probably obsoletes the trade and kick spam code.
|