|Naksuapina||Will the SCIStudio 3 source code still be available for public?|
|Eero R||It is already...|
Oh, there it is. Must've been blind not seeing the link.. |
Sorry about this :)
|Brian_Provinciano||Yes. It's GNU open source, so you can use it. However, as with GNU source, if you use it in your projects, you must make your source code available as well. You are also really enouraged to credit the author (me) if you do use it, otherwise, you'd be cheating.|
|Pikachu14||What about that decompiler you mentioned on the news page? I'd rather not work my butt off scripting something totally new cool and complex just to have some lamer decompile it all and use it in their projects behind my back.|
I've released the entire SCI Studio source code, as well as code for tons of other projects. I don't worry about the possibility of someone stealing my code, because the world already knows that I am the original author, and would outcast the lamer right away. If you decide not to code something because people might steal it, then it's kind of pointless to be a programmer.|
Also, the decompiler, for example, can't decompile a "Print" lablel, but rather will dump something like "proc_255_0" since, for example, "Print" is stored in the source code only.
You need to know more about scripts when dealing with decompiled ones than with ones in the template. They come out uncommented, and unlableled. Everything is "local123" "temp234" "proc_123_456". Believe me, people would have a lot easier a time coding their own stuff than going into your specific game to try and steal a bit of code which is totally unique. They'd be more likely to code it themselves or try to steal from Sierra's games.
The _real_ fact is though, if they could read, fully understand the scripts in their unlableled, uncommented form, and successfully rip the chunk and use it in their game, they will have enough skill to make their own code. Editing the scripts is mainly for power users who want to correct timing bugs and such in Sierra's games to create patches, as well as to complete SCI Studio.
Someone could always use a hex editor on scripts to change an author's name or change views, pics, etc. It can happen, but...
a) If some lamer does try to steal someone's code I blacklist them, refuse to release it on my sites.
b) Everyone knows who the original author is, and will just outcast the lamer anyways.
The moral of the story:
1) Don't steal people's code! If you use it, give them credit. (hey, I don't bother anyone, but you technically should give credit to me in all your SCI games since I did create the template, though few bother to mention me in their credits).
2) If you steal someone's code, you are a lamer and will be outcasted.
3) don't let lamers who might try to steal your code prevent you from programming to your fullest.
PS. I really really encourage people to distribute their source code for SCI creations as it really does help the community grow. A good half of programmers or more learn best by modifying existing code first, then getting comfortable and writing their own. Many people who were starting out have said that it would be a lot easier to learn if they had more examples. Anyway, would "Joe" want to steal "John's Quest", or create "Joe's Quest"?
Well put, Brian.|
I, in fact, have already released the complete source code for my Age Checking system. It has everything but some simple Control subclasses, supposing that if you can successfully integrate the Age Checker you can create the DTransText and DTransButton classes.
The decompiler's "localXXX"-style output makes me giggle.
About this decompiler thing,|
Brian, you might be insterested in this PhD. thesis written by ms. Tarja Syst
|Brian_Provinciano||I already have the whole code decompilation pretty much implemented, but thanks for the thought.|