mudlet-makers team mailing list archive
-
mudlet-makers team
-
Mailing list archive
-
Message #02881
[Bug 1112223] Re: Package Exporter - Applies the </MudletPackage> too early in the XML
Ok, I solved this by using my module export code instead of the generic
package exporter. I don't want to break anything in the generic
exporter and the modules are my creation so I know what they tie into.
I tested with a few cases, if you can compile feel free to test my
branch.
Commit:
https://github.com/Chris7/Mudlet2/commit/d846db9966532d92ae8cce2c930b761156dcee26
** Changed in: mudlet
Status: New => Fix Committed
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1112223
Title:
Package Exporter - Applies the </MudletPackage> too early in the XML
Status in Mudlet the MUD client:
Fix Committed
Bug description:
I created two seperate XMLs for small systems. Both inserted the
</MudletPackage> tag just after the Trigger package ended. When
attempting to import those XMLs, mudlet never read and imported the
Alias' or Scripts.
Mudlet ver. 2.1 - Current Build
OS X Mountain Lion
To manage notifications about this bug go to:
https://bugs.launchpad.net/mudlet/+bug/1112223/+subscriptions
References