Zitat Faile Bashere (BS/2 Author):
Okay folks, alot of reports are filtering in about BS/2 not ID'ing things properly or just simply crashing after March patch.
As of the time of this writing, there is no solution, only explanation as to what's happening:
In March patch, Turbine decided to redo how they update stuff for fellow-ship members to make it faster (fellow stats are now server-pushed instead of client-pulled). After doing it, that removed a function from their .EXE that we (Decal devs) call GetFellowStats. What little known fact they (Turbies) didn't realize that the function they removed had an old loophole which allowed to get Item stats and not only fellow-stats and of course silently. We (Sixth Sense, BS/2, Eltank, etc) used that function to silently ID items in corpses.
Quote from srand:
[srand] I didn't realize that so many plugins were abusing the hole in the fellow ID code. Of course, you probably didn't realize it was a hole, so I'm not pointing any fingers. Suffice it to say that the original design of the fellow stats update system was ... not as good as it could have been, and we should have fixed it a long time ago.
So, what does it mean now? Decal devs are currently struggling to find an alternative to this function. This may mean a new Memlocs being released, or perhaps even new BS/2, Eltank, etc. being released to fix this issue.
There are some other things that one must be prepared for. Recently Turbine changed the logic as to how their regular ID'ing of items went and they made it so that every ID took 0.5-1second to complete and that you couldn't ID more often. If we are forced to use new functions for ID'ing, we might be forced to 0.5-1second intervals between ID's.
Another possibility, is that the devs may not be able to find the silent ID function and we're gonna have to settle for a non-silent ID'ing (meaning your ID screen is gonna pop up for a sec during ID'ing of every item)



