Crazycolorz5

Upon discussion, we believe it to be for Hextator's format (not Cam's improved format). So it's useful for applying most of Hextator's patches, if you can find a .dmp of one of his patches, or, presumably, Brendor's patches.

Well, it's for the .dmp files for the hacks written to be in Hex's/(cam's improved version of it?) format. So not most of the .dmps we provide, but yes to most of the dmps Cam and Venno make.

First mug's cute. I approve of cuteness.

I see no purple statuses this must mean they're all not even close to done as it's only logical to increase the hue with nearing completion ending at Magenta.......... right?

It's more along the lines of "it wasn't a functionality in the original js file I was handed" combined with "and that functionality (along with parent-generating in general) hasn't been added" ... Or maybe I just messed something up. Kappa.

I have that card and I approve. (Of course, have it on me at Smash tourneys). edit: typo fix I should not be posting at like 2am

I just quickly worked out this logic; I checked the class sets page for all Females that have more than 2 class sets and they all only support with Corrin, so it's just never the case that they would be forced to pass down their third class (or any parallel class, for that matter) Flora troubadour darkMage mercenary Reina Sky Knight Diviner Ninja Scarlet Wyvern Rider Outlaw Knight Anna Outlaw Troubadour Apothecary All of them non issues, since only support with Avatar, so Kana only has at most ONE non-Nohr Prince/ss class, so cannot not-have the first two classes of the parent. Same logic for 2nd gen parents; One of their first two classes won't match Kana's 2nd class, and neither will match the first, so... pigeonholing... So it seems like I can keep just going down the list of classes until I find one inheritable, yaaaay.... (Really the only issue is just Corrin since I do have the Avatar having both Nohr Prince and Princess which would be the only time the count is messed with... but still no need to change anything, hahah).

By the way, is the Mother's third class ever inherited? Or is it that in all the cases where that could be the case, the second class works? Edit: Todos from here: Talent dropdown Generate parent options for the children? Python script to generate a base HTML file for this to work with (so you can have a row for every character etc). Anyway, try playing around with this for a while? And if you break it, please tell me how: https://www.dropbox.com/s/8rap8ubn14j0chn/fe-fates-max-stats-6-14-16-2-55-pm.zip?dl=0 More edits: https://www.dropbox.com/s/vess9b55qq6gf7j/Screenshot%202016-06-14%2014.16.47.png?dl=0 More Edits: Oke, talents should work properly with the avatar's dropdown/Kana's classes. By default, if no Talent is select, the Avatar has no secondary class. M000re Edits: I need to confirm: the page you linked has Ninja as the parallel to Cavalier. Is the observed in-game behavior that Kana inherits Samurai, or did you make a mistake while making the example, and it should be Ninja?

https://www.dropbox.com/s/tp9vop22u3nv4bu/Screenshot%202016-06-14%2011.47.56.png?dl=0 Most of the logic for inheriting classes is done; I just need to script in what class parallels to what. As per the flowchart, it goes: 1) try to inherit a class from the father 1.1) Do this by looping through his class set until you find something you can inherit (don't already have/isn't songstress) 2) try to inherit a class from the mother 2.1) Loop through his class set etc etc I have the loop in place for parallel classes but I haven't inserted the data of what class parallels to what into the class table yet. Also, for now, Kana (m and f) inherit all generic classes (from the Avatar). I think it might be worth it, in the future, to add a dropdown to set the Avatar's talent, and calculate the avatar's class set based on that.

You'd use MoveLeft, but that's the idea, yeah. [OpenLeft][LoadPortrait][0x02][0x01]Speaking.[A][MoveLeft] I bounced.[A]

Dragon's Veins? From Fire Emblem Fates?

http://feuniverse.us/t/fe8-arbitrary-number-of-weapon-types/753 maybe you can use this for your anima split but I have to admit I don't have experience using it myself/know what bugs there may be with it.

Yes but it doesn't look as orderly, makes it more difficult for subsequent replies, and makes it so that you can't link to a singular reply to give to someone else. In the end, they're just different conventions, and I don't think that the multiple posts for separate replies convention is worse. (By this one, we get very long posts, like this, which even nests a reply to (a single part of a post of) multiple replies into one)

idk man I think this hack is great I mean how do you even hack that kind of rpg battle system into FE?

http://feuniverse.us/t/fe8-the-grand-eventing-wiki-chapter-construction-guide-wip/1594 Here's the FE8-oriented eventing guide. You should be familiar with the chapter construction guide first, though.

I think it's fine because they're replying to different people

Spd? Res? Growth rates? That's a really high Def, if this is a level 1 unit. Not outrageously so but, like, Hector levels of def.

You should put Dragon's Veins in the hack :). how rood I live in Columbus

(among other errors - you may want to get an editor on the actual game script) grumble grumble mutter mutter still contributing to topic and is a significant amount of text grumble grumble mutter mutter

Aside from plot, what are you doing in terms of gameplay?

https://www.dropbox.com/s/p311y49slw2vng4/Screenshot%202016-06-10%2012.24.15.png?dl=0 Hm, looking good, looking good. (next up, inheritance based on defined class sets, then with fixed parent, then by flowchart)

Are you saying we should section off the dropdown box into like, for example --Base Classes-- Nohr Princess --Inherited Classes-- Sky Knight Ninja --Borrowed Classes-- <everything else> ... actually with the way I'm generating the class list right now, this is very feasible. I think, given those rules, it might just make the most sense to hardcode the class that the child obtains form the fixed parent (since it is fixed, after all) I'm trying out #3 right now. It requires an extra bit of data but otherwise works really cleanly. I think it's worth at least linking the base classes to the promoted ones, since then you can more easily declare each character's class sets (as 2-3 classes instead of a whole bunch of them). It also makes inheritance simpler, as you only need to list the one base class passed down.

1) Being tinkered with; you still need to set the characters' base classes in their class sets so they display on top and for inheritance purposes. 2) Done 3) Being worked on; is difficult. Do you have more details on how inheritance works, such as if the child already has the base class of the variable parent? Is Kitsune/Wolfskin passed down to not-Selkie/Velouria? Here's the copy I'm editing; it should always be up to date since it's just in my dropbox. I have not tinkered with the childrens' cap calculation yet. https://www.dropbox.com/s/rquoxpx2gczp7f0/fe-fates-max-stats.js?dl=0 I'll work on it more during class tomorrow again Yet another edit: I think it'd be handy to keep track of the base class corresponding to promoted ones, and vice versa. Expect to see it in the next edit I made to the code. Edit yet again: Linked wrong file Edit the 4th: Actually, keeping track of the bases that go with a promoted class won't work since there are multiple classes that can promote to the same class. So there are several solutions: 1) Have multple versions of each promoted class that keeps track of what it was promoted from 2) Give prepromotes their base class anyway in the calculator 3) Associate with each character the base class that they would pass down (possibly best solution) 4) ??? (profit?)(some other option)

I want to be a sub, in case someone dips.