Implemented data logger plugin

[touchtouch105]

Implemented plugin to log a ton of player data and events to a local .csv file.
What config looks like:

example csv output:

[runelite-github-app]

New plugin data-logger: https://github.com/touchtouch105/DataLogger/tree/3f92cd2075d5f2fdab3fd3ed51e077d907c809cf

[runelite-github-app]

This plugin requires a review from a Plugin Hub maintainer. The reviewer will request any additional changes if needed.

---

Internal use only: Reviewer details Maintainer details

[raiyni]

There exists a plugin that logs CSV data csvexport

[touchtouch105]

There exists a plugin that logs CSV data csvexport
That plugin logs every data point that can reasonably be queried every tick, not really equivalent

[tylerwgrass]

If you wanted a smaller subset you could PR/suggest that the existing plugin has config options to toggle different info from being saved.
To me this seems more useful than a separate plugin with the random subset of fields you have picked.

[touchtouch105]

If you wanted a smaller subset you could PR/suggest that the existing plugin has config options to toggle different info from being saved. To me this seems more useful than a separate plugin with the random subset of fields you have picked.

The existing plugin is both broken and not currently being supported as per the issue tickets that have been open for 5 months
That plugin is also not event driven so the amount of data it generates is not suitable for long term logging.

[tylerwgrass]

I would not assume that it is broken or unsupported just from the issues, granted I haven't used the plugin.
It is still preferred to contribute to existing plugins instead of creating new ones that practically do the same thing as multiple identical plugins.
If it is unmaintained, that is the purpose of the Plugin Takeover Policy.

[touchtouch105]

I would not assume that it is broken or unsupported just from the issues, granted I haven't used the plugin. It is still preferred to contribute to existing plugins instead of creating new ones that practically do the same thing as multiple identical plugins. If it is unmaintained, that is the purpose of the Plugin Takeover Policy.

Was basing it off i downloaded it and one of the two features isnt populatable, which has had an outstanding issue against it for 5 months.

These really are two separate plugins though, completely different use cases, the only thing they have in common is writing data to csv files which a lot of plugins do. I can go through the motions of a plugin takeover request if that is the desired action.