Quote Originally Posted by kaisim_2492829 View Post
frozen, right... and what info you capture to "freeze" it? all current levels, runes, armors, enhancements, etc... . all you need to do is to replace all the additional informations with the actual ID tags and you are all set. lets make an an example and say you would "freeze" a hero like its done in CW (as to my understanding) you would collect all the data, description, about current form, set and enhancement level from each item, state of each rune for starters but there is a lot more like passives, etc... so instead of "freezing" all that info let them save the actual ID tags instead. so the actual infos to save would look like this:
square 1: empty
square 2: hero1,
[list of ID tags for armor and weapon],
[list of ID tags for runes]
and so on...
to update the information after you upgraded your gear or runes, nothing has to be done because even if you level up a yellow rune from 10 to 12 it still keeps the same ID tag (hopefully lol). if a player then manually removes an armor and puts it on another hero it would move that ID tag around and unless he hits "save formation" it would return to the previous saved formation after a refresh for example.
from the programmers standpoint i remember writing in pascal and basic that where as "complicated" as that 30 years ago and maybe even harder than today where you have the computers do the work for you.
Then it is not just what we have in the CWF. There will also have to be an interface to manage the different formations along with the database schema update to hold it. My way does not require any information to be stored in the database and there is no need to create an interface to manage anything so it is a lot simpler to provide. It basically automates something that already exists that is the way we have to do it today (remove equipment, remove runes, swap heroes in and out of the Inn if needed, equip equipment, and equip runes) with the added benefit that we are not contained by the available slots in the Pack (except if a Staff or Swords needs to be stored, and that is only one or two slots) or open slots in rune storage.

The only interface changes is to adapt the Transfer interface, and that should be easy, and provide a button (or an icon) somewhere to invoke the function.