Poll: What do you think of the suggestion?
Good idea
Bad idea
[Show Results]
Note: This is a public poll, other users will be able to see what you voted for.
Post Reply 
 
Thread Rating:
  • 5 Votes - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Explosions: replace damage pool with dissipation for filling empty space
2017-08-14, 11:34 AM
Post: #101
RE: Explosions: replace damage pool with dissipation for filling empty space
A new version of SpinBlocksMadness is available.
It fixes a bug which prevented the SubConstructs to be damaged by the explosions...

I now divide the current health of the block by its size before checking for the threshold.
Also, I can now know if the explosion is a flak explosion or an HE explosion.
The AC power to apply is now only applied to the flak explosions.

Of course, it is possible to differentiate the other variables, but it will fast become a mess in the UI, and I'm a bit lazy... so for now only the AC is processed differently.


Now it is possible to make it so flak damage high AC less than HE.
I use these values, and it works quite well in my initial tests:
Boost coefficient: 1.0
Power to apply to AC: 1.5
Bleed coefficient: 1.3
Bleed explosion power: 0.35
Bleed explosion radius: 1.8
No damage threshold: 5.0
Blast effect for damaged blocks: 60.0
Blast effect for not damaged blocks: 80.0
Blocks sorted (don't know if it really changes something, but Nick did it... o I left it there)
Containment: Last iteration (never played with it, maybe it changes nothing, or maybe it changes everything)
No multiple hits simulation (that's much better I think)

Also, note that if we decide to remove the 'multiple hits simulation' feature, the memory footprint for the explosions will be divided by 2, and the propagation will be a little faster (not much... but anything is good to take!).
Find all posts by this user
Quote this message in a reply
2017-08-17, 01:11 PM
Post: #102
RE: Explosions: replace damage pool with dissipation for filling empty space
After trying(and failing Smile ) to make flak useful with the current subconstruct mechanics I've decided to scrap the stock propagation algorithm.
Now that I have a slight clue on FtD modding Evil4Zerggin's proposal looks very simple to implement.
I'll give that a go and see what happens, hopefully it leads to a savegame-compatible, simpler version of SBM.
Without the constant subconstruct projections it should even be pretty fast.
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)