Author Topic: Deactivated features in Blockland Add-Ons?  (Read 2072 times)

I've noticed that a few Default Add-Ons have some sort of features disabled by default, for example the Jeep has some lines of code leaded to sounds.
Quote
// Sounds
   //   jetSound = ScoutThrustSound;
   //engineSound = idleSound;
   //squealSound = skidSound;
   softImpactSound = slowImpactSound;
   hardImpactSound = fastImpactSound;
   //wheelImpactSound = slowImpactSound;
And I'm pretty sure I've seen other parts of codes in other Add-Ons that could work by default with the Torque engine but are deactivated for some reason, do you guys think we could make these few disabled features to work again?

At some point the place you learned how to make blockland-specific add-ons like vehicles was from default add-ons, so it could easily just be informational.

Filipe you are the vehicle god here so I assume you can.

I mean, have you tried uncommenting those lines and then actually adding the datablocks and assets? I don't see any reason why those would be actually disabled unless they were outright broken for some reason or another.

If engine sounds were that easy to implement I don't think we'd have such a hard time doing them and they'd be more common.
iirc I've tried these before, they're commented out because they don't work.

The football in the default sport item pack has a disabled punting function, it doesn't work and I have no idea how to make it work; I'd like to see someone fix it

Isnt blockland a theoratical beta? We have 3 beta versions.

i heard that there is partial code for the visor on the avatar moving up and down

i heard that there is partial code for the visor on the avatar moving up and down
There's an animation file for it, but the animation doesn't actually do anything.

In some general aspects, doesn't Badspot run this game by himself?
One man can't really code all of this without help, yeah?
From looking at this page I could think that he might want to save Datablocks in general, but I've come to feel that Badspot is just flat-out lazy. It's been more than a year since Blockland got Greenlit and released on Steam, and it still doesn't have a workshop.
Future releases or Easter Eggs aside, I would've liked something like this code to be a reality, but seeing how there ARE a bunch of Easter Eggs in vanilla, I literally have negative comments to say that I'd rather save for the Drama Section.

Keep in mind that those are probably engine variables left in there from TGE, and that GG didn't fully implement the feature. As for the reason they're in the script file and commented out, a lot of datablock code is copypasted from the default TGE example datablocks and then modified to suit.

There's tons of unused features in Slayer. For example, the fly-through camera, which will send players on a pathcam journey through the build at the beginning of the round.

There's tons of unused features in Slayer. For example, the fly-through camera, which will send players on a pathcam journey through the build at the beginning of the round.
Except if you know what your doing you can use it, i used it in one of my TDMs it was dope

There's tons of unused features in Slayer. For example, the fly-through camera, which will send players on a pathcam journey through the build at the beginning of the round.
But the fly-through camera isn't hidden away and commented out.

If engine sounds were that easy to implement I don't think we'd have such a hard time doing them and they'd be more common.
iirc I've tried these before, they're commented out because they don't work.
Filipe had sounds in his cars before but removed them because they interfere with a super popular mod