What Are You Working On?

Well I've realized a few fatal flaws with Tikal after watching @Xandrith and @MultiLockOn play it on stream. Ive got a few ideas on how to redesign some stuff, mostly revolving around the teleporter's role in the design. Thinking about moving the receiver to a newly designed part of the map.

Obviously won't be for the contest version, but I'm still going to strive to make the map play better.

 

The broken scripting didn't affect my opinion of the map at all, don't worry man. I think about the map as if the ship didn't crash

 

but we didn't intend rockets to "arrive" until the designated time, so it does change gameplay significantly. Also, it's embarrassing as **** that people are loading it up and playing it (not just judges, but onlookers and fellow contestants) just to see everything we bragged about simply not work. What sucks is that this is not something we could have every planned for... That a ****ing camera would introduce a "round" into the game when it is supposed to be a 1 round gametype...

oh well, I guess let us know when it's DQ'd so we can fix it.

Thanks,
(Clarification... scripting is not broken, the game is broken )

 

I'll give it a look then.

 

Thanks a million - feel free to use the video I linked to in my above plea to judge the intro cams (blue not shown) - otherwise, yeah, the early arrival of the rockets completely wrecks the gameplay and 'woah' factor of the shuttle arriving partway thru - not to mention all the little details we packed in there.

 

I do think that certain changes should be allowed to be made due to scripting errors. These are single / dual individuals working on maps and unique concepts. It isn't that bad to say "Hey we deleted the cameras as they don't affect gameplay and we tested the map that way due to know scripting issues."

 

Such rules would be too grey. Nobody could control anything anymore, everyone could change anything.

I didn't get finished with lighting either. Other people didn't get finished with something else. It is, what it is.

 

agree

 

I think it's pretty awesome if they make an exception and let you guys fix this one thing.

But that's it!

 

I think it would be pretty awesome if everyone takes the moral high ground like I did.

 

Lighting is a part of a static not dynamic design element, if the dynamic element becomes broken on a custom map due to the scripting bugs built into the game and it affects the map gameplay, they should be at the very least able to disable the scripting entirely. Lighting is a visual aesthetic and easily should have been addressed before the deadline. A light turning on or off or a dim area due to the designers lack of time management does not make a section of the map become inaccessible or exploitable due to it not being what the map creator couldn't "squeeze in" ... They went to great lengths to add extra dynamic elements, the game is bugged and the map travel paths are affected. Power weapons are negligible when they spawn as yes it ruins the intended flow of the map, but when the weapon is up there is a push to that section regardless what time it appears in the map. If someone made a platform that came out of the ground to connect the low and high ground together to allow access to a power weapon and it stopped working and that was the only way to obtain the power weapon, would it not be fair to say turn off the scripting and place the platform at a preset height until 343 has proper working scripting?

Their to effort to think outside the box and try to add a new element and it ruined the map gameplay, you could barely be bothered to sit down "to get to finish" for a bit and hold right on the D-pad to duplicate a few lights... There is a difference. If you couldn't complete one map in 6 weeks that met your standards, you shouldn't have entered it. Not trying to come off rude while saying that, but I'm sure if anyone looked around they would find you played customs or matchmaking or other games during the time you could have been building...

 

I don't mind them fixing that. This seems okay because it is clearly a bug in the game, but other than that I don't think there should be any sort of changes allowed. If somebodies scripting was just not tested enough that is their fault. Also, if this is a known risk with scripting maybe they should have focused more so on geometry and it's functionality without it. It is a contest for money not just bragging rights. If it was for bragging rights only I could see judges being more lenient.

 

Everyone had the same deadline snd opportunity to test their maps. Halo has had no update or bugs introduced since we announced this competition. I don't care what's wrong with your map. We said we will delete spawns or weapons. In this case it's scripting that will be deleted. I'm not up for fixing maps beyond deleting things. Yeah it sucks because some maps so far are going to place lower because of dumb errors but I'm not going to relinquish the integrity of this competition to be 'nice.' Sorry guys.

BTW we probably would be more lenient if spranklez didnt go ham about it. Turns out he never submitted his map. Blame that man, not us. lol

 

Bump

 

it's a lot less impactful than judges changing weapons, which almost happened. all we're asking them to do is remove something that is not gameplay related, not asking them to improve our map or give us a special edit window... Removing something that happens before the game even starts, and is clearly a 343i bug that no one has apparently seen before.

(there's some confusion in the posts above - we are NOT asking them to disable some scripted element that was intended for our map. We are asking them to remove CAMERAS ONLY because it introduces an extra "Round" into the match that , as far as I can tell, no one has ever discovered before last night)

there is no reason anyone should have anticipated that adding in some cameras would break something, ever.

also, we're not going to win so don't worry... there's a lot of amazing maps. Ours is special, but probably not the typical kind of map the judges will praise the most.

We just odn't want our work product ruined by a game bug... we just want the chance to have people unwrap it and see it as we intended it (and as we had it working that night). That's all. Gameplay is not going to be stellar, so chance of winning is almost zero next to some of the amazing maps y'all have produced. But, we want our work product presented w/o this ****ed up, out of our control, game issue.

Think of it like this. If they introduced a game patch tomorrow and it broke some maps that are in competition, wouldnt' it be fair to remove something so harmless just to keep things going? well, who knows when that bug was introduced, or if it was always a game flaw that no one found?

Look at the service I've done to the community of forgers even in just a few months. I've found some bugs or hidden features inside forge that you would never, ever have found. Deserve some points for that... For instance, would you have ever thought that FFA players are all considered by the game engine to be on the same team? I found that developing the "Eternity Ball" featured in this map.

I don't want special treatment, I just want to take a broken GAME element out of our work product because 343i has apparently not anticipated how stupid their decision to make pre-game "rounds" a thing...

 

clarification, we are not asking you to disable scripting, just delete cameras, which rae very similar to "spawns", and far less significant compared to weapons. thanks.

(disabling scripting was a suggestion for when you do the steps to remove the cameras. Instead, you can just load it up, select all cameras, and delete. save, done. Leave scripting on, plesae.)

 

well, true and... not apparently as complete of an explanation as I thought. when you are using a count UP from round start, that is true. It would subtract 13 or whatever... But when you do "Round Time" it counts DOWN, which is what we wanted for this arrival of the shuttle. HOWEVER, the pre-round is treated like a zero round where, apparently it works like this:

Scripted sequence is set to take place 8 min before end of round.
Game loads
Pre-round during cameras is obviously not long enough to include 8 min, so game decides to do all things that should have already taken place in the timeline of the round.

It would be fine if it reset itself at the start of gameplay, but it doesn't.

I have an idea for a workaround, but I wouldn't ask to insert that fix in the map, because that is what we could call a real "edit" and "fix". Out of trying to comply wit hthe spirit of the rules, we'd ask that they simply be removed for a later date.

 

I think the most important thing to agree on like No God Anywhere said, he will delete items that impact gameplay that are easily removable by just deleting them such as spawns or weapons. Deleting weapons or spawns do greatly impact gameplay and they are acceptable, What he is asking is to not delete the spawns, weapons or scripting, but to delete just the camera's.


On a side note, yes everyone appreciates your contributions to the community, but that should have no effect on exceptions during a tournament to give anyone more privileges over anyone else... My above statement in the post does however correspond to the guidelines of the set forth rules for the contest. Deleting items that affect gameplay at the judge's discretion make sense to help better the flow or spawning of the map for their testing, as should removing camera's.