Talk:No Bed of Roses

Regina + Physallis + (any AMoE chainer)
Alrighty! One of the problems I've had with Regina finishing these RAID's is that I often need to compromise her 3000+ ATK to get an element on her. Physallis provides a solution in the form of ice imbue + 100% ice imperil + a T-cast, and all at level 80! And this boss is already -50% to ice, so it is a perfect time to try it out!

So here is the go: Regina uses Pentacast (don't forget the Anti-Demon Module, and also put Diabolos on her). By herself unassisted, mine is doing 200 million-ish damage (lots of variation with the 2H gun).

Now, Physallis comes in. I don't have 7*, but you only need her at L80 to T-cast an ice imbue plus a 100% ice imperil. Regina's damage goes up close to 500 million now, but still not maxxing out the full 4200 Bonus. Looks like you need a full billion, maxxed out as 999999999, to get that.

Final step, is to introduce a chain. Physallis doesn't even have an option to W-cast, and her imperil move is an AMoE chain, so she will be T-casting: Frozen Bullet x2, followed by ice imbue to Regina (don't worry, the ice imbue will apply before Regina's final attack move goes in, which is all that matters). For her chaining buddy, any AMoE chainer with an ice weapon will do.

Start Regina's pentacast first, followed about 1.5 seconds later by the AMoE chain. Final output is around 2.2 billion damage. Thanks for coming, folks!

Shakers

Followup: is it a 32 bit limit thing?
Yep, it's me again, Shakers. What I didn't mention before is that I did not at first include any DEF breaks, and the thing is DEF breakable. Now, the obvious 2nd AMoE chainer of choice is actually Machina, with awakened Siphon Sword, which is AMoE and on-call 75% DEF/SPR breaks. I checked and the boss was in fact DEF broken when I used Machina, yet the damage did not increase beyond about 2.1-2.2 billion.

Aha! It finally dawned upon me. Is it not the age old FAT32 2GB limit problem? I am running 32 bit version on Amazon Memu. I wonder if this is fixed in 64 bit version? It should be.

Shakers

Note that a 4 byte integer uses one bit for sign, leaving the maximum possible value as 2^31, which is 2,147,483,648

Ok, I might be getting away from topic here, but you don't actually have to be a 64 bit application to use LongInt, which is an 8 byte integer. i.e. the max value is 2^63, which is... quite a large number. It has like about 18 0's at the end of it. However, that being said, even a 64 bit application does not guarantee that you won't have 4-byte integers. That is dependent upon the source code, or the compiler. The only difference between a 32-bit and a 64-bit OS, is that a 64-bit can process 64 bit things natively, rather than going through a software conversion process. Anything you can do in hardware, you can do in software, and vice versa. Sorry! That is all! let's just hope they sort it out before the year 2038, which is when UNIX systems will experience their Y2K if not using LongInt on their datestamps!