This Car MIGHT Explode When You Give it Gas...

[@Kickerofthetar]

Useful thought experiment when thinking about probabilities: If you flip 10 coins hundreds of times, you can expect to get 5 heads and 5 tails, on AVERAGE. But, when flipping 10 coins once, you are much more likely to get any other result, because there are more ways of NOT getting 5 heads and 5 tails than there are for it. Another thing to keep in mind is that this is more like flipping 10 coins and blowing up if you get 1 heads. It sounds like it's a 10% chance, but you don't only explode if you get 1 heads. You explode if you ever get heads, so you actually want the chance of getting all tails, because that's the chance you survive (about 0.1%). Extrapolating that out to the exploding car: At a 99.5 threshold for exploding, you have approximately a 0.5% chance of exploding each tick, which sounds low. However, the chance of surviving just 10 ticks is the chance of getting a result in the other 99.5% 10 times, i.e. 0.995^10 = ~95%. With a generous assumption of 30 ticks per second, you have about an 86% chance of surviving 1 second, ~74% chance of surviving 2 seconds, etc. If the tick rate is actually 60 ticks per second, which is pretty likely, that 74% chance is for surviving 1 second. At worst, the tick rate that determines the random number is dynamic and will just be 'however many ticks we can fit in a second', in which case: you're screwed.

[@spaghettiwaffles]

very much this, my guess is the number display can't actually keep up with the ticks. I would use the trigger from the percent tank cannon, which only gave one value per button press, but use the duration/delay feature to create a manual tick rate

[@spoofmotionstudios]

I think the reason that you were exploding so often is that you were holding the button but it didn’t have a delay or duration. Basically it was triggering every “0” seconds so maybe add like a 0.01 second delay or duration so if it triggers 100 times per second at a 0.1% trigger rate it would trigger on average once every 10 seconds, theoretically. Just a thought.

[@Elec007Man]

Yeah I dont think the display is keeping up with every number the randomizer is actually outputting

[@Pug-man01]

Agreed, i was gonna come say this but i was thinking maybe a delay from the throttle input to allow for getting up to speed and eliminate instant explosions so the randomness is still there but theres a safety buffer

[@benrboss]

the randomizer gives a new random number every frame so it is triggering 60 times per second

[@Vessekx]

@@benrboss Maybe more often, depending on whether it uses a rendering tick or a physics tick.

[@benrboss]

It uses logic ticks which are 60 fps

[@notonlyhuman6073]

Cool idea! Never would have thought of this!! Here’s a thought. If you make the wheels fall off/car fall apart with detachable blocks (set to “scrap parts”) instead of dynamite, then the chance of accidentally getting caught in the blast radius of an opponent is no longer an issue! Hope to see this concept in a future multiplayer video!

[@FatehdeepSingh-h5e]

this idea actually seems fun scrapman should try this

[@britishcrow]

And like one wheel falls off each time and you can only repair when they all fall off each

[@FatehdeepSingh-h5e]

@britishcrow yea that would be so entertaining to watch in multiplayer

[@gamingfrog1234]

getting caught in the blast radius is half the fun...

[@Pale_Kingg]

_Me (cool wizard) after accidentally casting _*_"Dismantle!"_*_ while watching motorsports:_

[@letchykatchy6461]

Maybe add a 5-second timer after spawning or respawning the car as a buffer, so you don’t immediately get blown up and end up out of the race due to the inability to respawn quicker.

[@timizorzom9506]

Add a timer for 5 seconds before the randomness starts. Accumulator from -5 to 0.1; if Accumulator positive AND randomness > 0.96 then explode

[@IgnavumFortuna]

Exactly my thoughts. That would prevent you from accidentally leaving the race.

[@ocaj75]

Maybe shorter so that it can still happen while trying to get going, like 1 or 2 seconds

[@IgnorantC]

He seems to ignore the accumulator, very sad

[@babarlebarbar2709]

Here are a few ideas to make it more interesting (I think ?) : - Manage the odds "dynamically", the more people use the throttle, the greater the odds for blowing up, using an accumulator. I know the compare block is deceiving in the sense that you can't compare two value (from accumulator and random block for exemple), but I think using the accumulator as an input in the random block with the "Input defines range" mode, if the accumulator defines the range, increasing the range should technically mean increasing the odds ( let say you blow up if value is greater than 9, if you random from 0 to 10 at first, you only have one number that will trigger the explosion, if you increase the range to 20, you now have 11 numbers than can trigger) assuming the Input defines range works like that. - To add some fun to it, using a sound box to make a ticking Beep when people have high odds of exploding, so the others can hear it and try to avoid you. It will add pressure to everyone and could lead to funny situations - last thing, but the reason it was triggering very often even with low odds is because like you said, it is taking a random number every tick, and the frequency also increase the odds. Let's assume that tick is based on framerate, it means at 60 fps, you're trying 60 times per second, so that's a lot of tries. If you could find a way to get a random number every second or so, you could lower the compare block to something like 95 or even lower without blowing every time

[@ledocteur7701]

If I recall correctly the tick rate is 20Hz, which is way more than what than the rate the display was showing values at, so that's likely why it seemed so much higher than the set percentage.

[@sakethpothkan9573]

You stole my words🥲

[@spacemanspiff8635]

For multiplayer, true random probably won’t feel great. Would suggest setting the smallest chance but use an accumulator and a subtraction block to increase the chance the longer they hold it. Helps prevent the unfair outliers.

[@sakethpothkan9573]

I have 2 suggestions, #1 adding an "overheating" element to aid our perspective of randomness #2 Testing throttle and speed control on a multiplayer weight appropriate vehicle to adjust for handling discrepancies. #1 In my opinion, I think that adding a "overheating" element to the probability would help the true randomness align more with our perceived randomness. This could be done with an accumulator; growing while the engine is on and reducing while it's off, this could then be subtracted from the maximum exploding probability you would fine tune (coming to that in #2) and then feeding that to the comparison logic block you have in your setup. #2 In multiplayer, for the content to be interesting interactions might be but in a battle or parkour or area-restricted arena and these will all most likely have their own weight categories differing from your F1 mockup. Therefore your vehicles might have a low stop speed and/or acceleration. I later realized that a potential solution would be adding more engines, but I kept it in for something to think about; however my first suggestion still holds true. Hope this helps!

[@Nullpersona]

Use an and block to require a minimum speed of 100kph to trigger the explosives. Prevents instant death, while still allowing more than double the speed at risk of exploding.

[@EmberTheFlareon3579]

Though we'll have to find a way to delay the explosion until we get over 100 so it's not exploding on spawn. Lol.

[@dd-di3mz]

You could add an invulnerability time of 3 seconds or something when respawning, additionally would cheese be allowed? You could just drive the entire course backwards, I feel like that would be faster.

[@chargyplays]

I want cheese

[@Fireheart318]

Something feels unsatisfying about this: The explosions themselves feel jarring and mess with the flow of the video, and the timer feels too spikey; like it either blows up immediately or not at all. To fix the jarring explosions, I suggest doing something that will make the car non-functional, but still keep the driver in the cockpit, allowing the car to careen out of control like a real crash instead of coming to an instant stop. Perhaps you could reduce the amount of explosives, place them differently, or even forego explosives entirely and have the wheels fall off or something like that. Maybe also add a short delay between the timer and the explosives actually going off, just for dramatic effect. The 500kg bomb in Helldivers 2 is a great example. Adding a warning beep wouldn’t hurt either lol As for the timer itself, I suggest doing something to make it much less likely to explode right off the bat, and then more likely to explode after a decent amount of time has passed. Maybe have three timers with different probabilities: Have the low-probability one active for the first 5(?) seconds, then the normal one for the next 15(?), and then the high-probability one turns on until the car explodes. Another option is to just lock out the timer for the first couple seconds after spawning the car/hitting the gas for the first time. Sorry for the wall of text lol

[@moroblizniak4457]

17:36 Lets put 3 light in the back and every light will turn on if your randomizer hit a threshold. So you have 3 chances to trigger the treshold until you just explode violently. Would be tense!

[@jimmiemcfunfloungel8384]

This right here. Great idea. Three strikes, you're out.

[@erwin2punkt0]

To fix the instant explosions, but still keep the fun of the randomness, you could add a Accumulator, so it needs to trigger like two or three times to explode, increase the chance to trigger accordingly and it will be way less likely to blow up instantly, but still possible and you have a gain from not pushing through a 5sec spawn protection.

[@dshadows2966]

So number generator that slowly ramps up from 0 to a set number while giving it gas and if it goes over that number it will explode, but it also slowly lowers over time when you're not giving it gas? Or have a number descending and have it act as a fuel gauge and have it cut off your ability to steer if it's lower than a given number?

[@mistere6299]

Maybe he can add an acumulator so that the first 5 or so ticks cannot trigger an explosion. Would fix the issue of being kicked out of the race from repeated explosions.

[@ThePotatoMemer]

Even though it's 0.5% (1 in 200) or 0.1% (1 in 1000) or whatever other small values you use, I believe the Trailmakers tick speed is 40 tics per second. This means that the logic gate is triggering the random cycle 40 times per second, so a 1 in 200 per tic is more like 1 in 5 per second. 1 in 1000 per tick is like 1 in 25 per second. The absolute lowest value you can go being 0.01% (1 in 10000) becomes 1 in 250 per second. At least that is how I believe it should work, and it seems logical. That's why so many of these instant explosions seem like they're on the first roll, but it might have gone through 10 before you even knew it. Not blowing up for more than a few seconds on the 0.5% model in it self seems very lucky. Also, correct me if I am wrong on the tick speed in Trailmakers. If it is different, that completely changes all of my assumptions.

[@davidmartins8152]

For a MMonday, just put the dynamite in the back axel, so your seat is still intact but nullifies you movement. Only 1 explosive, as you know multiples increases the radius

[@M_W_K]

I think what you want is a system where the chance increases the longer since the last explosion. You might not have enough decimal accuracy for it, but that would help prevent the feeling of the car exploding too early, or taking too long to explode.

[@SteffedPepper]

I'm just assuming here, but it is probably generating a number every frame/htz refresh. So even at 60 fps, in 2 seconds it would call 120 numbers. Meaning the 1% (99) chance is likely to occur in just a couple of seconds.

[@blueplasmayt7918]

I think you should try adding the same concept with planes except for cars and try to dogfight. Love your content, hope you use this concept in a multiplayer video!

[@jeffreyblack666]

Looking at the video, the randomiser is not updating the value displayed every time, but the randomiser is still generating values (the green/red displayed doesn't match the value). This means the random values are being generated a lot more frequently than you might think. Assuming it runs at 60 fps, that would mean you are getting 60 values a second. And if you think of the probability of not blowing up, it is easier to calculate. So at 99%, at 60 times a second, there is only a 55% chance to not blow up after a second. After 5 seconds, there is only a 5% chance. After 10 seconds, there is only a 0.2% chance. Bumping that up to 99.9%, after 10 seconds there is instead a 55% chance to not explode after 10 seconds.

[@Space-qs3ky]

What if you add some accumulaters to function as a timer before the system kicks in, so you have to have been already accelerating for some time before you can explode, also maybe a delay on the explosion + plus an indicator so you can freak out behind the wheel and try to cover as much distance as you can before exploding. Just a couple ideas to make it feel more fair, and maybe add something fun to the challenge. Imagine seeing yzuie meandering along then a blinking red light starts going off on his car you just see him start flying down the runway before exploding.

[@toniezajac5906]

I have Cool Idea! Make a Car that will have a counter that will go up with the throttle and if it hits maximum it will engage the raw jet, but when its engaged it will have a chance to explode, that way it will be cool idea for a multiplayer race when people can risk to get faster!

[@wesup7601]

Maybe add an indicator that you are going to explode like sirens, lights, or smoke, and after like 2 seconds of the activation, then you explode.

[@m.h.6470]

One thing you learn as a programmer: "random" for a human mind is different than "random" for a computer. A human considers random to be "averaged out", which isn't random AT ALL. Random literally means ANYTHING IS POSSIBLE. With true randomness, you could have 1 billion instant triggers and then 1 billion years of no trigger at all.

[@ekkarll]

make it register reverse too, right now you can just drive backwards and win lol

[@CanicusVoid]

I think you should use logic to add to an accumulator and once you hit 100 it explodes. Then the higher the speed the quicker the accumulator goes up? When not applying throttle you can reduce the accumulator again. That way you have more control over exploding or not.

[@troylogannx01]

What if you where to take the idea of “failure” to a,lesser extreme and add a 2nd randomization for what fault is triggered for say 2-3 seconds, for example a fault is triggered so it rolls a 1-4 logic and then applies that fault to the car for say 2 seconds, with things like 1) engine failure, 2) steering issues where the car goes left turn, 3) stuck throttle or 4) explosion This would make the increased chances less punishing to a degree but also harder to plan for.

[@rapha31b]

really cool concept. please add a timer to activate the dynamite after spawn. so you can actually start going and not insta die.

[@Shaderox]

If the explosions ends up being a problem when people respawn at the same checkpoints and blowing eachother up, perhaps the same principle could be applied to a car where all wheels are on detachable blocks. (even more fun if they have different triggers so you randomly lose wheels while driving)

[@que56b]

two possible changes, add a button that gives 3 seconds or so of gas without it rolling the chance to explode, so you don't instantly after reset, but it can only reset when you repair. second, use an accumulator so that it has to go above that number multiple times, creating the bell curve, it's harder getting 12 from dice than it is 6, because only one combination gets you 12, but a lot add up into 6.

[@TheAruruu]

pretty sure it's refreshing WAAAY faster than is visible. that's why you had to reduce it to such a tiny percentage chance before it wasn't instant, all the time. if you put in a custom refresh rate on the random number, then the percentage chance to explode would feel more random, and less guaranteed.

[@thisisgametime164]

so you could do some logic that when pressing the "w" it adds a number to the random number, then when you let off, it slowly subtracts, this way you have to be on it a for a couple of seconds before you hit the possibility of exploding, but when you let off you get a reprieve, so you really have to manage your throttle usage. Press for to long and its almost a guarantee, but rolling means you lose the race for sure. I also agree with spoof, a short delay would also mitigate the exploding right off the start. Anyways love the concept

[@adicsbtw]

I think logic blocks update once per frame, so the randomizer would be changing its output every frame, making it framerate dependent This means that, at 99.99, it should activate, on average, every 166 2/3 seconds, or about every 2.5 minutes I'm guessing that the number display doesn't update as quickly so that it doesn't flash rapidly, meaning you aren't likely to see the number that actually caused the explosion show up

[@goldenandesite]

Day 19 of asking for a battle where you each make a vehicle of your choice unknown to the other players. This might lead to a tank, a submarine, and a helicopter in a battle, so you would have to prepare a way to combat any threat (amphibious, etc.). In case of an OP build, you can let the losers have some more power cores and blocks to try and even the playing field.

[@bobisha772]

One thing that will make it less frustrating and more interesting is if you put the detonation on a 5 second timer but immediately toggle a smoke machine. This solves the problem of getting kicked out of the race because you know you have at least 5 seconds before detonation and it makes things more interesting because you know you're about to explode and you can see how far from the next checkpoint you are.

[@arnelilleseter4755]

Here's an idea. Distance sensors on the sides. If you get too close to the walls you explode. Or to make it less dramatic but maybe more interesting in a race, your engines shut off so if you want to cut the corner you have to coast through it.

[@crispybacon9870]

nice vid keep up the good work

[@Zequax]

Scrapman out here giving a new meaning to demolition derby

[@duffyoxopatt3950]

This would be cool to use in a knockout style tournament. Eveyone is racing on the same track (without checkpoints), but every time, the last one gets eliminated. This would force the players to risk it, which is what makes this car fun.

[@darkener3210]

Scrap man getting confused how rolling a dice hundreds of times results in it rolling really high really often Anyway for multiplayer it would probably be best to rout the random block into an accumulator This way the accumulator goes up at a random speed while your holding w when it reaches max you explode This way you never explode instantly which isnt fun and you will always explode eventually which is more fun then never exploding This also makes feathering even better because now your guaranteed to explode eventually and it has a measurable effect in not making the accumulator grow while doing so Ofc you dont have the accumulator visible, but it could be interesting to allow it to be visible, since theres no way to stop it only delay it

[@sharkyshark1]

I feel like you could add a delay or something that either makes it when you first accelerate it can't explode, maybe by saying under 20 MPH the RNG is disabled, or when starting at 0 MPH you get X secs before the RNG starts.

[@TheDeath-ii5wn]

"There's a bomb on the bus."

[@artursmolinski3813]

I'm not sure if this is easily doable in trailmakers but I think that it would be better to have a risk of explosion when You press the button instead of having a risk of explosion the whole time when You are holding the button. What I mean is to generate one random number when You press the acceleration button instead of generating numbers per every "tick" when button is pressed.

[@glubsncarrot]

I like the idea of an invulnerably period. I also think it would be fun if, once you hit the explosion number, it gave you like a 2-second warning before it exploded: you could try to hit a checkpoint or steer into an opponent in that time.

[@troffmad]

I think it's more likely to explode instantly during the acceleration stage, this is the time when you have to hold the gas button for a long time. It will be more comfortable if you turn off the possibility of an explosion until you accelerate to at least 100 km/h, anything faster will put you in a vulnerable position, but you can start moving at least.

[@CoolDude-il2mp]

You should do a multiplayer race using this car but every round the percentage chance of explosion increases. So start with 99.99 on the comparison gate, then 99.90, then 99.8, 99.7, etc etc. I think this would be good as the dynamic of the race would change continuously.

[@toddabbott781]

You should do a car with an accumulator that clocks up when you accelerates and clocks down when you coast, but explored if it gets too high... then race them. You can respawn after you explode. Have the counter good for about 3 seconds though so there is a lot of strategy with trying to cut close to the edge. You could also have areas on the track that are a different color and have a color sensor that lets you accelerate without increasing the accumulator.

[@elioney9115]

A cool idea for this could be, making it more likely to explode the longer you hold down the throttle

[@BigPMachinery]

Multi-player Monday idea: Similar concept, except you should put this idea into 4x4 vehicles and everytime you naturally decelerate uphill you have a chance to explode from “overheating” and race on a hilly track

[@unything2696]

Day 3 of ... 2025.

[@xrock4404]

Time flies

[@JohnsenJohnsonbabyoil]

The most GOATed year

[@janicaorme2372]

Still no flying cars

[@janicaorme2372]

Still no flying cars

[@TheBartholomewJinPing]

No shot you're doing this 365 times

[@Nar3ik25]

This is a very good idea for a multiplayer video, I think to make it more fair there should be a 3 to 5 second grace period when spawning in so that you can actually get going and don't get caught in that loop of exploding the moment you start moving.

[@QWERTIOX]

6:00 propably logic ticks happens before updating the display so sometimes it doesn't display the value before explosion

[@Gibztr]

Suggestion: Add a light and a short 2 second delay from when the number hits 99 and when the explosion happens. A light comes on and then they wait, adding suspension and tension.

[@adrianbowen9357]

Ideas to improve for multiplayer; Put a delay on the dynamite of 1 second and a light on the vehicle so the person driving knows it will blow up. Have a minimum speed - say 50mph so that if people want to, they could crawl along at 50 and never blow up

[@qdaniele97]

The random block is probably cycling through numbers way too fast, and maybe related to game tick which might explain uneveness of results (depending on what is going on in game it might be way too fast or not so much). It would probably be a lot easier to tune in a sensible probability by capping it to one trigger per second or something like that. Adding a 1 second timer connected to the gas input, sending the timer input to the random block and setting it to output a single number per activation should work.

[@davidannen7448]

You could also set it up with detachable blocks. Hook it up to drop off wheels, aero, engines, etc

[@coreytaggart128]

Using this mechanism and then doing a group endurance race with a group would be kind of cool. everyone gets 100 blocks and this has to be a core part. whoever does the most laps in say 2 min gets a point then evolve the cars and repeat. Use a small track and when you explode you have to start at the beginning of the lap again.

[@curtisshaw1370]

It depends how frequent each tick is. If there are 10 ticks a second, then the likelihood of it exploding within 1 second of acceleration is 1%, within 10 seconds is 9.5%, and within one minute is 99.8% at 0.1% chance per tick. You'd need to know the true number of ticks per second to calculate the true odds.

[@Gibztr]

Suggestion: Detach the seat. Instead of the car exploding, detach the seat to remove control and avoid blowing up other cars.

[@danthedude4444]

You could also add an accumulator that multiplies the chance of exploding that goes up when driving and down when not, to discourage holding down the button, once implemented this could allow you to adjust the chance without it feeling like it’s too low.

[@mihalydozsa2254]

This is how chances work :D You could implement a time delay after respawn to prevent exploding and still keep the higher chance.

[@brunokaliston]

Scrapman, you should add a delay of 1 or 2 seconds before activate the Randomize, so the car don't explode immediately

[@William_Kyle-Yuki_Yuuki]

At the end when you were ejected from the race, just letting your car settle for a second or so after respawning is probably enough to reset the leaving race timer and that will mean you shouldn't get two explosions back to back that will leave you no time left on the clock.

[@blueflame_sm]

ScrapMan used the term "likelihood" in place of "probably" about 2/3rds down the video. I just want to point out that, in statistics, these 2 are not the same. In fact the meaning differs when dealing with stochastic or continuous probability, but in general: "Probability" refers to how probable a certain outcome is in a given system. "Likelihood" refers to how likely a value came from a system. You may wonder, what's the difference? Well, the former refers to how probable ScrapMan is to explode after x seconds given that he has y probability each tick, whereas the later refers to how likely it is he used y probability given that he exploded after x ticks. "Likelihood" is used in certain machine learning applications. To find the model that best fits data. Finding this likelihood often involves simulations or heavy assumptions on the underlying system. These assumptions can then be used to compute likelihood from probably using i.e. Bayes rule. A common (and often completely wrong) assumption is thus independence of all random events. Your car isn't starting if the tank is empty, so slapping a 99% chance on the car starting and an independent 80% chance on the tank being empty makes no sense. And finally as an added bonus: "Odds" refers to the chance of some outcome compared to another, so in a fair coin flip your odds are "1:1" whereas the probability of heads is 50% (0.5 if we're talking math).

[@Leifon_Wulfein]

(First comment I'm making this year woo) The concept is interesting in my opinion, however I personally think instead of RNG, it would be more competitive if it was based on how fast the player went. As example: a vehicle that can travel pretty fast but say there is a bar/gauge that would accumulate if the player is traveling over a set limit and will destruct once it is filled. The bar/gauge/preassure will not decrease and the faster they are moving, the quicker it will fill.

[@DETHdressedInRED]

Really fun idea definitely would love to see this in a multiplayer scenario. Could put it in tanks and have a chance to explode when you shoot? XD

[@gladneyhardy1604]

Hi scrap man I've been watching your videos for years now and i just want you to know i love them 👍🏾👍🏾👍🏾👍🏾

[@Altimoo]

Maybe add a constantly decaying accumulator (throttle increases and activates randomizer) so holding the throttle for a second or two will start the random chances. Make the engines behave like the RAW jet but instead of a cooldown, they violently explode instead.

[@chargyplays]

Soft rock music and vehicle building game in the desert? Just try out Crossout at this point man! 😭😭😭

[@IdrisVanNuffel]

Instead of having it blow up, you can have random parts falling off. It gives you the choice to continue or repair.

[@Morfik45]

Reminds me of series where you was making vehicles afraid of stuff, for example that plane you made that was afraid of heights and exploded when being at certain altitude

[@googolplexfpv]

The radomizer changes or "ticks" 10 times a second. So you could essentially say the chance is 10 times the single probability per second. .1 giving you 1% change per second and .5 giving 5% chance per second.

[@voronwecalanon206]

I think an overheat guage that would go up when on the throttle, then slowly go down when off the throttle, and the over determines your probability would be better.

[@MrSystemXI]

What if you added detachable blocks to different parts of the car? Add other variables like loosing spoilers, or an engine, maybe a weight or a wheel, so you don't always blow up but still effected is some way.

[@andireasgermany9196]

This concept with 0.1% and dethrone would be awesome

[@Nevir202]

Add more logic, such that it counts down for one or two seconds after being spawned, and while that respawn timer is running, you can't explode. That way you at least can't get in that loop where you cannot get restarted after respawn.

[@josephle5373]

For the multiplayer race I'm thinking of halving the chance (so what was it? from 5% to 2.5%?) but allowing a Last Player(TM) to use a power. This power is: blow yourself up. But here's the twist: Last Player(TM) is not the last player, but whoever was last three seconds ago. This changes two things: the penultimate player can't just blow up the last player whenever they try to overtake (because they haven't been the Last Player(TM) for at least three seconds; and the Last Player(TM) has three seconds to maybe shoot for the second or even first player to make it more interesting (as in they overtake multiple people to blow up the furthest one they can reach). To make this easier to control just add three differently coloured lights to the top of the vehicle which circle in 1 second delays between them. As in "If I overtake on a red light i have until the next red light to blow up". I think this could make the race a bit more interesting, to add a level of mario kart-ing to the game without having to change the vehicle excessively. Which also gives back some control to the people (raises fists), so maybe it's good to balance the chaos with the conscious.

[@brandonfeeley514]

Holy Trailmakers batman! I feel like I have been stuck in Scrap Mechanic content for like a month...lol

[@Pumpnineteen]

U could add a timer to create a rate limiter, and a minimum blow up time. Or add a higher chance, but feed it into an accumulator

[@cyberhacks69]

you should add some delay between the number hitting, so you see that it hitts and you get like 2 secounds of dread, knowing you about to blow up, if possible maybe add some sound too it as an indicator

[@AlrenClan]

It would be interesting to see if you can make this so that you have a chance of exploding whenever you decelerate, so that you have to try and keep as fast as possible.

[@ArinJager1]

maybe instead of a randomly exploding car, try to make a vehicle that has like a limited nitro (turbo) - when you "boost" for too long, it like "overheats" (builds up heat), and then it explodes (TNT) when it reaches a certain threshold (100%) if you don't let go off of it and let it gradually cool down (like in the playstation 3 MotorStorm games)... I think there are thrusters that do overheat and then have to cool down before you can thrust again in trailmakers, but I mean it like a thruster that doesn't actually overheat, in-game (I know it doesn't actually explode on its own without TNT), but you make overheat & cooldown logic that triggers the TNT block(s)... if that makes sense... Then you can race with the boys with these cars... >:D

[@thatrandomguy7136]

well considering you have about 10,000 different numbers to get from the randomizer (using the decimals) you have a bit more of a chance of getting blown up than usual, of course it's very minimal but still slightly more chance and with more numbers it's harder to get a consistent average without hundreds of tests, if you limited it to rounding to tenths and as most people said already set a delay to the randomizer then this would definitely be a good concept for multiplayer

[@lordmaddog6003]

Don't do a delay like most are saying but rather use a accumulater that tics up the min amount on your randomizer when Gass is pressed and down when not pressed. So the more Gass you give the higher chances you have of exploding

[@DavidVYoutube]

I would do the inversion of this. Increase your chances of exploding if you slow down. That means people would have to try to drive to the course without breaking

[@jasiojakubowski2235]

Maybe make a limited fuel race with friends, the point is to arrive first at the finish, but you need to pay attention to fuel, because it will drain as you apply gas.

[@MikeGameOver]

“It either happens too often or not enough.” -Scrapman 2025 Bruh. You mean it feels random?

[@Adrian-3]

I think you need a delay between the "ticks" because we really don't know how long a tick takes. It felt like you were exploding unordinarily often for a chance of 0.5%

[@turrboenvy4612]

This would work well for a competition where the winner of each round has their chances of explosion increased.

[@Varjokissa]

Haha. Same system but implemented with 2-3 seconds timer of terror to explosion. And red light when timets starts :D

[@remijouault7398]

I think it could be a good idea to ha a litle delay and an indicator like a light or a horn before you explode .

[@jedliczosnek]

To be able to see the target number before explosion happens you could add a little bit of delay before triggering the dynamite. Like 0.2s 😅

[@nathancurnow2410]

After the condition is met for the explosion to take place, a 5 second timer should be triggered that must count down to zero before the cars explodes.

[@JoeMama-me5wp]

You could add a timmer that only counts the numbers after 5 seconds and/or you could have 2 number genorators with a and gate to lower the odds

[@lilstubthumb]

Make Red Light Green Light where your car blows up if you move at the wrong time. Make the car watch something on the track to determine if it should blow up or not so you can do it in multiplayer.

[@GuereroGrande]

I suggest having a weak and really slow motor that you can throttle safely and then having a boost connected to the random explosions!

[@astramancer]

I don't know what sort of display pieces you have available, but would it be possible to make sort of siren or alarm light that would light up when triggered and give you like 2 seconds between trigger and boom? Just for that extra dread of knowing you're about to blow and there's nothing you can do about it.

[@ala5530]

I'm curious- do multiple randomiser blocks (with the same settings) on the same creation sync, or do they each give different outputs each tick? Assuming they don't synch their outputs, you could potentially tune the trigger probability threshold with multiple randomiser blocks and an AND gate.

[@enderstudio3737]

Scrapman, if you want the race to be funny please add a 2 second delay before the bomb detonates where the screen flashes the number it landed on before it explodes!

[@AXLOTblue]

A max complexity dogfight is a really fun idea🙂