Nest bug fix, refund zeta please [MERGE]
I used my free zeta for her. I rather get it back now.
Forum Discussion
FoX and DN stacking is based on current HP like you described and always has been like that afaik
EDIT: Not a CG shill, but I do work in Software Security
Here's a small lesson in Software Security that is applied to things like bugs and vulnerabilities, there is a concept of probability of likelihood of a vulnerability being exploited AND the impact of the exploit,
Basically, no system is bug free and if anyone says there is no bugs in my program they don't know a thing about security. The example to use here would be a wall called Enfys Nest. This wall had a hole 3 feet from the ground level. There was water filled up to 2 feet high from the ground at the time of release. This is acceptable. As long as nobody can reach the hole and exploit it, its ok to release a product aka the wall (Enfys Nest) without patching the hole. There might be a few edge cases where someone might be able to take advantage of it (using Nest against Jango Fett) but the impact of being exploited is really low (not many players running Jango).
Spending time / cost on fixing a hole that will never be reached is pointless. What Jedi Knight Revan did was add 1 more feet of water, causing water to leak through the hole and cause a big upset.
The most important question before deciding to work on a bug is the Impact. How much impact does this vulnerability have in the game. This exploit ranked High, since it affected a lot of important PvP modes, which means CG had to rush over and put a band-aid on it real quick and ignore other more important bugs to fix
EDIT: Not a CG shill, but I do work in Software Security
Here's a small lesson in Software Security that is applied to things like bugs and vulnerabilities, there is a concept of probability of likelihood of a vulnerability being exploited AND the impact of the exploit,
Basically, no system is bug free and if anyone says there is no bugs in my program they don't know a thing about security. The example to use here would be a wall called Enfys Nest. This wall had a hole 3 feet from the ground level. There was water filled up to 2 feet high from the ground at the time of release. This is acceptable. As long as nobody can reach the hole and exploit it, its ok to release a product aka the wall (Enfys Nest) without patching the hole. There might be a few edge cases where someone might be able to take advantage of it (using Nest against Jango Fett) but the impact of being exploited is really low (not many players running Jango).
Spending time / cost on fixing a hole that will never be reached is pointless. What Jedi Knight Revan did was add 1 more feet of water, causing water to leak through the hole and cause a big upset.
The most important question before deciding to work on a bug is the Impact. How much impact does this vulnerability have in the game. This exploit ranked High, since it affected a lot of important PvP modes, which means CG had to rush over and put a band-aid on it real quick and ignore other more important bugs to fix
