(WotC Podcast 11/9) Monster Vault II & web-based DDI

buddhafrog

First Post
WotC's Nov 9th podcast (subscribe - they're pretty good) was about the new DDI and the Monster Vault 1 & 2

* There was a interesting bit explaining the DDI transition to web-based and it really sounded like they were on the defensive, pleading for understanding, and letting people know that they understand and are listening. With all the talk in here this past week, they did take notice (whether the resulting product is one that people support, well that remains to be seen). They presented a good explanation. They sold me on their intentions. Sounds like downloadable characters will come very, very soon - don't want to give a date in case they are a week late (not months, years). They discussed why they chose Silverlight. One aspect that I didn't hear WotC admit until this podcast was the role pirating played in their decision. Many of us assumed this, but here they made it seem like it was a critical factor.

* Of real interest to me was the short discussion about 2011's Monster Vault II. I've been intrigued by the Monster Vault but haven't planned on buying it. MVII, however, will be bought. MVII will be presented differently: it will list actual monster characters and their companions that can be played as-is. You will not get a Dragon type, but rather an actual dragon and her underlings. You will get a thieves guild with actual NPC thieves and leaders. You will get goblin tribes and their particular attire and characteristics. I like this idea a lot b/c I expect it will inspire my monster imaginations, give me monster organization ideas, and make it so easy to just pick monsters and play... Also, monsters are easy to re-level, so they will be easily adjustable.

I love this idea and am really looking forward to it. I hope it lives up to my expectations.
 
Last edited:

log in or register to remove this ad

I don't remember clearly but didn't he say that very early on they came to the conclusion that they would do an online builder? I wonder when that was?

I've heard that it was started in dev in March and I've also heard that they've spent six months on it.
 

I don't remember clearly but didn't he say that very early on they came to the conclusion that they would do an online builder? I wonder when that was?

I've heard that it was started in dev in March and I've also heard that they've spent six months on it.

I believe so - 6 month project, and they were a month or so late I believe. And Silverlight was chosen for many reasons, including they (thought they) could complete the project on-time with Silverlight. I haven't commented on this aspect b/c it is far beyond my non-tech brain. However, if Silverlight wasn't the best chose but was still chosen b/c of these time constraints, then to me this is very poor management decisions. One comment that was made that I found humorous, "If we would've chosen Flash, then it wouldn't work on iPads..." Silverlight doesn't work on iPads either, duh. (as long as it works on my hopefully-soon-to-released Notion Ink Adam, I'll be OK).
 

* Of real interest to me was the short discussion about 2011's Monster Vault II. I've been intrigued by the Monster Vault but haven't planned on buying it. MVII, however, will be bought. MVII will be presented differently: it will list actual monster characters and their companions that can be played as-is.
Is this the Nentir Vale Monster Vault or a different product?
 


However, if Silverlight wasn't the best chose but was still chosen b/c of these time constraints, then to me this is very poor management decisions.

You think that time constraints should not impact development decisions?

Welcome to the real world, where business needs are as important (and sometimes more important) than technology decisions, and sometimes compromises must be made to make things happen at all.
 

Welcome to the real world, where business needs are as important (and sometimes more important) than technology decisions, and sometimes compromises must be made to make things happen at all.


QFT. And it's true beyond high-tech applications as well. Step 1 of the design process is "Identify Customer Requirements". This can be production time, cost, performance based, whatever. In this case, the WoTC, identified their time constraint as a requirement.
 

I believe so - 6 month project, and they were a month or so late I believe. And Silverlight was chosen for many reasons, including they (thought they) could complete the project on-time with Silverlight. I haven't commented on this aspect b/c it is far beyond my non-tech brain. However, if Silverlight wasn't the best chose but was still chosen b/c of these time constraints, then to me this is very poor management decisions. One comment that was made that I found humorous, "If we would've chosen Flash, then it wouldn't work on iPads..." Silverlight doesn't work on iPads either, duh. (as long as it works on my hopefully-soon-to-released Notion Ink Adam, I'll be OK).

I would guess that being less than 1/2 hour drive from Microsoft has a lot to do with it. There are many employees who have worked for both companies.

It probably went down something like this
"We need it to be web-based but we don't know what we want. Heh I know lets call our friend/old coworker Bob, he works and Microsoft I bet he knows whats best for this" WOTC
"Well at Microsoft we use Silverlight" Bob
"Silverlight it is" WOTC
 
Last edited:

You think that time constraints should not impact development decisions?

Welcome to the real world, where business needs are as important (and sometimes more important) than technology decisions, and sometimes compromises must be made to make things happen at all.

Of course time constraints should impact development decisions. I said that if Silverlight wasn't the best choice, but was still chosen... Better wording might have been that if Silverlight "clearly" wasn't the best choice. I spoke it certainties about bad decision making when in fact things are far from certain.

I do know the real world of business in which time is important. But haste can also make waste - and this definitely applies to business decisions as well.. There are many scenarios in which silverlight could work out fine. However, if this product is inferior to the current DDI (I clearly think it is, but I'm open minded to how it might develop) and/or because it is inferior to what it could be or needs to be in a year or two, then this decision might backfire. I think that is a very safe argument to make - particularly when the current DDI was working at least relatively well.
 


Remove ads

Top