Hey guys, check this:
http://forums.openkore.com/viewtopic.ph ... 021#p64021
First idea is rather ambitious, but I don't see how else to fix the problem at hand.
Second idea should be tested, polished and at least be mentioned in the guide to find charblocksize imo.
Ok I just got another crazy idea, we could use this entire DB of recvpackets to test the entire kRO ST tree for correct packet lenghts and even TO BE implemented packetswitches etc.
2 idea's to improve kore's user experience
Moderator: Moderators
-
- Super Moderators
- Posts: 801
- Joined: 06 May 2008, 12:47
- Noob?: No
2 idea's to improve kore's user experience
One ST0 to rule them all? One PE viewer to find them!
One ST_kRO to bring them all and in the darkness bind them...
Mount Doom awaits us, fellowship of OpenKore!
One ST_kRO to bring them all and in the darkness bind them...
Mount Doom awaits us, fellowship of OpenKore!
Re: 2 idea's to improve kore's user experience
Hmm. As for packets. I hale a complete DB of them, that is RLY Fresh. Some Info is missing, but nothing RLY hard.
(Also an Additional CharBlockSize too).
If you need them to clean up and update kRO ST Tree or add/complete ST0, just PM me, and I'll send you them.
Last packet there is 098F
So it's Pretty Fresh!
(Also an Additional CharBlockSize too).
If you need them to clean up and update kRO ST Tree or add/complete ST0, just PM me, and I'll send you them.
Last packet there is 098F
So it's Pretty Fresh!
-
- Developers
- Posts: 1798
- Joined: 05 Dec 2008, 05:42
- Noob?: Yes
Re: 2 idea's to improve kore's user experience
Related: http://openkore.svn.sourceforge.net/vie ... tables/eA/extract all recvpacket files
-
- Super Moderators
- Posts: 801
- Joined: 06 May 2008, 12:47
- Noob?: No
Re: 2 idea's to improve kore's user experience
Hey, that's awesome EternalHarvest, didn't know that commit existed!EternalHarvest wrote:Related: http://openkore.svn.sourceforge.net/vie ... tables/eA/extract all recvpacket files

Anyways, ISTR that the packet_db file also contains the names of the binaries where packets got implemented/changed?
unknown binary + packet extractor to get its recvpackets + comparing with recvpackets files of known binaries = servertype finder maybe?
Maybe we should send a patch to rA/eA about 08B9?
One ST0 to rule them all? One PE viewer to find them!
One ST_kRO to bring them all and in the darkness bind them...
Mount Doom awaits us, fellowship of OpenKore!
One ST_kRO to bring them all and in the darkness bind them...
Mount Doom awaits us, fellowship of OpenKore!
-
- Developers
- Posts: 1798
- Joined: 05 Dec 2008, 05:42
- Noob?: Yes
Re: 2 idea's to improve kore's user experience
Can be done. If anything like that, I'm for empty serverType value for "automatic discovery if possible".Technology wrote: unknown binary + packet extractor to get its recvpackets + comparing with recvpackets files of known binaries = servertype finder maybe?
eA doesn't have related server version yet. We can send that to rA.Maybe we should send a patch to rA/eA about 08B9?
-
- Super Moderators
- Posts: 801
- Joined: 06 May 2008, 12:47
- Noob?: No
Re: 2 idea's to improve kore's user experience
Or as standalone script, listing the ST's that differ the least from the unknown binary's recvpackets, using the comparison as heuristic.EternalHarvest wrote:Can be done. If anything like that, I'm for empty serverType value for "automatic discovery if possible".Technology wrote: unknown binary + packet extractor to get its recvpackets + comparing with recvpackets files of known binaries = servertype finder maybe?
One ST0 to rule them all? One PE viewer to find them!
One ST_kRO to bring them all and in the darkness bind them...
Mount Doom awaits us, fellowship of OpenKore!
One ST_kRO to bring them all and in the darkness bind them...
Mount Doom awaits us, fellowship of OpenKore!