basically,

(i mean DLL file, raw is always in r90)

if i use r82,

>cannot join (see) aRev servers (in dedicated list)

>can use weapons without ammo bug in 4D1 servers

 

if i use any revision never diffrent than 82 (i tried with 88, 89 and 90* )

>can join (see) aRev servers (in dedi list)

>cannot use weapon in 4D1 (because of ammo bug feature)

 

* there is no 90's dll, dll was changed in revision 89 but in ToolBox's zip, it showing IW4M:3.0-1

note: dlls coming from ToolBox's updates. 2 days ago there was any problems and working great...

note2: tried jeremych's dll, still have ammo bug feature ( http://4d1.jeremych.com/z )

basically,

(i mean DLL file, raw is always in r90)

if i use r82,

>cannot join (see) aRev servers (in dedicated list)

>can use weapons without ammo bug in 4D1 servers

 

if i use any revision never than 82 (i tried with 88, 89 and 90* )

>can join (see) aRev servers (in dedi list)

>cannot use weapon in 4D1 (because of ammo bug feature)

 

* there is no 90's dll, dll was changed in revision 89 but in ToolBox's zip, it showing IW4M:3.0-1

note: dlls coming from ToolBox's updates. 2 days ago there was any problems and working great...

note2: tried jeremych's dll, still have ammo bug feature ( http://4d1.jeremych.com/z )

 

ToolBox probably forgot to change the value in the "buildnumber.h", (I have also revision 89 in my sig)

basically,

(i mean DLL file, raw is always in r90)

if i use r82,

>cannot join (see) aRev servers (in dedicated list)

>can use weapons without ammo bug in 4D1 servers

 

if i use any revision never than 82 (i tried with 88, 89 and 90* )

>can join (see) aRev servers (in dedi list)

>cannot use weapon in 4D1 (because of ammo bug feature)

 

* there is no 90's dll, dll was changed in revision 89 but in ToolBox's zip, it showing IW4M:3.0-1

note: dlls coming from ToolBox's updates. 2 days ago there was any problems and working great...

note2: tried jeremych's dll, still have ammo bug feature ( http://4d1.jeremych.com/z )

 

ToolBox probably forgot to change the value in the "buildnumber.h", (I have also revision 89 in my sig)

My buldnumber.h is perfectly fine. My sig's link should work flawlessly EXCEPT for the obvious no ammo FEATURE.

My buldnumber.h is perfectly fine. My sig's link should work flawlessly EXCEPT for the obvious no ammo FEATURE.

 

Sure?

It should be:

 

 

/* Generated by BuildNumber Version 0.8 */

#ifndef BUILD_NUMBER_H_ 
#define BUILD_NUMBER_H_ 

#define BUILDNUMBER 90
#define BUILDNUMBER_STR "90" 

#endif /* BUILD_NUMBER_H_ */

Or

/* Generated by BuildNumber Version 0.8 */

#ifndef BUILD_NUMBER_H_ 
#define BUILD_NUMBER_H_ 

#define BUILDNUMBER 1
#define BUILDNUMBER_STR "90" 

#endif /* BUILD_NUMBER_H_ */

This is what I have...

/* Generated by BuildNumber Version 0.8 */

#ifndef BUILD_NUMBER_H_ 
#define BUILD_NUMBER_H_ 

#define BUILDNUMBER 2
#define BUILDNUMBER_STR "2" 

#endif /* BUILD_NUMBER_H_ */

Why must it be edited?

This is what I have...

/* Generated by BuildNumber Version 0.8 */

#ifndef BUILD_NUMBER_H_ 
#define BUILD_NUMBER_H_ 

#define BUILDNUMBER 2
#define BUILDNUMBER_STR "2" 

#endif /* BUILD_NUMBER_H_ */

Why must it be edited?

 

#define BUILDNUMBER_STR "2" is standing for the revision

This is what I have...

/* Generated by BuildNumber Version 0.8 */

#ifndef BUILD_NUMBER_H_ 
#define BUILD_NUMBER_H_ 

#define BUILDNUMBER 2
#define BUILDNUMBER_STR "2" 

#endif /* BUILD_NUMBER_H_ */

Why must it be edited?

 

#define BUILDNUMBER_STR "2" is standing for the revision

._.

okay, Im gonna go and change it, though, im pretty sure it DOESNT matter....

This is what I have...

/* Generated by BuildNumber Version 0.8 */

#ifndef BUILD_NUMBER_H_ 
#define BUILD_NUMBER_H_ 

#define BUILDNUMBER 2
#define BUILDNUMBER_STR "2" 

#endif /* BUILD_NUMBER_H_ */

Why must it be edited?

 

#define BUILDNUMBER_STR "2" is standing for the revision

._.

okay, Im gonna go and change it, though, im pretty sure it DOESNT matter....

 

It doesn't...

Then why all the fuss?

._. Im done here.

Then why all the fuss?

._. Im done here.

 

* there is no 90's dll, dll was changed in revision 89 but in ToolBox's zip, it showing IW4M:3.0-1

note: dlls coming from ToolBox's updates. 2 days ago there was any problems and working great...

note2: tried jeremych's dll, still have ammo bug feature ( http://4d1.jeremych.com/z )

Then why all the fuss?

._. Im done here.

 

* there is no 90's dll, dll was changed in revision 89 but in ToolBox's zip, it showing IW4M:3.0-1

note: dlls coming from ToolBox's updates. 2 days ago there was any problems and working great...

note2: tried jeremych's dll, still have ammo bug feature ( http://4d1.jeremych.com/z )

Built it, and updated link.

Check this, that was interesting o.O

First, build number fixed (great!)

But showing only 4d1 servers (note, checked and rev is offline now, idk about it!)

 

And ammo bug not fixed, i think, you should change 90 with 82... its only checking this?

here is the screenshot

 

http://i.imgur.com/tsDUC.jpg

no ammo bug

is

caused

by

outdated

servers

(go back to r82 or tell the admin to update the server)

Check this, that was interesting o.O

First, build number fixed (great!)

But showing only 4d1 servers (note, checked and rev is offline now, idk about it!)

 

And ammo bug not fixed, i think, you should change 90 with 82... its only checking this?

here is the screenshot

 

http://i.imgur.com/tsDUC.jpg

 

1.*gg*

2.It shows u only servers? Jap thats FDO!

3.Ammo bug? -> Watch my sig.

yeah every1 knows this 'diffrent server version causes ammo bug feature'

 

and yeah again, we know this bug fix by using r82 client (which is same as servers')

 

but i want this: Using r90 (actually 89) with build number 82, i cant compile (yes i am n00b)

some1 please change its 90 to 82 and compile, it will fix everything...

 

why i am want this?

because i want legacy servers AND

play 4D1 w/o bug feature

why do you think changing a number u see in the top right will fix this issue ?

I seriously doubt it will

because i want legacy servers AND play 4D1 w/o bug feature

Its...

Im....

-Possible....

(atm)

because i want legacy servers AND play 4D1 w/o bug feature

Its...

Im....

-Possible....

(atm)

 

Right

Just wait for the forced update.

I tried diffrent situations (with noob work, also thanks every1 in this topic)

 

#define BUILDNUMBER "x"

this is which one server checks.

 

#define BUILDNUMBER_STR "x"

This is top right corner number.

 

 

Tried both 82 and 1-82... ammo bug not fixed. idk about Rev (they shutted down their server)

But, in source code, we can add more masterservers as 'legacy', going to add (actually change master.shtrev.net to server.steampro.de which is iw4play) iw4play's server, and test it

 

This (^ which is above this post ) developer using diffrent revision himself. i think that number coming from first m2, from aIW's m2... (and it can be 120 or more )

 

we need NT's buildnumber.h :mrgreen:

Ammo bug its caused because of outdated servers, so if they use r82 and you too it should be fine but the aRev thing was in r85.

Changing the build number doesn't downgrade your client. Use TortoiseSVN's 'Update to revision' function (or comment out the 'return true;' below the 'destructible_car' line in PatchMW2AssetRestrict.cpp).

or comment out the 'return true;' below the 'destructible_car' line in PatchMW2AssetRestrict.cpp.

And what will that do? Show aRev servers while having no no ammo feature?

or comment out the 'return true;' below the 'destructible_car' line in PatchMW2AssetRestrict.cpp.

And what will that do? Show aRev servers while having no no ammo feature?

It'll make it impossible to join legacy servers, but you'll enjoy the few other benefits of the current version (like the XP bar) while being able to connect to r82 servers without the 'no ammo' incompatibility.

l33chrev changed their master server, so maybe that's why it doesn't working with Legacy servers.