Droid Engineer Archive
Thread: Out of 10 how do you rate the Plan(tm)?
I may not be correct but I really dont wish to see ppl wanting to add Blaster Ranges, long short range modules to Protocols or R2..LOL. Just give us a fricken combat droid...simple. Just like the probot, except stronger than an entertain with a CDEF. Droideka would be perfect.
--Gefuri Ada, Master Droid Engineer
3
Compared to the CH plan, ours was a rush job wish list
I had high hopes for this, and *hugs* to our poor Sintrosi, you cant win against indifference..not your fault I know.
Its only 3 because Devs actually said something - as to solid content its a 1 at best.
4.
Better than ignoring us, but they seem to be listening to some of the wrong things.
As a wishlist or feature-add? 6-7
As a list of items that will be addressed currently which are wrong/dysfunctional that will be fixed in the short term? 0
I think that's the list we all expected to see, personally. Or, in reality, I think I was hoping to see both of the items above...along with some ETAs.
Honestly.
I know the Devs hate to give them...but I wanted them all the same.
And, I don't think it's impossible to ask for on or maybe even expect it. They are professionals. They should be able to provide such information....seriously.
This simply didn't seem like much of a "plan" document to me...more like it was written on a bar napkin (no offense).
/bow
Respectfully,
The plan has fulfilled some but not all of these, so I will subtract from 10.
Points on this plan deducted for:
* format: basically an open letter with some bullet points. not a Plan.
* listening without hearing: the DE Voice said "We want new combat droids", not "We want the 45th Kamikaze Mouse Brigade".
* the obvious paying-customers snub: CH gets the detailed 2-part plan hand-delivered by SOE representative, with extensive justification, explanation, and specific detailed changes. DE gets a coffee-stained post-it note, left on the door for Sintrosi to pick up. It didn't have to be so blatant.
* lack of justifications: why these particular and few changes? I mean, I understand that some will simply be low-hanging fruit, the minimal effort changes. Was the rest design-by-committee, ensuring blandness of plan? Design by junior designer? Design-by-desperation because of spaghetti code crippling the droid codebase?
* content-poor: There's just not much there, a skeleton without flesh.
All in all, a letdown.
2 for effort and on-time.
3 - It shows some promise but not enough to bother keeping the profession.
10 - for the fact that correspondant system seems to have some functionality and all the hard work on everyone's part. I am just a jaded DE.
MikeBauerTwo, Eclipse
MasterDE, Master Artisan, Noice Rifleman, Novice CH(Had to since my probots got owned all tooooo fast)