Difference between revisions of "Talk:Compatibility"

Revision as of 22:34, 6 May 2010

What if my mod extends both Single Player and Awakening?

@monkeysnest - good to have the update concerning the manifest. A few queries:

• Perhaps the article would be clearer if you explained which line has to change, rather than reproduce the entire manifest here?

• Would DAUpdater work? I don't see DAModder listed as a project download on the Bioware social site.

• We don't normally leave our signatures on the content pages of a wiki.

Thanks.

Proleric1 05:47, 8 April 2010 (UTC)

I don't think the "dual entry, single manifest" approach should be followed or encouraged. Creating two separate .dazip installations as mentioned in Compatibility: What if my mod extends both Single Player and Awakening? is IMHO the preferred approach.

--Nukenin 00:24, 24 April 2010 (UTC)

Override Events while minimizing compat issues..

I believe this may be useful to others - through trial and error, and with some help, I have figured out a way to override events only when my module is running - I had to add a variable to var_module.xls/gda (which is probably where the only potential compatibility issue will arise via string ID, though I am not sure what would happen if someone tried to override the same events - depends on which engineevents get's loaded last I suppose...).

The variable is defaulted to a 0....in my modules properties, I set the variable to a 1. My event overrides check for this variable to be == 1, if not, send it off the proper handler.

See the following post where I came to this 'workaround'...would love to know if there is a better way:

http://social.bioware.com/forum/1/topic/8/index/2371093/1#2531362