Chewett

Other reports of this occurring?

race condition, repeat it again to win a gold coin or filed away as not a bug for now, just bad coding that needs to be fixed "soon"

not a bug

Old accounts can break sometimes when big changes occur, not a bug for now

Doing something in the scene is movement of some kind, Im going to close this as not a bug for now :)

This is a new feature that hasnt been properly tested, Not fixing until I work on this at a later date. Beware for bugs.

Therefore not a bug :P

Not a bug your end, something server'y breaking, will look into, thanks for reporting

resolved as not a bug

Ann. 3040 - [2014-06-17 02:15:40 - Stage 12] Posted By Chewett Spells randomactionp and randomluck have now been fixed.

Ann. 3040 - [2014-06-17 02:15:40 - Stage 12] Posted By Chewett Spells randomactionp and randomluck have now been fixed.

silvertongue mostly fixed, silvertongue proper fix added to "later" list Slave auction going ahead

Ann. 3038 - [2014-06-17 01:28:41 - Stage 12] Posted By Chewett Silvertongue should work Silvertongue was broken after a number of unicode changes and server upgrades. All this means is that the spell wouldn't work at all for the majority of the characters. Iv spent over an hour debugging unicode issues and the result is we need some bigger database/script changes because PHP is horrible. Silvertongue has been changed over so that it all works, previously it entirely broke. I have planned the changes I need to make for it to work like it used to, but it needs some work and I am not coding new "features" to make it work with the new server software and such. Needless to say its going to be done, soon, but I'm not wasting more time on it now. ----- file may be utf-16 DB handler changes -> utf-16 Db changes File input changes possibly utf json to html entities

I and most probably council agree with this viewpoint. When was the last time a King came to be to request a power, a tool, anything? The answer is never. They have been given the power to run a land, request things, and iv literally seen none of them come to (ab)use this power. Come with me with a request for coding and a reason, if the reason if good then you can have it.

post/send it so I can read it.

Added: Fix Silvertongue - Its broken, fix it, need to restore from backup, blarge And a load of other stuff

Those that dont want to be a slave at this new rate can cancel their participation in the auction freely now.

I like this topic, people should reply.

Perhaps I should instate this into MD? :P

I pay attention to when matches are on because my favourite pub has happy hour to celebrate all the football watchers are in different pubs (They dont show football in the pub since its a nerdy awesome place, If you are in Southampton visit the Hobbit Pub :D)

No. Its still being discussed, there is a large document for us implementing it but that might change and is top secret at the moment.

Whats the world cup?

I now need to do stuff at GoE, so we have moved back to GoE lol

I replied to this as a new topic for discussion. See: http://magicduel.invisionzone.com/topic/15495-how-md-evolves/

Concepts? Models? Plans? Ha! How is development organised? - It isnt, not until recently. During the early days, Mur had a number of core features he code and such. things like combat, messages and such. Features that were tested by the beta testers before you could register and play normally. This was planned and such. Then before we had additional coders in the game Mur just worked on a general plan and moved forward with it. Sometimes items would be left, sometimes unfinished or broken, but he would work on something else. Little plans were written but Mur kept an idea of what he wanted to do. Over the past years Mur experienced a number of computer related issues and some plans that were made originally have been lost. In addition as Mur is spending less time in MD now, he has to rely on others to remind him of his plans, and has given others reign to create and move MD forward. He is consulted on general concept ideas, and then lets others implement the finer details. Example: AUTUMN2050 has a general plan for how it is going to work however the finer details of where to place items and such have been left up to us. These plans are written down since Mur is working with a couple of us, and we demanded (yes, how rude of us!) that we need written plans of whats going to happen before we could work on it. You need to remember that Mur is, first and foremost, a creative and not a programmer. He finds ways to express what he wants to do programatically and doesn't necessarily follow the normal procedures and design patterns. Much of codebase is archaic and not structured as well as it could be which then makes adding more code trickier. When Rendril was let onto the team he did a lot of work rewriting the combat system so that it was easier to modify, he also wrote a lot of unit tests to ensure that its working correctly. However it was primarily a rebase of how the old code worked, meaning that while it was massively changed for the better it did not function too differently. As I work on sections of the game I spend extra time converting older code to a newer and easier to manage format. Since January much of this has been in the form of database changes and optimisations. Boring stuff for you guys because you dont see a difference since "It looks the same" but massive changes under the hood. The idea is that making the database work better (aka like it should have been designed if it were planned and had not evolved) shouldn't change anything as far as you see. Its not just that Mur is not an experienced programmer for he is very qualified now, Its that the game has evolved over 9+ years and some of the code back from the very start still exists. As an example, only until last year we had two different ways to log yourself out. One of them would work and one wouldnt. Both were used in the code and by pressing a different button it would fail to log you out properly. This is because the two pages were written at different times and the older one was not changed to use the new system and therefore broke. This is common for older systems but since there was only one person working on it, he could keep in mind how everything worked. This pattern of generally coding what people feel like and whatever you want still exists, but now whenever I and Dude2 work on code we have plans, document things and ensure that code is left in a better state than it originally started in. This does make things slower, but makes it easier to add things next time. Recently a "coder manual" was started by myself and provides some information to Dude2 and Murry to ensure that they know how to do things "right". So, for anything old there are no plans, but anything new will have a lot more structure. We are aware of the issues but any software project has these, and are resolving to put measures in place to improve the situation. Further Questions?