Droid Engineer Archive
Thread: Did they nerf Adv Probots and Adv Protocol droids?
I did get your point. Up until the last patch, the most modules that could go into a droid were 5 (1 crafting station, the 3 "big" modules", and repair module), which made the extra slot on the adv R3 useless. The profession currently allows you to mix and match any module with any droid (with some expceptions because of bugs), and with the exploit there was no advantage to being a Master DE or to have advanced versions of droids. Your logic is flawed, going with the basic design. A master DE should have an advantage over other DEs because they are a master. That means they can put more into a droid than other DEs. As well, look at the advanced version of a droid. If what you say is true, what's the point of having advanced droids? None really, because you could exploit stack and get the benefit with lvl 1 modules.
Mazepa wrote:
Sadly you don't get the point so let me try to clarify. The point is droid engineering shouldl be about mixing and matching various droid modules to different chassis in order to promote variety in crafting and in the droids that people buy. I agree that the stacking of like modules to imitate higher level modules did not make sense and was a bug. What I don't agree with is not allowing the general module socket clusters to be used in the droid harness slots. The reason is it takes the fun and the "engineering" out of droid engineering. You have all these nice modules yet most droids can now only take two. Before you could get at least get six modules installed which made for more fun crafting and also made folks enjoy specing out a droid with varioiusoptions and most importantly having the freedom to pick different chassis. Now the only thing people will want to buy are R3's and probots. And the only modules they will be able to fit are medical modules and one craft modules (90% of the time is chemical). No more repair modules, item modules, data modules, etc. It used to be nice to tell folks pick what you like or can afford and as a master droid engineer, it can be built. Now it will be sorry you only get 2 unless you want an r3. That is not what engineering is all about.
If you read what I wrote, you will see that I merely proposed what droid engineering should be like: the ability to mix and match modules and chassis with the level of the droid engineer dictating how many modules can be stacked in a chassis. That way the Master Droid Engineer is the one who can make the best and most useful droids.Customers couldalso choose what they want or coudl afford. And this would encourage more variety to be out there and reward those who are more advanced in the class.
Unless there is some improvement in the long promised droid engineer update, this change will drive customers away from droids even more.
first off, not even 1 probot shematic ever said cluster.
they always showed module harness. period
if they took instead of single module a cluster then it was a bug. i never even noticed this lol and you did. good for you but now consider that bug fixed then and intended. live with it and now on build droids like they supposed to be. emmm buggy, worthless but cute lol
SigSauer wrote:
Wow, I didn't mean cause any hate and discontent here. I just wanted to know what happened to the socket clusters in the adv probot and adv protocol droid schems that I used to have. Yes, I repeat the schems I had listed socket clusters for both these droids. The schems did NOT list just socket harnesses.
If my posts were felt that they were targeted in a mean spirit at anyone they weren't and I apologize. This exploit has been fixed finally and it's time to move on. I do not blame the devs, they appear to have been listening to a select set of supposed experts on these forums, who I should add need to be subjected to refereed home drug tests before they, like you, are allowed to post again. Each change you ask for is carried out to the best of their understanding and then like people operating with the drug induced short term memory loss, you all howl about them.
You need to poke your head out of the intellectually incestuous little group of agreeables you hang with and actually see what most people *playing* the game rather than spending working hours in these forums feel about this profession...
By your own idiotic requests you have by my census 8 handedly emascualted all but two ADV schematics...
Congratulations. The biggest problems with the DE profession has turned out to be that no Devs actually play it so they have to trust numbskulls like you for feedback..
Call to SONY, Ignore posts from these forums, dedicate one dev to actually playing a master DE, I will provide SONY my login to use for testing...seems like the best thing to do till these forum eunuchs go clean of their respective medications.
Svengali/Kettemoor
Gribnitz wrote:
Welcome to the real world Exploiter. You screwed your brother DE's who were building droids the way they were supposed to be built. Now that you can't exploit every friggin droid you make, you are on an even footing with the 95% of Droid Engineers that didn't take advantage of a bug.
May all your droids rust in pieces.
Look, you are not exploiting a bug if you didn't know it was a bug. And this guy clearly did not know. Chill.
I'm sorry, Svengali, butwhat aretalking about?!? The dev's haven't implemented much of anything that the people here have been asking for. So your basic premise doesn't even have a basis in reality.
The cluster modules were never intended to go into the service module slots. Yes, the fact that they could meant you could make some really nice droids, but it was never intended to be that way.
The haven't reduced the profession to the point where only a couple of chassis have any value. The profession has always been that way. There was just a bug that let a DE work around that problem if they wanted to. They fixed the bug in preparation for the updates to the profession that they are planning in publish 7 and 8. Plain and simple.
Gribnitz wrote:
Welcome to the real world Exploiter. You screwed your brother DE's who were building droids the way they were supposed to be built. Now that you can't exploit every friggin droid you make, you are on an even footing with the 95% of Droid Engineers that didn't take advantage of a bug.
May all your droids rust in pieces.
Look, you are not exploiting a bug if you didn't know it was a bug. And this guy clearly did not know. Chill.
Mazepa wrote:
I agree that the stacking of like modules to imitate higher level modules did not make sense and was a bug. What I don't agree with is not allowing the general module socket clusters to be used in the droid harness slots.
Audio
Ackis wrote:
SigSauer wrote:Wow, I didn't mean cause any hate and discontent here. I just wanted to know what happened to the socket clusters in the adv probot and adv protocol droid schems that I used to have. Yes, I repeat the schems I had listed socket clusters for both these droids. The schems did NOT list just socket harnesses.
I hope my posts didn't come off as that. Usually I'm very very passionate about this exploit, however it's been fixed. Enough said.
Yes, you do come off that way.
And I have to agree with Svengali to some extent. By trying to defend the 'turf' of the master DE (on the servers with resources that support type six modules, which isn't all of them), you (and others) succeeded in making an already low value profession less while screaming that it needs to be more.
Stacking clusters, so you can make everything (eventually) six class six or better, out of crap components? Bad. Being able to make varied droid chassis with the same general capabilities? At least as good as giving bio engineers skins where the ONLY difference in capacity is what goes INTO the skin (take two roughly identical dna templates, put them into wildly different skins, you get the same pet in capabilities... but the look can be tuned to the end user's desire. Once, this could be done with droids. Due to your fervor, venom, and anger that it didn't meet YOUR vision of How Things Should Be, this ability is lost. Your profession is made less. Your client base, who might have ZERO desire for an R(x) that can't hold a paint job, is reduced.
But you holding the master tag can feel proud that you've got a miniscule purpose in an almost fatally broken profession.
Bravo!~
Gribnitz wrote:Welcome to the real world Exploiter. You screwed your brother DE's who were building droids the way they were supposed to be built. Now that you can't exploit every friggin droid you make, you are on an even footing with the 95% of Droid Engineers that didn't take advantage of a bug.
May all your droids rust in pieces.
And you, 'sir', are infinitely worse. Your attitude and your method of addressing people is exactly the sort of thing that makes others wish for assisted Darwinism. As above, removing clusters from general use (NOT the nesting bug/exploit, but clusters in general) does not level the ground, it removes customization and reduces the droids you see in the world, making the 'we want to see droids in wide circulation, it IS Star Wars' attitude suffer -even more-. To accomplish YOUR goal, stratifying skills so a novice can't imitate a master, look to the OTHER professions things have been done to. CL limits on certain skins for BEs, Pet level limitations for CHs, etc etc.
A better approach would've been more and varied cluster schematics (that could not be nested) with class 6 clusters only being master and the others scattered up the line so that EVERYONE could make droids desired by customers. But no, you wanted it (with so very much hostility) validated that what you thought of as an exploit was labeled as such, that it was closed off, and that your leetness of master of an impaired profession was protected.
I hope you enjoy Publish 7, Droid Evasion, where multiple new CL10 useless combat droids, utility droids that assist no actual in-game tasks, and RP aids that autostore and can't keep up with a squall are implemented... And that even that will be a step up from the current state of the profession.
Malitevv wrote:
Look, you are not exploiting a bug if you didn't know it was a bug. And this guy clearly did not know. Chill.
