Upgrade your account to a Community Supporter account and remove most of the site ads.

Reply to thread

Message: <blockquote data-quote="justanobody" data-source="post: 4598309" data-attributes="member: 70778">Sorry for back to back posts, but don't know if this would fit in the other post id this one ends up right next to it.Well it does involve the higher levels of a character like what happens when you choose a new power at a required swapping level? Does that work? You don't even have that range of levels to test.The idea of a beta is to give everything you have to people to try to break the core of the software.This "beta" is just like a toy preview to get people to buy in and not a proper beta test model. It isn't allowing for catching mistakes prior to adding new data such as the new books, etc. It is one of the worst beta test I have ever seen. I mean they are only having people test the free demo version that people get to play with, and not the full program, so those people testing the demo and using the demo will be hooked to buying into the service, but when they get the full package they will get broken software that was not properly tested.The testing method used as mentioned above is poor that is where the first MMO reference comes into play. I cannot say more than that in regards to MMOs and beta testing.The fact it is working like an MMO means they should have looked at MMO beta testing to see what is needed and how to do it.For example, many MMO or other video RPG type games you build your character via the "sheet" and it helps create the visual for you. You equip a sword, and your visual equips that sword.They are striving for that connection, and have made the program for that, but it is one of the higher level code functions mentioned above that will be missed in testing since they are separate programs na the visualizer is far form done, which means they shoudl have been standalone and only need to connect them so far as storing the sheet on WotC servers, and let the visual designer pull from that account database should someone want to pick things appropriate for their character, and then "paint" them up in their visual design software to be slightly different form other players in the event of meeting someone with a character so close toy our own.Go into the character builder and take ANY character and get to the stats screen. There are white boxes there that show after intial character creation what your adjusted scores are after 8,10,10,10,10,10 for the point buy, unless you have set to an array method. You will note the added racialbonuses in those white squares. You can type in those squares to make whatever scores you want, but you must remember if you roll a 16, you must mentally add the bonus +2 to make it an 18 for your elf racial bonuses to stats.Why is it cached in internet explorer temporary internet files and added to the wizards.com folder in your browser history?If you have something in internet explorer that doesn't allow 3rd party programs to access it for some reason:1- you aren't going to get that news.2- it should not be connecting to internet explorer or in some way be an extension for it to cause problems with your browser or be caught be some ad-aware or other program as a problematic BHO.It just needs to pull the file via the software. This shows me that any actual update of data will also go through internet explorer, and this is a security risk for WotC, as it will leave these history links in IE that will allow anyone to just crawl through the pages to try to get updates where the program should establish a secure connection to the server without going through IE to do so.It is poor design to have the languages selection first. Doesn't matter IF you can bypass them, but languages are one of the least important things needed to be recorded, while the ability scores will determine many more things and should be handled first so they are there and ready for things like feats, powers calculations, etc.I can't even seem to recall where languages will affect anything else either calculation wise, or in game unless your DM forces the issue in some skill challenge, It is that minimal that the required variables should be set up first, before some optional use thing that doesn't affect any other thing of the character. Technically languages should come AFTER feat selection incase you choose additional langues so that you can select them all at once rather than having to go forward and back to try to choose languages and end up forgetting about your bonus language due to feats.It is simply bad design and organization. Try making a flowchart of the process and see where language MUST be to get other things to work. It is not something that any other thing I have seen has a dependency on being done....Another problem is the bug reporting system. The software should handle it all itself and is another bad design to require you to go to two websites in order to report a bug.Microsoft, which Windows is required, has a bug reporting system that can allow for reports to be sent directly from the software, and even include the system specs and other running processes. This is what the software should do itself since it is built on that Windows system that helps with these things which is the .NET framework.When you click report a bug, it should be a part of the program that opens up and send the bug to a server for the developers of the software to get, not to customer service to get, and hope they send it correctly to the developers. It should go directly to the technical department so there is less chance someone along the line will screw up delivering the report.So there are many problems with DDI and WotC digital philosophies. They are still trying to do things the way they were done in the early 80's, and need to adapt much quickly to doing things the right way or at least on that is standard for todays market and technology.<img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f61b.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":p" title="Stick out tongue    :p"  data-smilie="7"data-shortname=":p" />That is the problem. Don't beta test a demo. Beta test the full product. Beta testing a demo only helps create that demo. Then you have to beta test the full product later anyway....<img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f631.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":eek:" title="Eek!    :eek:"  data-smilie="9"data-shortname=":eek:" /></blockquote>

Verification