Quick Modding/Hacking Answers Thread

Unfortunately, the textbox being open requires the event to be running from what i can tell. Which means as long as it's open, interacting with interactable npcs is disabled >.>
I've tried a setup like this:
#0101
<WAI0001<EVE0101
#0102
<CAT<MS20-1: Hello World!<EVE0101
In the hopes that maybe I could maybe use some out of bounds flag checking in event 101 to poll for the player pressing down, to actually enter the level or something while the textbox is still open, but unfortunately even jumping to another event closes the textbox entirely :<

(and even if it worked i guess without some other way of breaking out of a currently running event, that still wouldn't solve me wanting the textbox to disappear if you move away from the door >.>)

 

Yeah, I get what you're going for, but I think even with custom ASM, you won't be having any luck with how the TSC goes in Freeware. Maybe it can be more feasible through the other two engines, CSE2 and d-rs, depending on whether you'd like to take the extra time to learning C++ or Rust. I know there's some people in the CSMC that can suggest ideas for that, even if the TSC required for that won't be 1:1 to your plans on how they'll work.

 

Noted, thanks for your help in any case :>

 

The problem is the player can't interact with objects (like doors) while the textbox is open.

This might not help with the flickering but you could try using key-related flags to check for player input, for example using <FLJ9094
:XXXX to check if the player is holding down the Z/Jump key (arrow key flags don't work with controller).

 

I was trying to make a boss fight, and when I ran the game it crashed. I used <BSL0000 and <BOA0020 individually and they both crashed the game.
(I was trying to use The Dragon Sisters btw.)
The same thing happened with Omega but only when I ran <BSL0000.
(Note: I did not mess with any of the major boss fights except the X and Y coordinates for spawning Omega.)
Here's the event code:

#0100
<BSL0000<CMU0004<BOA0020<MNA<END

#1000
<KEY<CNP0111:0012:0004<CNP0110:0012:0004
<ANP0111:0020:0004<ANP0110:0020:0004<MM0<WAI0200<SOU0029<TRA0010:0090:0000:0000<END

The code is pretty much the same as when I was trying to load in Omega.

 

Hmm strange. I had no problems using these commands. As I understand it, you made a small hack to change the initial position of Omega right? If you look through OllyDbg, these commands are responsible for this:

0047B71E    MOV DWORD PTR DS:[4BBA60],1B6000
0047B728    MOV DWORD PTR DS:[4BBA64],20000

You edited this, right?

 

Yeah, I did.

 

Well, I repeated your actions and <BSL and <BOA work properly. Maybe the problem is something else. Did you do anything else besides this?

 

I don't think so. But in case I did, here's the EXE file.

 

I checked and I can say that both Omega and Dragon Sisters work without errors. Honestly, I can't say what the problem is.

 

Is there something that could make them act weird if certain SkipFlags are set? Because I do have a couple that are over 100 if that has anything to do with it.

 

I don't think so. Unfortunately, I don't know how to help you. Alternatively, you can send additional files related to the map where the crash occurs. Or even the entire mod. That's the last thing I can offer.
It would be nice if someone else responded to your problem besides me.

 

Is there something that could make them act weird if certain SkipFlags are set? Because I do have a couple that are over 100 if that has anything to do with it.

There's only 64 skipflags, anything above that will start poking unrelated memory. That said, I'd be surprised if that's causing a crash... usually that's more a sign of ASM hacks gone wrong.
You could also try running the game under OllyDbg and noting down what address its crashing at. That'll basically lead you (or someone else who knows their way around the exe) directly to the problem point.

 

Is there something that could make them act weird if certain SkipFlags are set? Because I do have a couple that are over 100 if that has anything to do with it.

Out of curiousity related to Brayconn's answer; what > 100 skipflags did you use?

 

Out of curiousity related to Brayconn's answer; what > 100 skipflags did you use?

100, 105, and 200 but they didn't do anything when I was playing the mod, just only when I was trying to start a stage boss battle?

There's only 64 skipflags, anything above that will start poking unrelated memory. That said, I'd be surprised if that's causing a crash... usually that's more a sign of ASM hacks gone wrong.
You could also try running the game under OllyDbg and noting down what address its crashing at. That'll basically lead you (or someone else who knows their way around the exe) directly to the problem point.

It's crashing at 0x007E549 which is something direction related I think.

 

That's a really weird address, it's like there's some digits missing.
If you meant 0x47E549, then that's somewhere at the end of the Sister's Heads' code(?)
Otherwise, really large addresses starting with 7 (or anything other than 4, really) typically belong to dlls, so maybe try disabling (by renaming or deleting) any extra dlls you're using (Modloader, Layers, DDrawCompat, etc.)

Alternatively, sending the first few lines of the call stack (bottom right window by default in Olly) can help determine how the code got to that address

 

My bad, I misread it. It's actually 0047E549.

I fixed it. I just did a <WAI for one tick and now it works!
Thanks Perwinkle.

 

When I test run the game, only some of the entities appear on screen, and not the tiles

 

When I test run the game, only some of the entities appear on screen, and not the tiles

Make sure you launch Booster's Lab in "classic" mode instead of "layers". You need a special hack to get layers maps to work, otherwise you just get the void.

 

There's only 64 skipflags, anything above that will start poking unrelated memory.

@Bi_N just so it's explicitly clear for everyone, this means the valid range of skipflags is <SK+0000 to <SK+0063. Skipflag 0064 is not valid. Anything higher will not function as skipflags and instead, iirc, it will function like a regular flag as it's bleeding into the next section of memory. To avoid problems just only use 0 to 0063 for skipflag usage and use regular <FL+ for regular flag usage.

Meanwhile the valid range of normal event flags are <FL+0000 to <FL+7999 (8000 flags), but don't actually use flag 0000 because you'll run into other problems (So really it's 1 to 7999 that's safe for those).

And write down the flags that you use somewhere! Like have a .txt document in your mod folder (what I used to do) or write them down at the top of the script for map 0 (what I currently do).