heroes outside of the heroes inn

[kaisim_2492829]

But in CWF it is not a saved formation. It is a 'frozen' formation. Any upgrades you make to equipment, runes or heroes is not reflected in the formation. In my opinion it would be useless.

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.

[Andy]

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.

[S.S. Dragon]

no it wouldnt mess it up because all items have a tag number, like an inventory number and its not relevant if item#123456789 is +30 or just been upgraded to +50, its still the same item. meaning if forms can be saved in game like during CW with equipment AND runes, it would make the game so much more user friendly and prevent so many frustrations with bugs (like armor pieces that just got upgraded dont transfer, weapon in inventory = no armor on switch, etc...).

regarding the additional heroes outside the hero inn you have everyones blessings and we been begging for it since the royal challenge and subrelease. as a fact, some where asking for it already when they implemented the heroes inn and all the stored runes disappeared into it and recovery was taking a lot of time. it should be no problem to just extend the scrollbar with a few more heroes, no need to add anything.

ps: i really dont know what the developer was smoking that had the "12 heroes is enough" idea and thought it would bring anyone some sort of strategic advantage or make the game more enjoyable, but its clearly not working out

oh wow. if thats how the rune and armor system works. then yes please add a reset/loadout option. it would make things so much simplier and smoother. thanks for that

[kaisim_2492829]

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.

like i said they have to use the "basic" interface from CW and go from there.
if you encounter problems like closed rune slots, the ID tag would either stay on the previous hero or go into the rune window, depending on how you set the defaults and then return back to the last saved position if you dont confirm/save the new form. if you deleted, sold or merged the old rune then there is no ID tag for the old, meaning the spot will be open. the same for the armor, weapons, whatever. ID tags are unique.
i am very sorry but i still fail to see your point in how it would complicate anything, except add a few days programming.

[Andy]

like i said they have to use the "basic" interface from CW and go from there.
if you encounter problems like closed rune slots, the ID tag would either stay on the previous hero or go into the rune window, depending on how you set the defaults and then return back to the last saved position if you dont confirm/save the new form. if you deleted, sold or merged the old rune then there is no ID tag for the old, meaning the spot will be open. the same for the armor, weapons, whatever. ID tags are unique.
i am very sorry but i still fail to see your point in how it would complicate anything, except add a few days programming.

Just the fact that it will require changes to the database to keep track of the formations complicates things. My way does not require changes to the database because nothing is stored. That is what makes it so simple.

[kaisim_2492829]

Just the fact that it will require changes to the database to keep track of the formations complicates things. My way does not require changes to the database because nothing is stored. That is what makes it so simple.

all items have an ID tag by design