Invincitinks on shard bombs
sam, 06/22/2013 - 05:34
These have been around since the new shard bombs were introduced, and it's almost as bad as the stun bug was. Here's a video of it happening and it shows how easily reproducable it is:
http://www.youtube.com/watch?v=BL-1tH-cyp0
Here's a rundown on what I think is happening:
- The core of my first bomb is hitting. The game registers this as one hit.
- The core of my second bomb is hitting. The counter responsible for managing invincitinks has reset at this point and the hit is registered as one hit..
- The shards of my first bombs both hit. This happens very quickly after the core of the first bomb, and the game registers this as three hits. Seeing that the hit limit has been reached, the game now enables invincitinks.
- The core of my third bomb hits. This happens before invincitinks has died off.
- The shards from my second bomb hits shortly thereafter, refreshing the invincitinks mechanic.
This is a bug for three reasons:
- The core is not supposed to be included in invincitinks. I quote Nick: "With the exception of the initial explosion, only 3 shards may hit a single target from the same bomb."
- The third bomb is a completely different bomb, and should not be included under the previous bomb's invincitinks. I quote Nick again. It's even the same quote: "With the exception of the initial explosion, only 3 shards may hit a single target from the same bomb."
- It's stupid.
There are a number of ways to fix this. Obviously I need to tell you this because you've had nearly a year to do so and you haven't been able to yet:
- Rework the invincitinks mechanics so they work exactly as described. Make a seperate counter for each bomb so that one bomb can't 'cause tinks for the other. I don't know the specifics of the Clyde engine. Maybe it's impossible, maybe it's not. I suppose it wasn't the easiest possible route seeing how you didn't take this in the first place.
- Disable cores from contributing to the invincitink counter.
- Up the invincitink counter to 4. While not completely removing the problem, it should make it much more rare.
- Unless you plan to seriously nerf certain weapons, just remove invincitinks entirely. Let me just pull up the maths for why there was absolutely no reason to have this fun-ruining, buggy mechanic implemented in the first place. All numbers taken from D24:
- Combuster's charge does 547 damage + 5x166 damage = a total of 1377 damage. This is very easy to consistently perform every single charge attack. It can also set things on fire.
- Prismatech Alchemer's charge does 383 damage + 4x3x198 = 2759 damage. This is a bit tricky to perform, but all you need is, say, two lumbers standing next to eachother or one enemy next to a wall.
- Deadly Crystal Bomb would do 128 + 8x166 =1456. This would be literally impossible to perform on anything but Vanaduke, and even then you wouldn't be able to hit with the core. Making it further impossible is disappearing shards that would render the player unable to actually gather the shards and hit the same enemy that many times with it.
Incidentally, alchemers are ridiculous.
Edit:
Herped the math a bit.
lun, 10/06/2014 - 13:02
#2
And BUMP.
This is still very much an issue with the bomb.
lun, 10/06/2014 - 14:39
#3
im vohtarak
I used shards once as a noob, im not picking them up again unless something gets fixed
mar, 10/14/2014 - 16:43
#4
.
The shard bombs would actually become a viable weapon if invincitinks were removed. Right now, they're not even on par with other bombs, which is pretty sad considering how other pure-damage bombs are completely outclassed by swords, and haze bombs are only good in a support role. But then, that's a totally different gripe of mine.
ven, 10/17/2014 - 07:22
#5
You may not like the hit limit for shard bombs, but this is an intentional design limitation. It's actually in the game code:
public static enum DamageLimiter
{
NONE(0, 0),
SHARD(3, 1000),
RAY_OF_LIGHT(5, 1000);
... }
where weapons classified as shard bombs have a 3 hit limit per 1000 ms (1 second). Ray of Light (Seraphynx 1st attack) has a 5 hit limit over the same period of time.
lun, 10/27/2014 - 20:20
#6
.
Just because it's in there on purpose doesn't make it a good decision.
mar, 11/18/2014 - 10:50
#7
Is it an intentional design limitation though?
As Nick, the party responsible for the design of the shards said- "With the exception of the initial explosion, only 3 shards may hit a single target from the same bomb."
In this case, the initial explosion and shards from the last bomb are counted as part of the limit, which goes against what Nick is saying, and kills the bombs' damage output.
sam, 12/06/2014 - 19:32
#8
You are experiencing a PICNIC ERROR!
This is good.
@Gear-Storm
I don't know if you'll ever see this, but...
How on earth did you get that code? I find it a little hard to believe, and if it was real code, wouldn't the GM's have smuffed it out?
Or maybe not.
lun, 12/08/2014 - 02:36
#9
i miss the old crystal bomb style
i miss the old crystal bomb style, being a pure bomber it came in handy for the soul reason it had range, and hit more then one targit.
i think that instead of it piling up in one spot it should shoot across the map like a gun dose
This. All of this.