If you\u2019re managing digital training, you\u2019re looking for both pedagogical efficiency and a smooth user experience. The VTS Editor Reset Block<\/strong> meets both goals: it restarts an interaction \u201cas new\u201d without affecting the rest of your scenario. You offer learners a clean second chance, enable iterative practice, and keep your graph readable. For training managers and HR teams, it\u2019s a direct lever for remediation and learner progress tracking\u2014while preserving reporting integrity (VTS Perform<\/a>, SCORM). For instructional designers, this means more trial and error on quizzes, drag & drop, matching, or sentence choices, without losing the adaptive logic of the path. New to VTS Editor? Full introduction here: VTS Editor<\/a>.<\/p>\n For designers looking to improve replayability without duplicating blocks, training managers looking to better manage attempts and remediation in blended or fully digital courses, and serious game creators who want to let learners explore different options without \u00ab\u00a0polluting\u00a0\u00bb the state.<\/p>\n The Reset Block restores the block it is directly connected to back to its initial state, as if it were being executed for the first time. No configuration. No parameters. It doesn’t affect variables, flags, global score, or progression. It only \u201ccleans\u201d the internal history of the targeted block: a Counter resets to zero, a Quiz shows all options again (if \u201cHide previous choices\u201d was active), a Drag & Drop clears placements, a Matching block releases its links, a Sentence Choice resets selections. You create a clean second chance without any side effects on your scenario logic.<\/p>\n The local reset acts like a \u201cclean & replay\u201d button applied to the next block in the sequence: no multiple outputs and no modified contextual data. Place it just before the interaction to replay, and trigger it when a learner clicks \u201cTry Again,\u201d returns from a remediation section, or when you want controlled iterations (e.g., via a Sequence or Counter). You keep the context (variables, flags, score) untouched, so adaptive paths stay active, and you avoid duplicating blocks.<\/p>\n The local reset targets a single block with a safe, predictable effect. In contrast, the global reset via Use local reset for training, trial-and-error sessions, and remediation. Examples: a salesperson replays an objection via Sentence Choice; a technician repositions components in a Drag & Drop; a manager retries a feedback scenario. Avoid it in summative\/certification evaluations where attempts must be locked, or in sequences where the historic path is itself the pedagogical signal (e.g., to keep a record of a wrong answer for debriefing).<\/p>\n Local reset supports spaced repetition and retrieval-based learning\u2014two proven learning strategies that significantly boost retention. See for instance the synthesis on distributed practice (Cepeda et al., 2006<\/a>) and the importance of memory retrieval (Karpicke & Roediger, 2008<\/a>). Giving learners a \u201cclean second chance\u201d reduces cognitive load and frustration. From a production standpoint, your graphs remain clear, with fewer duplications and shorter update cycles. For deployment and tracking, see VTS Perform<\/a>.<\/p>\n Typical use in compliance\/safety: allow two attempts before showing support. On the third error, route the user to a Remediation Slideshow, then return to the same activity with a clean slate by placing a local reset just before the Counter. Notify the learner of remaining attempts, reward persistence with a Badge, and track indicators (average number of attempts, success rate after remediation) in your LMS or VTS Perform<\/a>.<\/p>\n In onboarding, a quick quiz may hide previously tried options thanks to \u201cHide previous choices.\u201d To offer a fair second chance, trigger a local reset before sending the learner back to the same quiz. Make the rule clear (\u201cNew attempt: all options reappear\u201d) and, if needed, turn off local scoring to avoid inflating the global score. Use a separate Score block to keep tracking performance.<\/p>\n In sales, customer service or management, offer structured exploration. After an initial exchange, offer \u201cReplay scene\u201d that passes through a local reset and returns to the Sentence Choice block. Flags and scores remain intact\u2014use them to adapt the character\u2019s behavior the second time (e.g., more patience after a show of empathy, greater strictness after a risky choice). This results in a dynamic and progressive simulation.<\/p>\n In process training (quality, production, IT), learners frequently classify or match elements. A \u201cRestart\u201d button leads to the reset block \u2192 Drag & Drop (or Matching). In case of repeated mistakes, branch to an explanatory Slideshow or open a resource, then return cleanly to the activity. Alternate between guidance and practice until mastery is achieved.<\/p>\n In exploratory scenarios (safety, onboarding, showroom), it\u2019s useful to \u201creset\u201d the interface to repeat an action or review a point. Place the reset just before the Clickable Zones block. Reinforce the educational intent: a Sound reveals the new clue, a Gaze draws attention, a Media block updates the display. Add a Countdown to simulate time pressure: when the timer ends, route through a local reset for structured replay.<\/p>\n In an adaptive module, allow learners to repeat a step while preserving your progression rules (flags, Score Check thresholds). Place the reset only before the targeted activity. The learner redoes just that component; the overall logic remains consistent. You can display conditional feedback and offer retries without compromising tracking indicators.<\/p>\n In tests and demos, the local reset speeds things up: add a \u201cDemo\/QA\u201d Menu visible during preview, enabling quick navigation to key sections and clean replays of critical interactions. Add Notes to document your reset points and save time in validation cycles. To discover more real-world use cases, browse our client cases<\/a>.<\/p>\n Place the Reset Block immediately before the activity to replay. Typical flow: the learner clicks \u201cTry Again\u201d (button, area, choice), the graph goes through the reset, then replays the activity. All within the same scene, with the same variables intact; only the activity\u2019s state is cleaned.<\/p>\n The local reset doesn\u2019t alter data on its own: it gives you freedom to structure practice. Track key indicators: post-reset success rate vs. first attempts, average attempts per activity, time spent before\/after introducing resets, dropout rate, clicks on \u201cTry Again.\u201d Use this to adjust difficulty, clarity of instructions, or countdown durations. For full tracking of skills and analytics, explore VTS Perform<\/a>.<\/p>\n To go deeper into error-based learning approaches, see Metcalfe, 2017<\/a> (academic synthesis).<\/p>\n Target 2 or 3 activities where offering a clean second chance would make a difference (Quiz, Sentence Choice, Drag & Drop). Add a \u201cTry Again\u201d choice that routes through a local reset before the activity, measure the impact in your LMS or VTS Perform<\/a>, then adjust accordingly. To try out the software suite for free, request a 30-day trial: Try Virtual Training Suite<\/a>. And for a complete overview of the authoring tool\u2019s capabilities, check out the VTS Editor<\/a> page, as well as our client cases<\/a> for inspiration.<\/p>\n","protected":false},"excerpt":{"rendered":" Why the Reset Block in VTS Editor Is a Game-Changer for Your E\u2011Learning Modules If you\u2019re managing digital training, you\u2019re looking for both pedagogical efficiency and a smooth user experience. The VTS Editor Reset Block meets both goals: it restarts an interaction \u201cas new\u201d without affecting the rest of your scenario. You offer learners a clean second chance, enable iterative…<\/p>\n","protected":false},"author":12,"featured_media":6456,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1035],"tags":[963],"class_list":["post-6455","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vts-editor-en","tag-vts-editor-blocks"],"_elementor_source_image_hash":null,"_wp_attachment_image_alt":null,"_thumbnail_id":"6456","_yoast_wpseo_twitter-description":null,"_yoast_wpseo_twitter-title":null,"_yoast_wpseo_twitter-image":null,"_product_image_gallery":null,"_yoast_wpseo_focuskw":"Reset VTS Editor Block","_yoast_wpseo_title":"Boost Your Modules with the Reset Block in VTS Editor (Complete Guide)","_yoast_wpseo_metadesc":"Boost your e-learning modules with the Reset block in VTS Editor: replayability, smooth UX, and active learning without complicating your scenarios.","yoast_head":"\nWho This Article Is For<\/h3>\n
What You\u2019ll Learn<\/h3>\n
\n
Reset Block in VTS Editor: Simple Definition<\/h2>\n
How It Works, Key Differences, and Pedagogical Benefits<\/h2>\n
How It Actually Works<\/h3>\n
Local Reset vs.
resetAllBlocks<\/code> (Global Reset)<\/h3>\nresetAllBlocks<\/code> resets every block. Useful in testing\u2014not so much in production: it could break certain technical mechanics (auxiliary counters, timers, branches) or create unexpected state regressions. Potential outcome: a scene that \u201cforgets\u201d everything and confusing reporting. In production, prefer targeted resets.<\/p>\nWhen to Use It\u2026 and When Not To<\/h3>\n
Why It\u2019s Good for Learning and UX<\/h3>\n
7 Use Cases to Boost Engagement with the VTS Editor Reset Block<\/h2>\n
Restarting a Counter to Manage Attempts<\/h3>\n
Redisplaying All Quiz Options for a True Second Chance<\/h3>\n
Replaying Sentence Choice in Conversational Practice<\/h3>\n
Resetting Drag & Drop and Matching to Return to a Clean Slate<\/h3>\n
Reactivating Exploration Zones (Clickable Areas \/ Interactive Decor)<\/h3>\n
Adaptive Path: Repeat Without Biasing the Evaluation<\/h3>\n
Faster QA and Client Demos<\/h3>\n
Tutorial: How to Configure and Integrate the Reset Block in Your Graphs<\/h2>\n
Where to Place the Block and How to Sequence<\/h3>\n
Reusable Patterns (Proven Templates)<\/h3>\n
\n
Common Mistakes to Avoid<\/h3>\n
\n
Measuring Impact with LMS (SCORM) and VTS Perform<\/h3>\n
Quick Deployment Checklist<\/h3>\n
\n
Take Action<\/h2>\n