Kingers on 19/3/2005 at 11:51
[Mandrake] Just Shadow, I though ShadowLoader - Thief: DS Fan Mission Loader was a bit much. :rolleyes:
van HellSing on 19/3/2005 at 11:52
Yay :D
GlasWolf on 19/3/2005 at 12:22
Quote Posted by OrbWeaver
As long as the format for distribution is standardised and documented, it is of no consequence how many splinter groups wish to create their own loaders.
Technically speaking I agree, but it would simply be a lot of wasted effort and that seems rather pointless. Anyway, I don't want to put a downer on everything and I've made my point, so we'll agree to disagree.
Agetian on 19/3/2005 at 15:06
Quote Posted by GlasWolf
And as I see it, the problem with using something like .net is that people want a single, convenient download for a util like this. There's already evidence that some people (myself included) are uneasy about it, and eventually a group will splinter off and do their own version. The .net-reliant version will then die in the water, wasting the efforts of all involved.
I wouldn't really worry about that. People are free to make as many mission loaders as they want to, the more - the better. :)
I personally vote for the .NET-based version. Period.
- Agetian
OrbWeaver on 19/3/2005 at 15:36
Quote Posted by Kingers
Well everyone should be pleased to know that the interface and its underlying code are now finished and ready for testing when the final format for the maps is agreed upon!
I suggest using an INI-style format for MANIFEST.TXT (or whatever you want to call it), e.g.
Code:
[Mission]
Name=Robbing The Bank
Author=Whoever
NumMaps=3
[Data]
GmpFiles=Bank1.gmp,Bank2.gmp,Bank3.gmp
IbtFiles=Bank1.ibt,Bank2.ibt,Bank3.ibt
Quotes=Quotes.sch
;Other data that needs to be copied, based on mission packaging instructions.
[Briefing]
You are robbing the bank. Blah blah blah
Freeform text.
---
More Freeform text.
Etc.
Alternatively, you could just have all the relevant files added to the ZIP with their correct directory paths, which is then unzipped into the TDS folder. It depends whether you want to put "intelligent" file-copying code into the loader, or just unzip the thing and pass the onus onto FM packagers not to create an archive which wrecks the installation.
Kingers on 19/3/2005 at 16:05
The current setup is something like this:
title.txt - The Mission title
features.txt - The various features employed by the FM, a simple list such as custom map, custom textures etc.
brief.rtf - A Rich Text Format briefing, similar to that supplied for DarkLoader
FM files - Simply add the rest of the files preserving any relative path directories.
As for security I had not planned on adding this for certain file types, does DarkLoader do this? Has anyone ever tried to exploit a Thief FM user?
Mortal Monkey on 19/3/2005 at 16:24
Quote Posted by David
Darkloader, for example, will not extract anything executable. (EXE, DLL etc)
Wrong.
Kingers on 20/3/2005 at 17:14
OK people, suggestions beyond basic DarkLoader style functionality!
Zillameth on 20/3/2005 at 17:54
Frankly, I think Darkloader is such a great tool because it's so "basic". Don't add too many bells and whistles, just make sure it's stable, reliable, and won't try to format my system partition. :)
dracflamloc on 21/3/2005 at 01:54
Hey guys, I'm back from spring break and someone goes and makes a fleshloader?!?!!?
Too bad its in .NET
Do you have much other than the interface done? I'll start writing my own loader now that I'm back from my vacation, let me know if you want to consolidate the efforts or not. I'll be writing it in C.
