Quote:
Simpley put, NK needs to fix a bug, or buff super sentrys.
I managed to de-crypt the BTD5 Mobile apk and found the exact stats for all towers. I found for engineer they have 2 seperate scripts, which the game chooses from depending whether or not the player has a level 4 Engineer speciality building.
Buying the sentrygun upgrade makes Monkey Engineer...
-> Build Regular Sentryguns every 10s. Each sentrygun fires every 0.66s and lasts 25s.
-> Build Super Sentryguns every 20s. Each super sentrygun fires every 0.33s and lasts 37.5s.
-> If the Monkey Engineer has any attack speed buffs (Monkey Lab or Jungle Drums) the build time is reduced by that %. Ex: Jungle Drums reduces the Sentrygun build time by 15%, which would make it 8.5s.
Basically, the Engineer builds Super Sentryguns HALF as often, but they fire TWICE as much, cancelling eachother out. However because the Super Sentryguns last 50% longer, there will be 50% more active Super Sentryguns on average thus +50% DPS.
1.5x DPS from sentry guns is a pretty decent level 4 specialty upgrade I'd say, however...
The Fast Engineering upgrade in the script says it reduces Sentrygun build time by 4s. This means the Monkey Engineer will deploy Regular Sentryguns every 6s. The mistake the developers have made is they didnt make a script for Fast Engineering's effects on Super Sentryguns, thus having no effect.
Since Fast Engineering allows 60% more Regular Sentryguns to be built than Super Sentries, the Level 4 Workshop makes the Monkey Engineer's Sentryguns 10% less effective. So if you're fond of using the Fast Engineering update, don't use a Level 4 Workshop!
As for myself, I decided to make a simple mod for BTD5 where Super Sentryguns are built at the same rate as regular sentryguns, even with Fast Engineering, but I reduced their benefits over regular sentry guns. They now...
-Last the same duration as regular sentryguns (25s instead of 37.5s)
-Fire 25% faster instead of 50% faster (every 0.50s instead of 0.33s)
-Have 25% increased range
-Can pop +1 Bloons (3 instead of 2)
I'd say the problem is fixed... for me atleast.