6 réponses à ce sujet

[Abysshunter]

 What types of info can be passed between modules. I read in the wikis that add ins are the only way to communicate between modules.

[Proleric]

Module add-ins are a way of creating "one big module" where you keep adding new adventures. Players with saved games will be able to carry on where they left off, and explore the new material, too.

I'd guess we can save our character for use in another module (and maybe save some additional information that way). We'll know more about that when we see the client.

As far as I know, there's no equivalent of data base storage between modules, but I'm not quite sure why we'd need that, given the options already mentioned.

Modifié par Proleric1, 16 octobre 2009 - 10:18 .

[Abysshunter]

Thank you

[Niko Daemon]

hmmm

[Doc5thMech]

So then if one models the main game as a module, in theory one should be able to write an add-in, and custom materials (armor, jewels, weapons, spells) could be brought to the main game?  Is it possible then for a character to migrate back and forth between the add-in and the main module?

Modifié par Doc5thMech, 18 octobre 2009 - 11:08 .

[Proleric]

Yes. The add-in just makes the game bigger, so the player will wander around seamlessly, without knowing what's original and what's add-in.

[Adinos]

....and keep in mind that add-ins should be able to add just about anything - new companions, new areas, new quests, new spells, new specializations, new armours, new weapons, new loot and so on.



Also, an add-in can change/override just about anything, including various aspects of the game mechanisms - apart from GUI changes, though.