The Odd One Out--Spark and the Projectile Change
" Interesting. And for the proffered Vaal Spark one-in-fourteen example, how is that skill affected if I haven't got any piercing set up? It seems that you're intending this skill to simply have that one-in-fourteen chance. Which is your call, but then I ask again: flavorfully and balance-wise, should Spark be an exception? It feels wrong to have that one-in-fourteen effect on this spell. |
|
|
Based on my understanding, after the spark projectiles bounce, all of them have the potential to hit. Let's say Spark 2 is the one first one to hit the original target after the bounce (presuming all of them have bounced and there's enough duration for them to hit the original target again). it will be the only one to deal damage, while Spark 1 and Spark 3 will already have the memory of Spark 2 hitting it.
is this correct? Better stay in the land of the damned, Exile. Here, even the very words are corrupted by Nightmare. Last edited by enveratise#2153 on Apr 20, 2015, 5:23:57 AM
|
|
" That seems to be what he's saying. Odd that it's set up so that piercing and chaining are the only ways to do it. |
|
|
so i guess this memory for each individual spark is the culprit behind massive frame spike with vaal spark / gmp setup , hope the global thing solves it , partially .
Also really happy with no shotgunning change cant imagine the salt of all those ts archers :) chaotic neutral
|
|
" TS won't be affected. only skills that have a primary shotgun effect (such as FP) will be, while those that have a secondary shotgun effect (TS, KB, LA, Fireball) won't. Like I said in the other thread, it'll be the incinerate user's that'll be worried. and the FT users too. We really need to consolidate all this projectile change things. But while we don't know how they'll change the active skills... Better stay in the land of the damned, Exile. Here, even the very words are corrupted by Nightmare.
|
|
|
Let's bring this down to the basic level. Let's say you are in a room with a single monster. If I understand this correcly, when you cast a single cast of spark (which has 3 projectiles) and one of them hits the monster and pierces it, now you have three projectiles randomly flying around, NONE of which can hit the monster? Unless they bounce off of (or hit) something else first? Am I understanding this correctly?
How does fork work with this new mechanic? Do the forked projectiles share a memory with the original? Or eachother? Asking for the few sporkers still out there :D STD ign: Helevaperkale HelevaSCION
|
|
" nvm Last edited by TheDeathX#0331 on Apr 20, 2015, 4:59:05 PM
|
|
" It's not really a good habit to speculate on how code you've never seen works but what you say seems highly unlikely. Algorithmically speaking, checking the last item hit by a projectile takes constant time. It will grow linearly with the number of projectiles currently experiencing a collision. The collision checking itself is far more expensive for the CPU since it's linear in projectile count and at best logarithmic in the objects projectiles can hit. As for memory, the most likely scenario is storing a pointer or integer based identifier so storing a few hundred of those is a drop in the bucket compared to things like even low resolution texture storage. Oh BTW, TS is unaffected by this change according to GGG posts in the other shotgunning threads so it may retain the current behavior. |
|
|
Wait. Does 'bounce' refer to when it hits an enemy and keeps going or not?
|
|
" shared memory and all sparks will lose it when one bounces. bounce = spark projectile hits an object that forces the projectile to continue in a new direction like hiting a wall or and unpierceable object or the end of a the map.... Last edited by TheDeathX#0331 on Apr 20, 2015, 4:54:23 PM
|
|
