Platform: linux Ubuntu 5.10
Source: SVN from yesterday
Is it file Armor.txt generated yet? Where can I get it?
Armor.txt file not found
Moderator: Moderators
- SwiftSpear
- Classic Community Lead
- Posts: 7287
- Joined: 12 Aug 2005, 09:29
the mod is in *.sd7 format, yes. I put the file in trunk/game/mods directory and that's all.
link: http://www.fileuniverse.com/?p=download ... d7&ID=2372
link: http://www.fileuniverse.com/?p=download ... d7&ID=2372
- SwiftSpear
- Classic Community Lead
- Posts: 7287
- Joined: 12 Aug 2005, 09:29
I have the same problem.
My game/mods folder contains the files xtapev3.sd7 and xta_se_v066.sdz.
If I open xtapev3.sd7 in my archive manager it contains a file called armor.txt.
I tried replacing xtapev3.sd7 with the newer XTAPEV5.sd7 but it made no difference.
Any ideas? This game looks like it could be good.
My game/mods folder contains the files xtapev3.sd7 and xta_se_v066.sdz.
If I open xtapev3.sd7 in my archive manager it contains a file called armor.txt.
I tried replacing xtapev3.sd7 with the newer XTAPEV5.sd7 but it made no difference.
Any ideas? This game looks like it could be good.
AFAIK, xtapev3.sd7 is still the default on SVN. The windows build and possibly the released source zip have it set to xtape.sd7 though.
Anyway, yes, Armor.txt means the default mod can not be found (unless you pass a startscript to the exe, but that's another story).
Did you grab the taspring linux tarball? (refer to The SetupGuide for details)
Anyway, yes, Armor.txt means the default mod can not be found (unless you pass a startscript to the exe, but that's another story).
Did you grab the taspring linux tarball? (refer to The SetupGuide for details)
Because the linux installers all include xtapev3, I didn't change the svn mod name on release, as it would break all the linux builds again. (The last time I changed a lot of people started asking about, even though I announced it...)
But peoples builds have to break sometime, so I guess I can just as well do it now
Note that because XTAPEV4.sd7 is now renamed to XTAPE.sd7, this whole problem won't happen again everytime noize makes a new version.
But peoples builds have to break sometime, so I guess I can just as well do it now

Note that because XTAPEV4.sd7 is now renamed to XTAPE.sd7, this whole problem won't happen again everytime noize makes a new version.