Grognaks-Mod-Manager/readme_modders.txt at master · HelloChrisLowe/Grognaks-Mod-Manager · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
Mod Developer Notes

Creating an .ftl File

  An .ftl file is simply a renamed .zip with a specific file structure.
  For an example, try renaming and unpacking the example .ftl file that
  comes with the program.

  The root of the ZIP file should contain one or more of these folders:
    data/
    audio/
    fonts/
    img/

  You should ONLY put in the files that you want to modify. This keeps
  mod sizes low and prevents major conflict between mods.


The Append Extension

  Any file in your .ftl with the extension .xml.append will be appended to
  its respective vanilla file. (See the example mod.)

  It is highly recommended that you take advantage of this as much as
  possible. As a rule of thumb, if you're editing an event xml file,
  you're going to want to append your changes rather then flat out replace
  the file. Keep in mind that you can override vanilla events (among other
  things) to your pleasure by writing an event of the same name.
  Using .append helps prevent mod conflict.

  Overriding named lists can be problematic, so a special tag is available
  to add names to blueprintLists.
  ---
  <gmm:blueprintListAppend name="DRONES_STANDARD">
    <name>A</name>
    <name>B</name>
    <name>C</name>
  </gmm:blueprintListAppend>
  ---
  This will generate a new blueprintList containing all existing names,
  plus any you mention. The new list will then override the previous one,
  since FTL honors the last one it sees. Thus, multiple mods can safely
  edit the same list.


General

  When developing a mod, save your text files as ANSI/ASCII, or UTF-8.

  Unless you're overriding something, try to use unique names in your xml so
  that it won't clobber another mod and vice versa.

  Images should be 32bit PNGs (24bit color + 8bit alpha transparency).
  Things that *should* be opaque rectangles like backgrounds may vary,
  but that would be undesirable for ship floors that should reveal the hull
  under them.


Mac-Specific

  OSX adds a junk to .zip files.
    These commands will address that:
      zip -d mymod.zip __MACOSX/\*
      zip -d mymod.zip \*.DS_Store


Pitfalls

  FTL Bug (fixed in 1.03.3): If a ship is modded to have level 5 shields,
  asteroid storms will be abnormally fast.
  http://www.ftlgame.com/forum/viewtopic.php?f=9&t=11057

  The game will crash at the main menu or hangar if an event choice loads
  another event, which has a choice that loads the previous event. FTL
  does not like event loops.
  http://www.ftlgame.com/forum/viewtopic.php?f=12&t=12265

  When adding a music track to sounds.xml, the explore and battle theme
  files are played simultaneously as one song (mixing between them when
  entering/exiting combat). They should have similar duration because if one
  is longer than the other, there may be noticeable silence at the end of the
  shorter piece.
  http://www.ftlgame.com/forum/viewtopic.php?f=12&t=9111