The source code to all my programs.
- This topic has 57 replies, 34 voices, and was last updated 1 year, 11 months ago by
.
-
Posts
-
Unfortunately, you will find that MagmaCompiler is not something we have the source code for. It’s compiled in C++ I believe, and we couldn’t reverse it like Magma itself. The few changes we made to MagmaCompiler were very dirty assembly hacks.
As far as adding new languages and sub genres, remember that you can’t add to the game by modifying Magma…so that’s pretty useless. Neither the language nor the subgenre end up in the RBA file. The only thing that changing the language did was change the encoding that MagmaCompiler would use, to allow special characters. If you add new subgenres, you’d have to modify C3 CON Tools as well to get Visualizer to show them.
Unfortunately, you will find that MagmaCompiler is not something we have the source code for. It’s compiled in C++ I believe, and we couldn’t reverse it like Magma itself. The few changes we made to MagmaCompiler were very dirty assembly hacks.
As far as adding new languages and sub genres, remember that you can’t add to the game by modifying Magma…so that’s pretty useless. Neither the language nor the subgenre end up in the RBA file. The only thing that changing the language did was change the encoding that MagmaCompiler would use, to allow special characters. If you add new subgenres, you’d have to modify C3 CON Tools as well to get Visualizer to show them.
I’m familiar with C++, but that’s a shame that you couldn’t get it to work. Thanks for letting me know. I was looking more so for changes to the visualizer.
Well, the problem isn’t with understanding C++, it’s that once C++ is compiled, you can’t decompile it like we did with Magma itself as that was in C#. If you know assembly and know how to dirty hack executables, you might be able to accomplish something. But I have no idea. I had a law school friend who happened to have been a crack programmer for IBM before help me with that particular task.
Magma and C3 CON Tools are designed to work together. If you add custom stuff in Magma, you have to add it to C3 CON Tools as well so it can show it. That includes Visualizer stuff. It’s easy, relatively speaking. But you gotta do it.
Assembly is hard on the surface, just need to know the default processor architecture for the program order to interpret it. Assuming the program is for Windows (which I don’t know if it is or not), likely the i386 and/or amd64 architecture. I don’t know how to dirty hack executable files, but I can interpret assembly by looking at the language specs. It’ll be a ton of work though, I know of no way to easily work through thousands of lines of assembly code without doing it by hand.
Thanks for all the info. I’ll be sure the Visualizer additions are put across both tools.
Also find myself drifting away from the customs scene these days. Can’t remember the last time I played.
Thanks for all the tools (and site). And thanks for helping me out with my own utility, also!
Q. OMG, does that mean we can figure out how C3 encrypts its files? Are you crazy?
A. No, and maybe. The source code for all of these has been redacted where necessary to protect C3. There is nothing left in there regarding encryption or decryption of files, C3 passwords, etc. Sorry.
Does this mean that if we make changes to a program (say cPlayer or CON tools, just midi read/display changes) and recompile, does that mean the new version will not be able to read a previously C3 encrypted CON’s audio for playback? and making it behave like it does on official DLC.
Does this mean that if we make changes to a program (say cPlayer or CON tools, just midi read/display changes) and recompile, does that mean the new version will not be able to read a previously C3 encrypted CON’s audio for playback? and making it behave like it does on official DLC.
Exactly.
Sent from my SM-G935T using Tapatalk
aww crap
” src=”/wp-content/uploads/invision_emoticons/default_SA_frown.gif” />Well, here’s hoping the torch can be passed to a trusted person/team and include the encryption code with new updates. “C3 – The Next Generation”
There is still a hell of a lot of functionality that doesn’t involve the encryption, that I’ll probably tinker with when I get time.
Thanks again.
Well, unfortunately there was no way to remove the source code for it and keep the functionality in at the same time. If/when C3 gets a designated person to get the unredacted source code, that person will have the keys to the kingdom, so to speak. But I don’t see that happening anytime soon.
Yeah, that was my concern. Now that we’re not getting any more official updates from Nemo, any future updates would be lacking the encryption features and would always be a side-grade. I guess I’ll hold on to my old copy, bugs and all.
Well, I’m hoping to see other things happen beyond bug fixes to the existing tools. I’m really hoping to see people take the existing code and do other things with it. I mean, there’s enough there to make a cheap Phase Shift knockoff, for example, if someone wanted to. And this one could play CON files without needing to be converted at all.
Any chance you could isolate the encryption stuff into a separate closed-source library/exe that can be invoked by a custom build of these apps? That would keep the encryption secret and still allow people to make changes.
Is it possible? Probably. But I don’t know that I know enough to do it well, or that I will have the time to do it anytime soon.
- You must be logged in to reply to this topic.