Aleph

way too wordy, lost a lot of the humour

I stand by my suggestion despite

well go on post the sauce or like the search text

shh integ don't make objective observations about other peoples' posts a bunch of unrelated people you aren't even talking to will storm into the thread and give you hell for it!!

hard part is getting out of bed in the first place I put my alarm on the floor so I can't reach it. Sometimes I will still sleep walk to it, turn it off and then wake up hours later without realizing what the fuck happened, but USUALLY putting the alarm out of reach is enough. If I'm feeling bold I'll set the alarm a bit early and then set it a bit later again after it goes off. Having to turn a damn alarm off every 15 minutes will wake you right up. Do NOT use snooze. Too easy to accidentally overdo it. especially the eyes, oh how they burn

bitch I am the Light we discussed this

We did, but you won't because you insist on making negative posts that have zero content other than berating me, while I'm actually going through the effort to prevent hard evidence to the contrary of your claims. Yeah, it was a bit late; I'm sorry correcting you isn't my priority. This thread's title actually has my name in it and is probably not a place you should be posting in if you don't care for me. Don't mistake me helping you out by reminding you to read things labeled "Readme" (although it's like, why do I have to do that? For anyone? Yes, there are others) for continuing whatever you think this conversation is. Yes, DO read the Readme. Follow its instructions. If they say to read something else, read that too. This goes for everyone: there's not a whole lot of scrupulous ways to make the doc pop up in your face beyond naming the file "Readme", so at least do that, okay? This is a public service announcement. It is not an invitation to tie your panties in a not and complain to me about it. It is not an invitation for random people who are not involved to talk about how they are cringing from something that was not affecting them until they chose for it to. I have even asked the moderators to ensure this thread is about what it was supposed to be for and am still seeing posts by people about things that are not Hexware without any intervention on their part. If I had to guess, it is because they think you are mature enough to handle it. So handle it. Control your urge. Do not post in this thread if it is not about Hexware.

Celice you've made plenty of cringe worthy posts yourself

The title says "What are you working on", not "What are you working on in FE" so I've always used it as a "What have you reverse engineered lately" thread. ...Which in my case would still be Fire Emblem, because of Arch and Brendor's kind donations Where's the N64 love?

STRAIGHT from "Release Info.txt" which a file named "Readme.txt" right there in the root folder of the program says you MUST read: And here's the relevant line from "Readme.txt" that says you're supposed to read "Release Info.txt": And some bold, for emphasis: I consider it required reading each time a new release is reported. I mean. Like. Really, kid? Don't speak for other people. You are not everyone I have ever interacted with.

Bartholamieu Stabsalot.

"For some reason"? Why would they change? If they did that would mean those lines are calculated. I doubt that IS wasted pathfinding efforts on something that could be made static. The real questions are whether it's image data and whether it's embedded in the world map if so.

That is very likely free and has been used for old Nightmare modules in the past for that reason. FEditor and the community as a whole both do not acknowledge that area as free space and it is not well documented, but I am confident that it is safer to use as free space than most other areas in the ROM, including: This was never really confirmed. FEditor uses it as a consequence of gossip. I have seen a reported issue regarding the use of some part of that region as free space. Unfortunately I have lost that reference.

Depends who's rolling. If it's Dudu I'll take the 50/50. If it's Monica I would probably settle for a guaranteed 7 フフフ 何用かね？

Yeah shooters kind of suck. I love the genre but the games themselves are often poor executions. I have had better luck enjoying shooters that are of mixed genre - games like Borderlands 2, which is also a loothell RPG, and PSO2, which is a loothell MMORPG. My aiming skills from playing games like Halo and TF2 on par with professional levels (at least for Halo) has had some impact on my PSO2 success, and to a greater extent, how well I've done at BL2, but suffice to say if you're playing a shooting game that isn't just a shooting game, aiming skill and general skill with the genre isn't as important. At least you will be having more fun overall with all of the quirky additional features of the game, though. I do miss how Halo was around when I quit (played from 2 through Reach), which had become progressively more sandbox-based with the Forge system that even spilled over into many matchmaking modes operating almost entirely off of community made maps and, more importantly, the custom games playing with friends on maps we had made together was wonderful. I don't think I could go back to games like Halo 2, though, which had far less customization and were more about shooting stuff. There is some dissatisfaction in knowing you aren't as SUPERMLGPRO as you could be if you were playing against other humans in a purely competitive game (PvP is another thing I have grown tired of), or even just a game that is more skill based (i.e. a shooter that ISN'T also an RPG, where players can excel by dumping more time in the game rather than simply practicing and being better). However, the frustration of dull gameplay due to lack of customzation and asinine players who will always frequent competitive arenas certainly doesn't seem worth going back, at least to me. I don't know how much use you will have for "finally being able to aim" until game developers find a way to make pure shooters not suck. I could never play Call of Duty (and I have tried a demo of the campaign, so I have firsthand experience with hating it).

I miss Death :( I would miss Mori too but I suspect he might be a sociopath I don't think Fizdiz and I ever talked though

I treat people like you like you're beneath me, because you are beneath people. Don't post in here.

"Let's...let's not rule anything out" You could have not been so needlessly rude

The thing right after that looks like LZ data and the thing before it probably is too. To my knowledge a string of 0x00 or other bytes wouldn't ever become a string of 0x00 in the LZ data, but either way I wouldn't recommend touching that area. As a general rule, free space is going to be closer to the end of the ROM. Compilers pack stuff at the lower addresses (especially important for achitectures like the GBA's ARM core, due to addressing limitations of the machine's opcodes) starting with code and then data, scattering larger resources more toward the end which will be loaded using a reference (thus circumventing the addressing issues). FE7 is reported to (still not really confirmed) have a truckload of free space about a megabyte in length around the 0x00D00000 area, Now, some hacks, like FEditor's auto patches, use what is believed to be free space (I believe one of the FE6 autopatches actually isn't in free space and has not been moved since the late discovery of this unfortunate case) at lower addresses so that the code for those patches can "reach" and use the functions already in the game, as well as allow those functions be able to "reach" the patches. These patches shouldn't be borked in any way (although one of them are near the region you've highlighted because, as I have said, that does not even appear to be free space) and all of the actual original data shouldn't either, so no one mentions any regions at those lower addresses as being "free"...and it would probably be best if they continued to regard them as "used". As a fun anecdote for the technically minded, "user code" (stuff us hackers make) can be written to circumvent addressing limitations of the hardware by adjusting the calling convention in a way that unfortunately clobbers a register (one that is not an argument register, though, meaning it can be preserved on the stack if necessary). It's sort of awful to do in about 8 instructions what could have been done with just 2 in the past, as well as not using the instruction(s; BL is actually 2 instructions in Thumb) meant for calling other functions for its intended purpose (or at all, rather), but there's not really anything else you can do for a game compiled into Thumb code.

- Arch and I are working on Shaver and have confirmed that the issue is a synchronization issue with palettes similar to the issue that was just fixed in which sprites and their sheets were not loaded in synchronization. This is not a new bug caused by new code, it is an old bug that resulted from necessary code not being written in the first place, and the first step to fixing this bug has already occurred in the form of the recent bug fix. - The whole point of announcing an update to FEditor was to get people to flock to it and use it so they could report the bugs sooner. I have been relying on people to help me fix FEditor's bugs for years. Things have always been done this way. I can't possibly test FEditor as well as the people who actually have a large variety of test data they want to use in their hacks. I have a small amount of test data I've made for internel debugging and add to this collection when people submit things they have had issues with, whether it be because of a bug they found or mistakes they've made. Instead of being rude and unhelpful, you could be one of those nice people who donates their time to test FEditor and posting some videos and baseless, condescending accusations instead of the spell source is definitely not the way to do that. - Complaining about people correcting the spelling of the name of something they both worked hard on and know for sure the person who misspelled it is using regularly (and therefore has no excuse to not know the name of the program) is just as bad as, if not worse than, making that error yourself. I haven't made an account on the new FEU yet because I've got plenty of other stuff to do, but if people are going to shit up the thread and make it difficult for any progress to be made then maybe Arch will be a more reliable host in the vein of purifying the thread of such posts. e: The FEDS Thunder/Elthunder animation that is in the pinned thread in this same forum has the exact same issue. The video was made of the spell having been inserted with an older verison of FEditor. It's definitely not a new issue. Now, if anyone has any issues with the actual thing that was changed recently, feel free to let me know. No thoughtless assumptions please.

Yeah, they probably aren't. They really should be though. If it's hard for the police to catch them it's certainly not going to be any easier for a random person to be able to fend them off. It's kind of the job of the police to help people out right? Reminds me of old FEU though. We had a huge spam bot problem and obviously it wouldn't have been effective to look into a third party solution. Fortunately we were in charge of our own system and could make the necessary renovations to inhibit the spam bot process. A similar restructuring of how telephone communcation works could probably be done that would bot alleviate the issue and still allow regular calls to be as simple to make and uphold as they have been, but it would probably be expensive and nobody who cna do anything about it would care and people suck.

Yeah I'm hoping a moderator can clean the crust out of this thread. They have been notified as of a few hours ago so their repsonse time is already less than satisfactory. "The next FEditor" both figuratively and literally will probably be Nightmare 3. You guys should throw dosh at Zahlman and convince him to finish it already.

I am positive that issue is something else entirely. Weird blending like that (note the difference between blending and transparency - they are two completely separate hardware functions. Sprites do not have blending) is a result of a similarly weird "brightness" of the pixels in the map image. What you're showing with Shaver looks more like an insertion issue than a processing issue. It may be a bug, but if it is then it's probably been there since well before the latest FEditor update and whatever happy accident that allowed people to have the animation work correctly in the past is probably still possible. I don't appreciate you trying to convince other people to be a caustic counter productive git along with you.

Can't you just get the police involved since they're breaking some kind of law I'm surprised they're not scared enough to stop calling on their own when they realize the person they're calling knows what they're doing. You did make that clear, right?

As with most bug reports (like actually 99% of them, this is a serious issue with the user base) your "bug report" (read: baseless crap) looks like haphazard user error (as opposed to just plain user error, which implies at least some attempt to understand what they're doing prior to their mistake by comparison). Whatever "weird half-transparency" you're talking about could have been intentional for all I know, because anyone who remotely understands the changes made to update the code would be mystified as to how any bugs could occur that aren't: - A flat out crash - Issues with slow-down due to new code being added to a time-sensitive scene drawing function or, unlikely but possibly, - Some case where OAM sheets are loaded after a spell has finished being rendered which overwrites data in the VRAM it shouldn't - this would not result in some "weird transparency", it would result in a bunch of artifacts from the spell being blatantly scattered around the screen very much like the mismatched OAM and tile sheet issue that was just fixed. Yeah, bugs are bugs because people don't have the capacity to predict every possible error that can occur, so there may be a bug that's not even one of those 3 much more likely (again, comparitively) scenarios. Look at the bug that was just fixed, though - I fixed it as quickly as I did because I recognized what the bug was and thus already had a plan for fixing it. It was one of those bugs like the 3 listed above that "made sense". What if the weird transparency you're talking about is the short display of garbage data left over in VRAM that happens at the start of every spell, including Ereshkigal? You didn't really specify, so you could well be talking about a completely separate bug that was in the original game and unaffected by the fix of the custom spell bug that was recently targeted for removal. Did you even know about that bug? Is it really so hard to not berate people who put in the time and effort to make nice things for you, especially when it has been for free for 5 out of 6 years and is now being funded by other people anyway? Is it such a pain to correctly spell the name of a program you use regularly that saves you hours of efforts and even more hours of learning how to do what the program does in the case of having to do it manually? Do you want to post the spell you're having issues with and describe them politely like a decent person?