So this only works for the runs you have AFTER subscribing to the mod?

I plan to update the main post with these instructions, and to add a few new features to bring it up to speed for Repentance (Supporting tainted characters, quality-based item logging, etc).

Note that because this is a brand new save.dat, it will not include the seeds from your pre-Repentance seed log. The OG log should still be located in its original directory. If for some reason you care about keeping seeds from AB+, then back up the old log, or paste it to the bottom of the Repentance log.

We're back in business, lads. Happy seed planting :)

Great news! Turns out Seed Planter has worked with Repentance all along! They changed the location of the save#.dat files, which was why I thought it wasn't working. Took me way too long to figure that out.

By default (if installed on the C drive) your save1.dat file should be located in:
C:\Program Files (x86)\Steam\steamapps\common\The Binding of Isaac Rebirth\data\seed planter

@Birb Hed I think Repentance broke it :(

I've been busy with work, but I'll look into fixing it over the long weekend.

does this work for repentance?

Update 1.7's out! The main change here is that the defunct "Date" has been replaced with "Length". It's not quite as useful, but hopefully it'll help you identify which run is which.

In addition, I finished refactoring the code. The program is now FAR more organized than it was in 1.0, so any feature updates should be relatively painless.

Speaking of which, ideas for new feature suggestions are always appreciated. This is the last major update I've planned for the program, though I have been toying with the idea of adding tracking support for custom items and stages. I don't know if I'll ever get around to that, but it's on the table.

Until next time!

very nice

Update 1.5 is live! The biggest new feature is vastly improved performance: The mod now operates near instantaneously even with over 40,000 seeds in the log!

I also cleaned up the log page a bit and made a lot of under-the-hood improvements that should make it easier for me to update in the future. This update should be backwards compatible with your old logs, so you don't have to do anything different. I did change a LOT in this version, so please feel free let me know if you experience any bugs.

On a sadder note, it looks like I'll have to be retiring the date/time functionality. I looked really hard for a solution but as of now, the API just doesn't allow for it. I do plan on replacing it with something a little useful though. Maybe I can even implement a way for advanced users to reactivate the date tracking themselves. We'll see ;)

Stay tuned for more updates!

I just learned that a function that I thought was available for ordinary users isn't, and it was only working for me because I had the "--luadebug" launch option set. BIG whoops.

As a consequence, nobody's logs have been working properly. I'm sorry for any inconvenience this might've caused. I just pushed an update that temporarily disables date/time, which should let the mod start working for now. I may have to disable that functionality permanently, if I can't find a way to implement it without the 'os' library.

Awesome man. I hope it turns out well for you in the end.

@DrinkSomeMilk That was originally what I was planning to do, but as it turns out the actual size of the log file has, as far as I can tell, zero impact on the performance. I tested it with like 300k lines of text, well beyond the number of seeds any user would be able to normally generate, and it still worked instantly.

The performance issues seem to stem from JSON4Lua, an encoding utility bundled with Isaac that I'm using to load data structures to and from the text file. *That* slows to a crawl when encoding/decoding large files. But I can just choose to only decode the relevant, recent data. That should have very little impact on performance, but unfortunately requires me to redesign how the mod saves and loads the data. It's a little tricky for me but I'm making progress.

@Pesudogenesis A way you could fix that is by making to that when you hit 250+ Runs the mod will delete the very 1st run. You could also make it so the mod would have a extra document so you could add your saved runs. The mod would not delete or add anything to this document.

+1

I'll probably be releasing an under-the-hood update sometime in the next few days that improves performance. The mod is currently inefficient when it comes to very large log files - over 250 runs logged, for example. This fix should address that issue and make it run smooth as butter with any size of log file.

Thanks, and you're welcome!

thank you for making this.

@Pseudogenesis

gj! nice idea and work

idk

Though if you're really that worried about screwing something up, the only guaranteed way of avoiding that is not to use the mod. It's up to you I guess.

Oh you don't have to worry too much about that with this mod. All you'll ever have to do is open the log file and read it.

At worst, if you change something that ends up messing up the log file, you can always delete the save.dat file and the mod will start building the log from scratch again. But as long as you don't change something in the log and save it, you're good!

I always mess up my files with other stuff in it so i try to stay away from stuff that has to do stuff in the files because im afraid that ill f*** something up

@Joecool6406 Sorry, but I'll need more information than that to help you. What did you need help with?

i suck at using the files

ohhello

What do you mean, @Joecool6406?

i may have a hard time working this

This sounds cool.