Ok so let's say we do make powder script. Here are the functions I think we should include: toxy(00,11) - a function to move a particle to a certain location partto(PT_FIRE/*particle name*/, 22/*temp*/, 3/*weight rating*/) - changes the current particle to the one defined istouching(PT_DMND/*particle name*/) - returns true if particle is touching a particle of the defined type, false if not delpart() - deletes this particle changetemp(12/*new temp*/) - changes particle temperature changepress(112.1/*new pressure*/) - changes particle pressure Other things: logical operators: >,<,==,!= datatypes: floating number, character array(these two should be all that's needed)
cr15py Lol at the >,< But yeah that's basically ROBLOX scripts if I can reuse that reference. Pretty much metal would be coded as: ifistouching(PT_SPRK>PT_METL) function:passparticle>PT_METL/PT_PSCN/(ect.) Which would basically mean something like "If spark touches metal, then pass the spark on to the next particle of metal or an other conductor. That make sense? Not the real code but something like that.
Neospector I noticed that when I typed... I was sure someone would notice. And the istouching function would only need the name of the element the current element will react to.
i think it would be a great idea but then you would still have noobs saying that it doesn't work lol. ACME and i were thinking the same thing a few weeks back but i knda forgot about it cause we weren't sure how to implement it :/. it sounds like a cool idea. pros - easier to add elements and other parts to the program.
cr15py We must have a string with code, and some function will be reading code and when code is well, function execute this code. With this we can debug code and show errors before executing code.
Your idea is impossible, because impossible is real-time compilling and changing code in EXE.