(not sure where this would fit best, move if I mis-guessed)
So I've got three game sources - Duke, Shadow Warrior and KenBuild. I can compile KenBuild just fine, but the other two make Visual Studio's linker puke, as shown here...
Ommited to prevent further misunderstandings and decrease page size
Sorry Bill, I don't speak-a die Linkerese. Can somebody tell me what happened? I'd be rather forced to build upon KenBuild, which I'd rather not. That, and it just sucks not to be able to compile Duke and Shadow.
Edit for clarity: I'm using KenBuild, NOT Duke3D. I was just trying to compile it, nothing more.
Edited at
Kyoufu Kawa at
So I've been working on this game using KenBuild as a base and stealing little bits of code from Duke3D where needed...
So far, I've got a working, animated gun for the player and a turret from Duke3D as an enemy.
The turret sprays you with hitscanned bullets when you get near, as one would expect. Unfortunately, it's too damn fast, firing every single game tick. Is there a sprite[].something I can use to delay it's firing?
Edit: Ne'er mind. Seems extra -can- be used for it. I think it's time for a small demo release.
Kyoufu Kawa at
Allright, lessee if I can get a sensible reply with this...
This doesn't show the gun, but that's okay cos it's just the Uzi from Shadow Warrior. You can see it lying on the ground.
Note that my mapper is being busy with schoolwork and stuff. Seems like the aussie fool has an excuse for every day. That's why I use Shadow Warrior textures.
That, and because Poser's still downloading :wink:
TX at
Re: Trying to make my own JFBuild-based game...
Kyoufu Kawa said
Sorry Bill, I don't speak-a die Linkerese.
Or legalese. I'm sorry, but you're going to be in a bit of trouble if you release what you've created.
Duke Nukem 3D is licensed under the GNU General Public License, commonly known as the GPL. The terms of the GPL forbid the use of code licensed under the GPL in any project which is under a more restrictive license (KenBuild, in this case) without explicit written permission from the copyright holder (3D Realms Entertainment/Apogee Software, Ltd.).
It all basically comes down to this: you are using Duke Nukem 3D code illegally. You need to either remove any and all Duke Nukem 3D code from your sources, or you need to obtain explicit written permission from 3DR to use the small bits that you're using. I recommend you e-mail either George Broussard or Scott Miller about it and see what they say. You might want to link to this thread in the e-mail as well, just to make sure that there's a full understanding of the situation.
Kyoufu Kawa at
Trying to make my own JFBuild-based game...
1) I only tried to compile the Duke and Shadow Warrior codes. And it failed.
2) I'm not using either. It's KenBuild based.
3) I'm still working on it so "what you've created" is wrong in it's own right.
4) The little bits of Duke code I did use were only to figure out how the hell to do fullscreen images and loading custom palettes and such, all ending up hacked into unrecognizability. I don't recon the fadeout code counts either, being less than 5 lines, including braces.
5) The Shadow Warrior textures, the only remaining reason to end up in court, are temporary until suitable replacements are made. Emphasis on temporary and made.
6) Bite me.
Now, ignoring this legal mixup, what do you think?
Edit: Addendum to point 4, the bits I did copy weren't even Duke specific...
void NerrdSplash()
{
char nerrdpal[768];
long fil;
if ((fil = kopen4load("p_nerrd.dat",0)) == -1) return;
kread(fil,nerrdpal,768);
kclose(fil);
setbrightness(brightness,(char *)&nerrdpal[0],0);
rotatesprite(0,0,65536L,0,NERRDLOGO,0,0,2+16+64,0L,0L,xdim-1L,ydim-1L);
nextpage();
//Basic loop that waits for a key goes here.
}
Doesn't look too Dukeish to me. Sure, I got the basic code from it, but can 3DR seriously sue me for stealing code that opens a file (group-aware), reads some palette data and uses it? Eh? Try again.
TX at
Kyoufu Kawa said
Now, ignoring this legal mixup, what do you think?
I think sassing moderators when they offer you legitimate and useful advice gets your thread locked.