Submissions to Community Library

apricotslice · Post by **apricotslice** » Wed, 15. Apr 09, 01:50

Mods have a cat/dat.
Scripts do not have a cat/dat.
MD's only contain a mission file.

I do agree that if a script pack changes an egosoft script, then that should be highlighted. That way, when there is a patch, people can know if the script needs to be updated before they can continue using it safely. Its not a mod, but the core scripting of the game is changed and subject to a major failure should a patch overwrite it.

spacefueladdict · Post by **spacefueladdict** » Wed, 15. Apr 09, 11:30

jlehtone wrote:
Gazz wrote:[2008-12-16] Remove: Press (KEY) to turn off Classic Flight Mode by Graxster
for instance, is no hotkey script at all but only changes one entry in the TFiles to suppress a popup text in the middle of the screen. (sets it to an empty string)

It doesn't actually do anything so it has no function to be sorted by but it still changes a game feature.
My ... brain ... hurts.

The separation of scripts, which technically have On/Off toggle implemented with "AL plugin", does not add value. However, the separation into "scripts" and "mods" is technical and has practical importance. So what are "scripts" and "mods"?

The game reads data from files. There are clearly two sets of files: the "cat/dat" can have multiple versions of same data, with latest version superceding the others, while there is only one version of a "script file".

"Scripts" seem to add new features by adding new script files. There is chance of conflict, if two scripts introduce/use same symbol for different purposes. The Library lists such symbols (wares, commands, text).

"Mods" alter existing data. Addition of new ship type is mainly adding something new, but some existing files have to be altered.

There are two ways to alter existing data: to replace existing file, or supercede it with new version. "Mods" preferably offer a new version.

But one cannot do that for script files. And there are "scripts" that do overwrite stock script files. Those are thus "mods". Actually, they are worse than "regular" mods, because multiple mod packages can co-exist (although not as active), but anything overwriting stock files is very difficult to uninstall (unless the script installer creates a backup of the overwritten files).

So there is a technical division of S&M into three groups that require different installation/uninstallation procedures. I think the packages that overwrite anything should be clearly marked. But I have no idea which ones do.

@spacefueladdict: "Text id" is one
Code: Select all
<t id="nn">foo bar</t>
It seems that you want to reserve a Text File ID 9200, and that file will add/alter entries to multiple Text Pages, including Text Page ID 9200. Now, if you do check the Library, you will notice that Text File ID 9200 (and thus implicitly Text Page ID 9200) are claimed by yet unnamed work from author "spacefueladdict".

That unamed work by me is this one!

The name is now 'Sector size & background Mod V2.0. and alters pages '7' & '19'.

LV · Post by LV » Wed, 15. Apr 09, 11:35

jlehtone i've just added some more info to the posting format and found that my bountyboost plugin and RRF are no longer in existence, i looked at the t file ref page and many of my script t files are no longer listed, either i've not added quite a few scripts to the index which i thought i had or there is a problem

i've migrated the other cheats from the cheats stickie but have left the date format off for now due to the above

-------------------------------

In relation to the debate above people, my brain hurts as well

scripts = xml files

mods = cat/dat files

it's that simple, the points above may indeed have relevance but they also turn maintenance of this index and the "where the hell does this go" into a full time job

spacefueladdict

we don't need all that

e.g

Submissions to Community Library

Re: Submissions to Community Library

Re: Submissions to Community Library