Some probably already figured this out, but for the rest of us, ( especially Blender's Cycles Users ) I want to share an important discovery: A way of Actually getting shadows and highlights in the Cycles renderer. The Concept is simple, reduce the " exposure time ", and Increase the Lighting Streng...

Of course, Having a fully emulated Computer system Onboard to program my piloting subroutines would really solve all of my problems... but I'm getting ahead of myself.

Hmm? KSP? Sorry, I've never encountered this acronym before.

Considering the vast distances of space... It would take a long time to get anywhere. which wouldn't be so bad if you could shut down the program during journeys, and then start it up and load when you arrived. Dunno If i explained that very well. example: so you're set to travel to the fifth planet...

So Modules can be written for any adventure, as long as they are linked to the proper adventure? ( and Vanilla modules are linked to all extensions, then ) I thought for some reason that modules were for Vanilla only. :/

Here're My two bits: Tombstones(ShipWrecks, marked by a player name and score) could take the form of a daily Online High-Score Board, Where Only Ten Per System Exist, and they replace ones of a lower score. The System would have to check the internet to update this whenever a star system was entere...

It works now; I declared the Star System in the same file as the Adventure, and presto, all of my troubles floated away...

Maybe it's just me, but I find it's really helpful to know exactly where an error is in any scripts I'm cobbling up. I Haven't seen Transcendence supply a Line and position, which can make debugging a much more troublesome process.(In Fact, How Do I know that I'm not making more errors when I'm tryi...

Here are the updated files: Adventure: <?xml version="1.0" ?> <!DOCTYPE TranscendenceAdventure [ <!ENTITY unidEnigma "0xEA770001"> <!ENTITY unidSTAR7 "0xEA770002"> <!ENTITY unidEnigmaAdventure "0xEA770003"> ]> <TranscendenceAdventure UNID= "&unidEnigmaAdventure;" version= "1.0" > <AdventureDesc UNID...

Thanks for the prompt reply, declaration of UNID's was an area I wasn't entirely sure about, so that clears up some stuff for me. I think the error lies in the star systems file, as I can get the Adventure to work as long as I plug in a system declared in SotP. Just a matter of studying all of those...

Adventure Declaration: <?xml version="1.0" ?> <!DOCTYPE TranscendenceAdventure [ <!ENTITY unidStartSystem "0xEA770002"> <!ENTITY unidEnigma "0xEA770001"> ]> <TranscendenceAdventure UNID= "0xEA770003" version= "1.0" > <AdventureDesc UNID= "@1;" name= "Enigma" backgroundID= "" > </AdventureDesc> <Syst...

Thank you for the timely response-- If it's really as old as 1.03, I might as well just start with what I got.

Back in the day, I remember seeing a version of T called "Transcendence 2K" or something. I was told that it was a version stripped down to the most basic components, making the file only 2 Kilobytes large, or something to that effect. Since then, I think the Website was re-organized and I cannot lo...