Awesome! I've seen packets log in god client, ctrl+p as i remember. Sad new clients don't have names.
But there's chance that beta clients have names, since they were build with debug.

Is it possible to calculate the address and extract the packet table at runtime?

Well,

It's possible but you need to know what you are doing.

These are the problems you will need to face and solve:

1) The key feature in the algo above is IDA Pro's FindBinary function. You will need to implement that function in your language of choice.

2) You need access to the code segment of the client
2a) Use ReadProcessMemory (rather slow)
2b) Inject your code in the client's process as a thread (fastest method but also the most complex) (does not work from .NET)
2c) Open the "client.exe", since it's not encrypted you can do the memory search in there and then map the found file address to a memory address (in between solution)

I'm guessing you are using method 3? If so, you need to convert from a file offset to a virtual address:

You need the function CPortableExecutable::FO2VA.

I'll need to look into those two clients and see why it's not working, I'm guessing it's not finding the correct location?...

Here's a screenshot:

I just figured out... they replaced the old 0x00 Create Character packet with the new one (0xF8).

Does this table contains only Client -> Server packets, or both?

It's both. There is no difference between client and server in protocol...

Thanks a lot, Batlin. If you don't mind - I'll use your guide for auto detect packet sizes in my UOExt.