CoFuture Version?

[Deсker]

.

[Kiyono]

CoFuture is 4348.

[nTL3fTy]

Try using bone-you's patchlist:

[Kiyono]

That's odd as I'm pretty sure that I used the 4351 client to connect a few years back.

[Korvacs]

Theres 3 different versions of CoFuture just fyi...

[Spirited]

1. If you look around at the other versions, I think it's obvious which version it is. On top of that, I linked it to the original release thread that says what the patch really is. Anyways, I'll change that so a second person doesn't get confused with that. I'm not really updating the one on my blog anymore. I might take it down.

2. If you went to my client thread, you would of seen an entire section dedicated to patching the client. I put them there because I want to help you, so don't make it more difficult on yourself and read the thread or at least read the headers I put in.

3. Google says that "Null" means "nothing" or "no value", so... that leads me to conclude that GameClients[e.Conn].Client is null. The way GameClients is being used makes it look like a dictionary, so... the dictionary is null or the value in the dictionary is null. There's only one way to tell though. Right click it and select "Go to definition". Then, right click it again (after you checked to see what it is) and select "Find all references" (or whatever it is).

Hope that helped. You need to use your resources though! They're all around you. Members here have put them out there just to help people starting up like you.

[Kiyono]

Originally Posted by Deсker

I already checked out the patches, and actually tried to patch it up, but I failed. I found a 4343 client in Stig's old thread, and patched that up.

I read through the CoFuture thread, and I seen that the reason I'm getting those errors, is simply because I don't have C# 2005 (That's just what I read - I wouldn't know). I cba to download 2005 version.

Thanks for the help though

Have you tried reading through the thread? It has been a few years but I can vaguely remember something about an error caused by the wrong Visual Studio version and how to solve it, don't take my word for it though.

[turk55]

Back than you would of needed C# 2005 but thats a long time ago.
You should be able to work on a higher version too

[Korvacs]

Just perform an upgrade with VS 2010 and then fix any new compiler issues that have appeared over the last 7 years or so.

[Kiyono]

Originally Posted by Deсker

.

What I meant was that there was a fix for newer versions of Visual Studio; in other words a fix that does not involve installing an older version.