Updating.

I was just wondering what would be required to update a the CoFuture source to patch 5017, i have never done this and would be interested if someone could supply my with some information.

Update login sequence/encryption and the packets/offsets using other 5017 sources as a reference (lotf or hybrids basic one)

And that's my way of answering you without actually being the SLIGHTEST bit helpful ;)

<edit>

wait, encryption may not be different. I forget which patch in 1.0 changed it (they did change it at least once during 1.0 didn't they?) I was thinking for a sec they changed when 2.0 came out but they didn't cause you could log 1.0 servers with 2.0 client for a while before 2.0 was released.

As p4n said, you can take a 5017 source, and use that cryptographer and put it into the CoFuture Source. But of course, you would need to double check everything else to ensure stability.

Quote:

Originally Posted by pro4never Update login sequence/encryption and the packets/offsets using other 5017 sources as a reference (lotf or hybrids basic one) And that's my way of answering you without actually being the SLIGHTEST bit helpful ;) <edit> wait, encryption may not be different. I forget which patch in 1.0 changed it (they did change it at least once during 1.0 didn't they?) I was thinking for a sec they changed when 2.0 came out but they didn't cause you could log 1.0 servers with 2.0 client for a while before 2.0 was released.

Wouldn't it be better to take it out of hybrid's?
It is more stabler I believe.

I listed both. Hybrids is obviously far superior but there are a few things to remember

#1: Packets are going to be the same in any source (not how they are handled by the source but the FINAL CONVERTED version of the packet/encrypton is going the be the same seeing as it has to communicate with the client.

A fully converted packet should function exactly the same (assuming it is not missing certain information)

#2 hybrids source may be easier to pull packets from/better organized but it's a very basic source so much of what you are looking for will be missing, meaning you will still need to use lotf (or a packet logger on an existing 5017 server.)

There is already a version of CoFuture using the 5017 client...

[Only registered and activated users can see links. Click Here To Register...]

Quote:

Originally Posted by CptSky There is already a version of CoFuture using the 5017 client... [Only registered and activated users can see links. Click Here To Register...]

I was unaware of this, and its not the same source. I want the other one updated :D

still, if it's structured at all similarly it may be alot easier to pull the packets and any cryptions out of it.

Quote:

Originally Posted by pro4never still, if it's structured at all similarly it may be alot easier to pull the packets and any cryptions out of it.

Packets look very similar to those lotf.

Packet structures shouldn't change, the key should.

Quote:

Originally Posted by spare2 Packet structures shouldn't change, the key should.

I know the packets structures don't change, as stated before, but the way they are handled are similar to Lotf, any clues on how convert them, or just how to interpret them?

edit, fixed some grammer/spelling mistakes, can't seem to type.

You should try to first transfer the key from the 5017 source on to your source. Then, try and run the server and log-in.
Remember to backup your source before doing it.

Quote:

Originally Posted by spare2 You should try to first transfer the key from the 5017 source on to your source. Then, try and run the server and log-in. Remember to backup your source before doing it.

Doesn't work, what are are you talking about? You talking about the Key arrays? If so, it doesn't work, need to up date something else, no quite sure though.

It would help if you describe what's not working...

Quote:

Originally Posted by spare2 It would help if you describe what's not working...

I will pm you.