It has been a rough week for WorldWeaver. I have put so much work into it. And I DO have a working client for it. - I just don't like it. There is so much I dod wrong, and am doing better with the next iteration. But it is having some issues.
Maddening issues.
I have spent every night dealing with bugs that seem to make no sense. Case in point:
I am loading Attributes, and an Attribute can have a Type property set to 'attribute', and its value can point to the Attribute who's value it should use.
So you could define the Player template with a max_life Attribute, set to 25. Then you can define a life Attribute as type=attribute, and a value={player}:max_life.
So you could define the Player template with a max_life Attribute, set to 25. Then you can define a life Attribute as type=attribute, and a value={player}:max_life.
This would set the Player's life to the max_life value (25).
In loading the Attributes I noticed only two Attributes were actually getting loaded, even though the ResultSet had seven records in it. I commented out everything in the ResultSet read loop, then I did seven iterations. I put everything back one by one. It broke when I re-added the assigning of the Type property. Type is just a String that is being set to a value. It's wrapped in a try/catch - but wasn't throwing an error. Yet there it was - seven iterstions without, two with.
What the actual heck?!
After a lot of desk-to-head collisions, and nearly ditching the project, I discovered that a later method call was the culprit. But even after tweaking that to avoid issues there I'm still only getting two iterations. Even if I bypass it altogether when the type is blank (Only one Attribute has a type) I still only get two iterations.
We'll see how many times I decide to scrap the project tonight, before I change my mind and keep pressing on.
No comments:
Post a Comment