Board Thread:Wiki Discussion/@comment-3492791-20141017020334/@comment-26127993-20141021211254

a lot of work? well.. yes and no. its basically copy paste change the gif adress. Tbh I done far worse in the past, and I know I am not the only one with some free time in between when work is slow. So .. i would be more then happy to go through and do it if you think the work is the problem. Just you know.. tell me how the code should look ^^ as i know little about that.

If you make it so that all gifs open at once then you are using pointless bandwitth when someone is only interested in say miss kellogs blast as that is the only thing that is dangerous for instance so that is the one most players would be interested in, and if they have low bandwith they probably dont want to see all the other ones they dont have problem with.

I mean.. uff.. sometimes I have not speaking this language as my native one.. updating the code is a one time thing. sure it is a lot of things to do that one time but then it is done, so I don't think saying it is a lot of work is a valid defense against not doing the best way (whichever way is decided is the best way, not saying my suggestion is). What really is the big problem here.. is it bandwith then we should pick the option that uses the least bandwith. even if that is a bit more work. In my oppinion anyway.

My idea gives people information without the gifs, and if they want more info they can click the one gif they are interested in. And it likely wont be all of them, lets face it a simple stab attack is unlikely to be the one people have trouble with. (I do love that there is a gif of every attack though dont get me wrong). But giving some info that is just text can beenough for some.. oh.. yeah. it is parryable.. cool off to practise.. then.. hmm wait.. which attack is this.. *click watch gif* oh yeah.

if you have all info on an attack hidden someone MUST load the gif if they for instance just wants to know if an attack is parryable. sure it might be less coding work.. but.. again.. the code is a one time thing. ok i rambled enough but I hope my bad english was enough to get my idea across.