Droid Engineer Archive

/sigh

This might push me over the edge and actually use my 1 time respect and start to kill things in combat and leave the DE stuff to the ghosts.

---

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....

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.

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

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.

---

Drashk wrote:

---

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.

---

I've got a bunch of droid deeds (including a full combat probot) laying around my shop. I'll have to check it out this evening.

FYI, these droid deeds were pulled from the crate after Publish 18 went in.

Did I mention that the droids I pulled from the crate were probots? I don't have any other combat droid deeds.

FYI, all the pre-publish 7 probots were converted, but they were treated like they did not have a combat module installed. Health is 108 or something and I think the CL was 1. Looks like all the pre-publish 7 combat droids are finally getting wiped out.

---

Straker_Atrella wrote:
Yet others like Obo are saying...

---

If in doubt, ignore me.

---

Straker_Atrella wrote:

Drashk, ok this is what is confusing me a little I guess. ManI need to get home.

You are saying the extra Armor is being given from the total combat rating, 276+ giving 3k more armor. Yet others like Obo are saying it is 1k per module if it is over 55 rated. This isn't the first time I have seen this.

Which is it? If I am confused, I am sure others may be as well.

---

The chart listed at the begining of this thread is completely up to date. Keep in mind that the chart is for the complete Combat Rating that the Droid would have, when crafting the final deed. The one that is no longer showing up on crafted deeds.

Drashk, your charts aren't entirely accurate. I made two Advanced R4s this morning on TC-Corbantis. The one I put two highly experimented level 1 armour modules in and no other modules. According to your charts this should have come out as DL10, 2k Armour Effectiveness, but was actually DL15, 3k Armour Effectiveness. The second had two unexperimented level 1 armour modules and no other modules and came out as DL5, 1k Armour Effectiveness. Based on this I suspect the DL/Armour is based on the rating of the armour modules, not the level, a bit like data & item storage. I didn't have time to do thorough testing.

EnigmaBSc

---

EnigmaBSc wrote:
Drashk, your charts aren't entirely accurate. I made two Advanced R4s this morning on TC-Corbantis. The one I put two highly experimented level 1 armour modules in and no other modules. According to your charts this should have come out as DL10, 2k Armour Effectiveness, but was actually DL15, 3k Armour Effectiveness. The second had two unexperimented level 1 armour modules and no other modules and came out as DL5, 1k Armour Effectiveness. Based on this I suspect the DL/Armour is based on the rating of the armour modules, not the level, a bit like data & item storage. I didn't have time to do thorough testing.

---

Stacking rules do apply.Sorry,I automatically think of the rating of the module, or stacked rating, as the Level of the module. So, we are both correct. I guess that I have been a DE too long now, that I think of the stats of the item in terms of number, and use the Level rating as the 'label'

Module Stack MedicalItem Data Armor
Level Rating Rating Rating StorageStorage Resists
| 1 | 1 - 2 | --- | 55 | 1 | 20 | 4% |
| 2 | 3 - 4 | 3 | 65 | 2 | 40 | 8% |
| 3 | 5 - 6 | 5 | 75 | 4 | 70 | 12% |
| 4 | 7 - 8 | 7 | 85 | 6 | 110 | 15% |
| 5 | 9 - 10 | 9 | 100 | 8 | 125 | 18% |
| 6 | 11 + | 11 | 110 | 10 | 150 | 20% |

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-

All my Pre-18 droids are broke, no combat skills. I have already given refunds.

---

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-

---

---

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-

---

Sad to see this. But I'm surprised that happened. I would have thought any combat rated droid would also have at least a level 4 armor but oh well.

Any droid deed that lists a Combat Rating will not have combat functions. That is the big bug of this publish and is the reason for this warning thread.

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.

I guess in your case thecrafter didn't realise that this would happen and perhaps expected a base combat droid at the least after the update. Unless of course they havent been playing for over a week and didn't even know of the update at all.

It wasn't discovered that droid deeds were bugged until the day before the Publish went to Live. Red-Dwarf and I were the first to report the issue and alert the community about the issue. Majority of the DE community, on the forums or off, had little to no information about the issue, with the exception of the people who read about it here, or in thebugthread.

---