ETA on Advanced Class change?

That is not a transcript, it is by its own admission a summary. As the person who asked the question about Legacy level and legacy banks, I must caution you that the summary is not exact. My own notes say:

"BW said that raising the Legacy level cap and adding corresponding perks was "on the roadmap" but did not say more than that. One BW person said a Legacy vault — i.e. a place to keep all your alts’ mats and trade-able items — would require too much coding."

That BW person was not a programmer BTW.

Unfortunately it's hard to track down specifics. I've suggested that a week or two after a Cantina Q&A it might be a good idea if there was an official Cantina reveal through this site ( http://www.swtor.com/community/showthread.php?t=695561 ), but it was a suggestion that fell off the suggestion board pretty quickly. I know it would take some of the impact away form the fan coverage, but even Dulfy.net rarely carries a summary let alone transcript of the Cantina events. And, it would go a long way to removing inconsistent coverage.

Wondering what we'll be able to do with the legacy storage in the housing system then.
This leaves me worried and the too much coding puzzled.

WRT Legacy storage:


Please keep in mind that a non-programmer saying "it is too much coding" is not credible, and at best is just repeating what he has been told to say. Even a programmer cannot make an estimate of the coding effort required without some familiarity with the code already in use.

That said, as a programmer with decades of experience, my best analysis without seeing the code is this:
1. We already have one kind of vault and one kind of bank account (guild vaults and guild banks) that are accessible by multiple 'toons.

2. It is therefore possible that the Guild vault/bank code can be used to create Legacy vaults and Legacy banks by replacing the test for who can access the vault/bank from isMemberOfGuild(toon) to isMemberofLegacy(toon) and cloning the database structures for Guild banks/vaults into your Legacy. Note that an isMemberOfLegacy() test already exists in game to restrict who you can mail Legacy-bound items to.

3) If you want crafters to be able to access mats in the Legacy vault, you have to change the search-vault-for-mats code to search first your personal vault and then your Legacy vault, and sum the mats in each for display, and then deduct mats from each when you craft according to a priority scheme.. That's maybe eight lines of code if the code is modular, but might be more if there is a lot of duplication of functionality in the crafting code (for example, if the cybertech-realted code uses different source code to check/consume mats that the synthweaving-related code does. which may not be good software design but might still be the case).

So unless the code is incompetently structured, the majority of work for a Legacy vault or bank may simply be adding the appropriate UI elements to the game, and again, the Guild bank/vault UI elements give you a good head start.

tl;dr? If my guesswork is correct, I would expect that:

1. Legacy vaults would exist in your Stronghold, and maybe on Fleet, will look like the Personal vaults, but with a different color scheme. Do not expect Legacy vault access everywhere you have personal Vault access, that would require too many siting decisions and world database changes. (Alternatively, your "Legacy Vault" might just be Legacy tabs in your regular vault - highly convenient but more complicated to code and not as monetizable for BW.)
2. Legacy vaults would only allow unbound items to be placed in them; allowing BtL items is more code and doesn't have the payoff sharing mats does, IMO.
3. New Legacy vault tabs would cost something between what a personal tab and a guild tab costs,
4. in-ship Legacy vault access will be an upgrade you can buy, and
5. you might not be able to craft using mats in the Legacy vault at first, but eventually you will.

Well there are my fearless prediction, time will tell if I am on the mark.

Dont listen to Dewee.

Good to know experienced programmers do think in more possibilities.

Just so you know, your credibility is strained whenever you start posts in General that are stream-of-consciousness ramblings that would make J.D. Salinger weep.

Yes and reported.

Dont listen to Dewee.

Sorry for pushing your buttons.

You'll probably want to edit your post here where you criticized Dewee by name:

Or is it only okay if you're the one that does it?