Okay...
First get a client with Phoenix.
Import it's item table to the server executable and update all the right pointers.
Add a BI132 item to the drop items folder. (base it on one of the other premium items I guess)
Then dig out your packet sniffer and trace the packets between the client and the server when you use the item.
Run a similar trace on official server when using Phoenix and compare the packets the official sends out that ours don't.
Now you know what packets to send, and you can practice with injecting them into the socket at the right points.
Once you have that down to pat, you can break-out the code where our server doesn't recognise a packet, to a point where you test for the Phoenix packet, if it's not that continue as normal broken packet, but if it is you can tell your server to send back a packet like the official one.
Now Phoenix works, but disappears when you log out. That's about as far as most devs have got. What they need to do next is note down that a player has an active Phoenix somewhere, either in the player .dat file or in the SQL database, and re-apply the packet when they log back in.
Nobody is quite sure how to do that yet.
[sarcasm]Catch up. Hurry hurry.[/sarcasm]
kkkkkkkkkkkkkkkkkkkkkkkkk
