Surly wrote:Personally, I'm not sure that is true. Or at least not true in the way it should be. Generally (and this applies only to larger or more recent changes) feedback is sought after the event. The best example is the white links. There was a massive outcry against that... if that thread had been posted before it was implemented, the outcry would have been noted, and a problem avoided. It should be noted that the more vocal forum members do not represent every single player... if there are many complaints, then maybe, just maybe, the fault lies with the programming not with the players?
The Programming Department can't ask for suggestions on any topic before the implementation. Some are just too trivial to ask permission for (e.g. white links - nobody could have anticipated it would be this controversial) while others are supposed to be hidden from the players, at least at the beginning. I think the main problem is lack of communication between the players and the Programming Department - I mean serious, constructive criticism and suggestions, not whining, on the part of the players and information about what changes are supposed to be good for on the part of the department.
The fact that there was that belief when it was implemented... does that not indicate the lack of communication that Naeelix was talking about? I don't think it was 100% thought through, as my short essay explains, and I think that's the problem. I would much rather that prog didn't have to work through the night... that extra time was taken, and the small things (like a back button on the clothes main page) were implemented rather than flawed major changes.
No lack of communication there. Deterioration and repairing was created and implemented by the same programmer.
At the moment big things take priority over small things, because big things can make a lot of difference to a lot of people and create more equality in game. Besides, small things such as additional back buttons are left for the programmers in training to do, who get a feeling for Cantr code that way.
Meh. Did that... but I never got the chance to make an impact before I was kicked off for a, admittedly rather serious, mistake I made. Which made no impact on my job as a staff member. And I was not given a single chance to defend myself... so something is wrong somewhere...
Breaking the Capital Rule can mean you lose the privilege to play Cantr, not just your staff position. Because of the possibilities of abuse that a staff position can entail, staff members are held to an even higher moral code than simple players. It's also a question of trust: how can you trust somebody to work for the good of the game with one hand if he's seriously disrupting it with the other? When your application was discussed, we were all convinced that you were past cheating, otherwise you wouldn't have been accepted in the first place.
Neelix wrote:I may have been a bit blunt with things, but I feel very frustrated with the game and have a feeling there is something fundamentally wrong that I cannot change.
I'm sorry to hear that, Neelix. Trust me there is not. I still think the best way for you to see that would be to join the staff and get an idea of how people work and how Cantr works. That would give you a much better understanding of what is going on, why some things happen etc.
I mentioned the use of a shadow Cantr last night and he said something along the lines that it used to be there, but wasn't anymore.
There still is a testing environment, but it has been changed somewhat to protect it against abuse.
My main gripe is that a lot of changes are being added and end up badly, because people don't seem to want to fix bugs or change the way the system works now, so that it works better and may in the end become easier to maintain.
All bugs reported on Flyspray are getting fixed. Some of them very quickly. Some bugs are fixed before they get reported. The system also gets optimised. You obviously can't see when code is optimised, but you could for example notice that tiredness was adjusted a lot of times, because the initial calculations didn't work out as they should.
And about data loss: you have a very different view on that then.
"Data" is not lost on my computer, ever. If something makes data go away inadvertently, I will make very sure that that program is kicked off of my computer for ever.
I'm not talking about programs doing this on purpose. It's just a side effect of usage called corruption. When you open a file, change something and save it, or just copy it, and do that hundreds of times, there will eventually be flaws in the copy that come from the file not being saved 100% correctly. Perhaps a byte on your HD refused to be adjusted. Perhaps the reader jumped over a byte of the original file. That kind of thing. Usually it isn't noticeable until your HD software tells you that there are inaccessible sectors that can no longer be worked with. The same thing happens, on a much larger level, to the Cantr database. There are tables that are accessed and changed millions of times per day, for example the locations table. Finally it corrupts and can no longer be accessed - that's when you get that SQL error message. If some script tries to change something in there while it is inaccessible, that data gets lost and you'll e. g. have ships that stay in the vortex even what the table has been repaired. It's nobody's fault.
As for me volunteering: I'd love too, if I had the time to do it right. I only want to do things if I can do them right and that would just take too much of my time, which I don't have.
If you're looking for an advisor, then perhaps I could do that.
Everybody volunteers as much time as he can. Particularly Programming Department members often wind up spending more time than they expected when signing up, that's why I reacted a bit sharply.
Frankly I don't see how you could advise on matters of implementation, programming style, staff communication or the like without knowing how the system works at the moment. It's more complex and well-thought out than you appear to think at the moment. Your suggestions on what could be added or changed to make Cantr a better playing experience are welcome though.
I hope that you don't leave Cantr forever. Considering that all things you mentioned are either not as you think or are being fixed, there really isn't any reason for leaving.
Judith