[X] My Assistant

Hm, it might be better to round profs at some point. From time to time I can see gain of like 0.0n000000000005, or 0.0n99999999999 points, what is obviously not quite true...

Hm, it might be better to round profs at some point. From time to time I can see gain of like 0.0n000000000005, or 0.0n99999999999 points, what is obviously not quite true...

Replicated this bug and fixed it.

However, we seem to have created a new bug with all the additions, which seems to be related to caching and the cookie.

Bad Request

Your browser sent a request that this server could not understand.
Size of a request header field exceeds server limit.

Cookie: Apache=/error code stuff/

I have to go in and delete the cookie to get past. The strange thing is I've had enormous item and equipment arrays before and I never had this issue.

Edit:
I've attached the beta version (it has a different name and cookie so it won't overwrite anything and it also uses my personal highlight colors). DOWNLOAD ONLY IF YOU WANT TO HELP DEBUG, USE AT YOUR OWN RISK. (Attachment temporarily removed for further testing)

This post has been edited by cmal: Sep 25 2009, 03:05

I'm really happy to see the developments on Battle Buddy! Lots of good ideas here.

One thing regarding cookies, is that it is sent to the server (from your browser) on every request. Which is why we must be smart about what to put in there.

You've already noticed that there's a max header size, so you'll have to shrink the cookie down.

Suggestions:
- store only raw data, never computed data
- don't track every piece of equipment/drop
- use short variable names (ie. _cache.eq instead of _cache.equipmentName), saves a little bit of space

Just some thoughts. Keep up the hacking!

I figured as much, I'll be going through and abbreviating some variable names and double-checking to make sure only raw data is getting stored.

The Script is great, Thaks.

I've abbreviated as many of the new (added in the Enhanced version) variables as possible and the header is still getting too large after a couple rounds. The only thing left is to change the way the kill score is recorded from independent vars to an array, which will probably save a little more space. Other than that, the number of things BBE is tracking may have to be cut, like being more selective about the drop lists. So feedback plz.

Time display bug has been fixed. Thinking about whether a custom title could be added considering the space problems its already having.

Interestingly enough, I do not encounter a single problem with my custom BBE... What heavy stuff did you add in the new wip? Or I just don't grind that deep?

As weight reducing, maybe Profs as array as well? And, maybe there is shorter var type?
And If everything else fails, kill the kill count. It weights a ton, as I perceive, and does not that important.

And there is also an option of praying to Snowflake Tenboro for bigger header size limit...

This post has been edited by hen_Z: Sep 25 2009, 23:07

I was testing the new beta version (has prof and proc tracking) with a brand new cookie ub arena challenges and it error'd out after the first few. If you want to test it out, I can post it.

Right now, I'm considering merging the arena and drop tabs. The reward stats go on top and the actual items are folded into the normal drop array, which should free up a bit more space.

But what I'm really wanting is for people to give feedback on what they think is important as a feature and what they could live without. For me, I really don't care about the specifics of the item (non-artifact and non-equip) drops. I just want to know how many in total and a general idea of what all is dropping. I do care about specifics on the more valuable items like Godlies, Elixirs, Scrolls, and Infusions. Maybe condensing the drop list to generalized categories and valuable items.

If you want to test it out, I can post it.

That would be nice

Same disclaimers as before: This is a beta and has known issues. It can fuck your shit up, so use at your own risk. If you get the cache error, you have to disable the script and delete its cookie before you can browse HV again. Don't download it unless you want to help test it.

Removed because of release.

This post has been edited by cmal: Sep 28 2009, 21:20

Unless this was suggested already, maybe you could add a tab with all the items/equipments that were found, including a reset button just like the "Stats" tab. The items found tab would have a list of all the items that were found and the quantity of each item, and as well as every piece of equipments that were found.

Also, +rep.

Unless this was suggested already, maybe you could add a tab with all the items/equipments that were found, including a reset button just like the "Stats" tab. The items found tab would have a list of all the items that were found and the quantity of each item, and as well as every piece of equipments that were found.

Also, +rep.

You mean like this:
(IMG:[gannonman.com] http://gannonman.com/image/bbeitems_766024448.jpg)
(rest button not pictured)

Of course, now we're running into the problem of catastrophic cookie bloat due to all the stuff we've added.

Haha. Just like that.

If a cookie bloat is an issue, then please make a tab only for equipment drops (without including the item drops). If you also take out the statistics and focus entirely on an equipment drop list, there shouldn't be a problem.

Well, the long-term stats logging really are the core of Battle Buddy v2. But splitting the item logging off into a separate cookie might not be a bad idea if its possible/feasible. Or even a whole new, separate script so it doesn't have to compete with the main script and people can optionally use it.

Come on, folks, throw those ideas out there, tell us what you want. This is a community effort.

cmal, doesn't you find it weird that beta script you posted always shows 0 prof gains?
If you do, then, for goodness's sake, delete

CODE

            } else if (content.match(/you gain/i)) {
                if (isHighlight) node.css("color", "#ba9e1c");

lines!

Aside from that, yet to encounter any errors. Lets see how it will handle the cakefest next...

This post has been edited by hen_Z: Sep 26 2009, 19:11

I noticed that since I was changing things around to try to lighten the cookie.

Also noticed that there might be some sort of bug with the v1 stable. I know it picked up artifacts (picked up a Small Nuke right before release) and Tokens (picked up at least two), but I just picked up 3 Tokens and a BFG and it didn't register. I'm not sure what the reason is. Either I messed up the capture code somewhere or the number of elements in an array is limited (I've been running without a clear for almost three days, so my item list is pretty long now).

I really hate double-posting, but I need to make a new post so people know there's new info.

Header overflow issue:
So I tried shoving the item arrays into its own cookie to lighten the main cookie -- no good. Still got the header error. Tried sticking the item list into its own script -- mostly successful except for the part where I was overwriting the main script's Stats tab and I couldn't figure out why. Unless someone else wants to do this, I'm going to give it up. Which means you folks need to tell us what you want to do about this.

Other news:
Domino Strikes does not have a proc message -- it just happens. I switched to a 2H to test prof tracking and I Domino'd a couple of times but its not a proc like Overwhelming Strikes. So a question for stick users, is there a message in the battle log whenever Coalesced Mana procs? I'm assuming there is, but I wanna make sure. Nevermind, I just checked it myself.

This post has been edited by cmal: Sep 27 2009, 05:55

(IMG:[i36.tinypic.com] http://i36.tinypic.com/s49f82.jpg)
25 4 Blue Hedgehog hits you for 20 crushing damage.
25 3 Bleeding Wound hits Blue Hedgehog for 48 damage.
25 2 Your attack procs the effect Bleeding Wound on Blue Hedgehog.
25 1 You hit Blue Hedgehog for 100 slashing damage.
24 5 Blue Hedgehog hits you for 17 crushing damage.
24 4 Bleeding Wound hits Blue Hedgehog for 48 damage.
24 3 Your attack procs the effect Bleeding Wound on Blue Hedgehog.
24 2 Your offhand hits Blue Hedgehog for 57 slashing damage.
24 1 You hit Blue Hedgehog for 87 slashing damage.
23 2 You dodge the attack from Blue Hedgehog.
23 1 You hit Blue Hedgehog for 90 slashing damage.
22 3 You evade the attack from Blue Hedgehog.
22 2 Blue Hedgehog uses Spin Attack
22 1 You hit Blue Hedgehog for 84 slashing damage.
21 2 Blue Hedgehog hits you for 21 crushing damage.
21 1 Blue Hedgehog dodges your attack.
20 4 Blue Hedgehog hits you for 13 crushing damage.
20 3 Effect Bleeding Wound on Blue Hedgehog has expired.
20 2 Bleeding Wound hits Blue Hedgehog for 48 damage.
20 1 Blue Hedgehog dodges your attack.
19 5 Spin Attack hits you for 40 crushing damage.
19 4 Blue Hedgehog uses Spin Attack
19 3 Bleeding Wound hits Blue Hedgehog for 48 damage.
19 2 Blue Hedgehog has been roused from its sleep.
19 1 You hit Blue Hedgehog for 86 slashing damage.
18 4 Blue Hedgehog is asleep.
18 3 Bleeding Wound hits Blue Hedgehog for 48 damage.
18 2 Your attack procs the effect Bleeding Wound on Blue Hedgehog.
18 1 You crit Blue Hedgehog for 157 slashing damage.
17 3 Blue Hedgehog is asleep.
17 2 Weaken procs the effect Weakened on Blue Hedgehog.
17 1 You cast Weaken.
16 2 Shield procs the effect Shield on yourself.
16 1 You cast Shield.
...
0 6 Spawned Monster E: MID=14 (Blue Hedgehog) LV=37 HP=904 MP=22 SP=2 NA=93 Type=hostile

It seems that there has been an error in the calculations, I actually did it 901 damage and it shows as if it was 904 as you can see in the picture. Dunno if it can be fixed or not just thought I'd share this with you~

This post has been edited by Ido013: Sep 28 2009, 06:39

I've seen that a couple of times before, as well. Taking a look at the code for that, the HP displayed is actually based on the HP bar and scaling the monster's max HP based on how much of the bar image has been decreased. It doesn't actually count the damage that is being done and calculating by subtraction. So there will occasionally be small errors like this. I don't have any ideas right now to improve the accuracy, so I can't guarantee anything for BBE but gillian might do something about it.

Another update on BBE:
I converted the monster tracker into an array and got it working. Testing for header overflow now, but its looking good (an array takes up much less space since there's only one variable). If all is well, it should be ready for release in the next day or two.

I STLL cannot make that header overflow, using earlier beta. Looks like you slay FAR more monsters than I do...

This post has been edited by hen_Z: Sep 28 2009, 13:24