[Aliese]

Originally Posted by Maximvs

This is why I score them a 6.5... they do tend to be giving out more - but these areas should be addressed by now or in very short order.



Before I comment on this one - I agree that many of these were fun I'm also gonna leave Hex out of it for a sec and just go with everything else...

Its funny that the things broken that we enjoyed we call 'glitches' and the things we don't like 'bugs'... but in reality - they are all broken, and need to be fixed. True, its too bad they seem focused on the fixing on the 'harmless' breaks (or what we see has harmless as we have no true idea on what the code is doing to the stability of POTCO) and not addressing the more 'harmful' breaks...

But in the end - its all broken and would need to be fixed. Pirates were never -really- supposed to fly off ships (I think they would call that witchcraft back then LOL ). I know this was a favorite of yours (just a Hex was a favorite of mine - coming up) - but I think its focus was to stop SvS issues - and not directly against us It is a broken issue - it got fixed, lets hope they continue to work on the other issues you've listed.

Okay, I admit - I'm greedy. I don't care if something was intentional or not - if it's fun, don't take it out. Work on it and make it a legit feature, but don't take it out. The flying glitch was a massive happy accident IMO, and considering the TPing (come on, pirates go swirling up into the sky! LoL) and Voodoo usage, they could have explained it and made it work. Have it be a special skill that's unlocked with a quest...something. Just let me fly.

Now for my Hex...

I'm probably the BIGGEST poster here on Hex (if not the biggest - then the most whiny haha! ). I've posted more than once that then fixing Hex was wrong... I've sent in several detailed reports asking them not to fix it... I've logged more than a couple of Blogs of it Here in my profile... but - there is more to it...

I knew Hex was broken. I knew it would have to be fixed one day. Having creatures totally useless allowing me to just beat away at them I knew was not going to last forever. I wouldn't like it if the NPC's could hex me and I could never fight back and just die...

My messages to them were not to fix Hex - UNTIL they had a viable working bullet that allowed an enemy to be 'stunned' for a period of time and if they did revive - allow me to Hex them again.

Though they have done it backwards (took it away before putting in the real method)... on test now the Hex shot is doing just that (abit - its too short at 10 seconds and need to be increased - but it works - we can always push for more now that the code is right)

Changes never come fast enough when we want them - but I have to think change does come (and sometimes we don't want change - but it arrives anyway Thats why since Hex has been changed I've been working on new methods of obtaining my goals - the change (as with many others) have made me try different methods to accomplish the goal

Now - if they just increase it to 20 seconds...

Well, I have the same attitude about hex eater as the "fun" glitches, because I loved it the way it was. The problem was with how they described it - instead of just draining Voodoo, it should have said drained and disabled (period). Yeah, it's unfair and unrealistic and all that, but it's a Disney game. It was easy, and I liked it that way.

It sounds like they're going in the right direction now, but really - how are nades going to work with even 20 seconds? I'll be spending all my time re-disabling each one in the group...

Originally Posted by Sven Niscadae

I'm going to chime in on the money cap of 65k from a programming aspect. 65k is a magic number in programming. It seems to me that Disney used an integer data type to define "gold". An integer's upper limit is 65k (actually 65,535). Why did they pick an integer data type is probably because the most expensive thing you can buy in the game is the War Frigate for 60,000 gold.

So why not make the upper limit higher? The next integral data type available is a long integer that has an upper limit of about 4 million (4,294,967,295). Sure you could set the cap somewhere within that variable but there would be some wasted memory. Even if you don't use the maximum, an application reserves the maximum memory the data type allows for the variable (e.g. int = 32 bits, longint = 64 bits). It's a best practice to use the smallest data type per your application's needs.

Even if they decided one day to change the data type of "gold" to a long integer, they would have to go through the code, find every routine that uses "gold", and verify there will not be any sorts of conflicts between the different data types. I don't know how their code is structured but I'm sure the very idea would make them cringe at least just a little bit.

I can understand why they made the gold limit. I can understand some pirates are a bit miffed at gold falling to the bottom of the ocean because they've reached the cap. But even if you had the gold, what are you going to do with it?

Okay. I'm done with my programming theory lesson today.

Ah, now it makes more sense! However, they could maybe add money "pouches" without changing the data type, right?