txrangersxx
Member
Suggestion making it configurable to make them at all.
Thanks!that's a very interesting script !
No, because the only way to get the turn to look for a semi-rare is to eat or drink something with relatively low adventure yield. Personally, I use semirares in-run, but am not interested in them in aftercore.semi-rare
Perhaps. I am planning on adding a (configurable) monster to olfact. That's because I am curious about building in support for the Icy Peak, and there is one obvious best monster there. There is also a reasonable choice in the Hidden Office Building - and in Barf Mountain, for that matter. If I do that, then there is a reasonable choice for digitizing/arrowing. If not, not so clear.digitizing/arrowing
Same comment, but I expect not.copiers (can of rain doh, chateau, etc)
I expect not.yellow ray
Interesting idea, which would induce me to learn more about the topic.free kills (shattering punch, jokester's gun, replica bat-oomerang, etc )
Probably not, since spending turns with a less-optimal farming familiar seems less desirable (to me) than getting items which are worth less in the mall (for either buying or selling) then my expected Meat yield."easy" to get familiars drops
I recommend you make the changes yourself. I expect you'll have fun.(I'm not asking you to do it, it's just to know what I should try to add to your script myself)
And I learned something new. I have found six so far.Perhaps even the solid gold jewel. I'm conflicted because, although are very valuable, they are (or used to be) rare, since they were Spelunky leaderboard rewards. But since Mr. Screege's spectacles, I've found quite a few of them...
item [int] clip_art = define_property( "VMF.ClipArt", "item", "", "list" ).to_list_of_item();
item [int] clip_art = define_property( "VMF.ClipArt", "item", "", "bucket of wine|bucket of wine|bucket of wine" ).to_list_of_item();
item [int] clip_art = define_property( "VMF.ClipArt", "item", "bucket of wine|bucket of wine|bucket of wine", "list" ).to_list_of_item();
// define_property( PROPERTY, TYPE, DEFAULT )
//
// Both DEFAULT and a property VALUE will be normalized
// You can edit the default here in the script and it will apply to all
// characters which do not override it.
//
// define_property( PROPERTY, TYPE, DEFAULT )
// define_property( PROPERTY, TYPE, DEFAULT, COLLECTION )
// define_property( PROPERTY, TYPE, DEFAULT, COLLECTION, DELIMITER )
//
// Otherwise, you can change the value for specific characters in the gCLI:
//
// set PROPERTY=VALUE
//
// Both DEFAULT and a property VALUE will be normalized