+++ Latest 6.5b Beta Patch release +++

[Maximus]

wow, with all of the new bugs I am sorry I even bought 6.5. I don't want to lose box scores now.

[endgame]

I may be mistaken, but I don't think this aspect is new to 6.5 at all. In fact, it may date back to version 5. Suffice to say, now that I hear it being talked about -- it sounds like an old topic and been around for some time.

[Sweed]

Originally Posted by endgame

I may be mistaken, but I don't think this aspect is new to 6.5 at all. In fact, it may date back to version 5. Suffice to say, now that I hear it being talked about -- it sounds like an old topic and been around for some time.

I actually think it was there in v4. In those days there was a utility that needed the playoff boxscores as the game didn't keep track of career playoff stats. IIRC when I went to get those boxscores they were overwriting the early games of the season.

So perhaps it was fixed for v5 when the almanac was added to the game snce this gave you the option to keep all boxscores. But for whatever reason it's only a problem with imported schedules which no one caught 'til now?

[RchW]

Originally Posted by Comedian2004

It seems to only happen when you use custom schedules that are imported.

What about schedules done in Stickware?

[playball335]

Originally Posted by alinkens

"Once the playoff games are started, it starts the numbering over, so the 1st playoff game is box1.html, which overwrites the original box1.html file. This continues thoughout the playoffs, overwriting all of the early box scores."

This happens in 6.5 too.

Why couldn't playoff box scores be stored with a "p" in front of them (ie: pbox1.html)?

I really dislike the fact that player id's and box scores are re-used. These are key fields that should have unique id's.

[endgame]

Originally Posted by RchW

What about schedules done in Stickware?

Distinct possibility that this errs as well, given that it is a custom schedule. I'll look when I get home tonight at last years Almanac and check out the early games. I always use Stickware.

[endgame]

Originally Posted by playball335

Why couldn't playoff box scores be stored with a "p" in front of them (ie: pbox1.html)?

I really dislike the fact that player id's and box scores are re-used. These are key fields that should have unique id's.

Because then we'd need to change the "p" back to an "r" at the end of the season in order for Cato to .... oh, no, that's something else. Just kidding.

To my recollection, it's a function of the game's mechanics and won't ever change. Even using ctorg's Unique Images formula, while the p#'s are under a great deal more control I still occasionally get someone picking up an old history in their text. One of the drawbacks to versions 6 and prior I think we'll always have along with the off-setting benefits of a version.

[Comedian2004]

I hear that quite often... that bug was in version 4 or 5... yet, if you go to

http://www.ootpdevelopments.com/newsletters/nl0010/

You will see that this was the announcement when 6.0 was released...

"The game engine has been completely re-written from the ground up."

Apparently they used some of the old dirt in the ground.

Originally Posted by Sweed

I actually think it was there in v4. In those days there was a utility that needed the playoff boxscores as the game didn't keep track of career playoff stats. IIRC when I went to get those boxscores they were overwriting the early games of the season.

So perhaps it was fixed for v5 when the almanac was added to the game snce this gave you the option to keep all boxscores. But for whatever reason it's only a problem with imported schedules which no one caught 'til now?

[Sweed]

Originally Posted by Comedian2004

I hear that quite often... that bug was in version 4 or 5... yet, if you go to

http://www.ootpdevelopments.com/newsletters/nl0010/

You will see that this was the announcement when 6.0 was released...

"The game engine has been completely re-written from the ground up."

Apparently they used some of the old dirt in the ground.

Well I've always taken game engine to mean the "in game engine". That is that the DIPS engine was written from the ground up. Nowhere did they say, as they are now for ootpbm, that the game was written from scratch.

It was obvious the data base stayed the same as you still had the same old limitations like 25 year careers, rbi limits, etc.

I'm just saying that with v5 and the almanac allowing you to save the boxscores could be why it was fixed. But for whatever reason it still overwrites when using custom schedules, so Markus would have to figure out why. I would imagine the reason you don't see it in a 24 team league with custom schedule is you don't reach the point where it rolls over.

Of course all just speculation on my part.

[Comedian2004]

I did not use custom schedules in my 24 team league, and it never rolled over.

It has to do something with the 'end' of the season would be my guess.

I discovered this flaw when I was writing my HTML schedule routine. I could not figure out why my program was not working for this league and then noticed how it was changing the playoff boxscores.

[Comedian2004]

BTW, this is the same page that still shows:

AND Coming Soon to an OOTP Baseball Game Near You!
A boon to multi-player leagues, full head-to-head play over the Internet!

[Maximus]

So this bug is only there when using custom schedules, correct?

[Comedian2004]

So, yes, this is what my testing has shown.

Originally Posted by Maximus

So this bug is only there when using custom schedules, correct?

[jjguards]

what happened to the 6.5 a patch

[Bluenoser]

Originally Posted by jjguards

what happened to the 6.5 a patch

6.5a has been out for quite a while.

[Malleus Dei]

Originally Posted by Maximus

So this bug is only there when using custom schedules, correct?

That's been my experience of it.

[StyxNCa]

So when is this patch due out? While waiting for it I have discovered another game which is slowly eroding my interest in OOTP.

[Malleus Dei]

Originally Posted by StyxNCa

So when is this patch due out? While waiting for it I have discovered another game which is slowly eroding my interest in OOTP.

http://ootpdevfiles.com/ootp/ootp65b_beta.zip

Which game? Diamond Mind or PureSim?

[endgame]

Originally Posted by Markus Heinsohn

Here it is:

Download 6.5b beta

The following things were fixed or enhanced:
- Fixed the 'bad player bug'
- Fixed throwing error scoring
- Fixed displayed fans interest in team financial report
- Fixed importing of historical rookies, some players with few career ABs got overrated
- Fixed importing of single players
- Fixed reporting of contract extentions in the player HTML report
- Changed the transaction reports so that Catobase should work in the future
-----(endgame's edit)---- apparently NOT confirmed (see continuation of post)
- Roster limits in the postseason are now correct
- Players who retired mid-season no longer go to the free agent pool
- Traded draft picks are now properly reset when the draft happened
This should be the last beta... please list things that I forgot to fix. After these have been fixed, the patch will be officially released.

Now that this thread has fallen to the second page, I thought it timely to ask for a reasonable current assessment. It appears that the fixes alleged above were indeed addressed adequately, with the exception of Cato that still has some quirks being worked out occasionally in the forums.

Beyond that, it seems from my vantage, the list seems quite small. Please comment if it appears I've omitted or assumed anything incorrectly. Also, I've reposted one of my earlier comments as a conclusion because I still believe it's integral in the public domain to communicate effectively.

That being said --- after a quick review, this is what I see --

Issues Awaiting Official Response or Action:
In no particular order of impact or importance --

Duplication of players related to the All-Star Break
DFA Service Time
Box score overwrite with playoffs and custom schedule
Handling of substitutions after ejections
Handling of substitutions after PH
Misc clerical items
Injuries without origins
- New problem with 6.b and Catobase -- see SandMan's link:
http://www.ootpdevelopments.com/boar...4&postcount=18

Some of the above are explained in --
Original early Beta Testing thread
http://www.ootpdevelopments.com/boar...d.php?t=103299

And, as I indicated, a previous comment I believe needs re-stated:

Originally Posted by endgame

Frankly, I don't care where what's posted as long as somebody's actually taking the time to review, filter, and priortize the comments. But I can't say my confidence (normally a staunch advocate) is high at this point. I would prefer if we knew what was on the table still being looked at, but at this juncture who knows what, if anything, remains there. The inference is nothing beyond what we now choose to address. What about this thread?

http://www.ootpdevelopments.com/boar...d.php?t=103299

Isn't that a reasonable resource beyond the traditional, yet unconventionally quiet Beta-testing "team", to gather the what-I-forgots"? I don't mean to sound overly critical, but the more I read the announcement, the more troubling it became. If there are issues that are going to be determined dead-in-the-water/nothing-gonna-happen, then it should be addressed and put to bed. When something is in progress to be evaluated for its merit to fix, say that. Just so all issues have some type of status or determination rather than leaving a public's participation more akin to throwing ring-toss and then waiting for the mail-carrier to tell you if you took home the big teddy bear or the plastic de-coder ring.

[endgame]

bump

Given no one has been inclined to comment, I've updated the list (in bold) with the recent addition of SandMan's finding with 6.5b