Droid Engineer Archive
Thread: DE Goodies for Publish 6
/bow
Drashk wrote:
Just an observation here, but I find it interesting to see some peoples reactions after having asked that bugs be fixed first, before new content is added.
While we wanted the bugs fixed, I guess that the profession at large would have chosen different things. Maybe not...just a guess. For example, the fact that we cannot yet name droids that take a Personality Chip (Protocol, Surgical, LE Repair) says to me that AudioOrgana will probably be sad as will others.
I also find it interesting to see that people were hoping new content to be added, even though the community has voiced that it would like to have more of a say into what is added.
We wanted new content, yes. The fact that BLLs and Protocols now have more of a purpose is a good thing. However, I don't see that as "new content". I see it more as correctly a mis-implemented feature that we had at launch. That's not content. That's a fix.
Yes, many of these items should have been addressed in the first months after release, but unfortunately Player Cities, Mounts, and Vehicles took center stage.
Actually, a lot of this stuff should have been addressed even before release...but that's a different story (and now water under the bridge).
Those three items have changed the way that many people play SWG.
Everyone really needs to keep in mind that none of our issues are going to be fixed overnight.
Drashk: We have been told that we were "on deck" for many, many weeks. That hardly constitutes "overnight". Even 2-3 months of being a 'priority' should allow for a lot more than what's on this list to be accomplished.
New content takes a long time to develop.
That's all well and good. However, I do not see new contentin thislist...in my definition of "new content", anyway.
I've made my thoughts clear to TH that communiction is a major issue, especially in regards to items such as the Droid Invasion.A lot is happening right now and the only advice that I can give everyone is to be patient.There are no quick fixes to our profession.
I see the communication gap as a major issue as well. As a matter of fact, I have a pretty strong feeling that if we'd had more direct input from the red-names (and feedback to them on those posts made by you/Sintrosi), we might have a patch that more closely fit what was important to address.
Basically, I feel that this update would have been more to all DEs' liking had they simply engaged us a lot more directly on what they were thinking should be done next.
As best as I can tell, they chose some pretty low priority items to work on here. Am I wrong?
Respectfully,
TheRealTK421 wrote:
Drashk wrote:
...aren't 100% guaranteed to make it out with the patch.
I find this particular statement to be very worrisome.
I put that it because I just want to make the community aware that snags do happen.Each time a patch hits TC there is usually some item that is pulled before it hits Publish.Case in point, the Customization tools the first time on TC and the Combat system in the last patch. Now that there are more Droid Engineers on Test Center, the droid issues will be tested a bit more. What IF, an issue popped up that made it impossible for Cluster Modules to be used at all, on the last week of code tweaks? IF something like that happened I would rather that the code be pulled and added a few days later instead of it being added with the rest of the Publish. That is all that I was pointing out.
TH is still trying to find out some info about a few of the concerns I had about the patch notes.
What are those concerns (or are you not allowed to share them with us)?
My concerns were about how many modules per the BLLs and Protocol Droid, whether or not the customization tool change included XP for using it, exactly what changes were made to the Cluster Mods (if it included which droids they can be placed in), and if the crafting station fix was in reference to the droid/private station issue that some have reported. I'm just trying to find out all the information that I can, to clarify for everyone so that the questions that have popped up alreadycould be answered.
There has been a major outcry coming from some of you for information about the Droid Invasion.
Just to clarify...does the information below constitute the "Invasion" or something that's just leading up to a bigger push? I think it would be good to know.
I only report what I can and what I see. I have no information that can be passed along about the 'Invasion'. I just wanted to give everyone a sign that there is communication between the community and the DEVs and that what we asked for, bug fixes first, has been heard.
Kollos wrote:
Given SOE's history, it is far more likely that they would take steps to preserve the functionality of all those droids - after all, the end user might not have known whether or not the droid they were receiving was an exploited droid. Some Droid Engineers simply used the bug to get around the need for level 6 modules by putting in a pair of level 4s instead... and that's something that the end user cannot detect.
Look at what they did with the smugglers... they banned those who exploited and I believe they deleted the guns. Why not the same stance for the droids?
Drashk, it just seems that this is just another attempt to keep us quiet. The battery issue, armour issue, customization issue, broken chassis', etc. are not even addressed. It's just... meh... I don't see how increasing battery time is a game wide issue, I don't see how making colour stick with the droid is a game wide issue, I don't see how increasing the customization charges is a game wide issue, I don't see how rebalancing the DE schematics so I don't need as many **edit** MA parts is a game wide issue... these are all things that can be discussed in one day and implemented in another day. Changing a few values here and there (with the exception of the droids colour not sticking through, but they have the armour colourization thing working so why not add a 1 free colour to a droid that anyone can do immediatly after its tamed?).
FFS, patch #6 and they're FINALLY getting around to fixing the lvl 2 storage?!?
That would have beena nice fix. Who gives a crap about custumization tool droid exp?
BlueMorgoth wrote:
Drashk, one request for further clarification: Is the bug with item storage modules in the Surgical (2-1B) frame fixed too? I really hope it is because that's the only thing preventing me from selling a hell of a lot more of these to Docs. Docs want Med + station + item storage in a single droid and in the majority of cases would prefer to have the Surgical frame as that is "more star-warsy" than having the same setup in an R2 or R3.
Ackis wrote:
Look at what they did with the smugglers... they banned those who exploited and I believe they deleted the guns. Why not the same stance for the droids?
That was a "game breaking" exploit. It basicly allowed you to turn a weapon into a one **edit** killer against any target or a set of armor to the most powerful eefectiveness allowed and 0 HAM costs (almost). Also, they apparently put in 'triggers' to catch people using those exploits.
"Who gives a crap about custumization tool droid exp?"
no one. exactly.
who gives a crap about knowing how much power their droid has left and having to recharge it every 15 minutes - everyone
or having 2 droids out at once (CH can have multiple pets out at once so surely it can't be that complex)
or being able to call my droid without being in a freaking camp (as easy as changing a 0 to a 1 somewhere).
I have to admit, I would NOT mind seeing 'impossible' droids being affected in some way by the update. If a probot's got 10 item storage, medical, food crafting and a repair module, it's obviously been made incorrectly. But a probot with JUST 10 item storage and medical is quite possibly 'legal' (although it's certainly possible that the storage came from a cluster, rather than a level 6 module).
Droid made using exploit (ie: more modules than possible) morphs into a Cyborb Ancient Krayt that agros you. w00t!
Ahhh... I'll go to lunch now.
I see a few needed patches (especially on the exploit) as a really good thing. And, for several reasons. First, for the patches themselves. Second, it means they are taking the time to think through the changes happening to DE (hopefully). And, third, hopefully they will discuss things with us to see not only what we think would be useful, but what we think would be a hinderance or abused.
I just hope that they are taking the time and making the effort to consider droids and their impact on the game. And, I really do hope that they consider the input of the DE and player community in what and how to implement.
Ackis wrote:
Look at what they did with the smugglers... they banned those who exploited and I believe they deleted the guns. Why not the same stance for the droids?
And look what they didn't do with all that exploited Krayt weaponry. Every single one of those guns that had already changed hands still exists. The only ones that were deleted were the ones still owned by the exploiters who created them.
I'm not aware of the smuggler issue you refer to. What exploit was that?
Basically, it comes down to knowledge. SOE will not punish an unknowing end user. The recipient of a Droid deed is in many cases unknowing, so SOE can't risk deleting all of those droids.
I agree with others. Its nice to see they are doing something, but there is no new content in the list you've provided. Those are all no-brainer fixes that address a couple thing that have been obviously broken for ever.
If that's the droid invasion then I have to say it is quite falsely billed. Giving the protocol droida slot doesn't actually make it useful. It makes it so it can do something, but, like the surgical droid, he still can't be named, still can't be programmed properly, andstill has no more functionality than an Advanced MSE mouse droid. There's still no reason to actually buy one other than the way it looks. The same is pretty true of the BLL. Even with a couple slots, the easier to craft R-series droids are still better than it is in every conceivable way (other HAM and maybe looks). But HAM means nothing for droids that can't fight, and most customers are not interested in a good looking droid that does less than most other droids, oncethey realize that they can only own one droid.
Sadly, the list you've provided is a list of things that should have been hot-fixed months ago. All that list tells me as that some developer is finally looking at the profession. Doesn't give any indication that they understand the issues or have plans that will really fix the problems with this profession.
I'm very glad to see some bug fixes and improvements to current chassis. This is a good sign and I'm glad they're correcting and improving bugs and problems that have been around since publish. Good work.
I'm NOT happy that we're still completelly in the dark about this future "Droid Invasion" plan that is being cooked up by the Developers. I understand that notes for Publish 6 wouldnt' necessarily touch on in-development issues, I'm just speaking overall. The silence is deafening.
We need the communication SOE... put your money where your mouth is.