Choosing a Fire Season Response Path That Starts With a Digital Sandbox

You've read the job description. Heard the stories. Maybe you've even watched a few YouTube clips of fire crews digging line or helicopters dropping buckets. But the first real choice — which response path to pursue — still feels like a blindfolded dart throw. Hand crew? Engine module? Helitack? Dispatch? Each branch has its own culture, physical demands, and pace. And once you commit, switching isn't always easy.

So what if you could try before you buy? That's the promise of a digital sandbox: a virtual environment where you can simulate fire response roles, test your instincts, and see where your natural strengths fit — without the heat, smoke, or consequences. This article is a field guide for anyone weighing fire season options and wondering if a simulation-based start could save them time, money, and regret.

Where a Digital Sandbox Shows Up in Real Fire Work

The Tabletop That Catches Fire

I walked into a state forestry training room two years ago and saw a whiteboard covered in sticky notes—each one a simulated engine, a dozer, a single resource. That was their sandbox. Paper maps, dry-erase markers, three radios crackling on a table. The exercise? A lightning bust in the Siskiyous with 14 new starts in two hours. The crew boss ran the clock, and every fifteen minutes someone had to re-draw fire perimeters based on spot-weather updates. It worked—mostly. But the seams showed: nobody could practice the radio workflow without stepping on actual transmissions, and resource ordering turned into a mess of scribbled notes nobody could read afterward. That's where a digital sandbox stops being a gimmick and starts being the tool. It gives you the same pressure—compressed time, incomplete intel, screaming radios—but with a log you can rewind. You don't just debrief what happened; you scrub back to the moment the order got garbled and ask: what did we actually hear?

Agencies Already Inside the Simulation

NIFC runs digital sims for their S-520 advanced fire behavior course—has for years. State forestry departments in Oregon and California now require contractor training programs to complete at least two sandbox sessions before a crew can mobilize on a Type 2 IA contract. What breaks first? Usually the resource ordering interface. The odd part is—that's exactly the seam that bleeds time on a real incident. I have seen a dispatcher freeze during a simulation because the digital form wouldn't accept her shorthand; ten seconds lost, and the next engine got routed wrong. That pain is valuable—it surfaces a procedural hole before it costs a real helispot. Contractor programs use these to weed out teams that can't handle the digital layer, and they're right to. The catch is that not every agency has the budget to run a full-immersion sim. Some still rely on tabletop exercises for the bulk of their training, then drop into a digital sandbox only for the final evaluation. That split approach works—until the tabletop group never touches the software and shows up lost on day one of fire season.

Day-to-Day Tasks You Can Practically Grind

Map reading isn't a lecture skill—it's a muscle. A digital sandbox lets you drop a lat/long pair into a tablet, zoom to the correct 7.5-minute quad, and mark the ridge where the spot fire sits. Do that twenty times in a session, and your thumb learns the gesture. Radio comms? Same. You key up, transmit a size-up using the ICS-209 format, and the sim logs your transmission latency. Too slow? The digital dispatcher (a real person behind the curtain) moves on. You learn to talk faster without mumbling. Resource ordering gets its own grind: type in the overhead request, select the correct agency code, confirm the ETArrival. Wrong code? The system rejects it—just like the real ordering portal does. That's not a video game. A video game rewards you with points. A sandbox rewards you with a cleared order that doesn't get kicked back. The trade-off is boredom—you'll repeat the same order five times until it sticks. Most teams skip that repetition. They shouldn't.

What a Sandbox Is Not

A digital sandbox is not a flight simulator for fire. You won't feel the heat or smell the smoke. What you do get is friction—the exact bureaucratic friction that stalls a real incident: radio traffic overlapping, a resource that's marked available but isn't, a weather update that invalidates your entire containment line. That friction is the training. The sim doesn't care if you're stressed; it just enforces the workflow until you either adapt or crash. I've seen a Type 3 IC crash his sandbox twice because he kept skipping the spot-weather request step. Third time, he finally embedded it into his mental checklist. That's the win.

“Simulation won't teach you how to fight fire. It will teach you how to manage the system that fights fire—and that system is where most operations actually break.”

— retired NIFC training officer, interviewed during a 2023 annual refresher

The pitfall is treating the sandbox like a game you can beat. You can't. The scenario resets, the variables shift, and the system will always find a seam you didn't patch. That's the point. Your next experiment: pull the radio logs from your last real incident, build a ten-minute sandbox scenario around the worst five minutes of radio traffic, and run it with your crew. See who can decode the order without asking for a repeat. That's not theory—that's Thursday.

Common Misconceptions About Simulation-Based Training

Myth: simulations teach bad habits because they're not real

The worry makes sense on paper—fake dirt, fake fire, fake consequences. Surely you'd pick up sloppy reflexes that get someone hurt on a real line. I have watched that exact fear keep experienced Rangers out of the sandbox for years. Here's what actually happens: a good simulation doesn't let you cheat physics or ignore safety. The bad habits people worry about? They come from poorly designed exercises, not from the medium itself. A sandbox that punishes you for skipping a communication check or misreading wind direction—that reinforces real discipline. The catch is fidelity traps. Teams load a simulation with hyper-realistic tree species and flame lengths, then forget to build in the subtle human cues—radio chatter lag, fatigue, ambiguous orders—that actually kill decisions in the field. That's not a sandbox problem. That's a design problem.

What usually breaks first in a simulation isn't the fire behavior model. It's the decision loop. You stare at a screen and think I have time, then the clock runs out. Wrong order. Not yet. That hurts—and that's the point. The real gap isn't realism of the smoke; it's whether the simulation makes you practice the same high-stakes trade-offs you'd face at 2 a.m. on a roadless ridge.

Myth: you need to be tech-savvy to benefit

This one gets thrown around a lot, usually by people who've watched someone fumble with a joystick for thirty seconds and called it a waste. I get it. But the assumption conflates interface skill with operational judgment. The best sandbox user I ever worked with was a sixty-two-year-old squad boss who couldn't navigate a smartphone without swearing. He crushed every scenario because he knew where to anchor a line and when to pull people off a slope. The simulation software was just the table he put his experience on. Most teams skip this: treat the first session as a UI orientation, not a fire exercise. Let people break the controls, ask dumb questions, reset three times. After fifteen minutes the tech layer disappears. What's left is the problem. If your organization skips that warm-up, you'll confuse tool frustration with tactical failure—and walk away convinced the sandbox is the wrong move.

The real cost here is lost talent. People who would shine in a decision-heavy environment never get past the login screen. A short, low-stakes onboarding—not a manual, not a lecture—fixes that.

Myth: sandboxes are only for beginners

Oddly persistent. You see this in teams that slot new hires into simulation weeks but leave veteran crews running paper maps in the corner. That's backward. Beginners need the basics—safety zones, escape routes, communication protocols. Veterans need the messy stuff: resource constraints, conflicting objectives, political pressure from an IC who wants a different outcome. A sandbox lets you run the thirty-year veteran through a scenario where the only good decision is also the unpopular one. That's not beginner content. That's leadership pressure-testing under zero physical risk. I have seen experienced squad bosses walk out of a simulation visibly shaken—not because the fire was dangerous, but because the decision stack exposed a blind spot they'd carried for a decade. Beginners can't learn that lesson yet. They're still learning which end of the hose is which.

Honestly — most forest posts skip this.

'The simulation didn't teach me how to fight fire. It taught me how to think about fighting fire—and that was the part I'd stopped practicing.'

— Type 2 IC, after a scenario that forced a no-go call on a burn that looked good on paper

So the sandbox works in reverse of the stereotype: it's the experienced crew that gets the most uncomfortable return on time invested. Beginners get confidence. Veterans get humility. Both are valuable. The mistake is assuming only one group needs the practice.

Patterns That Actually Work When Choosing a Path

Start with your comfort zone: dispatch or logistics first

Every fire season I have watched new Rangers assume they need to chase the most intense operational role — engine boss, hotshot crew, helicopter manager. That rush usually backfires. The smartest path I have seen people take starts where they already feel competent: dispatch or logistics. These roles let you interact with the digital sandbox without the pressure of a twenty-person crew staring at you. You learn the terrain, the resource ordering rhythm, the radio discipline — all inside the simulation. Then you pivot. The catch is that people who skip this step often wash out because the sensory overload of a full incident command post drowns their decision-making before they build any muscle memory. Start boring, then expand.

Use sandbox data to identify strengths: speed, accuracy, communication

The simulation logs don't lie. After three or four exercises you will have hard numbers on how fast you placed resources, how accurately you read the fire behavior model, how many radio calls you missed. Most teams skip this: they run the scenario, debrief vaguely, and move on. Don't. Pull the timestamp data. I once worked with a Ranger who thought they were a tactical genius — the sandbox showed they were just fast at clicking, but their communication score was bottom quartile. That hurt. But it redirected them toward a planning role where speed matters less and coordination matters more. The numbers tell you where you actually belong, not where you wish you belonged.

Cross-train virtually before committing to a physical crew

You can test five different roles in a single afternoon inside the sandbox. Try division supervisor for one module. Then switch to air operations. Then try safety officer. The simulation lets you fail cheap — no real helicopter, no real fireline, no real consequence except a bruised ego. That sounds fine until you realize most people never do it. They pick one track based on rumor or peer pressure and lock in for a whole season. Wrong order. Cross-training virtually exposes the mismatch between what a role sounds like and what it actually demands. A logistics officer told me the sandbox showed her the constant multitasking of air support — she swapped to supply chain management and thrived. The simulation gave her the honest preview.

I spent two years on a hand crew before I understood I was better at predicting where the fire would go than swinging a tool. The sandbox showed me in three hours.

— former crew lead turned fire behavior analyst, personal conversation

Success stories: a dispatcher who found their niche via simulation

One of the cleanest examples I have seen involved a dispatcher who cycled through four different sandbox roles over two weeks. She started in dispatch — fine, okay. Then she tried planning: hated it, said it felt like staring at spreadsheets while the world burned. Then she tried operations: too much noise, too many voices. She almost quit the pathway entirely. On a whim she ran the logistics module — resource tracking, supply ordering, base camp setup. She finished the scenario with a perfect resource allocation record and zero radio errors. That was her spot. She built an entire career trajectory from that one sandbox session. The pattern here is simple: you don't find your path by thinking about it. You find it by running the simulation, checking the data, and letting the results embarrass or confirm your assumptions. Then you adjust. Then you run again.

Anti-Patterns and Why Teams Revert to Old Ways

Over-relying on sims and ignoring physical fitness

The sandbox feels real. You run a perfect ignition sequence, watch the fire edge curl exactly where the model predicted, and your spread rate chart looks like a textbook. That feeling is dangerous—because it tricks you into thinking the simulation is the job. I have watched crews spend eight hours in a digital environment tweaking wind vectors, only to fail a pack test the next morning. The sim doesn't sweat. It doesn't cramp at mile five. When the real fire calls, your body doesn't care how clean your digital firing order was. The trade-off is brutal: time spent polishing a perfect simulated burn is time you didn't spend carrying a hose pack up a ridge. Most teams that revert to old ways do so because they got humbled by the physical reality of the fireline, not because the sim was bad. The sandbox is a tool, not a substitute for lungs and legs.

Treating the sandbox as a one-time test rather than a practice tool

Wrong order. Some crews run a single simulation at the start of the season, declare it done, and then wonder why the tool gathers dust by July. That's like taking one archery lesson and expecting to hit a bullseye in December. The catch is—simulations decay faster than physical skills. A fire behavior model you ran in April won't reflect the fuel moisture in August. I have seen squads treat the digital sandbox like a certification check: pass once, move on. What usually breaks first is the habit loop. You skip a session, then another, and by the time August hits, no one remembers how to load the scenario. The teams that stick with digital tools don't treat them as a test. They run short, ugly, imperfect sessions—ten minutes before a briefing, a quick "what if" during lunch. Fragments of practice. That consistency beats one heroic four-hour session every time.

Ignoring human factors: team dynamics can't be simulated fully

The sandbox models fire spread. It doesn't model the crewmember who stops talking under stress, or the IC who freezes when two squads call for resources at the same moment. That's the dirty secret: you can run a flawless digital operation and still fail on a real fire because of communication breakdowns. The sim gives you clean data—perfect radio discipline, no fatigue, no personality clashes. Real fire gives you a tired sawyer who misheard the anchor point call. One crew I worked with ran complex digital exercises all spring, then collapsed on their first live burn because nobody had practiced listening through the noise. The sandbox can expose decision-making gaps, but it can't replicate the human friction that kills operations. Ignore that, and you'll blame the tool when the real problem was sitting in the crew truck next to you.

'We ran the digital scenario six times. Everyone made the right call. Then on the actual fire, three people froze and nobody said a word for four minutes.'

— former squad boss, after a near-miss on a timber burn, describing why his team stopped using sims for a full season

Why some crews ditch digital tools after a season

It usually isn't because the software failed. It's because the sandbox became a chore. A tool that requires login credentials, a specific laptop, and forty minutes of setup before you can run a fifteen-minute scenario will die. The odd part is—crews that ditch the digital path often replace it with nothing. They slide back to "we know the ground" intuition, which works until it doesn't. That hurts. The anti-pattern here is treating the sandbox as a permanent fixture rather than something you must actively maintain. If the tool doesn't fit into the rhythm of a fire camp—quick, dirty, accessible—it gets left behind. Not because it was wrong, but because it asked for too much attention. Keep it simple. Keep it fast. Or watch the digital sandbox become a digital shelf.

Reality check: name the conservation owner or stop.

Maintenance, Drift, and Long-Term Costs of Digital Sandboxes

Software updates and subscription fees

The sandbox doesn't stay still. I have watched teams build a solid digital practice in March, only to find the platform restructured by June — new menus, retired features, a billing tier that now charges per user instead of flat-rate. That sounds fine until the annual renewal hits your station's budget line you forgot existed. Subscription creep is real: one tool at $30/month feels cheap; three tools plus a cloud storage add-on plus the map-data license pushes past $150/month before you've run a single drill. Most crews skip this calculation. They see the free trial, build momentum, then hit the paywall mid-season when morale is already fragile.

Skill erosion between seasons: how often to run drills

The gap between fire seasons is where digital sandboxes rot. You spend October through February maintaining quals, doing PT, maybe teaching — but the simulation muscle atrophies faster than you'd guess. I have seen a crew that crushed their April sandbox scenarios show up in July unable to navigate a basic interface change. The catch is that running drills monthly feels wasteful when there's no active fire. But skip three months and you're effectively starting over. The odd part is — the digital terrain shifts beneath you even if you don't, so that perfect workflow from last August may now throw errors or load slowly on updated browsers.

• Monthly 20-minute refreshers beat quarterly two-hour slogs
• Pair sandbox drills with real gear checks to justify the time
• Track login frequency, not hours logged — consistency matters more

Hardware requirements: laptop vs. mobile, internet access

Not every sandbox runs on a five-year-old government laptop. That's the pitfall most individuals miss when they pick a path based on slick demo videos. Mobile-first sims look great on a new iPhone, but try running them on a tablet with spotty cell coverage at a trailhead. The screen real estate shrinks, touch controls misfire, and suddenly the tool you chose for portability becomes a frustration generator. Wrong order: teams often buy the software before checking whether their field hardware can handle it. What usually breaks first is the rendering engine — complex fire-behavior models lag on integrated graphics, and then people blame the tool instead of the mismatch.

Organizational buy-in: getting your crew or agency to adopt

The loneliest sandbox is the one you maintain by yourself. I have watched a motivated individual build a beautiful digital practice only to have their captain shrug and say "we don't do that here." The long-term cost isn't just the subscription — it's the friction of being the only person on your crew who understands the simulation workflow.

'We bought the license, trained three people, and then the season hit. Nobody touched it again for eight months. The renewal felt like a bad joke.'

— crew lead, Type 2 IA hand crew, following a season with zero simulation use

Getting buy-in means showing how the sandbox saves real time on real fires — not just talking about career exploration. That hurts: you have to run parallel systems for a season, proving value while the old ways operate alongside. Most agencies revert because the double workload of "sandbox plus actual fire" burns out the early adopters. The fix I have seen work is to start with one specific, painful problem — radio communication failures, or map-reading gaps — and solve that in the sandbox before expanding. Nail the narrow win first. Then the organizational cost feels earned, not experimental.

When a Digital Sandbox Is the Wrong Move

If you're already on a crew and need field time, not screen time

You're five days into fire season, boots blistered, sleep bank empty. The last thing you need is another hour staring at a browser-based incident commander trainer. A digital sandbox shines brightest during the off-season — when you're building muscle memory for resource ordering or practicing look-ahead calculations without the adrenaline dump. But mid-fire assignment? It's a tax, not a tool. I have watched crews burn an entire afternoon trying to "validate" a firing operation in simulation while the real burn unit sat idle. The trade-off is brutal: every minute in the sandbox is a minute you aren't reading fire behavior, feeling the wind shift on your neck, or learning the social terrain of a new overhead team. Wrong order.

If you can't articulate why you're running the sim — if the answer is "because it's Tuesday" or "because the contract says we have to" — shut it down. Go dig line. Go brief. Go stand in the smoke.

If your learning style is purely kinesthetic

Some people learn chainsaws by taking one apart. They learn firing operations by holding the drip torch, feeling the heat, adjusting the rate of spread by doing. A digital sandbox abstracts exactly what these learners need: the physical feedback loop. Mouse clicks won't teach you how a fusee feels when it's about to gutter out. A drop-down menu for "wind direction" won't replicate the moment you misread a drainage and the column starts to lean your way. The catch is — sandboxes often advertise themselves as universal, but they're heavily visual-auditory tools. If you process through touch and motion, a simulation becomes an expensive screen saver. That hurts.

One fix we tried: pair the sandbox with a physical map and poker chips. Move chips by hand, then mirror the action in the sim. Still — if the software doesn't let you triangate by hand, skip it. Not every path needs a login screen.

If you lack basic fire terminology (sandbox jargon will confuse you)

A sandbox assumes you already speak the language. It won't pause to explain what "flank" means or why "anchor point" isn't optional. Drop a rookie who still confuses "head" and "heel" into a resource-ordering sim and they'll spend the session fighting the interface instead of learning the decision logic. The simulation becomes noise. I've seen it happen: the person walks away more confused, convinced they're bad at fire, when really they were just thrown into a tool that assumed fluency they didn't have.

'A sandbox doesn't teach you the alphabet. It teaches you how to write a sentence — if you already know the letters.'

— typewritten note pinned above a shared crew computer, 2022 season

Start with a whiteboard and a mentor. Build the vocabulary first. Then the sandbox becomes a rehearsal, not a foreign film with no subtitles.

When budget is too tight for even minimal hardware

A digital sandbox that lags, crashes, or runs on a five-year-old tablet that dims in sunlight is worse than no sandbox. It erodes trust. Crews learn to game the glitches instead of the scenario. The odd part is — a cheap, broken sim often costs more than none: you pay for the license, pay for the failed training day, then pay again to undo the bad habits people pick up while fighting the interface. That said, I have seen a crew run an entire sandbox session on one decent laptop and a projector, and it worked. The difference was intentionality. If you can't afford stable hardware and a dedicated facilitator who knows when to kill a frozen module, don't start. Wait until next season's budget or borrow a functional setup from a neighboring unit. A scraped-together sim that frustrates everyone is not a sandbox — it's a time sink with a login screen.

Not every forest checklist earns its ink.

Your next experiment: audit your crew's current hardware. If the oldest device in the pile can't run the sim smoothly for 45 minutes straight, scratch this approach for now. Go back to tabletop map exercises with rocks and pine needles. They cost nothing and they never crash.

Open Questions and Frequently Asked Questions

Does simulation experience count toward certification hours?

The short answer is: it depends on who's signing off. Most state and federal fire agencies still draw a hard line between simulated and live-fire hours. I've seen qualified candidates told their sandbox log was "informational only" at the certification review board. That stings. However — and this is shifting — some Type 2 incident management teams now accept up to 40 hours of simulation-based decision drills toward continuing education units. The catch is you need proof: time-stamped logs, a qualified evaluator's signature, and a clear syllabus tying each scenario to a specific NWCG competency. Without that paper trail, your sandbox time is just practice. Worth doing, but don't count on it filling a cert gap unless you've cleared it with your training officer first.

Can you switch paths mid-season based on sandbox feedback?

Yes — but only if your team treats the sandbox as a diagnostic, not a report card. The most agile crews I've worked with run a three-week cycle: two weeks of real assignment work, one week of sandbox replay. If an engine lead consistently outperforms in the sim on air attack coordination, they might shift into a liaison role for the next rotation. That's smart. What usually breaks first is the ego piece — people read a sandbox score as a demotion rather than data. The trick is framing: you're not swapping paths, you're calibrating the team's edge. One crew I know lost a solid squad boss because the transition felt like a punishment. Choose your words carefully.

How do you know a sandbox is realistic enough?

You don't — not at first. Realism isn't a switch you flip; it's something you test against. A good rule of thumb: if your experienced operators can break the simulation with tactics that would work on a real fireline, the sandbox is too brittle. Oddly, that's a better signal than pretty graphics. The worst sandboxes I've seen looked gorgeous but ignored wind-shift timing or allowed unrealistic escape routes. Ask yourself: does this sandbox punish the same mistakes that would kill you in the field? If it's soft on safety violations but harsh on paperwork, it's training for compliance, not survival. Start with free options like Wildfire Sim Lite or the basic USFS sandbox — those are ugly but behaviorally honest. Upgrade only when the cheap tool stops teaching you new things.

What's the best free option for a trial?

For a no-cost proving ground, the Incident Command Simulator (ICS-209 lite) from the Wildland Fire Learning Portal is your best bet. It's clunky, browser-based, and the interface looks like a 2012 spreadsheet — but the scenario logic holds up. You'll get stressed by resource ordering delays that mirror real dispatch bottlenecks. Another option: the FLAIM Trainer demo if you can borrow a VR headset from a local training center. That one's more immersive but harder to set up solo. Free trials tend to cap at three scenarios; run each one twice, once for speed and once for thoroughness. If the simulation feels too easy, you're probably ignoring the constraints the tool can't enforce — real fatigue, radio noise, bad intel from the lookout. That's the gap free tools won't close for you.

Most teams skip this: they test the sandbox, not themselves in the sandbox. Your first experiment after reading this? Pick one free tool, run a single scenario with your crew, then debrief with exactly one question: what did we learn about our decision speed that we didn't know before? No scores, no grades — just that gap. Answers will tell you if the path is worth pursuing.

'The sandbox didn't teach me how to fight fire. It taught me how to say yes to the wrong plan faster.'

— retired strike team leader, after a debrief that went sideways

Summary and Your Next Experiment

Recap: sandbox as a low-risk probe, not a crystal ball

The digital sandbox won't tell you which fire season will kill you. That's not the point. What it can do is show you how your decisions bend under pressure—without the real smoke. I have watched teams treat a simulation like a prophecy, then get rattled when the actual fire doesn't match the pixel. Wrong order. The sandbox is a probe, not a deck of tarot cards. You drop into it, you make a call, you see what breaks. Then you adjust. That's it. The catch is that most people want a neat verdict (Path A wins, Path B loses) and the sandbox gives them a mess instead. Good. A clean answer about a messy job is almost always a lie.

Action step: pick one free simulation this week and run it twice

You don't need a license or a budget for this. Grab the Wildfire Simulator from the National Interagency Fire Center's public tools—it's clunky, it's free, and it's honest. Run it once with the default strategy. Then reset and run it again making one deliberate change: push a different resource allocation, delay a burnout, skip a dozer line. The goal isn't to find the "right" answer—it's to feel how tiny inputs ripple across the map. What usually breaks first is your assumption that you had time. Most people discover on the second run that the first run's calm was an illusion.

'I ran the sim three times before I noticed I was always late ordering air support. That delay wasn't in my briefing—it was in my head.'

— Type-2 IC, 18 seasons, personal correspondence

Reflection: note what felt easy vs. frustrating

After the second run, grab a sticky note. Write down one thing that felt smooth and one thing that made you swear. The smooth parts are your natural drift—you'll lean on those when tired. The frustrating parts? Those are the seams where your usual playbook doesn't fit. Most teams skip this reflection entirely and just run more sims faster. That hurts. Without the note, you repeat the same blind spot and call it practice. The trick is to keep the reflection short—two bullet points, two minutes—so it actually gets done when you're tired.

Next: join a forum or find a mentor who used sims

The sandbox is quiet. Real fire decision-making is noisy. You need other humans who have blown a simulation and lived to talk about it. The Wildland Fire Leadership Council's online discussion board has a sandbox-specific thread that stays active during off-season months. Post your sticky-note observations there. Or find a retired strike-team leader who cuts their teeth on sims in the '90s—they will tell you stories about map projections that were wrong by a quarter mile and the lesson stuck anyway. A mentor won't give you a path; they'll show you how they walked into walls and kept walking. That's better. You don't need a crystal ball—you need someone who has seen the sandbox flood and rebuilt the walls anyway.