What's the word on the release date for the next version of Decal?


Anyone?


Locked: Trolling

read the sticky threads.

Given the frequency of previous updates and the date of the last update, one can extrapolate that it will be between 1 minute and 2 months.

 

-----signature-----

he measn the stickeies that have not been changed in over a month....

I mean the stickies where it says not to ask for any ETAs.

the problem I'm seeing is that there are 2 {soon to be 3 Alpha versions} of Decal floating around, and pluggies are getting stranded in "previous" versions of decal. You have to run different versions, to run different plugins.


getting kinda cornfusing


But Thanks for the hard work....didn't want to forget that

 

-----signature-----

Beezamen: since decal isn't really meant for end-users right now, that shouldn't matter.


As was pointed out on the ACDev forums, if you're not running the latest versions of alpha, then you aren't assisting the decal developers. That isn't to say that some of the plugin developers don't feel differently... although they should be developing for the latest version of decal.


The only one I'm publically aware of that wasn't developed for Alpha 4 was ELTank because of the busted HUD rendering code, and that is acceptible. However, developers shouldn't allow plugins to be downloaded and used for older versions if they write a version for newer Decals. Gouru removes all traces of his plugins when he upgrades and he asks that people do not mirror or allow downloads of older versions because they are unsupported.


the confusion is in that people are trying to "play" with Decal which is in a very fluidic alpha stage. The different versions of plugins for Decal are mainly because of the interface changes which won't allow older versions to work with it. Once Decal hits Beta, all of those changes should have been made, and plugins should be able to be used across Decal versions. It shouldn't be like it currently is where certain plugins will not work AT ALL with newer versions of Decal.


Decal is not in a "playable" state. It's in Alpha TESTING, and only the latest versions are supported.

Yea... don't run decal, but if you run decal only run the latest to help, but don't report problems because we wont help as your a end user, rinse and repeat.

That's not completely true.


(although partially is)


The thing we WANT is people posting singular issues and requests with the appropriate information to the appropriate place.


This is usually not done properly by someone who is considered an "end-user"


what we DON'T want is people testing making new threads about known issues, complaining, asking for support with inaccurate or incomplete problems and generally just causing problems and delays with the Decal Devs.


There is certainly something to be said for accurate and complete bug reports. There were a lot of bugs found in the first stages of alpha through public distribution. But for every GOOD report, there were 10 bad ones. Sifting through those 10 bad ones to find the one good one was a waste of time, and lead to a LOT of frustration.


So that is why I said it's not completely true, but at the same time is.


"End-Users" shouldn't be looking for support in Decal until late beta and release.


"Testers" can look for support at the next phase of alpha unless otherwise specified in the announcement thread.


and legitimate "plugin developers" can always look for support.


It's a tiered system. Plugin Devs are at the top, followed by Tester (Computer Professionals), followed by End-Users.


If you think you can create proper bug reports, and don't need someone to hold you hand to get Decal to work, then you might be able to upgrade yourself to a Tester from an End-User. Only time and posts will tell. Just be aware that at any time based on your bug reports, it is possible you can be degraded to an end-user.


(when I say "ou" I mean anyone reading this.. no particular "ou" I am talking to. Just a general statement for self thought)

I came so close to copy pasting 90% of that statement and putting it into an annonymous email to our entire Cs and Qa staff here at work.