Crazycolorz5

Well, that was in reply to me. Edit: But yeh, this be it, so, like, I'm waiting/will be here.

I did a tech demo. https://www.youtube.com/watch?v=51bMPF0xexo also idk how to embed and idk how to spoiler but it's worth a click i swear Check out the rest of my tech demos in my sig, while you're at it. Edit to say I'll make a thread for it soon with a release. But too lazy right now.

https://www.dropbox.com/s/9rxeq15o4rhnzew/Dismount%201.png?dl=0 https://www.dropbox.com/s/j54y0zzsn0f3881/Dismount%202.png?dl=0 Trying to get Dismount/Mount done tonight. Then will restructure the save files as an extension of my suspend expansion hack and go for Str/Mag. (Also, the editor yells at me when I try to embed those images, so, *shrug*)

Ok gonna close off requests for a bit (maybe a weekish) so I can work on these. Shouldn't be too hard.

The only thing difficult sounding with fatigue that I wouldn't want to do is making some kind of indicator or bar for it on the unit menu. But if I can get @circleseverywhere on board with it, I'll do it. Mostly it's a concern since you'd have to change the menu around for that bar, but then if you wanted a magic split, it'd require a completely different menu.

Can you give me specific specifications on how they work? Think about boundary cases too. Edit: Do the stat bonuses show up on the stat screen? Like weapon equip bonuses. OK OK How does this work, specifically?

Don't tell me what to do; I'll regard it if I want.

I suck at graphics. I'm better at calculation changing, specializing in battle calculations. I can also do AI shenanigans but that's more through EA wizardry (AI Assembly.txt) than actual reprogramming.

I have two (groups of) questions. Is the only way to develop and test hacks for FE14 hacking to have a hacked 3DS and manually test it out? No emulation? Also, do we know what dialect of assembly the 3ds runs on (actually I should be able to wikipedia that one(Edit: It indeed still runs off of ARM)) Second, is the 3DS architecture Big Endian? I'm seeing a lot of pointers beginning in 08? If not, where is the beginning address of the ROM? Edit: Also, what is debugging 3ds games like? Can I still set breakpoints/ break conditions?

No Real Subsection Seems To Fit This I want to encourage hacking in FE8, as well as increase the amount of available hacks and documentation for it in general. So I'd like to put this out as a request thread for assembly hacks/engine modifications/etc. for me to do. To be clear, request only if you are interested in seeing the hack in FE8. I reserve the right to refuse any request (some things can be deceptively hardimpossible). That said, feel free to request things that may sound difficult, as some things can also be easier than they seem. Also I can do some cool stuff. Anyone want to start?

Do you have download links for any of these? None of them seem to be downloadable. Also, are these open source? (the reason I'm asking is because I want to include it in the directory of open-source assembly hacks I'm making).

The my knowledge, you'd have to just use different character IDs for each of the ones you wanted to change. I'm not 100% certain and am too lazy to check right now, but I believe that it's a different code that reverted changes. Is she the active unit? DISA doesn't work on the active unit. In fact, most event commands don't. It's rather unfortunate.

Because sometimes FEditor just curbstomps your rom I made an executable parser based on anti-huffman encoding. Needless to say, this method of text insertion requires the anti-huffman patch. This patch is auto-applied if you have opened and saved your ROM in FEditor. (If you'd rather not have FEditor touch your ROM at all, an EA installer for the Anti-Huffman Patch, based on the FEditor version, is here: http://feuniverse.us/t/fe7-fe8-anti-huffman-patch-ea-style/1703) Here's the link: FEU Another Text Parser Thread The usage is by basically making a file with the formatted text, then opening it with the parser. You can also parse a whole folder of text at once. It'll generate a .dmp file and you can insert that in the ROM and point to it, anti-huffman style (anyone got anti-huffman tutorials still lying around?). There's also an executable for parsing all text files in a directory/subdirectories. The newest version also allows declaration of your own directives, such as: (in definitions file:) [LoadEirikaPortrait] = [LoadPortrait][0x02][0x01] (in text file:) [OpenLeft][LoadEirikaPortait]Eirika says hi![A][X] Another example input: [OpenRight][LoadPortrait][0x01][0x01] [OpenLeft][LoadPortrait][0x02][0x02] [OpenRight] Eliwood, let me tell you[NL] about a lost art.[A] [OpenLeft] What is it, o wise[NL] question-mark man?[A] [OpenRight] Once upon a time, before the[NL] time of FEditor, we did text[A][NL] a different way. The anti-[NL] huffman way. This involved[A][NL] hex editing. In fact, FEditor[NL] only automates this method.[A][NL] [OpenLeft] I see. Why are you telling me this?[A] [OpenRight] Since it's what FEditor is based on,[NL] people should know how it works.[A][NL] That way new ways of editing text[NL] based on it can be created.[A][NL] For example, imagine if we could[NL] insert text through EA...[A][NL] [OpenLeft] That sounds like a[NL] useful option to have.[A] [OpenRight] By the way, there are bandits[NL] behind you, Eliwood.[A] [OpenLeft][MoveLeft] Ahh![A] [ClearFace] [OpenRight] Bye![A] [ClearFace][X] And this is the hex output: This can then be pasted somewhere in the ROM, and a text table entry can be repointed to it (add 0x80000000 to the pointer to tell the engine that it's anti-huffman'd). This process can be automated by EA, keep an eye out for a tutorial on that soon!

Because it's against the rules doesn't mean it wouldn't happen; Tangerine was saying in the first post that I should have PM'd this topic instead. Do you happen to have the rules Serebii and Zelda Universe have on it? It might be interesting to see how they implement it/to what success/how it's viewed. I'd also argue that a built in system (such as autolocking) is different than a rule against it. To be honest, I doubt the efficacy of tagging. Since they're user-generated, I don't think they'll match up very often (with searches or other threads with the same tag). I do think some kind of public forum for discussing new rules would be useful. If the topic is going to be dead anyway, is it necessary to have a rule specifically against posting on it? And if no one is going to reply, would it fall off of the front page again quickly? And if it doesn't, well, that means that people are replying and it has again become a worthwhile topic. On the second section I'm addressing, I disagree; several people simply voicing their opinion is valuable. I'd like to point specifically to @henrymidfields's post in particular.

@Tangerine (as I don't know how to make a direct reply post on this forum software) Sorry; the way that clause was phrased in the Code of Conduct sounded like it was more directed towards appeals and things like that. Furthermore, I wanted a public post to be able to discuss specifically the merits of having such a rule, and to get a more public opinion. I do see your point about how someone determined enough would make a thread anyway, but again, this unnecessarily populates the forum with threads (which also makes the forum harder to search alongside just having additional clutter), and it is still a barrier to post. The forum should be as accessible as possible, and I think in the mindset of many members, starting a new threads take a lot more determination and possibly understanding of the community than a simple reply. As another point, starting a new thread wouldn't retain previous discussion, so rather than refer to what has already been said, the points would be restated. Though I do suppose having very, very old threads can complicate this. So how about if the rule is amended to have one year since the most recent post as the freshness cutoff, with a general exception that the OP may always post in their thread? @Tricky I think it's ambiguous at best whether they fall under that exemption. The things in question aren't specifically fan works, and it's not so much of an update being posted as an alternative version. To complicate matters, it's not even the creator of the thread/original work that is adding to it. I suppose it could be argued to fall under the second exemption, but since it's not clear, it'd, by proper following of the code, require PMing a moderator, which is another step hindering the posting of useful content, making the forum less accessible. If the post is non-productive, it should be able to be caught under the rules about being off-topic, so necroposting never needs to enter as a the reason to punish to those kinds of posts.

The SF Code of Conduct states that: I'd like to discuss the merits of such a rule. What are the specific benefits of having an explicit rule for this? At the very least, look at this post: http://serenesforest.net/forums/index.php?showtopic=46060&p=3301367 ; I believe this to be an acceptable post, as it answers (and provides more information) to an unresolved problem. In general, I believe that necroposting rules bring very specific cons: - Inability to add on new documentation to an old problem/request. - Creation of many threads asking the same question/making only small incremental steps to one end. - Discouraging continued discussion on a topic (one must agree that creating a new a thread is a much larger barrier to posting than simply replying). Next, allow me to give a few examples of "necroposts" that undeniably helped the community in question and were on topic. FE8 Native Instrument Map Danger Zones In sum, I'd like to propose the following point: A post should be acceptable as long as it is on topic and contributes to the topic of the thread. (and, of course, following all other regulations). At the very least, there should be an exception to documentation-based threads, commonly found in Fan Projects, that would be more general than the stated "You have a bug report or constructive advice for a fangame." However, I firmly believe that any post that is productive and contributes to a topic should never be discouraged.

I have 3 points. 1) Ultimately it comes down to what our culture values and cares about. 2) I feel like a part of it comes down the prevalence and seriousness of a disease. Namely, Heart Disease, Cancer, Alzheimer's, Accidents, Suicides, COPD(usually as the result of smoking or pollution), and disease of the nephrite are the leading causes of death (not in order). I don't think, in general, it's acceptable to make much light of any of these conditions. 3) It could be your own perception; selection bias in particular. There may be actually only very few instances of jokes about certain conditions, but you /notice/ those few instances because they anger you. So it may not be as widespread of a mindset as you think it to be.

Hey guys I sucked it up and accepted my warn after a year and a half finally (with a bit of encouragement from Arch). So I can post now. Wassup. Some of you know me. I'm not awful at this game. I swear. I think. Edit to actually put a topic of discussion: What region are all of you from? I'm in Central Ohio (Columbus, to be precise).

... >.> >.> ... <.< <.< ... Yeah, uh, uhm, sounds prohibitively difficult. Yeah.

Klokinator actually made a thread on FEU inspired by this thread. Here it is for those of you that are interested: http://feuniverse.us/t/fangames-what-are-you-working-on/663 Some more recent highlights include: Pair Up Gifs! Dual Attack Mockup Gif! Female Great Lord Gif! Checklists upon checklists! A recreation of Cam's 2015 FEE3 entry in FE8!

There shouldn't be a rule against necroposting in the first place. It's necessary to add new research and documentation to old questions. As long as it's on topic to what was being discussed, I see no problem with it.

I'd say $15-$20 sounds more fair given the amount of content. So is this in project concepts because we actually want to make this hack, or...? Because, like, I think this is more realizable than most of you think.

Typesetting seems iffy -- you have line breaks in somewhat odd places. I'm specifically looking at King Marc is just a puppet King[NL] who just sits on a[A] The first line is significantly longer than the second; you could fit another word or two on the second line, as the [A] there makes little sense; it leaves the reader in suspense rather than being a temporary stopping point. A lot of other lines also seem unbalanced. Another example is I hear sounds to the[NL] south west, and south east area.[A] (For proofreading reference, that should be "south-west and south-east area.") The second line is significantly longer than the first. I find it more natural for the upper line in the block to be longer than the second. Aside from that issue, I came here to ask, is there any wizardry/assembly-hacking/engine-mods/special-effects you think this hack will need? I might be interested in doing something small.

Something is very off here... ... I do agree with most of the other people -- despite its simplicity as a recolor, I like the Virginia portrait. I hope the other future portraits will have the same charm.

Oh, is that Yeti's map maker? More on topic, I noticed you said you wanted to fix the RNG. What specifically about it are you modifying?