Am I right that the original Ken's Build source code release would be different from the Build that comes with the Duke Nukem 3D and Shadow Warrior source codes?
The question is, how compatible is JBuild to the Build that comes with Duke Nukem 3D or Shadow Warrior? And can you make maps in JBuild for both Duke Nukem 3D and Shadow Warrior?
Assuming JBuild project compiles to a Build.exe file? Does Duke Nukem 3D original source code compiled to Build.exe and Duke3d.exe?
Semicharm at
I haven't played with the orginal build code that Ken released, but I think that there are some differences. Namely one of the souce files was overriden with a different file. astub.c I think. Other than that I'm not sure.
Provided that it writes verison 7 map files I would assume that I would work.
Yes, the Duke3D source compiles both the game and the editor.
kevingpo at
Semicharm said
I haven't played with the orginal build code that Ken released, but I think that there are some differences. Namely one of the souce files was overriden with a different file. astub.c I think. Other than that I'm not sure.
Provided that it writes verison 7 map files I would assume that I would work.
Yes, the Duke3D source compiles both the game and the editor.
Ah yes, it says on JonoF's site that his JDuke3D uses the updated JBuild basecode. So hopefully everything should be consistent. Such as, people using the JBuild to create/build map files, that will work with JDuke3D and JShadowWarrior?
JonoF at
If you've used the Build editors for the DOS versions of Duke3D and Shadow Warrior, you'll have noticed that there's features in each version that aren't in the other, features which are specific to the game in question. That's the reason for there being specific versions of the editor for JFDuke3D and JFSW. Someone particularly brave could work on unifying the two but I personally don't see the point.
Jonathon
kevingpo at
JonoF said
If you've used the Build editors for the DOS versions of Duke3D and Shadow Warrior, you'll have noticed that there's features in each version that aren't in the other, features which are specific to the game in question. That's the reason for there being specific versions of the editor for JFDuke3D and JFSW. Someone particularly brave could work on unifying the two but I personally don't see the point.
Jonathon
How about the difference between JBuild and JDuke Build?
JonoF at
Have a look at this diagram:
http://jonof.edgenetwork.org/misc/bpflow.png
This shows how the code of each of the ports passed from the original release into each port via whom. On its own, JFBuild is the engine plus a demonstration game and editor stub to show the game developer how to use things. The engine mixed with the code from Duke3D or Shadow Warrior produces a game and editor specific to that particular game. The difference between the editors is in the stub files that get compiled with the base editor code that is shipped with the engine.
Jonathon
kevingpo at
JonoF said
Have a look at this diagram:
http://jonof.edgenetwork.org/misc/bpflow.png
This shows how the code of each of the ports passed from the original release into each port via whom. On its own, JFBuild is the engine plus a demonstration game and editor stub to show the game developer how to use things. The engine mixed with the code from Duke3D or Shadow Warrior produces a game and editor specific to that particular game. The difference between the editors is in the stub files that get compiled with the base editor code that is shipped with the engine.
Jonathon
Ah cool. Nice diagram. Wasn't Duke released in 1 April 2003, and SW released on 1 April 2005?
TX at
kevingpo said
Ah cool. Nice diagram. Wasn't Duke released in 1 April 2003, and SW released on 1 April 2005?