Droid Engineer Archive
Thread: Pre-Publish 18 Droid Deed Warning
Drashk wrote:
RasalTheWise wrote:
Also, I can confirm pre-patch droid deeds do indeed come up with combat stats and do fight. It's sad to see the AE of my probots go from 9000 to 1217.
Just to confirm this.....
- A deed that you built prior to Publish 18 is coming out with combat stats?
- What exactly does the deed list?
- Was this droid on a vendor?
1) This was a deed that was crafted via factory before Publish 18 went in, and it does have full combat stats (damage, armor, etc).
2) It actually shows all the combat stats I normally see from a pet, but I'd have to log back in this eve to get the specifics
3) This deed was pulled from a crate that I pulled from a factory output hopper.
RasalTheWise wrote:
1) This was a deed that was crafted via factory before Publish 18 went in, and it does have full combat stats (damage, armor, etc).
2) It actually shows all the combat stats I normally see from a pet, but I'd have to log back in this eve to get the specifics
3) This deed was pulled from a crate that I pulled from a factory output hopper.
Sweet.
So at least Factory crate pull deeds are converting properly.
Would you happen to have any single deeds sitting around, that are not on a Vendor? The problem we are seeing may only be limited to droids that are currently listed on a vendor.
When you check the deeds tonight, besure to keep an eye out for the Combat Rating. I think that is the key factor here. If there is a Combat Rating listed on the deed, when you use it, then my conclusion would be wrong. However, if the Combat Rating is not listed on the deed, then it only helps to illustrate that deeds with a listed combat rating are not converting, because the system does not recognize the rating in its old form. If that is the case, then a fix may be easy to create.
RasalTheWise wrote:
3) This deed was pulled from a crate that I pulled from a factory output hopper.
Before or after the publish I suppose is the real question.
I couldn't find any crated combat droids myself, so I can't test it.
Drashk wrote:
Xrystal wrote:
Hmm, so are you saying that the combat droids I made with at least 1 Combat Module and 1 Level 4 Armor Module is likely to mess up. The Only Combat Droids on my vendor are pretty much ones I created in the last few weeks.
The List of my combat related droids are as follows: Would they be affected so bad with this bug ?
Pure Combat Droids
Probot Advanced5 Combat+ Level 4 Armor
R3 Advanced 6 Combat +Level 4 Armor
R2 Advanced 5 Combat+ Level 4 Armor
Probot 3 Combat + Level 4 Armor
Combat Medic Droids
Probot Advanced 3 Combat + Level 4 Armor
R2 Advanced 2 Combat + Level 4 Armor
Scout Droids
Probot Advanced 2 Combat + Level 4 Armor
R2 Advanced 2 Combat + Level 4 Armor
R2 Advanced 3 Combat + Level 4 Armor
All of these I think were re-crafted in the last 3 weeks at the most so post CU made droids. What do you foresee the problems with these?
If all of those droids only have 1 Level 4 Armor module, then they will all end up being CL20 Droids. None of them will have the attack or guard commands, and will not participate in combat. They will not have any combat abilities at all, so they will turn tail in combat, the moment one of those droids takes any kind of damage. They will not attack a target at all....
All Droids have full armor as in both armor slots are used .. so I assume 2 Level 4s would push it what a single Level 6 gives you. Combat Only Droids are literally that combat modules and armor modules. Scout droids contain various scouting modules to go with their combat modules. Any droid I sold that was intended to be combat contained at least2 combat modules as I mentioned above. I am pretty sure these droids had at least 2 armor slots which I would have used up. The only optional slot I do not use is the Droid Personality Chip.
Eg. Medical Droids (crafting, medical, storage and maybe combat)
Eg. Scouting Droids (harvest, trapping and maybe combat and crafting)
Even my crafting droids utilised the full armor slots (still level 4 though) but I never sold them with the idea that they were able to be used in combat. If customers chose to do that (shrugs).
Well, to be on the safe side I've removed the remaining 29 droids from my vendor and will simply recraft them along with the replacements for the ones sold so far this week. My Bounty Hunter Droids (MSE Detonation/Arakyd and Seekers) shouldn't be affected by this armor / pre cu problem and neither should my space R5 Astromechs as they were not designed to do anything than what was advertised.
Hmm, so no combat ability at all even with combat modules in the droids ?
Unless each droid is equipped with some other type of module, such as storage, medical, etc.. the droid will be as useful as a standard BLL droid. IE the version of the BLL that doesn't have a module slot and is pointless to build, unless you are bored, or grinding FS XP.
My character all have varying droids for different purposes but I think all but a couple have combat ability (or did). Some are Pre CU some are not so would be interesting to see how they are all affected too. The question is what complaints I will get because they messed the droids up.
I honestly do not see a fix for this issue happening any time soon, especially since Red-Dwarf and I seem to be the only two people on the entire TC-Corby server that bothered to run a full line of tests. (Yes this is an exageration and I appoligize to those that tested the droid changes. It just how I feel currently, with the route that the DEV team has decided to take with TC-Prime as a testing bed. If you spent more then an hour in Mos Eisely, you would understand why I am frustrated. :robotsad
Yeah, I was testing when I could and only had the ability to test the few I posted on the site here. Was in the process of running a second factory run of common components so I could continue when I saw this update going through... so guess testing was no longer an issue
) Now of course if theyd cloned Radiant I would have had plenty of resources and components to test the full line
)
Unless the DEVs have a magic bullet that they are going to pull out of their hats in the next 8 hours, all exisiting deeded combat droids will become instantly useless.
All droids in every datapad, that has at least 1 combat module or 1 armor module, will become CL30 combat droids, with maxed out health and damage. (This one isn't 100% certain, since I only had 3 droids in my datapad, thatfit this hypothosis,on TC-Prime to compare this to, before the server was mothballed to make way for TC-Coprby)
There is also the posibility that all droids made pre-Publish 7 will be converted to CL1 droids. This could also include all of the old pre-nerf Probots. This in based on 1 droid that I had in my datapad that was CL18, prior to Publish 18, that was built 2 days before the first Droid Invasion publish. It was originally built with 1 Level 6 Armor module, and every other single module that was available at the tiem. It is now a CL1 droid.
Well, I would suspect that this goes in line with the character combat ability. All my crafting characters (no fighting abilities) are CL1. An MSE or R5 at least, with no combat module are Level 1. So I would guess that any droid that does not contain a combat module will become level 1. In my case this should not be a problem apart from my harvest/trapper droid that I guess I should have had the forthought to include a combat module in case the trapping makes it get attacked by the critter. Even more fortunate is that since I have kept records (Pre CU) I have not sold one of these so I guess since I am recrafting my droid set I will review which droids sold well and concentrate on them for now.
Obo_alCan wrote:
Actually I just found an Adv R3 combat what was sitting in one of my buildings for about half a year or so.
Okay, so this was a deed, it had both its Health and Combat Rating listed (600).
When I generated the droid, it has no Attack or Guard commands nor does it have any damage stats.
It's Armor was listed as 6000 (probably had a Lvl6 in there), and was CL30 3742 Health.
Same thing happened to me with some old Post-Publish-7-pre-Publish-8 probot deeds I had stored - they were factory made but were pulled from the crate long ago. They show up with 3742 health and either 549 or 502 combat rating on the deed (I had two different runs of them with different quality combat modules).
For a moment there I thought they might be sellable again, but after reading this thread, they're likely not; without attack abilities.
I was crafting deeds today and they list no battle rating whatsoever on them and these are newly made
after reading all this i went from indignant to shocked to outright angry now that i have had my biggest selling items just yanked out from under me
guess i need to contact my merchant and have her pull the droids until they fix it
Dasim Ar'Tah Droid Designer
Ar'Tah Droids{AD} Peko Lake Naboo Naritus server (3421 3327)
kordeth4 wrote:
I was crafting deeds today and they list no battle rating whatsoever on them and these are newly made
New droids do not list a Combat Rating. It is one of the known issues.
If a droid is showing a Combat Rating, then it will more then likely not be combat capable. This is the issue that is currently making all pre-Publish Droid Deeds useless.
Drashk, thanks for the hard work and commitment tomaking us aware of whatthis latest patch has done to our profession.
You know, with the Devs knowing the major problems this publish was gonna cause for us DEs, why in the world did they go forward with it? This is insane. Just when my business has really picked up, this is most likely gonna bury it
Message Edited by RenObiOne on 06-16-2005 03:04 AM
Message Edited by RenObiOne on 06-16-2005 03:08 AM
Drashk wrote:
Xrystal wrote:
Indene wrote:
As a customer I would like to add my voice (bugged in game and on forum) to the call to fix this. I bought a combat droid this morning after the servers came up. It showed a combat rating in the 300s but when I readied it for action and went to program it low and behold no attack or guard command. It was on a vendor and had its stats showing so i presume the DE had reloaded it to get the stats to show.
-Indene-
Another thing I found was that the LE Repair Droid no longer repairs droids as default. Droid Engineers now have to add a Droid Repair Module to the droid before it can do that.
LE Repair Droid have always required a Repair Moduleto be installed.Its been that way since Launch. It wasn't until Publish 6 before an LE repair Droid could even be used to repair another droid. The program feature wasn't available due to the Converse sytle programming.
Oh, I swore I read it in the Droid 101 section that it was a latent abilitiy .. but just re-read it and not there. My apologies... How no-one who bought my LE Repair Droid that held just 2 Auto Repairs complained I don't know .. *hangs head down in shame* .. well at least I know now.