I do see your point, but i don't really agree with that. I understand that changes can break things, but fixes should not! Let me paste here exactly what the STEAM Update says:
- Cstrike FL_FAKECLIENT fix (3rd-party bots should work fine in cstrike once more) This is partially true! FL_FAKECLIENT is fixed, Yet bots do NOT work fine at all. Btw, i think Valve CAN test their product with the most used programs out there. Simply run a PODBot server , launch it, add bots, run for 5 minutes. Done. If this was done before release STEAM then the bug was already found (so you can see for yourself the statement 'bots should work fine' is not true) and so the statement should never be made in the first place. Don't get me wrong , i am not trying to bash Valve at all, as i apreciate their hard work, yet sometimes i get frustrated with things like this. This is not the first time that happened, and i never said a thing on the list before... This time however, i did report it and i hope something will be done about it. On Bots-United we are discussing possibilites on an information channel with Valve? IF Valve is interested in such a thing we can provide support from that scene and make sure things work, and keep on working with every release. -Stefan -----Oorspronkelijk bericht----- Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Namens Jeffrey "botman" Broome Verzonden: vrijdag 13 februari 2004 15:52 Aan: [EMAIL PROTECTED] Onderwerp: Re: [hlcoders] STEAM Update and messing up bots (Again) S. Hendriks wrote: > Suggestion: > - When releasing fixes for bots, TEST THEM FIRST. > > Wait, let me rephrase that: > - When releasing ANYTHING, TEST IT FIRST (and ofcourse, with > everything. Run a bot server, run a metamod server) Actually, it's not really Valve's responsibility to test a server with Metamod, AdminMOD, AMX, bots or any other type of plugin. Valve makes no guarantee that a new release won't break third party applications (although they try not to do this when they can). Valve obviously can't test each new release with EVERY single third party plugin, stats package, or server management tool that's out there. Some stuff will break. It's up to the plugin, stat, or server management author to check out their third party tool with each release and fix any problems that might arise. You can usually contact someone at Valve directly if you can't figure out what the problem is (or if no one else in the community can figure out what the problem is). Since there has never been any well defined interface between MODs and plugins (in terms of how the MOD and plugin interacts with each other), whenever the MOD code changes how something behaves, it's likely to break some plugins that are "leaching" on to that data. Since not every plugin author handles the same problem the same way, some plugins will break and others will be uneffected. This is just a fact of life if you are hooking into a MOD without that MOD's knowledge or consent. If a MOD team wanted to REALLY nasty, they could change how every single function was implemented each time a new version of the MOD was released making it very difficult for plugins to keep updated and working with new releases. Luckily, none of the Valve's MODs have ever done this, but occasionally performances changes in the MOD code effect how things are done and require plugins to be modified to work properly. -- Jeffrey "botman" Broome _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
