I don't need anything right now. I simply know there are many teams of forgers out there, but wanted to create one based solely in scripting that could be relied on for almost any of the communities problems. First I just need to see if there are enough people interested in creating one who have enough experience in scripting to solve most problems. If I misread your comment and you were asking @Ray Benefield, than I have no idea what he needs.
I program for a living and while the scripting is a bit clunky and glitchy (and I'm new to it), I think I'm quickly getting the hang of it. I'd be glad to help out. I definitely don't have credentials but I did script a simple on/off switch where the switch is inactive for the on/off animations. Pretty proud of that one and it seems to me like you could have implemented something like that on your elevator, Egggnog... if you want to take a look, GT: Rethal Sepsis Filename: SINGULARITY Just instead of despawning and spawning in switches everywhere. I'm about to start on my first significant motion script as well, and I'm trying to figure out alternative timing scripts (ie, despawning and respawning at intervals such that you have varying times of the spawned item - therefore, vents that steam periodically, etc). Anyway like I said I'd be glad to help script when I have time.
I took a look a singularity and thought about doing something similar on the elevator, but I have a severe lack of faith in 343's multi input scripts and it seemed to incorporate even more channels, especially because I would need it for multiple switches and timings.
Your distrust is not misplaced. Something I found when writing my on/off loop script is that the "minimum conditions to trigger" sometimes means minimum conditions and sometimes the "None" condition is counted as one of those conditions. Which is aggravating. But, knowing that is half the battle! For yours, it would be a simple matter of the switches all "running" on the same power source. They all turn it off when they activate, which despawns a timer plush. the timer plush respawns after the amount of time you want your elevator running for. So just something basic off the top of my head: Switch 1: sends message alpha if (alpha and alpha power on): sends message bravo if (bravo): bravo power on, alpha power off if (charlie power on): bravo power off if (delta power on): bravo power off Switch 2: sends message charlie if (charlie and alpha power on): sends message delta if (delta): charlie power on, alpha power off if (bravo power on): charlie power off if (delta power on): charlie power off Switch 3: sends message echo if (echo and alpha power on): sends message foxtrot if (foxtrot): delta power on, alpha power off if (bravo power on): delta power off if (charlie power on): delta power off So this way, each switch turns off all switches when it activates, and turning on one switch turns off the other switches. That way, whichever power is on is the one that is currently activated. I'm not going to use those in this example, but you could potentially use them to create multiple timer piggies, each responding to a specific situation. So if bravo is on, that means that the elevator is at switch/floor 1, charlie means it's on floor 2, and delta means it's on floor 3. So you could have a plush for 1 floor transit and a plush for 2 floor transit. And maybe a 0 floor. They both turn alpha on when they spawn... actually I'll script them. Timer piggy: if(bravo power on and delta): despawn if(charlie power on and bravo): despawn if(charlie power on and foxtrot): despawn if(delta power on and delta): despawn on spawn: turn alpha on Timer whale: if(bravo power on and foxtrot): despawn if(delta power on and bravo): despawn Resetti Chief: if(bravo power on and bravo): alpha power on if(charlie power on and delta): alpha power on if(delta power on and foxtrot): alpha power on So essentially what happens here is that you have the pig timing all single floor transits and the whale all double floor transits, so they can have different timers. The elevator would have something for each position as well: so like if bravo power on and delta, move blah in blah. That way the elevator, too, "knows" where it is and where it's going. I get not trusting the scripts but a little bit of tweaking can make bad script design work well edit: also, glad you looked at singularity! I tell ya, the hardest part of that dang map was getting the switch to not somehow start a chain reaction. That was one of the "minimum conditions" problems I was talking about.
Yeah. It would basically run on the same dolls I already have running, but rather than spawning and despawning said switches they would add into the conditions of the elevator running. Quite a good setup you've got there. Well done sir!
After rereading my original post, I am beginning to get the idea that there is some confusion here. The original purpose of this thread was to find scripters, and maybe a couple of others, who wanted to be a part of something more official, to give back to the community and try to help and teach others. This isn't an exclusive thing, you could be part of this and another team, and I don't really feel qualified to lead. This team will require different types of people, so if you're someone who just wants to script that's fine, but if you're someone who wants to be a media liaison and spread the word, or wants to make YouTube tutorials or be an administrator, you are perfectly welcome too. I know that sometimes forgers just might not be sure where to ask for help, so having a reliable group that they are certain will help to the best of their and the games abilities would be a welcome resource. If you just read that whole paragraph, thank you. It shows dedication and we'd love to have you. Send me a message or post a response if you're at least interested.
Fundamental Laws of Halo 5 Scripting 1th Law: If you want something to spawn as a sequence of events, make sure there is a "On Round: Start / Despawn" script before it. 2nd Law: If you want something to despawn as a sequence of events, make sure there is a "On Round: Start / Spawn" script before it. 3rd Law: It doesn't matter if Timers run while Despawned or Spawned; they are your enemy. 4th Law: Stated Power uses binary logic, and its call to Action is continuous until complete. 5th Law: Sent Messages' call to Action is not repeated unless the condition is a Timer, and the Repeat Timer is above 0.00. 6th Law: Never use Stated Power when a Sent Message will suffice. 7th Law: An object cannot Spawn if a player is within the object's physical boundaries when the call to Spawn has been made. 8th Law: The default of Stated Power is the Off State. 9th Law: There should be some sort of visual indication as to if a switch is operable or not. 10th Law: Anything that's reusable within a single round should use Stated Power.
Is @buddhacrane still gone? He's the master at reducing the number of scripts and power channels needed. I don't even know how many times I've figured something out only to find out that @cookies4you had already said it, but in some way so that I didn't properly understand. Cryptic bastard. Ha. I keep forgetting to raid @Captain Punch 's maps to see what he's done. I do have a doc started (open to the public to edit, copy, whatever) that has all the conditions and actions documented along with some other info, but I haven't updated it in a few months. If you can find a better home for it than Google docs, then be my guest. There is a bunch of info on the power states, messages, and Multi condition. The move, rotate and velocity actions have a bunch of info, but those things make me wanna just forget about this Forge. Here's the file: https://docs.google.com/document/d/1bnW0QHucyEcH4kReWQHIV9LJ2kOEiO1DgtX_yIqoD3Q/edit?usp=drive_web I usually can't get anything actually done, mostly testing like cookies does, I think. But I might know something that can save you a bunch of time, so just pester me until I get off my butt and answer. Also, keep checking YouTube for good scripting stuff and the people that pull it off. Good to see people working with Wally on stuff.
I was kind of hoping this thread wouldn't be bumped, because this was an initial feelr thread and now my next one will look like spam.
At least this one got the attention of some community notables. And I just learned that C++ is at least still worth mentioning (I'm so out of date... See you in hell, ActiveX!). I think we're allowed redos and people will understand. Maybe try another approach or be up front about trying it again with lessons learned.