it depends on what you are trying to revert, and how far back it goes:
-if you are trying to revert changes that have been saved (File->Save/Save All or Ctrl+S) then your only real option is source control
-if you are trying to revert something that was changed in the editor without hitting save regardless of auto save is to just exit the editor. The auto save exists only as a fallback in case the editor crashes (these are work in progress programs and things can go wrong). by default the auto save will not overwrite what is saved to the disk (in the content drawer) the auto-saves exist in the “/Saved” directory.
–on exiting the editor will ask if you want to save the things that have not been committed to disk, and each item can be unchecked as you see fit. after that dialog box has been cleared if no errors occurred during saving what you did want to save then the Editor will exit and anything not saved will be lost.
-in the event of an editor crash anything that is in the Saved directory will first be attempted to be re-applied to the editor, but if the editor cannot do so a recovery screen will appear telling you if you want to try to recover something.
even though most guides, tutorials, and so on will tell you to “always save and compile” after every change. the save is not always necessary as the Play button will use what has been compiled most recently for each thing, not what is saved to disk.
disabling auto-save is a very poor work around as if you are not great at saving your work periodically yourself (and if you are trying to have a functional revert point you probably are not saving periodically) any given crash could lose you everything you have done since you last launched the editor.
disabling auto-save could have viability if you are doing something that you know will crash, and could corrupt your project, or you are potentially hitting storage space ceilings, but otherwise it exists as a QoL especially for those that are not saving periodically.