What do you have as your current information in : currentSpecialBountyItem ? (ie what does typing "get currentSpecialBountyItem" on the CLI result in ?
New Content - Implemented Bounty Hunter Change
- Thread starter Darzil
- Start date
What do you have as your current information in : currentSpecialBountyItem ? (ie what does typing "get currentSpecialBountyItem" on the CLI result in ?
Any chance we could have a to_bounty(string) function so that we can actually do get_property("currentEasyBountyItem").to_bounty() or something similar?
r13581
Any more experienced devs feel like pointing me in the direction of where to start for this one?
Ensiferum
Member
No idea as I completed them manually, but testing with another account last night proved that it was definitely related to the special bounties from Psychoses jars.
However, all seems to be working fine now so thanks for figuring it out.
$bountys[] already works (without any extra work being done). I wouldn't even know where to begin with making $bounties[] work the same, but I doubt that any implementation would make the current one stop working, so it should be safe to use in scripts.
Not that I think we should worry about coding for it now, but I now expect Jick to give us a reason to add a $cookie[] data type eventually.
Bale
Minion
I'd like to request that you add another field to $bounty[]. location, please! It is nice to know the monster, but getting a location from the name of a monster, while not impossible, is kinda unwieldy. It would be quire helpful if the location was simply provided along with the rest of the bounty info.
TIA!
TIA!
What would you want to be in that location? If you mean the location given on the bounty hunter page, that is sometimes a container rather than an adventuring location (eg Hidden City). I guess just the location that AdventureDatabase holds (which is the first location it comes across containing that monster, rather than necessarily the best)?
Bale
Minion
If it is more than 1 location that has the monster, I think the best would be best. Unless there is a reason you'd prefer the first?
The first is just what the old code does. I might code the location into the datafile, as that is easier, especially with things like non-combats that can result in a fight with the monster.
Theraze
Active member
It's kind of odd, but any chance we could replicate KoLs own names for the bounty types? They use low, high, and special, rather than the visible easy, hard, and special, for the html/action codes. If we use those as our names, we could use ("action=take"+bounty.type) to take bounties, and ("action=giveup_"+substring(bounty.type, 0, 3)) for dropping bounties. We could make ourselves functions to convert those over, but there don't really seem to be any great reasons for the current types besides that it's the visible.
