We installed custom pets. there lines for the pet_db.txt was out of order, causing any custom pet from any mob in the mob_db.txt to rearrange the structure and cause a leak in the map_server-sql.exe and the map server would go KABOOM and close off. I was in school a majority of those times but I carried my handy dandy flash drive with my PuTTy =) When I got home I cleaned up the source code and took out 0x800 in the MAX_PACKET_DB under clif.h because it is not needed, so I defaulted it to 500 as it's been, which caused @ii <monstername> to not crash the server, that made 2/4ths bugs fixed. I later found out some items in the item_db2 and the source's files not having anti WPE/CE packets to ensure no hacking wasn't in, I made manner.txt server side based on OnNPlay's revisions. 3/4th's of the bugs were fixed in the matter of 2 days
And guess who did it?
A small little 16 year nick named on the intrawebz Aeromas.
First of all, you screwed the pet database, which you should have tested. Second, your mob database was screw after your pet database was screw. Third, if the database is the problem, it has nothing to do with the source to begin with. Fourth, if your mob database is broken, @ii will crash the server because it uses the file to search for the item drop rates. Fifth, the item database uses the same structure for all of its items, which has nothing to do with WPE packets. Sixth, you did not specific what source code you used to check WPE. And since packets are send all the time, you won't know for sure which one is infected nor natural, actually the server only takes in specific packets already. Seventh, I have no idea why you would want to make the
client-side file manner.txt into the server code. The client has a built in swear filter.
You could have fixed the problem by restoring the old mob/pet database and log on to the game and type @reloadmobdb. Once again, you did all the bullsh
it, only to dig a grave for yourself. You did it only when you are 16 years old and that was the inside joke I made up. Plus only 3/4 of the problem was fixed. You could have fixed it in 2 minutes. Not 2 days.