Originally posted by YARR4MOD

---

This reminds me of this guy my dad knew who had this fat snake. Huge thing.. forgot what it was called. It had an entire room dedicated to it, with ropes everywhere and stuff. The owner would go out and get kittens like you're giving away or at the pound and stuff and feed it to the snake. Hoo ha.

---

Originally posted by Kegan Marius

---

Case in point: you can get the Microsoft Visual C++ .Net 2003 optimizing compiler and linker for free now at microsoft.com. It's missing a few features, like no IDE, debugger, or profiler, and there's no STL, DirectX, or OpenGL libraries, but if you're only looking for a plain C++ compiler this works.

---

Originally posted by Jagori

---

I use Bloodshed Dev C++. Actually, I normally use MS Visual Studio for C++, but I got Bloodshed because it can also compile C. Very good free IDE.

---

Originally posted by Colleen

---

Heck, I saw a ball bearing company once on the 401 highway called "FAG".

---

Originally posted by MajinBlueDragon

---

not exactly a risque name like what many of you have seen, but um...there's this thing just outside of Noorwood/Wstwood, I beleive, called Object management Group. And on their building is just a huge sign that says "OMG." ...yeah, lame but it seemed much funnier at the time

---

5 BYTE	(148, 106)	0 x 9	eb (left edge)
EXT 4 	(146, 104)	? x ?	da ()
EXT 4 	(128, 96)	? x ?	fd (prevent downward scroll into same screen)
5 BYTE	(150, 105)	1 x 7	e4 (horz. flower platform)
EXT 4 	(144, 96)	? x ?	fd (prevent downward scroll into same screen)
5 BYTE	(150, 116)	4 x 0	6e (multi color stone blocks)
5 BYTE	(162, 113)	0 x 6	eb (left edge)
EXT 4 	(160, 110)	? x ?	da ()
5 BYTE	(154, 109)	0 x 6	ec (right edge)
EXT 4 	(152, 107)	? x ?	d5 (big right facing rock)
EXT 4 	(160, 96)	? x ?	fd (prevent downward scroll into same screen)
EXT 4 	(237, 107)	? x ?	82 ()
5 BYTE	(106, 113)	0 x 14	ec (right edge)
5 BYTE	(162, 120)	0 x 7	67 (orange filler block)
5 BYTE	(122, 113)	0 x 14	eb (left edge)
EXT 4 	(120, 112)	? x ?	dd ()
5 BYTE	(123, 119)	1 x 0	67 (orange filler block)
4 BYTE	(71, 114)	0 x 3	63 (horz. wooden platform)
EXT 4 	(69, 108)	? x ?	15 ()
5 BYTE	(64, 101)	8 x 110	c6 (diagonal down right coins)
4 BYTE	(240, 112)	0 x 0	63 (horz. wooden platform)
4 BYTE	(54, 99)	0 x 8	c4 (coin)
4 BYTE	(54, 101)	0 x 8	c4 (coin)
5 BYTE	(123, 114)	1 x 4	67 (orange filler block)
EXT 4 	(150, 103)	? x ?	50 ()

Originally posted by HyperHacker

---

IMO the real problem isn't advanced data formats, it's 3D. Programming 3D editors is HARD. They take up a lot of RAM and CPU power, so they wouldn't work on crappy video cards *cough*likemine*cough*...

---

Originally posted by Toxic

---

Well, at your house Kram, there's no alternative. You should just get your faucets to produce soda.

---

Originally posted by knuck

---

wtf
WTF
Cellar, this is teh same thing as saying "omg giev me teh sorce so i cna use oit".
Release the source is acceptable, but only if the project die.

---

Originally posted by FuSoYa

---

Because it's in multiple places and formats, so putting it all together and explaining it would be a project in and of itself?

I started out with the sole intention of creating an editor, not comprehensively documenting the ROM in a way that someone other than myself would be able to understand it. My initial notes are all on plain paper (and before you ask, no I don't have a scanner). A few months after that, I switched to text files on my computer since it was easier to keep them together with the ASM traces. For things like the objects, I simply labeled in the trace what they were and included what few notes I made in the source itself while recreating them. My initial SNES ASM hacks were done in SPASM - meaning no commented source code (which I eventually realized was a bad idea, so I switched compilers to something that used source files and wouldn't crash so often - but consequently it was rather annoying when years later I needed to replace some of the earlier ASM code and didn't have any source for it). Some of the things I found were only done by request, so they're in my old email. And many, many things I found while looking through ASM traces of the game in the earlier days of the editor simply weren't documented at all.

---

---

As far as porting goes, in the time it would take to do it properly I could probably get a pretty good head start on a whole new editor for another game. The source code is more C than C++, and is filled with win32 specific calls. That, and a fair amount of the code depends on the little endian format, which would cause problems on the newer Macs since they're big endian IIRC. And I don't have a Mac to begin with.

And I'm not planning to release the source to anyone for various reasons, most of which have been brought up before (don't wish to proofread it for release, easter eggs would be revealed, and just plain don't want to).

---

---

So, to summarize: I don't intend to put together a bunch of SMW data for release, port Lunar Magic to another OS, or release the source code.


There, now if someone asks about it again in the future, we can just direct them to this thread.

---

Originally posted by knuck

---

Yeah right, a GPL is soo going to stop people form using it...

---

---

Cellar: So you bash me because of a "teh"? Right after i post i always check if it has any errors, and then, if needed, i edit the post. But i have something called life, and it's more important than a message board.

"Plus, I look over my posts for spelling errors before submitting them."
So, what does this has to do with source codes?

---

Originally posted by FreeDOS

---

And I have another idea: Why doesn't some one/group change stuff via Lunar Magic, compare in hex editor, write notes, etc. This way, it can be essencially reverse-engineered to figure out what Lunar Magic does. Though it won't tell how.

---