Author
Topic: Whore Master Editor 0.7.1 (Read 154806 times)

Here's another new version. This one has basic support for editing config.xml, it's not much butit may help some. Currently there's no error checking so you can enterrubbish instead of required values (which you could also do withregular text editor anyway) so be careful what you enter. I suppose thegame will crash if you enter "gfde" instead of "43" or "0.75" ,and also, it may crash if you enter something as "1,0" instead of "1.0"(or better said, I'm pretty sure using , instead of . will not bringanything good). In boxes where values are percentages (they have (%))try to refrain yourself and enter only values from 0 to 100, I don'tknow what will happen if you enter value larger than 100. Asbefore, when you overwrite existing file bak will be created. But ifyou messed that one already you can just press reset button and savethat. Those are (should be) default values.

Here's the girl I did some time ago converted in new format using the editor (actually, writing her data manually in notepad was what motivated me to make this app). It/she was posted on first reincarnation of the forum. It's no one "famous", just something I rendered for this, so in that sense it's original .

- added "Small Weapon item type- removed ability to save as old items/girls/rgirls files, they don't support this and previous change anyway so there wasn't much sense to keep them any more

v0.67

- added new field to items tab, GirlBuyChance, it works (will work) as described here, it should only be used with XML format- added some new fields to game config tab

v0.66

- added preliminary support for editing config.xml, based on 1.29.4.6 config.xml

v0.64

- fixed PCHate crash when clicking on an item that has it, this only happened with items saved to XML format, if you have XML file load it in this version, it'll check if there's an item with this problem and tell you if it need fixing. To fix it just resave the file, it'll fix it automatically.

- I also added drag and drop support. Now you can just drop files into program window and it'll load them and switch to corresponding tab. You can drop one or more files, it'll load all of them, even of different types. Only "drawback" is that it'll switch to the tab of last file it reads (i.e. if you drop 2 girls(x) and 1 rgirls(x), chances are rgirls(x) will be processed last so editor will switch to that tab when it finishes)

v0.63

- fixed blank line between entries when adding or updating them and saving them in old format

v0.62

- fixed another typo, this time in "Pregnant by player" string, I think this will be the last fix on item tab, I don't think I updated any of the other strings so they should be OK all over the code

v0.61

- fixed small (well, at least as bugfixing goes) issue with some traits being screwed up while adding to the list or updating that The Alpacalypse noticed. Only 0.6 was affected by this, no need to worry that 0.55 and down messed something up. This was because an oversight, while adding XML support I corrected few typos in names of these strings (libido, agility, controlled) but I missed few occurrences of them so there was a little discrepancy there.

- fixed bug when overwriting existing files, now it should get saved in every case, also, when overwriting existing file it will now add .bak extension to old file before saving a new one, just in case

v0.54

- added ability to filter girls on girls tab by their type (normal, slave, from catacombs), should work fine, but it needs to be tested little more thoroughly before trying to implement similar feature for other tabs- swapped places of delete selected entry and clear list buttons on all tabs. I think it's safer to have delete selected button next to save, if you press it accidentally you'll loose just one entry, which you can add easy anyway since it's data will be displayed, but if you press clear list accidentally it's all gone

v0.53

- girls, random girls and items in their list are now alphabetically sorted

Would it be feasible to add a sorting function to the lists in the editor? For example, sort the girls list alphabetically, by age, by Constitution, by normal/slave/catacombs status, etc. The same would be nice for items, though I think it is less of an issue there.

Logged

Capitalization is the difference between "I had to help my uncle Jack off a horse" and "I had to help my uncle jack off a horse."

Possible yes, feasible so-so. Alphabetical sorting is rather easy, but would probably require change of some concepts, so list entries would remain in sync with girl data that is stored DataTable. As it is now when entry is added to list (only name is added to list) it's added at the same time to DataTable. So when you click on an entry it gets it's index and calls the item from DataTable that's under the same index. It's simple, but it works. If I sort lists that stores items and girls these index' wouldn't be in sync. There would need to be either some other memory object that would link indexes from the list to the ones in DataTable or DataTable would need to be sorted at the same time so they remain in sync. Or sort just DataTable and fill list entries from that... Hmm, that's perhaps the best solution and would require least meddling in the code, if I can figure out how exactly to do it.

As far as rest of sorting goes that would definitely require rewrite of major code behind this tool. And personally I don't see the point in it. There's no practical reason to be able to sort them by these stats. Most of them are anyway from some more or less famous anime toons/games so that really doesn't do anything. It's not that girl A will affect girl B if her stat A is higher/lower than stat A girl B has. Or interactions like that.

Alphabetical sort would help to deal with names that are used twice, but for the rest I don't see the point.

Alphabetical sort is easy, I just tried it and it's easy to implement.

Other types would require more work. Adding just one more way (like normal/slave/catacombs you mention) can be made easy (I just got an idea) to do via the same method as alphabetical. Although it wouldn't be very nice solution from "good code" stand of view . My biggest problem is how to allow users to select what sorting method to use.

Updated with version 0.53, this one sorts lists automatically when you load an existing file, if you resave it output will also be alphabetically sorted.

Other potential sortings won't be so so quickly done, I'll need to rework code to do it. Although I still think it won't be that useful . Only one case where it will be is sorting items by category, consumable, clothing, weapon...

As an alternative to sorting by girl or item type, what if you just filtered them into different lists? All slave girls go in one list box, all normals go in another. Consumable items in one, weapons in another. Maybe use a drop box that allows you to select all entries, or those in a single category.

Logged

Capitalization is the difference between "I had to help my uncle Jack off a horse" and "I had to help my uncle jack off a horse."

Well, doing that would require same thing as "normal" sorting as I would still need to get into data for each entry to read required value the same way as normal sort would do. Sorting now works on source data, data is read into table, that table is sorted per some key (at the moment name) and then list is updated with this sorted table. Doing different lists would require complete re haul of this as this concept wouldn't work, plus it would be pretty much harder to keep list and table data in sync. Now it's rather easy, simply after sorting that table list gets rebuild so i.e. entry 5 on the list corresponds to entry 5 in the table. If list doesn't have the same number of entries as table this doesn't work.

New version with filtering of girls by their type is upped, so far it's only for regular girls to see if concept works before I apply it to random girls and items.

I used drop menu as you suggested, having separate listbox' for every type would need a redesign of the app interface so I think this is better solution. One idea that came to my mind after it was done is about save button. At the moment, when you press it, app will automatically switch to "All" list (if it isn't already) and then do as it did so far. I could make it ask the user if he want's to save whole list, or just currently selected one. But I'm not sure if that's really an useful feature.

Having the option to save the currently displayed type in a separate file would be interesting, but I don't know if anyone would use it. I consider myself to be a bit of an organizational freak at times, but only in a fit of OCD would I find it necessary to save girls of different types into different files.

Then again, I don't think it would hurt to have it, if for no more reason than someone might forget they are working on a subset of the characters and accidentally save the whole set when they intended to save only the subset.

Logged

Capitalization is the difference between "I had to help my uncle Jack off a horse" and "I had to help my uncle jack off a horse."

Found a bug in the items section: when you load an item list, delete something off the list, and save to the same file, the deleted item is saved along with everything else. If you save to a new file, the deleted item is properly removed.

« Last Edit: November 09, 2009, 03:36:21 PM by zodiac44 »

Logged

Capitalization is the difference between "I had to help my uncle Jack off a horse" and "I had to help my uncle jack off a horse."