Valiant Force Forum

by ensuring you guys actually do beta testing on a separate server next time

ya sure there are bugs but your not to suppose to discover the bugs during actual event, have a separate server for testing out the implementations when event rewards are at stake

by ensuring you guys actually do beta testing on a separate server next time

ya sure there are bugs but your not to suppose to discover the bugs during actual event, have a separate server for testing out the implementations when event rewards are at stake

Self entitled fool. No such thing as a bug free game. Even AAA games are not bug free. What's important is that bugs are fixed ASAP and proper compensation are given out to players. VF team has been doing great fixing bugs. 

by ensuring you guys actually do beta testing on a separate server next time

ya sure there are bugs but your not to suppose to discover the bugs during actual event, have a separate server for testing out the implementations when event rewards are at stake

Self entitled fool. No such thing as a bug free game. Even AAA games are not bug free. What's important is that bugs are fixed ASAP and proper compensation are given out to players. VF team has been doing great fixing bugs. 

if you have no constructive feedback then stop spouting gibberish you delirious fool

and admin what is the status on master level now?

Constructive feedback?

by ensuring you guys actually do beta testing on a separate server next time

Developers have at least 2~3 systems, usually 3 for those who cater online, which are Development, QA, and Production. Development is where they code, QA is where they test, Production is the active server for users. Before any change can go to production server, obviously it has to go through Development and then QA servers.

ya sure there are bugs but your not to suppose to discover the bugs during actual event, have a separate server for testing out the implementations when event rewards are at stake

Yes, it is a major screw up to find a bug in the actual event but there is no such thing as a bug free game especially online games. Production may yield different results for the test scenarios they ran through Development/QA system because it is the running server and will always have the most data. Also, there are a limited amount of testers and test scenarios compared to the vast amount of players who actually run a lot more different scenarios. Finding bugs in the Production server is a bad thing but it is already expected in any kind of development.

Source: I am a developer for a very large multinational company. After the development, most developers are moved to another project while some are retained to support for 1 year (mandatory) because bugs are expected to pop out every now and then and the actual action is to resolve it as fast as possible. The timeline is obviously a lot shorter for online games because there will be ongoing updates.

Constructive criticism/feedback is given by people who actually know how stuff works. It seems to me that you have no idea at all because you actually thought they run tests at the production server. As for me, I have no constructive criticism for the dev team because as I've said, bugs are expected to pop out every now and then and the correct action is to resolve it as fast as possible. They have already acknowledged it and are resolving it. Your "constructive feedback" to do tests on a test system is not constructive at all as it is already the norm.

Funny to be called a "delirious fool" by someone ignorant to how this kind of stuff works.

Constructive feedback?

by ensuring you guys actually do beta testing on a separate server next time

Developers have at least 2~3 systems, usually 3 for those who cater online, which are Development, QA, and Production. Development is where they code, QA is where they test, Production is the active server for users. Before any change can go to production server, obviously it has to go through Development and then QA servers.

ya sure there are bugs but your not to suppose to discover the bugs during actual event, have a separate server for testing out the implementations when event rewards are at stake

Yes, it is a major screw up to find a bug in the actual event but there is no such thing as a bug free game especially online games. Production may yield different results for the test scenarios they ran through Development/QA system because it is the running server and will always have the most data. Also, there are a limited amount of testers and test scenarios compared to the vast amount of players who actually run a lot more different scenarios. Finding bugs in the Production server is a bad thing but it is already expected in any kind of development.

Source: I am a developer for a very large multinational company. After the development, most developers are moved to another project while some are retained to support for 1 year (mandatory) because bugs are expected to pop out every now and then and the actual action is to resolve it as fast as possible. The timeline is obviously a lot shorter for online games because there will be ongoing updates.

Constructive criticism/feedback is given by people who actually know how stuff works. It seems to me that you have no idea at all because you actually thought they run tests at the production server. As for me, I have no constructive criticism for the dev team because as I've said, bugs are expected to pop out every now and then and the correct action is to resolve it as fast as possible. They have already acknowledged it and are resolving it. Your "constructive feedback" to do tests on a test system is not constructive at all as it is already the norm.

Funny to be called a "delirious fool" by someone ignorant to how this kind of stuff works.

ramblings of a retard, how do you even know its a norm for them to run test on a test server? if it is so then its funny that something so easy to spot on a master stage cannot be even found, seems to me like the QA process is weak

if your not the developer flr the game just keep your delusions to yourself

Constructive feedback?

by ensuring you guys actually do beta testing on a separate server next time

Developers have at least 2~3 systems, usually 3 for those who cater online, which are Development, QA, and Production. Development is where they code, QA is where they test, Production is the active server for users. Before any change can go to production server, obviously it has to go through Development and then QA servers.

ya sure there are bugs but your not to suppose to discover the bugs during actual event, have a separate server for testing out the implementations when event rewards are at stake

Yes, it is a major screw up to find a bug in the actual event but there is no such thing as a bug free game especially online games. Production may yield different results for the test scenarios they ran through Development/QA system because it is the running server and will always have the most data. Also, there are a limited amount of testers and test scenarios compared to the vast amount of players who actually run a lot more different scenarios. Finding bugs in the Production server is a bad thing but it is already expected in any kind of development.

Source: I am a developer for a very large multinational company. After the development, most developers are moved to another project while some are retained to support for 1 year (mandatory) because bugs are expected to pop out every now and then and the actual action is to resolve it as fast as possible. The timeline is obviously a lot shorter for online games because there will be ongoing updates.

Constructive criticism/feedback is given by people who actually know how stuff works. It seems to me that you have no idea at all because you actually thought they run tests at the production server. As for me, I have no constructive criticism for the dev team because as I've said, bugs are expected to pop out every now and then and the correct action is to resolve it as fast as possible. They have already acknowledged it and are resolving it. Your "constructive feedback" to do tests on a test system is not constructive at all as it is already the norm.

Funny to be called a "delirious fool" by someone ignorant to how this kind of stuff works.

ramblings of a retard, how do you even know its a norm for them to run test on a test server? if it is so then its funny that something so easy to spot on a master stage cannot be even found, seems to me like the QA process is weak

if your not the developer flr the game just keep your delusions to yourself

How do I know? It is the norm for all development teams. Who the actual F does tests and direct changes on a production system? It seems that you're the one delusional as you can't accept the fact that your ignorance has been exploited.

Constructive feedback?

Developers have at least 2~3 systems, usually 3 for those who cater online, which are Development, QA, and Production. Development is where they code, QA is where they test, Production is the active server for users. Before any change can go to production server, obviously it has to go through Development and then QA servers.



Yes, it is a major screw up to find a bug in the actual event but there is no such thing as a bug free game especially online games. Production may yield different results for the test scenarios they ran through Development/QA system because it is the running server and will always have the most data. Also, there are a limited amount of testers and test scenarios compared to the vast amount of players who actually run a lot more different scenarios. Finding bugs in the Production server is a bad thing but it is already expected in any kind of development.

Source: I am a developer for a very large multinational company. After the development, most developers are moved to another project while some are retained to support for 1 year (mandatory) because bugs are expected to pop out every now and then and the actual action is to resolve it as fast as possible. The timeline is obviously a lot shorter for online games because there will be ongoing updates.

Constructive criticism/feedback is given by people who actually know how stuff works. It seems to me that you have no idea at all because you actually thought they run tests at the production server. As for me, I have no constructive criticism for the dev team because as I've said, bugs are expected to pop out every now and then and the correct action is to resolve it as fast as possible. They have already acknowledged it and are resolving it. Your "constructive feedback" to do tests on a test system is not constructive at all as it is already the norm.

Funny to be called a "delirious fool" by someone ignorant to how this kind of stuff works.

ramblings of a retard, how do you even know its a norm for them to run test on a test server? if it is so then its funny that something so easy to spot on a master stage cannot be even found, seems to me like the QA process is weak

if your not the developer flr the game just keep your delusions to yourself

How do I know? It is the norm for all development teams. Who the actual F does tests and direct changes on a production system? It seems that you're the one delusional as you can't accept the fact that your ignorance has been exploited.

somehow i suspect that if your a developer you must be a pathethic one, quite clearly if they had done the QA it be easy so spot somethig so glaring in the master stage where it just requires one run to find out

so stop running around like a headless chicken trying to be an actual chicken, i prefer if the developer answer the question instead of a crackpot like you

ramblings of a retard, how do you even know its a norm for them to run test on a test server? if it is so then its funny that something so easy to spot on a master stage cannot be even found, seems to me like the QA process is weak

if your not the developer flr the game just keep your delusions to yourself

How do I know? It is the norm for all development teams. Who the actual F does tests and direct changes on a production system? It seems that you're the one delusional as you can't accept the fact that your ignorance has been exploited.

somehow i suspect that if your a developer you must be a pathethic one, quite clearly if they had done the QA it be easy so spot somethig so glaring in the master stage where it just requires one run to find out

so stop running around like a headless chicken trying to be an actual chicken, i prefer if the developer answer the question instead of a crackpot like you

Finally, it seems that you've been convinced that they actually have a test/development system.

When there is a maintenance, the system will be down. That's when they transfer changes from Test/QA system to Production System. Heck, if they have only one server, where do you think they develop? You can't develop or do changes in an active production server as it may crash other users. Editing codes in production system are usually locked to ensure this.

It's true that this is something easy to be checked. In these cases, there are usually 3 things to look for. 
1. There were some codes not included in the package transferred to the production system which caused inconsistencies in the production system.
2. This is a timed update. Meaning the updates were already transferred during maintenance and they simply activate after a set amount of time and the server doesn't need any downtime. For example, maintenance was done X days ago but this update will activate after Y days. Reward orbs will be automatically given out when completing an event after the timer for the event start runs out. In this case, it was not checked right after the update hit. This one is hard to test as it usually has to be done quickly during maintenance period and is usually overlooked too.
3. They simply overlooked it during testing which is possible but highly unlikely unless they are really incompetent.


They have already acknowledged the bug and are already working on it. VF team has always given out proper compensation for this kind of stuff. What else do you want? 

How do I know? It is the norm for all development teams. Who the actual F does tests and direct changes on a production system? It seems that you're the one delusional as you can't accept the fact that your ignorance has been exploited.

somehow i suspect that if your a developer you must be a pathethic one, quite clearly if they had done the QA it be easy so spot somethig so glaring in the master stage where it just requires one run to find out

so stop running around like a headless chicken trying to be an actual chicken, i prefer if the developer answer the question instead of a crackpot like you

Finally, it seems that you've been convinced that they actually have a test/development system.

When there is a maintenance, the system will be down. That's when they transfer changes from Test/QA system to Production System. Heck, if they have only one server, where do you think they develop? You can't develop or do changes in an active production server as it may crash other users. Editing codes in production system are usually locked to ensure this.

It's true that this is something easy to be checked. In these cases, there are usually 3 things to look for. 
1. There were some codes not included in the package transferred to the production system which caused inconsistencies in the production system.
2. This is a timed update. Meaning the updates were already transferred during maintenance and they simply activate after a set amount of time and the server doesn't need any downtime. For example, maintenance was done X days ago but this update will activate after Y days. Reward orbs will be automatically given out when completing an event after the timer for the event start runs out. In this case, it was not checked right after the update hit. This one is hard to test as it usually has to be done quickly during maintenance period and is usually overlooked too.
3. They simply overlooked it during testing which is possible but highly unlikely unless they are really incompetent.


They have already acknowledged the bug and are already working on it. VF team has always given out proper compensation for this kind of stuff. What else do you want? 

and it seems to me that you dont understand simple english, my contention all the time was that they are not doing the testing before the event started. i dont even know why i bother speaking with illiterate people.

the point is not compensation, this happened the last event and they kept quiet about it until the end. point being is that their testing is not being done properly so stop being an advocate for the company when you have no authoritative.

Kyon, 

It's perfectly acceptable to have bugs in games as long as they are looked into and resolved promptly. The issue here is that simple/obvious testing doesn't seem to have been done like using Talissa in the current event ladder. (She has bonus stats and is the current event hero. Obviously people would use her in master/legendary event stages).

And the same points bug that happened in the last ladder event is occurring again now. Making the same mistake twice is quite sloppy, don't you think?