Settitle files not updating Badge Count?

[Derek Icelord]

I recently decided to delete and reverify a character's badges on CIT. I used the bind files from Titan, and tried the ones from Badge-Hunter.com. Neither settitle file will update my CIT badge count past 464 badges, but selecting the badges manually will. I'm using HeroStats 5.4.0.0 (with all the latest updates). I've run through the entire settitle sequence on both bind sets.

[eabrace]

In every Issue, the settitles seem to get shuffled around.  We haven't updated the settitle numbers in the database yet, so when you generate the settitle bind files, it's going to give you a lot of incorrect settitle numbers.  At least I know that's true for the script that generates the bind files here.  I assume that's true for Badge-Hunter as well and they haven't updated settitle IDs for the badges yet either.

If you look for one of the badges that didn't verify in the checklist and see what its settitle should be, try manually entering  the settitle command.  If the badge you're looking for isn't selected as your new title, that's what's going on.

This can be worked around by going into the bind files and tweaking them manually.  For example, assuming you generated binds for all badges, open 1.txt.  You should see this:

t "settitle 2$$settitle 5$$settitle 6$$settitle 7$$settitle 8$$settitle 9$$settitle 10$$settitle 11$$settitle 12$$settitle 13$$bindloadfile "C:\binds\settitle\2.txt""

Notice that if any badges are now assigned a settitle of 1, 3, or 4, they won't be hit by the bind file.

You can change that file to read as follows:

t "settitle 1$$settitle 2$$settitle 3$$settitle 4$$settitle 5$$settitle 6$$settitle 7$$settitle 8$$settitle 9$$settitle 10$$bindloadfile "C:\binds\settitle\2.txt""

Similarly, if you change 2.txt to call for settitle codes 11-20, 3.txt to call for 21-30, etc, you should start picking up the badges that were missed the first time around.

I know.  It's tedious.  It's still a little better than clicking each badge, though.

I don't think you'll find any badges exist beyond settitle 1600 right now, so at least you know where you can stop.

The easiest way to handle this if you have any experience with just about any programming or scripting language is to write a quick routine to automatically generate the files for you.

I honestly wish I had a better answer, but at the moment, that's the best I think we've got.

(I'd be overjoyed if someone proves me wrong.)

[TonyV]

I'm in the process of doing a pretty massive database update.  It will probably take a few more days.  Honestly, if you want to avoid a lot of work, I would suggest waiting until I post another update before doing the /settitle bind thing.  We really are really close to having all of the Issue 18 updates done.  It's been a pain, because we're not just updating the new badges, but going back and enabling tons of old badges to be "dual-homed," that is, available to heroes AND villains, that were designated as one-side-only badges before.

Before Issue 19 is released, I'm working on implementing an auto-update feature that will avoid having to go through all of this work again.  :)

[Defcon Kid]

Before Issue 19 is released, I'm working on implementing an auto-update feature that will avoid having to go through all of this work again.  :)

Cool!  8) 8)