# How can I ensure that a plugin's settings are not lost after updating a plugin?

**URL:** <https://iplug2.discourse.group/t/how-can-i-ensure-that-a-plugins-settings-are-not-lost-after-updating-a-plugin/844>\
**Category:** Uncategorized\
**Created:** [15 December 2023 00:05 UTC](https://iplug2.discourse.group/t/how-can-i-ensure-that-a-plugins-settings-are-not-lost-after-updating-a-plugin/844 "2023-12-15T00:05:59Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kallyn](https://avatars.discourse-cdn.com/v4/letter/k/848f3c/32.png) [@Kallyn](https://iplug2.discourse.group/u/Kallyn)\
**Post date:** [15 December 2023 00:05 UTC](https://iplug2.discourse.group/t/how-can-i-ensure-that-a-plugins-settings-are-not-lost-after-updating-a-plugin/844/1 "2023-12-15T00:05:59Z")

</div>

Hello!  
My worst fear with plugins in general is losing information when downloading a new version. I want to make a plugin like an effect rack, where new effects could be added in the future. I am creating Effects as structs derived from a base Effect class, and adding definitions for their constructor and process() functions in the plugin.cpp file. If I update the plugin with new effects, how does that work with users updating to a newer version? Is there a way to avoid losing that information if an update is installed?