Return of Reckoning

When you send a rather large file to us you should include a change log or patch note. Get your **** together and stop changing and fixing your bullshit ad hoc.

Seem's like you're the one who needs to get their **** together tbh.

we have not changed large files in a very long time. Also each time we do we do have a patch note. However sometime due to technical reasons the client patch may be delayed and as such the patch notes and server patch happens before the client patch

Dackle wrote: Tue Jul 30, 2019 11:20 pm When you send a rather large file to us you should include a change log or patch note. Get your **** together and stop changing and fixing your bullshit ad hoc.

duno but if you dont like that you need to stop playing this game, sry stop playing online games in general cuz its a normal thing nowdays. duno what you mean but if there is an update you can see the patchnotes here direct on mainpage. Maybe just a troll?

maybe that guy is still affected by the old days when "stealth Patches/changes happend" ¯\_(ツ)_/¯

Nastylicious wrote: Wed Jul 31, 2019 11:04 am maybe that guy is still affected by the old days when "stealth Patches/changes happend" ¯\_(ツ)_/¯

and back then we didnt even have a patcher to download files for us. ¯\_(ツ)_/¯

why not just put a small note on when the client will be patched or was patched for each update. I too looked for a changelog when my client updated yesterday (i think it was)

Just a reminder: constructive feedback is really welcome. That includes also a proper language.

Constructive criticism is, even though it is a small dev team, there is no reason to cut basic corners and implement systems based on tried and true strategies.

I recommend adhering to this:

1. Define requirements

• Through user involvement and analysis of existing system

2. Initial new system design

3. Construct and evaluate an initial prototype

• Rough (skeletal) system attribute framework

4. Construct a further (refined) prototype

• Basing it on evaluation of initial prototype

• Defining its scope

• Planning its development

• Implementing it

5. Overall (system-wide) risk assessment

6. Prototype assessment (as per step 4) and possible development of further prototypes

7. Repeat steps 1-5 until refined prototype meets user expectations

8. Construct the system (based on final refined prototype)

9. Test and maintain the system

You note under 4, continuing on 6, Defining the scope and assessment. That is what the OP asks for, define it (patch note or change log) and let us have it.

No reason so sell yourselves short and create other problems later. Documentation is key to a successful project.

dude you sound like the ror staff have a company running when in reality its just a bunch of guys and girls sitting at their computers when they have free time. documentation is there. its called patchnotes. sometimes the client push comes a bit a after the patch notes or before, doesnt mean the documentation isnt there. youre making a scene because of nothing ¯\_(ツ)_/¯.