The version strings for mods are still broken; ie, you cannot specify even 1.05; it refuses to load. This is particularily a problem with certain dockscreens (from 1.04, noted by Atarlost), and mods with the new AutoTargeting Devices, which would need to have properly definable mod version strings.
Its this thing btw:
<TranscendenceExtension UNID="0xE314FFFF" version="1.05">
Edit- this is even worse than in 1.04 given that 1.04 worked with version strings for previous ones like 1.03, but 1.05 chokes on 1.03, as noted by PKodon.
[closed] Mod version strings are still broken
-
Aury
- Fleet Admiral
- Posts: 5510
- Joined: Tue Feb 05, 2008 1:10 am
- Location: At the VSS Shipyards in the frontier, designing new ships.
The following version strings nolonger function:
1.01
1.02
1.03 (This one did work in 1.03, as confirmed by PKodon)
1.04 (This one never worked)
1.05 (This one should work)
http://wiki.neurohack.com/transcendence/trac/ticket/624
I found future versions like 1.1 do however work
http://wiki.neurohack.com/transcendence/trac/ticket/625
edited, turns out that pkodon wasn't using 1.04
1.01
1.02
1.03 (This one did work in 1.03, as confirmed by PKodon)
1.04 (This one never worked)
1.05 (This one should work)
http://wiki.neurohack.com/transcendence/trac/ticket/624
I found future versions like 1.1 do however work
http://wiki.neurohack.com/transcendence/trac/ticket/625
edited, turns out that pkodon wasn't using 1.04
(shpOrder gPlayership 'barrelRoll)
<New tutorials, modding resources, and official extension stuff coming to this space soon!>
<New tutorials, modding resources, and official extension stuff coming to this space soon!>
-
Aury
- Fleet Admiral
- Posts: 5510
- Joined: Tue Feb 05, 2008 1:10 am
- Location: At the VSS Shipyards in the frontier, designing new ships.
Ok, 1.01 is oddly enough not affected by the bug that allows 1.1 to be accepted as valid.
However 1.01 also has a bug where it refuses to load its own extensions. >.<
However 1.01 also has a bug where it refuses to load its own extensions. >.<
(shpOrder gPlayership 'barrelRoll)
<New tutorials, modding resources, and official extension stuff coming to this space soon!>
<New tutorials, modding resources, and official extension stuff coming to this space soon!>
-
Aury
- Fleet Admiral
- Posts: 5510
- Joined: Tue Feb 05, 2008 1:10 am
- Location: At the VSS Shipyards in the frontier, designing new ships.
Hold on, something fishy is up with PKodon's report. 1.03 doesn't work with 1.04 either, so I'm wondering what version he was using his mod on.
(shpOrder gPlayership 'barrelRoll)
<New tutorials, modding resources, and official extension stuff coming to this space soon!>
<New tutorials, modding resources, and official extension stuff coming to this space soon!>
-
Aury
- Fleet Admiral
- Posts: 5510
- Joined: Tue Feb 05, 2008 1:10 am
- Location: At the VSS Shipyards in the frontier, designing new ships.
you may want to read edit 5 here: http://www.neurohack.com/transcendence/ ... 674#p35674
Can anyone find a version where 1.03 works as a mod version string? Because PKodon got it working, and I can't.
Can anyone find a version where 1.03 works as a mod version string? Because PKodon got it working, and I can't.
(shpOrder gPlayership 'barrelRoll)
<New tutorials, modding resources, and official extension stuff coming to this space soon!>
<New tutorials, modding resources, and official extension stuff coming to this space soon!>
-
PKodon
- Militia Lieutenant
- Posts: 127
- Joined: Sat Apr 18, 2009 6:03 pm
- Location: "Minocs. I've got a baaad feeling about this.... This is no cave!"
Clarification:
I did not get it working in 1.03, I looked at 1.03 and still had the version string 1.0.
Also, what seems to have happened is that, for some reason, while working on the FalconCV mod in 1.04, since I knew version strings were not working right, and it wouldn't take 1.04, I put in version string 1.03, but then NEVER TESTED IT (because I got distracted working on a weapon in another file in the mod). However, when talking with Wolfy on IRC, and looking at my code, I "thought" I had had it working before.
Now, it does not make sense to have to use 1.0 as a version string, when, as Wolfy says, you are using functions and strings not valid in earlier versions. So, that needs to be repaired, pronto.
PK
I did not get it working in 1.03, I looked at 1.03 and still had the version string 1.0.
Also, what seems to have happened is that, for some reason, while working on the FalconCV mod in 1.04, since I knew version strings were not working right, and it wouldn't take 1.04, I put in version string 1.03, but then NEVER TESTED IT (because I got distracted working on a weapon in another file in the mod). However, when talking with Wolfy on IRC, and looking at my code, I "thought" I had had it working before.
Now, it does not make sense to have to use 1.0 as a version string, when, as Wolfy says, you are using functions and strings not valid in earlier versions. So, that needs to be repaired, pronto.
PK
"Don't ask ..., I don't wanna know, and I don't wanna care!" - PK
Meet us on IRC -->
"... the hornet battlepod is the closest we have ingame to flying into battle in a wheelbarrow
with a bathtub nailed upside down to the top of it to provide armor." - The Shrike
Meet us on IRC -->
"... the hornet battlepod is the closest we have ingame to flying into battle in a wheelbarrow
with a bathtub nailed upside down to the top of it to provide armor." - The Shrike