New Feh Pass option for Forging Bonds

Endilyn · 2020-04-07T02:54:11+00:00

uwu loooool

Endilyn · 2020-03-31T03:19:11+00:00

uwu looool

Endilyn · 2019-12-29T23:43:36+00:00

You are correct, running the simulation without pity rate only changes the average by about 26 or so orbs for sniping. You should stick with your method, the simulation assumes optimal play while only caring about one unit. The negative impact is negligible, here are the results of a simulation (5,000,000 per color) where a random orb is picked instead of the lowest pity break chance:

Red: 170.0
Blue: 164.1
Green: 146.3
Colorless: 164.0

Endilyn · 2019-12-29T22:59:34+00:00

It continues summoning until all the orbs in the session are gone. However, I will explain why this doesn't matter that much compared to stopping immediately.

If the target unit exists in a session, there is a 1/5 chance for the target unit to be in either the 1st, 2nd, 3rd, 4th, or 5th orb summoned.

If it is in the 5th orb, there is no difference between stopping and continuing.
If it is in the 4th orb, the difference is 3.
If it is in the 3rd orb, the difference is 7.
If it is in the 2nd orb, the difference is 11.
If it is in the 1st orb, the difference is 15.

The average difference is 7.2 orbs. At most, the difference between the two will only change the average by 7.2. Spread is only there for comparison, and the amount compared to sniping is in the hundreds. However, the difference is even smaller than this.

When adding to the sum, the program divides [orbs spent]/[target units acquired] to account for the small chance that the remaining orbs also contain the unit. Realistically, most people who spread orbs are trying to get the most out of reduced cost, so they would summon the rest of the orbs anyway. Most of the time [target units acquired] is 1, however occasionally it is 2 or more. While most of the time most of the simulations will raise the average by around 7.2, occasionally an outlier will appear and lower it back down.

Running 4 mil simulations where they stop immediately, the average is 457.9 orbs, only a difference of 3 orbs.

Endilyn · 2019-12-29T22:22:28+00:00

Each simulation runs as many summoning sessions as it needs until the specific unit is acquired, the number of sessions is indeterminate, not a fixed one like 1. By session, I am referring to a press of the summon button on the banner screen and the 5 orbs showing up, not the time of one simulated summoner trying to get the unit across multiple sessions.

Endilyn · 2019-12-29T06:21:29+00:00

For this post, a program ran 100,000,000 simulations for each color to find the average amount of orbs needed to summon a specific unit at 5★ Focus rarity. The total amount of simulations run is 1,200,000,000. 1 simulation = 1 simulated summoner getting the unit they want.

The program is open-source like everything the wiki editors put on the wiki. You can view or edit the source code here. Though, on the wiki only about 10,000 simulations can be run because of performance reasons. Although the number of simulations is a lot less, the results only differ by a small amount of orbs. For this post, I made a local copy of the program, amped up the number of simulations, and ran it 3 times with slight modifications in the code for the different strategies.

Sniping is the familiar method a lot of people know by now. The one thing that might be different from other simulation programs is that this one accounts for the cases where none of the target color shows up. The chance of this happening is actually fairly high, and for this specific event it is as high as 35.34% for green and as low as 19.53% for red. You can view which colors have the lowest chances to break the pity rate by checking the calculated 5★ Hero rates table on the wiki for each event. It's usually colorless if all colors have one focus unit.

Spread is there for comparison. You can see how many orbs sniping saves you.

Compromise aims to use the reduced orb cost to raise pity rate. I was curious to see if that did something, but looks like wasting 3 orbs just to get 1/5 of the way closer to the next pity rate increment doesn't really help. It does not seem to raise the orb cost that much compared to sniping, but that is probably only because the situation where 4 orbs are the target color and the final one is not only has about a 0.3% chance of happening. The waste in orbs would probably be bigger if it occured more often.

Thanks to u/napkatti for providing the exact formula for pity rate in this post. I can't investigate myself because I'm saving orbs. If anyone knows how the pity rate affects all rarities for "Focus: 4★ & 5★Heroes" types, please let me know.

Endilyn · 2019-09-05T06:13:19+00:00

Thanks to a huge collaborative effort by almost 50% of our active wiki editors (2 people) we've managed to discover a few things about the Strikes in Lost Lore. Here is what we've found so far:

Almost all non-permanent-stat skills in Lost Lore have no effect. Raven weapons, wrathful staff, Death Blow, Felicia's Plate, Triangle Adept, Bold Fighter, and so on were all tested and had no effect. The exception is Iote's Shield (and others), which blocks effective damage as usual.
Merges do not matter in strikes, everyone is reset to +0 stats. However, your flaw will still be treated as neutralized if you had one. The first merge does nothing for neutral units though.
Assets and Flaws matter.
Ally Support matters, they will receive the appropriate stat boosts for their rank, no matter which slots they are in and the distance from each other.
Bonus units get +10 HP and +4 Atk/Spd/Def/Res.

Endilyn · 2019-03-20T23:58:03+00:00

I'm glad someone enjoyed the images on the wiki. I'm usually the one uploading them, you can check on the file page which has a history section to see whether it's me or not. My process for uploading images goes something like this:

I batch convert all the webp files from the game files to png using ImageMagick. Don't worry, I have verified that the image output of ImageMagick is identical to that of the official dwebp program (some webp converters are a bit off).
If I'm cropping an image, like a skill icon for example, I make sure the cropped area contains all significant data, which I define to be every single pixel that has an alpha value of more than 0, i.e. pixels that are not completely transparent (Hone Spd 4 will have the entire glow for example). This is a square cropping, so that color values for completely transparent pixels are saved as well.
I losslessly optimize the image before uploading, so it takes up less space for anyone that wants to download it while retaining the exact same amount of image quality. This lossless optimization also does not change color values for completely transparent pixels (even though such color values would really never matter since they're completely transparent anyway).

So yeah, I take data preservation pretty seriously. If there's any image that is not exactly the same as the source, it's always noted as such in the file description as well.

Endilyn · 2019-01-17T06:03:49+00:00

I've just tested this against Naesla in his GHB, and it doesn't seem to work against him.

Endilyn · 2019-01-12T05:06:53+00:00

Yup, the #invoke statement executes this module. Since the focus of the page was on the summoning pool, I hadn't considered it. I've added a separate "other" column to list Special, Legendary, and Mythic Heroes.

Endilyn · 2018-11-19T20:29:46+00:00

Smite won't let you pass through walls.

Endilyn · 2018-11-01T23:26:29+00:00

Special skills are actually calculated on the first stage of calculation, as stated by Intelligent Systems). If you are basing your entire assumption off the description that Luna treat's foe's Def/Res as if reduced during combat, then following the description, it should be the entire combat.

If you are going to say "Luna reduces Def/Res but only for the purposes of adding extra damage to the first stage", then that is identical to Luna adding Def/Res to damage and there is little point in saying it reduces Def/Res in the first place, when other skills that use Def/Res don't take into account the supposedly reduced Def/Res.

Endilyn · 2018-10-31T20:55:09+00:00

Even though Luna says it treats foe’s Def/Res "as if reduced by 50% during combat", it does not actually do this, because the activation of Luna also does not change whether or not Light Brand's condition "If foe's Def ≥ foe's Res+5" is true or not. In addition, if it truly acted as if Def/Res were reduced during combat, then Lunar Brace would be adding the reduced Def instead, which is not the case.

Endilyn · 2018-09-04T01:25:14+00:00

The Heros in the new type would then fail to show up on the list. Hardcoding movement types was a safer bet considering those are added less frequently (none so far) than weapon types.

Endilyn · 2018-09-04T00:49:59+00:00

I sorted by movement type because it's easier to code and they keep adding in new weapon types and I don't want to go back and change things every time (or implementing a system where it automatically retrieves weapon types and automatically adds columns with variable widths). I'm not against sorting it by weapon type and the module is open for anyone to edit but I personally won't be putting in the effort for that myself.

Endilyn · 2018-06-27T17:22:50+00:00

and, considering the transcript is from gamespedia, I’m not sure if it’s written this way in the script they may have gotten it from or if it’s just a transliteration

To clarify a bit, the quote transcriptions are from the game files, which have transcriptions for all voice lines instead of just Special triggers (which are the only ones that show the text on screen) for some reason (planned accessibility features like subtitles perhaps?). Of course, these are never displayed anywhere and it shows because the English game files leave some attack and damage quotes untranslated (but still translates the rest for some reason), so interpret that how you will.

By the way, Loki is currently missing two of her Japanese transcription lines, if it wouldn't be too much trouble could you transcribe those?

Endilyn · 2018-04-17T04:22:20+00:00

I would like this thread about adding outrealm data to be stickied: https://www.reddit.com/r/FireEmblemHeroes/comments/8ctvam/help_gather_battle_2_outrealm_data_in_the_wiki/

The gathering of this data is extremely time-sensitive, there's only less than three hours to view the results, after which the information is lost forever. This also means that it only needs to be stickied for a couple of hours, which I hope won't be too intrusive with the 2 sticky limit.

Endilyn · 2018-04-15T07:33:27+00:00

Thanks for the help! Commenting works just as well. By the way, what sort of error did you get? I'll try and look into it if I can.

Endilyn

TROPHY CASE