Adapt Manifest.xml for use with non-standard mods
Reported by John Vanderbeck | December 2nd, 2009 @ 04:35 PM | in Beta 2
Part of supporting non-standard mods
We need a way to know the mod is non-standard. We can co-opt the
use of Manifest.xml since we would want to store most of that same
data anyway. I propose to use the TYPE attribute of AddInItem. All
mods i've seen use a Type=1. Non-standard mods could set that to
say, Type=5 to identify themself.
Comments and changes to this ticket
-
Alex "Alexspeed" Bachner December 2nd, 2009 @ 04:46 PM
is this TYPE attribute set by the modder when hes making the mod or is that made by the application while installing?
-
John Vanderbeck December 2nd, 2009 @ 04:57 PM
It is set by the toolset when it creates the manifest for you. Type=1 means AddIn, but you can't change it. Its always set to that. And every mod i've looked at including Bioware DLCs and completely new campaigns all are set to 1. Someday that MAY changed, but byt gogin with say 5, we should be safe.
DAModder would set it for the builder when packaging the mod.
-
Alex "Alexspeed" Bachner December 2nd, 2009 @ 05:07 PM
i see, thank you for the explanation, i agree that should be safe then.
-
John Vanderbeck December 3rd, 2009 @ 11:10 AM
- State changed from “new” to “resolved”
Found an easier way to do this, and implemented in B1.6
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
DAModder is a full featured replacement for Bioware's DAUpdater program -- with more features!
John Vanderbeck