Search results

He means quadruple-resolution and quadruple-size bitmaps, of course (twice the width and twice the height).

Re: A quick guide for assembly for the very beginners My only complaint (without even looking at it) is that it's a text file... EDIT: And a quick scan suggests that it's not really a tutorial; more like a reference. Perhaps a detailed read-through would reveal differently though.

Re: Translating "Hack 9" to English? Actually, this forum encourages resurrection when you have something to add. So don't worry. :confused:

Hm. This must be why the assembly class at my school teaches 68k assembly rather than x86 assembly despite the latter's architecture being more prevalent.

Even if it's hard-coded, the values are stored somewhere in the executable. And what's that about height and width being multiplied by the row/column offset?

I finally got around to colouring the drawing of Curly by Onlineworms. It's only flat colour, though. I may yet shade it.

Well, that may not be the only problem. Assembly is about the least intuitive programming language there is. Though, to be honest, TSC isn't much better. If you do decide to learn assembly, make sure you find a tutorial on x86 or i386 assembly (I think those are the same thing). There are other...

Does this mean you're storing them as (left,top,width,height) rather than (left,top,right,bottom), or do you mean something else altogether?

I dunno, maybe they use a debugger to step through the code as it runs?

Um, this is a save editor, not a game editor. If you really want to edit text, I can give you a program that will allow you to decrypt the tsc files, edit them in a text editor, and re-encrypt them. I don't intend to release it anytime soon (it's going to be released someday as part of a suite...

Re: Cave Story Officially Announced for WiiWare I'm almost wishing I had a Wii now... Heehee, I'm pretty sure most of this post is wrong. First of all, Cave Story (the PC version) is probably technically copyrighted. It may or may not be legal to distribute mods of Cave Story, but in general...

Hm. I'm actually not sure why this doesn't work for you. You do need to make sure that Cave Story is not running when you do this, otherwise the prefs file will be overwritten again when it closes, but it sounds like it wasn't running. The only think I can think of to suggest is moving...

If the patcher is built into the editor, then it will know which offsets to apply each value to. That's the whole point – the editor knows where to put everything, but the patch doesn't specify where. It only specifies what. Not true. On Mac, applications are "packages", which are folders...

False. A patch file such as I described is nice because it doesn't require full documentation. The editor simply needs to know what has changed, not where. It then knows where to make the change. It doesn't need a complete list of what is stored where. I'm not going to argue about which is more...

Um... I don't think you understand my suggestion. It essentially means outputting a "patch" in a format that both Mac and Windows editors can understand. The use of such a file would be to port a mod between the platforms; with the patch file, porting would consist of copying all the data files...

Oh, hey! You're right! So, I'll update the CSC to reflect that.

What about this suggestion?

Oh! Random thought! If it's not too much work, I'd suggest interpreting the TSC files as Shift-JIS text rather than extended ASCII; that way the Japanese characters in a couple of the files will be visible (as long as the user's computer can display such characters, of course).

Because '/' is less than '0', but '^' is greater than '0'. We should probably work out a standard representation for these. My suggestion is to only use symbols in the leftmost digits for large numbers, and for negative numbers to use the same "spelling" as for equivalent positive numbers, but...

Let me guess. Pixel doesn't actually check if the values are digits, but simply subtracts 0x30 ('0', 48) from them and then adds them up using the formula (1000a + 100b + 10c + d) (for a given number abcd). Since '~' is 0x7E or 254, that means '~~~~' would encode the number 282194. Am I...

So... 0x4A5B34 holds the first argument to the command, while 0x4A5B34 holds the id of the command. It seems to me that it would be a bad idea to use any argument other than 0 to <NUM, then. What I really wanted to know is if there's a way to determine the size of the variable that was...

Not good enough. The offsets are almost certainly different on the Mac, so just knowing the offsets that have changed is not sufficient. For my suggestion, it would need to specify what has changed in an offset-independent way. For example, if the only change made is to remove (C)Pixel and...

Not good enough. The offsets are almost certainly different on the Mac, so just knowing the offsets that have changed is not sufficient. For my suggestion, it would need to specify what has changed in an offset-independent way. For example, if the only change made is to remove (C)Pixel and...

I have a request. Could you add a function to export a list of changes made to the executable to a plaintext file? Just the changes affecting the executable; not those that affect the maps, images, and scripts. If you do this, then if and when a Mac editor ever gets made (and I am considering...

The brackets are equivalent to C's * operator, right? So, there's a pointer to 0x4A5B34 (call it "long* p"), and there's the input (call it "int n") and the function returns p+n? (ie it adds n*sizeof(long) to the value of p, where sizeof(long) = 4.) Something like this: void NUM(int n) {...