Numbering all of releases PB2.6mm
 

Because there is still the same location and still the same file name (podbot.zip) for all releases, maybe is better add the version number for each release - for example PODDBOT2.6mm ofic. release 15.
Somebody suggested to change the file name for adding date to it, but maybe my idea is more confortable.
All known me metamod plugins have this number for each release - for example:
StatsMe 2.8.0.7 beta 15, ClanMod 1.80.19 beta 1 , etc.
Additionally - for all these numbers You have specials variables and You can use them in, for example, statsme sm_motd. Here You have an example to better understand, what I mean:

sm_motd " * {C.statsme_version?StatsMe $:#}"
sm_motd " * {C.clanmod_version?ClanMod $:#}"
sm_motd " * {C.admin_mod_version?AdminMod $:#}"
sm_motd " * {I.atac_version?ATAC $:#}"
sm_motd " * {C.chicken_version?Chicken $:#}"
sm_motd " * {C.hlguard_version?HLGuard $:#}"
sm_motd " * {C.csbld_version?CSBLd $:#}"
sm_motd " * {C.plbot_version?PLBot $:#}"
sm_motd " * {C.booster_version?HL-Booster $:#}"
sm_motd " * {C.amx_version?AMXMod $:#}"
sm_motd " * {C.axn_version?AXN $:#}"
sm_motd " * {C.bmx_version?BMX $:#}"
sm_motd " * {I.t13_killcam_version?Take13 KillCam $:#}"

There is a missing line ;):

sm_motd " * {C.podbot_version?PODBot $:#}"

If You don't like my idea, please simply remove this thread from forum.

Re: Numbering all of releases PB2.6mm
 

keep going......keep going

Re: Numbering all of releases PB2.6mm
 

Yes, that's a good one. Besides, it would make it easier to talk about bugs / fixes / improvements / overall performance of different versions. The RealBot guys can say something like "In this or that respect, WIP #9 is even better than Final 1.3" or something - we can't. We must look up the date of the file, that's a bit more uncomfortable for all of us.
But it's also uncomfortable for the coders, at least if they don't keep older dll versions on their HD. Imagine this: Bug A is finally fixed, but bug B (which had been fixed earlier) suddenly appears again - Now if you could compare all relevant parts of the last source code (where B was fixed) with the new one, you might find the problem faster.
I'd suggest posting new / fixed / hacked dll's here in the filebase (with version numbers) and keeping the last thoroughly tested and approved one at the "normal" download link...

Re: Numbering all of releases PB2.6mm
 

cool i was gonna say this....
i will also look back through the old pb thread so i can seperate the version history by date ..and was wondering if build no. will costitute to the the no. of releases since pmb started to work on podbot?