Forum: empire-en
Board: [818] General Discussion
Topic: [315142] Feeback to GGE's developers
[-315142]
Van Snott (SKN1) [SKN1]
:: Aug. 3, 2016, 10:03 a.m.
You want feedback well here it is:
1. Have your own test team, set up testplans pr update you lanch. Test plan should involve all the functionality
that is changed in the update, and sevral other standard functionality.Most important that it is a own team, never set developers to test their own code. When running tests take a backup from one of the live servers and run the
test on that. And alternate between servers. When a new update or launch have cleared the test prosess inform us on the forum that its ready and have passed testing.This is nessacery for us to start trusting you again.
2. Plan the big events like kalas well before you start them. Set up run plans for all the small events including in
the big event. And most importen, stick to the plan and DONT make any changes when the event have started.
(If you have started with point number one, You don't have to make large changes while runing the event.)
Inform the players by using the forum of the full run plan for eatch event. That will help us to plan how to get the most out of eatch event.
3. Never start or stopp big events on weekends. Make shure you have a team ready to deal with problems on start
and stopp. And the same goes for ANY update or launch. And most importen, bug fixes must also clear the test process. Never ever do bug fixing directly on live servers. And yet again inform us players about the bug fix progress.
4. When you plan system update give us at least 24 hour heads up. Use the logon splash screen to tell the players about this updates.
5. You have to have bether information routins when problems happens. Always have a plan B ready,
I doubt this information will reatch enyone in charge in managment, but now i have at least tryed.
1. Have your own test team, set up testplans pr update you lanch. Test plan should involve all the functionality
that is changed in the update, and sevral other standard functionality.Most important that it is a own team, never set developers to test their own code. When running tests take a backup from one of the live servers and run the
test on that. And alternate between servers. When a new update or launch have cleared the test prosess inform us on the forum that its ready and have passed testing.This is nessacery for us to start trusting you again.
2. Plan the big events like kalas well before you start them. Set up run plans for all the small events including in
the big event. And most importen, stick to the plan and DONT make any changes when the event have started.
(If you have started with point number one, You don't have to make large changes while runing the event.)
Inform the players by using the forum of the full run plan for eatch event. That will help us to plan how to get the most out of eatch event.
3. Never start or stopp big events on weekends. Make shure you have a team ready to deal with problems on start
and stopp. And the same goes for ANY update or launch. And most importen, bug fixes must also clear the test process. Never ever do bug fixing directly on live servers. And yet again inform us players about the bug fix progress.
4. When you plan system update give us at least 24 hour heads up. Use the logon splash screen to tell the players about this updates.
5. You have to have bether information routins when problems happens. Always have a plan B ready,
I doubt this information will reatch enyone in charge in managment, but now i have at least tryed.
[4511458]
John OGroat (GB1) [GB1]
:: Aug. 3, 2016, 10:06 a.m.
6. Leave gaps between events so that when the inevitable happens and something goes wrong, it can be fixed without messing up the next event to run.
[4511920]
THE DARKSIDE (GB1) [GB1]
:: Aug. 3, 2016, 11:03 a.m.
'I doubt this information will reatch enyone in charge in managment, but now i have at least tryed'.........Now learn to spell. Right click on the words underlined in red....that would help. PMSL