For both official and other firmwares i request an option to “lock” the saved/creted/emulated dynamic code remotes so that the file doesn’t change with each press/send and the code sent is the same and not a dynamic creation / calculation of the next code.
Example, on a keeloq emulated remote one would “lock” the file so that pressing send would re-send the same hopping code instead of creating the next one.
Another option/version of this would be to have 2 options when using an emulated rolling code command, one with “send” that we already have and one with “send the same” or “re-send” that would just send the SAME code (replay atack) instead of creating/generating/calculating the next code.
This would be of use to test dynamic code systems to see if re-sending old codes would work, to test for example if denial of service is possible and to prevent saved files captured from systems to change when a new send action is done.