Planning your chars LP gain

[erozaxx]

I have played a bit with the curious and the set based on 16 slots to plan ahead chars development based on the actual time, I can log-in to change curious. I dont have all the necessary data of course, so there is also link for the excelsheet and feel free to amend yourselves.
If someone would be able to turn this to a webbased calculator it would be awesome - I could prolly do it too, but I am really short of time currently and also would need to refresh my php skills for that (what I really dont have time for currently).

Suggestions in separate thread, we don't want to hijack this thread.

Plans for particular times based on easy to obtain curious (e.g. foraged with midlvl per*exp cca 30*30).
Just an info: Empress and Queen are surely not THAT hard to obtain, but still I am leaving them out of easy to obtain ones. Its based on luck I did not want to have luck too much involved in it.

http://muaddib.cz/curio/haven_curious_fastpace.html
http://muaddib.cz/curio/haven_curious_hourly.html
http://muaddib.cz/curio/haven_curious_weekplan.html

Source xlsx (rename the suffix when downloaded).
http://muaddib.cz/curio/haven_curious.xlsx

[pyrale]

It could be interesting to add a quality entry, because every curio isn't equal when it comes to raising quality.
It could also be interesting to optimize given material constraints, or to optimize the ressources needed to reach a given LP objective.

I'll try to make a simplex spreadsheet for that later on.

[erozaxx]

I have an enhanced calculator in head, but need a time to refresh php skills.
The idea is:
INPUT> your att limit, base q of your curios + ability to modify it per curio, how often you are able to login/renew
OUTPUT> sorted list from best to worst with the three suggestions based on 1st best item set, 2nd best item set leaving out rare items, 3rd best item set using only craftables + all the information (LP gain, time/att need and such)

[Sevenless]

Mmm, for less work you can do something similar using the wiki tables. There's four factors on curiosity usefulness assuming you're willing to log on any time of the day to do this.

http://ringofbrodgar.com/wiki/Curiosity_Table I just use this

Availability, LP/Hr, LP/Hr/Attention, Study size.

Availability is the obvious one. If you can't have it, you can't use it.

After that though. at <100 int you're going to want to maximize the LP/HR/Attention.

With excess int, but still not filling the screen further, pay attention to LP/Hr alone.

And finally, when you have as much int as you need and have lots of curios available, paying attention to LP/Hr/Study size will become important.

[erozaxx]

actually if you check my table 70 att is enough to stop paying attention to att/lp/time and you can start focus on time/lp only

[pyrale]

Actually, there are more than one things you may want to optimize.

-Ressource use optimization given desired LP gain
-LP gain optimization given curio availlability
-LP gain optimization given ressource cost
-...

[erozaxx]

Maybe checkboxes next to curiosities. Where you can toggle, which to involve into calculation and which to leave out?

[MagicManICT]

I was thinking of something like this that could plug into one of the custom clients. It would check and see what curios you have in the inventory and tell you what would be best to use.

[erozaxx]

sound interesting but that is for someone else, I dont do java... ME NO LIKE JAVA

[Mashadar]

I'm currently working on pretty much the same thing. It allows you to list all your curiosities with their respective qualities, the timeframe you will be available to equip new curiosities and it'll use that to generate a plan of what you should equip (or unquip) at a given time (and in which slot).
It's GUI-based, but I suppose I could do a web-based version too. I was thinking about integrating it into the client at a later point, so you don't have to manually keep track of which curiosities you have.
I've been using a similar inventory system to keep track of all my items in W4, but it still has some quirks that need to be worked out (such as items being counted twice if someone else adds or removes something from a container).