Still Waiting For Bb3 Documentation?

What's the status with documentation? Is there an ETA?

Can it be published in its current state and added to over time like you do with versioning of the actual BB software? I'm sure there are some useful guidance in there that could help us now, rather than delaying it until every aspect of BB3 is added.

I checked the current articles out here... but it doesn't look like it's been updated since last year.

 

Thanks, I've already checked that out. It touches the surface but really just want documentation for using the software.

What's the ETA? a week? a month?

 

Good to hear. Look forward to reviewing!

Thanks

 

any closer? Almost a month since last response.

 

Been doing work on it with the team on it, it's very close at this point. Basically going through last revisions and will go live

 

Music to my ears!

 

Awesome. Can’t wait for this.
I’m sure you know already but “this.worldPosition()” is documented incorrectly.

Also as discussed in Discord, worldToScreen() doesn’t work post-export.

 

As a software project manager responsible for Agile teams....just remember "don't let perfect be the enemy of good enough". Release, inspect, adapt.....

 

wooooah a manual too, i just found out about the tutorials, def learned somethings that i didn't know from it..
made an easy to playlist:

 

ETA?

 

The team is filling some last needed entries as we speak. It is incredibly close, sorry for the delay

 

We have to remember that if a exact date is given, everyone will get their hopes up. If we find something out that makes it take longer. People will be more upset that a date had to be delayed. When it comes to software ETAs get changed a lot. It’s best if we don’t confuse anyone with an ever changing ETA

 

no confusion... i think there's just 4 people waiting on documentation, lolz

 

"The team is filling some last needed entries as we speak. It is incredibly close" ... incredibly close ...
I don't know what to think about this term "incredibly close". The last time I checked .. it meant a few days.

 

I've been incredibly close to releasing my game for the past year. I think it must the that kind of incredibly close

 

you do need to understand that while we can be incredibly close one minute, it doesn't take much to change the time needed. this is just how coding is. we going through all this, so you don't have to.

 

That makes sense when it comes to adding features to the software itself but not to fundamental documentation. You can't remain in a perpetual state of adding articles to unpublished documentation when chasing a continually evolving product. That's digital product 101!!!

Something has to give. You have to stick a flag in the ground and just publish something.

I mean, that's what's going to happen to it anyway when you add new features to the software further down the line. You're going to have to align documentation updates simultaneously with the software (well, at least it should be the case but judging by the current state of affairs I'm not confident that will be how things proceed).

What's frustrating the most is that this has been going on for far too long. I appreciate resource is tight but no way should it take so long to produce. When I first voiced this grievance, Trey responded acknowledging it as a priority. That was in June. It's now November.

It wouldn't be so bad if support was more responsive but it just isn't and so we have to rely on forums that are pretty unresponsive at the best of times. You cannot realistically expect the community of a paid product do the work for you.

Enough now. As @chadh0130 correctly said: "Release, inspect, adapt".

 

Exactly! They need to provide us with documentation though it may be 0.0.0.1. version. And over time, it needs to be constantly updated.
Man I'm just mad at their way of thinking !!