Grapjas

Feel free to add it. If you need help lmk.

Thanks alot

lmk if you need some help or have some suggestions when you get to it, would love to hear it.

@real_tabasco_sauceYeah i plan to expand upon it with different types of envoirementals in the future with some even having some beneficial effects. It's technically an template entity with an aura. I made a small component for the moving and spawning, but needs a map script[1][2] i made so that i can control what maps get what types of envoirementals. Not familiar with the random map gen code but i guess it should be failry easily if you wanted to.

Big update! New structure: Braziers! Ranged units near it will shoot flaming projectiles and apply burning. Can be toggled on or off. While on it consumes 1 wood per second. Han civilization is working Arcing projectiles! (thanks to @BB code with some of my own modifications to it) Improved rearm aura code Numerous prop & animation fixes Code cleanup Better flaming projectiles Walls can be built on top of tree's (tree's will be destroyed upon completion) Improved tooltips (added ammo and energy stats to them aswell) Unit resistance corrections Pikeman and spearman cav bonus fixed Add bleed status effect to the game (dogs have this now) Envoirementals like sandstorms! (just sandstorm for now). They will spawn randomly throughout the game and move around and dissapear after some time. Sandstorm effects: Slowly damages organic units caught within and heavily reduces vision range. sandstorm maps: atlas valleys, butana steppe, crocodilopolis, death canyon, egypt, golden oasis, hindu kush, libyan oasis (2p, 4p), median oasis (2p, 4p), saharan oasis (2p, 4p), sahel, syria, team oasis, tarim basin (2p, 4p) Probably other new stuff i forgot to note down along the way. sandstorm.mp4 sandstorm showcase arcing_fire_projectiles.mp4 brazier & arcing projectiles showcase Updated orignal post download links. @Stan`when you have time can you take a look and approve on modio? Also why is my orignal post hidden after edit?

Hmm so it was the walls over trees mod? Interesting.

It gets called alot throughout when the foundation is being built, but the statement should still only run once. Maybe twice, but engine.DestroyEntity does nothing gamebreaking if the ent doesn't exist anyway otherwise i'd expect it to throw an error. EDIT: you are right the var should be emptied if it does called multiple times though

Well, as i said it was more of a prototype code and expected someone to build off of it . As for entsToDestroy, it doesn't need to be cleaned or emptied because a foundation will just start with an empty variable to begin with and be gone when the foundation has been built. The new zip below has some fun JS edge case (also why are empty arrays truthy ) going on where it pushes ent twice, not really an issue but it shouldn't regardless. Also got the shading to mark entities red that would be destroyed semi working aswell (not in this zip tho) but i've honestly got to much projects going on to finish it anytime soon lol. Lemme know if this one's better and tweak it as you need. BTW, can't you simply delete my mod (or files) to test if it still happens without? walls_destroy_trees.zip

The last line in Stan's link is pretty important and different from a "normal" component type aswell so be sure to get that right. If that doesn't solve it, could you share your code on pastebin or something?

Just a heads up this line should be if (this.GetBuildProgress() == 1.0 && this.entsToDestroy) and i also didnt check OOS (probably fine though). Was more of a prototype code.

Was a bit bored so i made it anyway, lol. Do with it as you (anyone) please. Delete the Foundation file if you want the trees to disappear the moment they start building, otherwise they will only be deleted until the wall is done (to prevent exploits?). walls_destroy_trees.pyromod Btw, the tooltips like "cannot be built on another building or resource" for walls aren't working in vanilla. A project for someone else

You could probably do something like replacing this line with let collisions = cmpObstruction.GetEntitiesBlockingConstruction(); then check if those entities are a tree class (or whatever class it is) and pass ret as "success". Not sure if that would delete the trees but if not then you probably need to tweak the commit function in foundation or the IsFinished() function if you only wanted them deleted when the building is done.

Could try to add these to the tree template <BlockConstruction>false</BlockConstruction> <BlockFoundation>false</BlockFoundation> But it would work for all structures though. If you need, I can share a snippet on how you can probably do this in components tomorrow.

since TemplateLoader returns undefined, i'm guessing you either are missing a template you are referencing to, or have a typo to a template you are referencing to (within the mixin's/parent's template ref). I think the errors that come after the 2nd error line are just the result of templateloader not returning anything. Which could explain why you can just play a civ just fine, but only untill that buggy template comes into play, if you haven't encountered it yet while playing it's probably a not much used unit. Those are my quick 2 cents but maybe someone else might help you better. EDIT: I also just noticed you have `.keep` files in your templates folder for mycea in both units and structures which troj doesn't have, you can try deleting those. It might be that templateloader is trying to initialize those.

Happy gaming