Post by christophersax on Nov 3, 2012 0:09:33 GMT -5
I think it would be great to see a changelog for the server that lists any modifactions, tweaks, nerfs, and buffs, and rule changes to our server. The list would be numbered and updated when the change was officially made so there is no misunderstanding and it should be archived so that anyone can see the progression of the changes to the server.
It would also be beneficial if there were a list that showed a "beta" of each "patch" to our server so that changes don't come unexpectedly or out of nowhere.
I.E. if there is to be a change in the rate of fish caught per hour, there would be an announcement in the BETA changelog that described the problem, the intended solution,and the current status (there is a 50% chance to catch fish). When the numbers have been tested in the testing server and the staff and testers have arrived at a satisfying solution, the change will be marked as "Release" in the server change log and an announcement will be made as to when the change is intended to become official.
Example:
10/08/12 BETA
Livewire 0.9.8
There is a 55% chance to catch a fish. (up from 50%)
10/12/12 BETA RELEASE 11/01/12
Livewire 0.9.9
There is a 35% chance to catch a fish. (down from 55%)
11/01/12 RELEASE
Livewire version 1.0
There is a 35% chance to catch a fish. (down from %50)
Notice that the change reflects the change from the previous release version rather than each consecutive BETA data update.
Also notice there is a marked release date on the last BETA entry.
The change log is not limited to 1 change per entry. It is limitless. However, the intent is to specify the exact change, what the work being done to it is, and when it is going to be released.
It would also be beneficial if there were a list that showed a "beta" of each "patch" to our server so that changes don't come unexpectedly or out of nowhere.
I.E. if there is to be a change in the rate of fish caught per hour, there would be an announcement in the BETA changelog that described the problem, the intended solution,and the current status (there is a 50% chance to catch fish). When the numbers have been tested in the testing server and the staff and testers have arrived at a satisfying solution, the change will be marked as "Release" in the server change log and an announcement will be made as to when the change is intended to become official.
Example:
10/08/12 BETA
Livewire 0.9.8
There is a 55% chance to catch a fish. (up from 50%)
10/12/12 BETA RELEASE 11/01/12
Livewire 0.9.9
There is a 35% chance to catch a fish. (down from 55%)
11/01/12 RELEASE
Livewire version 1.0
There is a 35% chance to catch a fish. (down from %50)
Notice that the change reflects the change from the previous release version rather than each consecutive BETA data update.
Also notice there is a marked release date on the last BETA entry.
The change log is not limited to 1 change per entry. It is limitless. However, the intent is to specify the exact change, what the work being done to it is, and when it is going to be released.
