Need Somebody to make me a module.... Please Read

[Legacy_Tythesly]

               I need a module designed to evaluate how good a person is at beta testing... It needs to have bugs ranging from obvious to almost invisible. Please make sure to include a list of every bug in the game. Thank you!
 
Also if possible please explain how to make it work so that if the testers miss something I can fix what they found and let them try to find the rest of the bugs.
               
               

               

                     Modifié par Tythesly, 05 septembre 2011 - 07:30 .
                     
                  

            

[Legacy_NWN DM]

               Is this a serious post?
               
               

               
            

[Legacy_CainMaris]

               Sadly, there's a good chance it is. That level of entitlement coupled with a complete failure to grasp the scope of a request is depressingly common in business.

Don't usually see it here.

Let's be charitable and assume someone is frustrated with their own clients, and venting.
               
               

               
            

[Legacy_Tythesly]

               ........ It is a serious request. Im just starting to learn how to make modules and I have a couple of friends that dont want to learn how to build just test and play... I am working on a huge castle module so that my friends and I can chat in the game.... I was hoping somebody could do this for me so that I can continue to work on my castle (and go to college).
               
               

               
            

[Legacy_werelynx]

               Nowadays you should be happy that you HAVE betatesters, good or not.
               
               

               
            

[Legacy_Shadooow]

               

werelynx wrote...

Nowadays you should be happy that you HAVE betatesters, good or not.

Well said.

Also in real testing you DONT know what are the bugs.
               
               

               
            

[Legacy_Tythesly]

               ..... These beta testers have never played the game before..... Why is everybody against this post.

Can somebody just help me with my request.
               
               

               
            

[Legacy_lordofworms]

               the problem is several.

your asking what? someone ELSE to do ALL your work for you so YOU don't have too?!? why? because your too busy doing RL and your own thing? and if THAT wasn't enough..the way your asking is a bit forceful. I mean most builders ask for help sure, I myself have asked a million things on this board and have always been met with friendly advice and answers, BUT I only asked for HELP in what I am doing at the time, not asking for someone here to just "do it"

that is why 'everbody is against this post'
because your not looking for help, your looking for slaves. which I don't think we do around here.

now, I myself, many would say, would have been more than willing to 'help' you out, but I absolutely won't just do the whole thing for you.. and if someone were inclined to actually take your request seriously...I *think* you need to at least offer more info than

"I need a module that helps track bugs"

mind you, I am not flaming you, we ALL encourage builders to grow with this game, and that being said I have never,ever had this much fun building for a game, even after all these years..and this community( although it may not seem it because of the kinda shocked answers we are all giving based on your *request*) has to be the most helpful and encouraging community around!
               
               

               
            

[Legacy_Lightfoot8]

               I think the real draw back of the request is that I see no reason for beta testers to test on anything but a real module.   Why waste the time, a beta tester module will not make better beta testers nore will it help them find bugs better then simply testing a full module.   Now it would be a great tool for teaching players how to exploit the game.  Even the how to fix them would be of little use for the sole reason that every case is different and the same bug in a differant module would most likely need a case specific fix and not a generic one.    

My opinion is that bata testers are not trained they are born.
               
               

               
            

[Legacy_AndarianTD]

               

Tythesly wrote...

..... These beta testers have never played the game before..... Why is everybody against this post.

Can somebody just help me with my request.

No.
               
               

               
            

[Legacy_Tythesly]

               
               
               

               

                     Modifié par Tythesly, 09 septembre 2011 - 12:01 .
                     
                  

            

[Legacy_Tythesly]

               Actually maybe you can help me out with a different request....

1. Where can I get the CEP, CTP, and CAP


2. How do I install the latest version on my computer.


3. How do I add it to my modules? And how will it affect people if they didnt install it. Do they players have to install it to play a module that was built using it?

Im so confused about these things.

I wish bioware didnt take away the community site....
               
               

               

                     Modifié par Tythesly, 09 septembre 2011 - 12:06 .
                     
                  

            

[Legacy_NWN DM]

               

Tythesly wrote...

Actually maybe you can help me out with a different request....

1. Where can I get the CEP, CTP, and CAP


2. How do I install the latest version on my computer.


3. How do I add it to my modules? And how will it affect people if they didnt install it. Do they players have to install it to play a module that was built using it?

Im so confused about these things.

I wish bioware didnt take away the community site....

1. NWVault

2. Latest version of what?

3. Can't play the module if you don't have the hak files associated with it.  As for associating the hak files to an existing module, if you look on NWVault for a tutorial (there's a few), it will tell you how to do that in the Toolset.

There's a learning curve.  You can't circumvent it... you need experience and the only way is to dedicate the time and effort and dive in... like the rest of us did.  If you're not willing or able to do that, my advice is stop now.
               
               

               
            

[Legacy_olivier leroux]

               Hey! Don't worry, it can be somewhat confusing at first, but it will get better once you understand the basics.

You can find the latest version of the CEP on this Vault page. You install it by downloading "CEP_24_a.rar" (direct link here, just ignore the other download links on that site), unzipping it (you need an archiver capable of opening .rar files, like WinRar or 7zip), then placing all .hak files in the "hak" folder in your Neverwinter Nights directory and the .tlk file in the "tlk" folder.

This article about the CEP might be of use to you, it also features a link to the CEP 2.4 file list. Read the article and click on that link, then open your module in the Aurora toolset, choose "Edit/Module Properties" and the tab "Custom Content", look for the drop-down menu next to the "Add" button, open it by clicking on the arrow, then refer to the CEP 2.4 file list and add all necessary files by selecting them one after another, always pressing the "Add" button. They will appear listed in the window above. You can use the "Move up", "Move down" buttons to make sure the file order in this window is the same as on the CEP 2.4 file list. if you're done press "OK", "Yes" and after the toolset is done adding the files "Done". You now have access to all of the CEP 2.4 content when building with your module.

Your players just have to unzip the CEP 2.4 files into their "hak" and "tlk" folders in order to be able to load your module, they don't have to mess with the toolset.

I don't know about the CTP and CAP and to what degree they are compatible with CEP, that's a question for someone else to answer; but I suggest you start small and try to work with just the CEP until you've understood how it works and are comfortable using it.

Or, if that sounds too complicated for you (although it's quite easy if you follow the instructions), you could search the Vault for a CEP starter module, so that you don't have to add the haks in the toolset yourself.

Feel free to ask for more help and advice whenever you need it, we're always glad to help out if the request is reasonable! '>
               
               

               

                     Modifié par olivier leroux, 09 septembre 2011 - 09:51 .
                     
                  

            

[Baaleos]

               

ShaDoOoW wrote...

werelynx wrote...

Nowadays you should be happy that you HAVE betatesters, good or not.

Well said.

Also in real testing you DONT know what are the bugs.

I agree to a degree.

I'm a software engineer/tester for a Consultancy firm, and I guess the statement is true depending on how you look at it.


In software testing, you can create test-cases, to test areas of vulnerability or risk.
eg - The important areas of a Commerical website, would be the Billing sections, and the login sections etc.
Different testing methodologies would allow you to identify the different tests to perform.

eg - Boundary Analysis would suggest to try to input the highest and lowest acceptable values, and expect the system to allow it, and then to enter highest value + 1, and lowest value -1, and expect the system to disallow it.

That in itself would be a simple test.

Gaming is somewhat different, depending on what phase of testing you are wanting to simulate.

If this is functional testing, then you want to verify that the conversations are working, scripts are doing what they are designed to do etc, and areas are all accessible as needed.

Functional testing also relies on testing different scenarios, so if a PW uses Subraces, you would need to assess which subraces you need to test. Normally, a wide range of variation would be good enough.

eg - If 20 subraces are using letoscript, then you dont need to test all 20, testing one or two letoscript subraces would verify the letoscript functionality. (assuming they do relatively different things).

Beta Testing usually arrives around the EUAT Phase  (End-User Acceptance Testing Phase)
This is testing by the end user/target audience.
A game, being tested, by gamers etc.

Its more aimed at
1. Is the game playable,
2. Is it enjoyable
3. What does the player want added to make it better etc
4. Is the game feasible on a players system.  (Letting players play the game on their own pc, gives game companies better insight into how the game will perform on their whole customer bases systems.)

(In house game testing would only provide about 10-15 different game platforms, simulating different OS's and Hardware specs)

These are usually designed to be optimum for the game, and dont simulate real life systems, that have Virus Scanners, and other apps running at the same time.


Beta Testing is more Ad-Hoc testing.
Play the game, until something jumps out at you and says 'Im a Bug' or 'Im broken'

If you want to add some common bugs.

1. Typo's - Spelling mistakes in Conversations.
2. Conversation Conditionals - Make a quest giver reward the player if they DONT have the items required (eg - having the true and false the wrong way round)
3. Plot Flag - Turn this on and off on certain objects, to make them invulnerable, or vulnerable, depending on the situation. eg- Maybe you want to make a monster, like a goblin, that should obviously, be easy to kill, but instead, you can make it erroneously look god-like invulnerable.
4. Waypoint typos  - Change a few waypoints to have the wrong tag - A script that tries to teleport, will try to teleport you to the tagged waypoint, if the tag is mispelt, it wont teleport you.
5. Make a spell overpowered -  (not a bug per say, but User Acceptance testing 'should' highlight it as a bug. Eg - If Magic Missile was doing 200 damage (for a level 1 spell), a good tester would report it, if you are testing these people as testers, then they should find this bug, and report it, if they ignore it and exploit it, then they arent all that good.)
6. Infinite Loops - Take out the GetNext.....  from a loop, and see if the players/testers report the bug appropriately.




Bug/Defect Reporting.

If your trying to be their Manager or whatever, you need to have a clear and conceise defect reporting strategy.
Make some sort of template, that allows them to fill in the data about the defect.

Make sure you are clear, about requirements.

You cannot fix a bug, if you dont know how to reproduce.
Steps to Reproduce is probably the most important part of a defect report.
Also include time of defect, when it occured etc, a developer can check in the logs to see what happened at that time.


Anyway... enough of my rant.
Hope you have fun implimenting some/any of this.