Meeting Minutes

[camronCollinsworth]

[ date if not submitted on the day of the meeting ]
Excused: [ list of those not in attendance who notified the group ]
Absent: [ list of those not in attendance who did not notify the group ]

Summary: [ summarize the topics that were discussed ]

Action Items: [ list of action times by assignee ]

[quinnshultz]

Excused: Damian

Absent:

Summary: Sprint 0 Planning

Action Items:

Fix IndexOutOfBounds exception so that the game can be built - Quinn
Design new runner - Cameron
Create level mockups - Annika
Summarize AI resources - Camron C
Document existing game behavior - Nathan
Create AI mockups - Andrew

Minutes:

Nathan: Have you seen the feedback from the professor on our Project Plan Draft?

Nathan: The jumping feature is the most fun I have had in the game. But, I did get stuck at one area of the map.
Annika: Is that how the original worked?
Annika: I think we should spend some time becoming familiar with the game issues.
Tavi: I have some thoughts on that, we could dedicate an issue to CI/CD. Focusing on the output package for Sprint 0 could be a potential objective.
Nathan: I believe Quinn already has done that.
Quinn: I built the game, but the output exe crashes at the start.
Annika: The general team could start creating a new mockup, map, or other feature.
Camron C: The AI team could brainstorm some features, for instance the AI Runners could be looking for powerups.
Andrew: We should also discuss the difficulty of the game.
Tavi: I remember that a study of AIs doing more damage caused them to seem smarter.
Nathan: Unreal has a feature for causing a runner to follow, or to move on a surface. From there it is easy to implement "move to player".
Tavi: A task could be to look at the existing codebase and sumarize the AIs performance.

[quinnshultz]

Summary: Sponsor Meeting

Action Items:

Project Plan

Minutes:

[Camron Collinsworth]
alright. I met 1 30, not at 3 my apologies alright.

[Ben Bettencourt]
How's it going, Ben? Oh, what's going on with you guys doing fantastic!

[Camron Collinsworth]
It's great to meet you so we are Kitty Cat Studios.

[Camron Collinsworth]
We're the team working on this project I'm Cameron, the appointed team lead for this sprint.

[Camron Collinsworth]
So let's go ahead. and get this started is there anything opening up that you wanted to say about the project to given that you've worked on it before.

[Ben Bettencourt]
Yeah, yeah, I'm not sure how much He told you guys about the project or about about me.

[Ben Bettencourt]
But i'm i'm a graduate student at Bsu. actually i'm I work on a research team there.

[Ben Bettencourt]
And I I was a senior last semester, and I worked on this project.

[Ben Bettencourt]
So I actually reached out after last semester to Professor Henderson, because I know that it's kind of a pain to get broncod drum in an ide and get source control setup. So I I really reached out to be like hey?

[Ben Bettencourt]
If you need me to come in and help them get set up on things let me know.

[Ben Bettencourt]
And he's like why don't you just be the sponsor.

[Ben Bettencourt]
So here I am. So I will try my best to be a good sponsor and whatnot so i'm interested to see what you guys you guys, have planned.

[Camron Collinsworth]
Yeah, just pulling up some of our plans right now, so we could go over them.

[Camron Collinsworth]
So. One thing that we we really wanted to focus on was the Ai as well as making a new map for broadcat room.

[Camron Collinsworth]
Did you have anything we were thinking? We talked about this briefly.

[Camron Collinsworth]
For a map, having kind of the area around the Student Union Union Building, and then possibly even connecting it to the current map.

[Camron Collinsworth]
Because I know that's at the bsu stadium and so those like geographically are located very close to one another.

[Ben Bettencourt]
Yeah, Henderson kind of wanted something to he mentioned having students be familiarized with the area.

[Camron Collinsworth]
I'm not sure how well we could really do that but maybe if you had any suggestions or wanted to speak to that at all.

[Ben Bettencourt]
Well, that's what he told us last semester as well. the issue that we had as the second team coming in

[Ben Bettencourt]
Well, there were a couple of issues. hello you! I guess so.

[Ben Bettencourt]
First and foremost, the first team that took care of this a year ago.

[Ben Bettencourt]
Now when they set it up they didn't set it up with persistent levels, which i'm not sure how many of you have used unreal before.

[Ben Bettencourt]
So persistent levels is the go to nowadays with unreal and essentially what it does?

[Ben Bettencourt]
Is it heavy loads? everything at the beginning so you don't have large loads times during the game.

[Ben Bettencourt]
The only reason why bringing this up is because Bronco Drum Isn't set up that way and then you will run into issues with that.

[Ben Bettencourt]
And when you look at the Api 9 times out of 10, they will mention persistent levels, and it's just not set up that way.

[Camron Collinsworth]
So I I want you guys to be aware then right away.

[Ben Bettencourt]
We tried looking into refactoring, but that's just going to take so much time.

[Ben Bettencourt]
That that might be a semester thing in and of itself, just to try and get it refactored into persistent levels.

[Ben Bettencourt]
Just be careful of that. So when you add new levels, just just keep in mind as gonna it's gonna up the load time, Which is it necessarily a bad thing?

[Ben Bettencourt]
Just just something to watch out for. another thing to watch out for.

[Ben Bettencourt]
That we tried tackling a little bit last Semester is we don't want to shoot other students in the game right?

[Ben Bettencourt]
So when you're looking at enemies we tried at least the Ai team on our in our team last semester, they tried to give the guy some kind of personality.

[Ben Bettencourt]
But it's it's so minute that it's hard to even tell

[Ben Bettencourt]
So yeah, you'll have to watch out for that when it comes to locations.

[Ben Bettencourt]
I think the student Union building around there that'd be nice it's gonna be kind of hard to model all that.

[Ben Bettencourt]
So you're gonna have to have someone probably dedicated to modeling.

[Ben Bettencourt]
Or multiple people taking it on, I guess. So just just watch out for that.

[Camron Collinsworth]
But I I would think that it's a good a good avenue, and then to tweak the ai so that it's maybe more more smarter, obviously.

[Ben Bettencourt]
But yeah, I think that's I think that's a good path to go on.

[Camron Collinsworth]
We've all had the chance to play the game at least I believe so.

[Camron Collinsworth]
And yeah, we could tell that the Ai is quite rough along with

[Camron Collinsworth]
The movement a lot. It just feels really floaty, like the the physics of the game.

[Ben Bettencourt]
Yeah, and and believe me, when I say it it's a huge improvement from when we got our hands on it.

[Ben Bettencourt]
Yeah, there were. There were no goals there. were no scoring there was you couldn't even die.

[Ben Bettencourt]
And so they were just. There were so many things that were wrong with it when we got our hands on it.

[Ben Bettencourt]
And that that's all we really want is to see progress here.

[Ben Bettencourt]
So. yes, so tweaking that ai to make it even smarter would be would be amazing.

[Camron Collinsworth]
Yeah, We were also wondering about maybe adding new game modes and new new difficulties, or possibly new new cars, new runners with their own specific attributes. would you care at all if we kind of took a little bit of creative

[Ben Bettencourt]
license with the game or like. Is that an issue with you or No, not necessarily.

[Ben Bettencourt]
So did he talk to you about death drone at all.

[Camron Collinsworth]
He did Some of us have the chance to kind of look at some gameplay as well and then it's hard to even emulate it.

[Ben Bettencourt]
I think one of our guys on our team was able to but I couldn't figure out how they actually emulate it.

[Ben Bettencourt]
So yeah, yeah. in in death drone, they have different runners that you could choose from, and you could unlock and whatnot.

[Ben Bettencourt]
So something like that would be would be kind of interesting to see as well.

[Ben Bettencourt]
And that would that would give you guys a little bit more creative.

[Camron Collinsworth]
Leeway. so that would be that would be cool to see cool

[Camron Collinsworth]
Aside from that, We're just gonna focus on you know some general improvements to the game making it just feel a lot more polished.

[Camron Collinsworth]
Is there anyone else from the team that wanted to jump in and speak about anything real quick before you move on to?

[Nathan Maroko]
Maybe some of the some like stretch polls that we'd like to like to accomplish Yeah, I wanted to mention just something real quick.

[Nathan Maroko]
So when it when it comes to polish, I just had a couple ideas in mind.

[Nathan Maroko]
I just wanted to run that through you before actually committing to that and deciding some like things that I was thinking was maybe when jumping, there could be a really soft rumble on the screen, and maybe some particle effects like

[Nathan Maroko]
some lines that come off. and then, when the vehicle lands again, kind of a bit of the same maybe some dust particles something like that.

[Nathan Maroko]
And then I was thinking maybe when when shooting too, there's maybe a soft rumble, a little more feedback on that regard as well.

[Nathan Maroko]
The power ups I was thinking maybe when you call it there's I don't know if there's a sound effect.

[Ben Bettencourt]
I I tried to, but the there seems something weird. Okay, cool.

[Nathan Maroko]
Then I was thinking in that case, maybe a designated sound effect for a specific power up each part of has a different sound effect, or something like that.

[Nathan Maroko]
And then some text on the screen that says collected this, and maybe like a a timer that says, how long you have that power up for?

[Ben Bettencourt]
Yeah, that that all sounds fantastic. Cause: Yeah. So there were No, there were there.

[Ben Bettencourt]
I can say there were no power ups there was one power up that that we were, that when we got it it wasn't even really implemented.

[Ben Bettencourt]
So what would happen when we first got it? It was the speedup power up, but it only tricked.

[Ben Bettencourt]
If you were standing still. which for speed up power up doesn't make a lot of sense right?

[Ben Bettencourt]
So obviously we tried to add a bunch of power ups in and we tweaked them a bit, but we never got around to

[Ben Bettencourt]
Those refinements, So that would that would be nice to see as well for that polish.

[Nathan Maroko]
Yeah. cool. Yeah, I mean, those are most of the ideas that I had currently.

[Nathan Maroko]
But if I think of any, am I? Am I free to email you with those ideas?

[Ben Bettencourt]
And yeah, Absolutely. Okay. cool. Thanks. Is there anything in particular you really wanted to see out of us for the semester, like any specific advancements?

[Ben Bettencourt]
I think the Ai would be probably the biggest, just making sure that the the game is really you know, actually fun.

[Ben Bettencourt]
You know we got it our team. got it running and got the goals set up right.

[Ben Bettencourt]
We we actually set the goal post because you can't really have a game.

[Ben Bettencourt]
If there's no goal. but but when it came to tweaking things.

[Ben Bettencourt]
That's where we kind of fell through that all those short So just to see that kind of thanks and fun, I guess, would be nice, you know.

[Ben Bettencourt]
And yeah fixing ai getting those polishing that'd be great.

[Ben Bettencourt]
And then, obviously, if you guys i'm not sure if you guys want to have the other level as a stretch, maybe

[Camron Collinsworth]
But that's that's completely i'll i'll leave that up to you guys, because if you guys want to focus on making a new level like i'm i'm down for that as well you know as for like

[Camron Collinsworth]
bookkeeping and checking in with you. is there?

[Camron Collinsworth]
Would you like us to have like scheduled emails?

[Camron Collinsworth]
Or you can have progress reports getting sent to you, and anything like that.

[Camron Collinsworth]
Or is it just come up to us? Would you like maybe one at the end, or

[Ben Bettencourt]
Maybe maybe one every couple of weeks just a just a quick hey?

[Ben Bettencourt]
Here's what we've got you know here's everything that's going on kind of thing.

[Camron Collinsworth]
Yeah, are. are you okay, with the the license I I can't remember the current license on it. but it's I don't think it's Yeah, I believe it's mit I I don't recall looking

[Damian Sappington]
at it, but I would I wouldn't doubt it it was an it so, hi, it is mit yeah okay, cool.

[Ben Bettencourt]
Yeah, yeah, just leave it like that that's fine we're not looking to, to to sell it or anything like that.

[Camron Collinsworth]
Did you have any issues run getting an executable out of unreal by chance?

[Ben Bettencourt]
I think that's something we were trying recently. it was a bit of a pain.

[Camron Collinsworth]
Yeah getting the windows one wasn't too bad the Linux exe was was was the most difficult, I believe.

[Ben Bettencourt]
But those are the only 2 that we that We were asked to deliver was was a windows, and it Linux and I was in charge of that.

[Ben Bettencourt]
But it's been months I still have those exes in my Google drive.

[Ben Bettencourt]
Yes, I do but when it comes to the process i'd have to, i'd have to try it out again myself.

[Ben Bettencourt]
It does take a long time, though, like it'll take maybe 1520 min, I believe, depending on on your rig.

[Camron Collinsworth]
My rig's, not top of the line but but yeah, it'll it'll take a while. and even then you might run into some issues.

[Ben Bettencourt]
If anything like deprecates or something like that in the code which you're using an older version or we use an older version of because that's what the original team did as well.

[Ben Bettencourt]
They used chaos, I believe. which I think is like 3 or 4 marines behind something like that.

[Ben Bettencourt]
There will be some issues that you'll have to kind of scratch around to see what you can do.

[Ben Bettencourt]
If that makes sense. Yeah, getting those executables was was kind of tough.

[Damian Sappington]
What kind of issues have you guys seen so far I just didn't let it run long enough, so i'll try on my my Pc.

[Ben Bettencourt]
Is pretty good. I'll see if they can get to that 1520 min mark.

[Quinn Shultz]
I actually had a error when I launched the executable after meeting it it was like a index out of bounds.

[Tavi Kohn]
Error. I'm not sure what it is interesting Let me

[Camron Collinsworth]
Hello, i'm curious about a couple of things one is what the over our ching sort of goal of the original project was, and if we should be following that at all So the original sponsor wanted

[Ben Bettencourt]
just something that was close to depth Drum because he was a fan of that game back when he was younger.

[Ben Bettencourt]
So and we've got it close to that so just just getting it even closer.

[Ben Bettencourt]
Would be would be good. So So yeah, So anything that you can see that might further that to just to get it closer to what death drum was would be would be ideal which improved ai and more

[Ben Bettencourt]
polish and stuff like that is is exactly on that path.

[Camron Collinsworth]
Okay, I think our team is mostly been thinking about improvement.

[Camron Collinsworth]
That will make the game more fun and just better in general.

[Ben Bettencourt]
Yeah, So it seems like going in that direction it's also Good.

[Ben Bettencourt]
Yes, yeah, absolutely. sorry i'm i'm downloaded the deliverable that we had, and i'm unpacking it.

[Camron Collinsworth]
Obviously like I said this was I. I made these like months ago.

[Ben Bettencourt]
So. i'm gonna see if I can run it see if I get that error.

[Camron Collinsworth]
Hopefully. would it be worth it? Trying to update this project to a newer version of unreal?

[Ben Bettencourt]
We we have that same idea when we took the project on it it I would say, if you want to look into it, maybe maybe give yourself a timeline of a week to see if you can.

[Ben Bettencourt]
If you're if you're getting to that point where it's just it's gonna take too much effort.

[Ben Bettencourt]
Just forget about it. kind of thing you know, but if you think that it's worth it.

[Ben Bettencourt]
I would say, go for it. and it might very well be because if you can get it updated

[Ben Bettencourt]
Then, yeah, you might be able to use some of the someone more cutting edge packages and stuff like that.

[Ben Bettencourt]
The more optimized stuff. So yeah, just just try not to get bogged down on.

[Ben Bettencourt]
I guess So so hold on. Let me I don't know how loud this is gonna be.

[Ben Bettencourt]
Let me on the executable. You want me to share my screen with this

[Ben Bettencourt]
It'll ask me if you try to I think right so all it says is host disabled participants screen sharing crap.

[Ben Bettencourt]
Does everybody know how to do this? I do Go ahead and give me.

[Camron Collinsworth]
Make me a co-host, There should be like an error or an arrow go to share screen.

[Camron Collinsworth]
You see, the carrier share screen advanced. Oh, okay, there we go.

[Ben Bettencourt]
You should be able to cool. I also made anecdotes so awesome.

[Camron Collinsworth]
Alright. can you guys see the bronco drone?

[Ben Bettencourt]
Alright. So yeah also if you click on this it'll give you a list of the previous people who worked on it.

[Ben Bettencourt]
And then there's also room for you guys to add your names, and on that I did. My primary goal was getting high scores.

[Ben Bettencourt]
And I was also team lead. So I was kind of wrangling everybody in the at the same time.

[Ben Bettencourt]
Okay, So let's see

[Ben Bettencourt]
Another guy in our team. did this updated music

[Ben Bettencourt]
So another thing that I remember that was kind of weird when we were looking at it was like your gun will shoot down so sometimes like the the checkout will hit the ground before it hits the enemy runner.

[Camron Collinsworth]
Yeah, that's really nice also could you speak a bit about the aiming system, or you're kind of like through play testing, not really understanding what the goal with aiming was and we're trying to narrow down on like

[Ben Bettencourt]
a method of locking on the enemies. Yeah. So that was actually the original team.

[Ben Bettencourt]
The regional team set up that aiming so we didn't do anything with the aiming other than we made new models and stuff like that, and that's it so we didn't tweak that at

[Damian Sappington]
all. So is it. We need new projectiles. because before the checkouts were just spheres that you were shooting out. so we tried to make them more laser like. Is it targeting based off of who's

[Ben Bettencourt]
near the radius it should be. It should be the closest enemy, if I remember critically. Okay, Yeah.

[Ben Bettencourt]
So what if it's like behind you won't target but if it's in front of you and close enough they will target it right.

[Andrew Jacobsson]
I believe so alright way. too fast it's like No, that's an issue that we had before as well excellently go back to the main menu do you know if they're what what

[Ben Bettencourt]
they're using behind like the auto targeting was in the beginning, because the the original background doesn't have. I can't remember how death drone did it I wanna say they had something similar either it was either auto

[Ben Bettencourt]
targeting, or it was just shooting straight in front of the of the runner.

[Andrew Jacobsson]
Yeah, cause from the gameplay. I saw I I thought that's how they did it that it just shot where you pointed instead of like pointing towards the enemy.

[Ben Bettencourt]
But, my gosh, that painting ridicule is not happy.

[Damian Sappington]
Yeah, I found that the Radical being very strange and random, it almost feels awkward.

[Ben Bettencourt]
Yeah, So there were what you'll find is especially with the older version of unreal.

[Ben Bettencourt]
There are a lot of you're gonna have to get creative with a lot of your fixes and stuff probably just just as a heads up the high scores.

[Damian Sappington]
It's literally a text file mike I literally just wrote to a text file, and then I had a checking thing that was read.

[Ben Bettencourt]
The text file and that's that that also leads into we'll lead back into the resistant Levels issue that I was talking about before, cause, like if you have persistent levels.

[Ben Bettencourt]
You can. You can save variables just in the upper level, and it it can go to everything.

[Ben Bettencourt]
But since the levels are technically disjointed, I click too fast again.

[Damian Sappington]
Since the level are just too disjointed it's it doesn't work that way.

[Ben Bettencourt]
I clicked too fast. I wasn't able to save my high score.

[Damian Sappington]
But yeah, yeah, okay, So if we wanted to go about changing the shooting system, because i'm watching this death drum video back again, it looks like it's going just in front of like it's just shooting.

[Damian Sappington]
Straight. so wherever it's targeting in its forward position it's just shooting straight instead of the weird ai targeting.

[Ben Bettencourt]
Yeah, would that be a thing that we could potentially change?

[Ben Bettencourt]
Maybe as a stretch goal. Yeah, yeah, if you wanted to see a change that might That might be better, cause that that would be more like death drum. And I don't think it would be a difficult thing to implement instead of the targeting it would just have to we'd

[Damian Sappington]
have to take away the targeting that it has essentially straight on click.

[Ben Bettencourt]
I guess my my biggest or i'm at my my advice would be just to be careful, because like if we're gonna take away the auto targeting and just have it shoot in front of the the the runner we would need to

[Ben Bettencourt]
tweak the how the runner moves so it could move much more smoothly.

[Damian Sappington]
If that makes sense. watching even like this test on video, when it bounces a lot of the part of deaf drone and obviously pumpkin drum, is that when it bounces off of obstacles or like

[Damian Sappington]
a wall. It kind of glides itself towards looking at something other than the wall.

[Damian Sappington]
But in the current game that we have, it just sticks on the wall for a second.

[Ben Bettencourt]
Yeah, that was something that one of our guys was supposed to take care of.

[Damian Sappington]
But he never got around, too, that gives us good ideas of what more we could implement.

[Ben Bettencourt]
Maybe later on. Yeah, Yeah. and that that the way that he said it to the team when he proposed doing that was like, Well, if you think about Mario cart right? you kind of just bounce back a little right and it's a

[Damian Sappington]
good idea. it it, you know. it helps the flow of the game and whatnot. So that that is a good idea to do, and it shouldn't be too hard to implement. I see that.

[Damian Sappington]
But yeah, we all know how this works it shouldn't be too hard. But it might take a week or 2 of work.

[Damian Sappington]
And maybe yeah, yeah. So something yeah, good ideas, good ideas. And with the shooting, I think we were imagining it to be like a toggle on and off, or it correlates with difficulty.

[Nathan Maroko]
Settings. So if we have like an easy mode, the auto targeting can be turned on.

[Nathan Maroko]
But if we have like a like a bronco mode or something like that, I don't know It would be more.

[Damian Sappington]
It would be the straightforward Gotcha.

[Ben Bettencourt]
Yeah, And if you do that, you might even make like auto targeting like a like a power up or something.

[Damian Sappington]
Yeah, that'd be good was no turning without moving no, not not really.

[Ben Bettencourt]
We really Didn't touch much of the movement we were using a lot of what was given to us in that sense, so I don't think so.

[Damian Sappington]
I I wasn't part of the original team who set that up the the original movement setup.

[Ben Bettencourt]
So I don't think so I think they were because when we got it it was essentially more of a tech demo.

[Ben Bettencourt]
It was like, Hey, look! you have this card. You have a gun.

[Ben Bettencourt]
It can shoot these spears. So it was more of a proof of concept, I guess, than anything else, And then we got it, and we tried to make it more of an actual game.

[Ben Bettencourt]
So we wanted to. an actual game loop. That was our big goal.

[Ben Bettencourt]
Last semester was to just have have a functional game loop.

[Damian Sappington]
Maybe not the best to the most fun one. But yeah, definitely functional.

[Ben Bettencourt]
So that yeah, So So yeah, when it came to tweaking like movement and stuff like that, that all got pushed to the side.

[Damian Sappington]
For the most part. Okay, what else do We need to go over our milestones camera?

[Camron Collinsworth]
Julie, I have them right in front of me. milestones.

[Ben Bettencourt]
Toby I believe. so i've been they used a a package that's specific for chaos. which is actually a good thing to watch out for.

[Ben Bettencourt]
Because if you do update, you might lose that functionality.

[Ben Bettencourt]
But yeah, that's just something to look out for if you guys run into that issue of like, if it if you are looking to update the the version of unreal.

[Ben Bettencourt]
Yeah, just just be careful, because I I think that's one of the very few things that was used with the chaos engine specifically was, they have a a go cart functionality or a library.

[Ben Bettencourt]
I believe they also have some part of particle effects.

[Ben Bettencourt]
That was another thing. There used to be partial effects when you shot.

[Ben Bettencourt]
But when we were given the game, I guess I should mention

[Ben Bettencourt]
The original team, the head, everything in large binary files, A.

[Ben Bettencourt]
An Lbf. which in theory it should have made it a lot easier to like

[Ben Bettencourt]
Pass it along to people and whatnot. but what it ended up happening is, if I remember quickly, Lbfs

[Nathan Maroko]
You set them up on a server. Essentially you have it connected to a server, and whoever had set it up, they were no longer a part of anything to do with Braco Drones.

[Ben Bettencourt]
So when we got the Lbf files we couldn't we couldn't actually get onto his server to get everything.

[Ben Bettencourt]
So we actually had to revert back, and he was. It was a big whole deal.

[Ben Bettencourt]
It took us like a month of our initial time when we got it.

[Ben Bettencourt]
So it's kind of a mess so I like the particle things that we had.

[Ben Bettencourt]
It was kind of messed up like it was shooting out errors, and I I don't recall if we just turned it off or not.

[Damian Sappington]
It's been so long. I apologize about that I don't think there's any particle effects anymore for shooting. I don't think so.

[Ben Bettencourt]
I think it's just shooting out like a a little *d.

[Ben Bettencourt]
Object.

[Ben Bettencourt]
On top of your head. Do you remember what the ai subjective is?

[Ben Bettencourt]
Yeah. So I was not part of the Ai team, but the Ai team, the way that they said it is

[Ben Bettencourt]
If the Ai gets close to anything like a wall, or another runner, it will try to turn away from it, which, as you've noticed correctly.

[Ben Bettencourt]
Mr. Cameron Seoul: Yeah. it usually results in them just running around in circles.

[Damian Sappington]
Yeah, I notice that they get caught there's a part on the broncos that they get caught under, and they don't get out of definitely one of the things we'll try to fix on that Yes, Yeah, I was not I was

[Ben Bettencourt]
not part of the Ai team, But that was that was what they got cause yeah, before.

[Ben Bettencourt]
Yeah before, if i'm ever kind of little we got it they wouldn't even move.

[Ben Bettencourt]
So yeah, again, : improvements not perfect, cool, cool.

[Ben Bettencourt]
Yeah. So I was looking over the milestone I know.

[Camron Collinsworth]
It was milestones is brought up I don't think anything that we have written down is terribly relevant for this meeting.

[Camron Collinsworth]
One thing our team did talk about is that we are a 100% committed to getting multi butter up and running.

[Ben Bettencourt]
I know we all agree to that. that would be that'd be cool to see

[Ben Bettencourt]
That was one thing we talked about in our team, but that really has to be one of the major focuses for for a semester.

[Ben Bettencourt]
Yeah, at least in our mind. when we were looking at it.

[Ben Bettencourt]
Cause yeah, it's gonna that's probably gonna be a lot of work.

[Ben Bettencourt]
But that would be cool to see it really would I remember I made Gosh!

[Damian Sappington]
I'm not sure who out of all of you who has it already set up in your id and whatnot I do, sweet sweet, because i'm not sure if he passed you guys or not.

[Damian Sappington]
But we made a a long read me of like how to get things set up and whatnot It was helpful awesome.

[Damian Sappington]
So we did pass it to you guys awesome, or at least just the breeding, like I just went through the read me and worked out.

[Ben Bettencourt]
So okay, cool. I I know I have it here somewhere, like Google drive.

[Ben Bettencourt]
Oh, my goodness

[Ben Bettencourt]
Anyways. If you guys have it that's great it's just we had one thing I will warn you guys about is unreal doesn't really work well with version control.

[Ben Bettencourt]
If I remember quickly, I put in that read me like how to do it.

[Ben Bettencourt]
But it's still kind of a slog like You'll have to jump back and forth between unreal and vs.

[Damian Sappington]
Code and and not be as good just visual studio.

[Ben Bettencourt]
Yeah, it's it's doable just be careful It may. It makes version control harder than it has to be.

[Damian Sappington]
Okay, there is in unreal chaos. There is its own, like virtual control.

[Damian Sappington]
Settings that you can try tweaking but we couldn't forget that figured out so we just used that weird method of jumping back and forth between digital studio and and unreal like you'd

[Damian Sappington]
you'd have both up at the same time you'd make a change, and i'm real, and then you would go over to visual studio and make sure that it's logging that that thing changed you would push it

[Damian Sappington]
up from visual studio. Oh, which yeah it you'll get you guys will run into those issues as well but I've been there.

[Camron Collinsworth]
I know it's a pain so just Do your best to avoid taking up too much of your time. I know you're a busy grad student.

[Camron Collinsworth]
We're coming up on 30 min so I just wanted to open up ebay on the team.

[Camron Collinsworth]
Has any final comments, or if there's anything that you'd like to say to us before we sign off anybody

[Camron Collinsworth]
I suppose that's it? Then I really appreciate having you we all do.

[Ben Bettencourt]
Is there anything you'd like to say before we leave or you guys are always pretty email me so like I said it's been a few.

[Ben Bettencourt]
It's been a few months and like you said i'm a busy grad student, so I got so much stuff that's coming in that I have to push out other things.

[Ben Bettencourt]
But I have my old files and whatnot for broncos drum.

[Ben Bettencourt]
So if anything happens, let me know I can. I can dig back into what we did and what not, and tried to help out.

[Ben Bettencourt]
I know you guys said you had. You were getting some errors when trying to run it.

[Ben Bettencourt]
I know. Yeah, I don't know what's going on

[Ben Bettencourt]
I have the executables that we had for our presentation.

[Ben Bettencourt]
If you guys ever need those. But i'm not really gonna do too much for you.

[Damian Sappington]
I don't think but but yeah you guys are always free to email me.

[Ben Bettencourt]
I might not get back right away. but and then if you ever see me at the Ccp.

[Ben Bettencourt]
I'm not usually there. I try to stay remote I have some things at home that I have to watch out for my dog.

[Camron Collinsworth]
He's kind of towards the end of his life yeah.

[Camron Collinsworth]
So I constantly have to hey karen party hear that? No, you're good. you're good. but if you ever see me at the Ccp.

[Ben Bettencourt]
You're more than welcome to say hi and whatnot I'm, usually on the third floor.

[Ben Bettencourt]
I work with Dr. Fails with the cast team or kids team as well.

[Ben Bettencourt]
So we have our lab on third floor of Ccp.

[Camron Collinsworth]
So have you ever seen me around there? you know, plug it down, if I recognize it.

[Camron Collinsworth]
Sounds good. Thanks again. we really appreciate you taking the time. we'll be sure to keep in touch .

[Ben Bettencourt]
I'm excited to see what you guys, do do you guys need to sign off anything.

[Ben Bettencourt]
No, we're gonna send this recording to Dr. henderson, and you'll take care of that. sweet sounds great or hopefully have something good for you if you have a semester look forward to it all right Thank you you

[quinnshultz]

Summary: Sprint 0 Retrospective

Action Items:

• Plan Sprint 1 Goal

Minutes:

Nathan: Did we have a sprint goal?
Quinn: No, I don't think so.
Annika: For the next map, do we want to use the inside or outside of the SUB.
Cameron: We could also talk about transistioning between maps.
Andrew: I think something that limited this sprint was the lack of communication after our first sprint.
Nathan: Totally agree, in hindsight we could have use the time after the sponsor meeting to discuss more about Sprint 0.
Nathan: I think something that would improve the sprints would be to have the leader make a plan and all stick to it as devs.
Andrew: How do we approve pull requests?
Cameron: We can assign each team to review each teammates pull requests.
Damian: How many pull approvals must be made for each pull request.
Annika: Are there any required comments for approvals.
Andrew: Not that I am aware of, I think we can add them as necessary.
Nathan: Are there any other details about the sprint retrospective that should be discussed.
Annika: The loading time of the map is extremely slow, is this an issue in Unreal or in our project.
Andrew: How does the responsibility of the team lead work across our AI and general team?
Annika: I think they will need to check in during sprint planning meetings.

[CameronSewell]

Action Items
User stories to be created by each member with the goal for the sprint being 4 users stories completed in total
general team sprint 1 planning meeting minutes
Annika, Nathan, Tavi, and I discussed our overall goal: new map, new runners, general gameplay improvements
The point was brought up of whether or not we want to completely overhaul the movement for runners. There have been
thoughts among the team of updating the engine version and the sponsor informed us that in doing so we would need to completely
redo the movement system as it is depended on modules specific to chaos. This discussion was tabled as it seems like it would
also affect the AI team and needed to be a full team discussion. we decided that our sprint goal for sprint 1 would be
to get 4 users stories completed. we all want to work on different aspects of the game so we thought it would be more fun to take over
a section of interest and base our sprint success purely on story completion.
Annika will work on the new map,
Nathan will work on polish and UI,
Tavi will work on general game play improvements as well 3D Models
Cameron will work on implementing new runners.

Each member will write their own user stories and task to accomplish these goals. Depending on the size of some
feature they may be broken up into smaller users stories spread across multiple team members

[timblegoorn]

Date: 9-15-22 (1:30PM - 2:40PM)
Excused: None
Absent: None

Summary: Project Plan & AI Sprint 1 Planning

Team meeting (AI and GENERAL):

We started the meeting with Tavi talking about if we switch unreal engine version. Ultimately, we decided that we would not change the current engine version but that future development work that we do will not conflict with future versions of Unreal so that if it is ever upgraded it will be easier to do so.

We then talked about the project plan and getting the final copy completed. Annika mentioned that she incorporated some of the feedback already received from the professor. We discussed the architecture diagram and determined we would come up with a higher level class diagram with a flow chart for AI behavior.

The team then began working on the project plan briefly, going over some of the sections, primarily improving 1.1 incorporating instructor feedback. After about 15 minutes we decided that we would continue this work through communicating via Discord with a goal of finishing it this weekend.

At approximately 2:05PM we split up into two separate meetings for each team.

Team meeting (AI):

We began by talking about potential story ideas, but then brought up the question of if we should refactor the AI since its current state is extremely rough. We determined redesigning the AI from the ground-up would ultimately allow a more streamlined design process that would be easier than fixing the existing AI. Our goal is to tear down the existing AI and produce a new AI with the equivalent features (albeit working) over the next 3 sprints.

We came up with the following sprint 1 goal as a result:

Sprint 1: Remove existing AI functionality and Redesign AI - Spawn new modular AI agents based on difficulty levels and provided parameters

Effectively, in sprint 1 we will focus on stripping down the present AI to its barebones and redesigning it with better systems in place, with the goal being improved AI spawning with modular attributes based on difficulty levels for this sprint. The AI will not be functional, but will have a good spawning algorithm and have their base attributes built so that the next sprints can build on those attributes for AI functionality.

We determined we would begin coming up with stories on our own and reconvene over text on Discord later this evening to write our stories on Github and assign them. We will creating a AI specific branch in the repository so as not to interfere with the general team.

Action Items

• AI team come up with stories for Sprint 1
• Finalize project plan
• AI architectural diagram

[timblegoorn]

Date: 9-16-22 (6PM - 7:30PM)
Present: Andrew, Camron, Damian, Quinn
Excused: None
Absent: Andrew (I was absent for the first 30 minutes of the meeting but joined in at 6:30pm)

Summary: AI Sprint 1 Story Planning

Team meeting (AI):

We talked through what we want to work on and how we want to redesign the AI. Damian set up a new team specific branch for the AI team. Damian is going to kick things off by cleaning out the existing AI system in place and the rest of us will begin re-implementing a new and improved AI system. We all worked on writing our user stories and making sure we were all okay with them and signed off by the product owner (Camron).

We then worked on the Project Plan AI milestones and talked about designing our architecture diagram. Quinn will be working on decision trees for the AI and will add that to the AI architecture diagram.

Action Items

• Continue to work on project plan and clarify AI milestones and design decisions

[CameronSewell]

Meeting notes from 9-15-2022
discussion about new engine version
tavi - three possibilities, stay on chaos and try not use chaos dependencies, migrate to a new version. middle option
is preferred
quinn - runners movement is what depends on chaos so we could find a different way to implement that
nathan - likes the middle ground proposed. engine update could be a stretch goal. lay the ground work
for the next group to switch over
tavi - next item is project plan
damian - end products and architecture are outstanding

tavi- we need to incorporate feedback and architecture should be a model of how the game functions
it will probably be closer to a higher-level class diagram
Camron - is ai structure in unreal modeled in a tree structure anyway?
Damian - does the GitHub have the old architecture?
tavi - does anyone have strong feelings about future architecture?

no one really said yes

Nathan what sections need to be done
tavi - architecture and deliverables
Camron - and incorporate feedback
Nathan - we removed all the empty sections before we submitted so we need to add those back

tavi - so what parts of the architecture do we need to incapsilate our end goal of a generally better game
nathan - a flowchart is probably the easiest way to show how everything interacts with each other as well as a timeline
of improvements
tavi - we could make a flowchart of what we want users to experience
anika - that would require too much user testing
nathan - we should split into our two teams and define general and ai architecture separately

sections of the plan
1.1 - we need to refer back to the end goal
1.2 - done
1.3 - needs to be a lot more specific
2.1 - needs at least one alternative approach
2.2 - architecture
3.1 - done
3.2 - needs work
3.3 - needs work
4 - done
5 - done

general team

tavi - we could use the class hierarchy of the game
nathan - agrees
nathan - how are we splitting that up
tavi - we need to include the game loop
annika - volunteered to do the entire general architecture

Action Items
get user stories in by Monday

[timblegoorn]

Date: 9-20-22 (2:15pm-2:45pm)
Present: All (Cameron remote)

Team Roles for Sprint 1:

• Team Lead: Nathan
• Scribe (general): Cameron
• Scribe (AI): Andrew
• Product Owner: Camron

Summary: Continuous Integration & Sprint 1 Update

Team meeting (General & AI):

Our current continuous integration works for the most part and tries to build a Linux build (but currently fails), and the Windows build is currently disabled. The biggest issue is we have a ton of linter errors from the existing codebase. We talked about the pros and cons of the current build system and ideas to fix it, put a band-aid on it, or just try other solutions. We ultimately decided that we should fix the existing script. We talked about each team's workloads and how they're feeling to see if anyone would want to take on the workload. General team is feeling like they have a pretty heavy workload. AI is feeling pretty good about things. Quinn said that he could work on the CI and we concluded that we would try to get it to build the code and fix the existing code for the linter errors.

General team talked a bit about the workload regarding building the new map. Talked about redesigning the map structure as our sponsor mentioned that there isn't persistence between maps. Talked about removing rain map (since it's nonfunctional anyways).

Action Items

• Fix existing CI system to actually build the project
• Fix existing linter errors in the current codebase

[timblegoorn]

Date: 9-22-22 (1:30pm-1:50pm)
Present: All (Nathan/Andrew remote)

Team Roles Currently:

• Team Lead: Nathan
• Scribe (general): Cameron
• Scribe (AI): Andrew
• Product Owner: Camron

Summary: Discussing Sponsor Feedback & General Discussion

Team meeting (General & AI):

Our primary purpose of meeting today was to discuss the feedback brought up by our sponsor from our project plan. The problems in 1.1 was a simple wording fix. The 1.3 problems, we agreed with the sponsor for the most part, we will yield to the sponsor's feedback, but may revisit the power up spawning locations as a stretch goal for increased difficulty. The 3.1 problem was a typo/misunderstanding.

We also talked about where we were at in our sprint and how we need to get into gear.

Action Items

• Revise project plan and send to sponsor
• Add "practice mode" with map selection, with no high score
• Actual start working and getting our stories done

[camronCollinsworth]

AI - Meeting
date: 9/27
Excused: none
Absent: none

Summary: Planned for sprint 2 and spoke about troubles and insights learned from the first sprint. Ultimately decided to give another 2 days to think more about quality stories to make it into sprint 2

Damian: stated that he wants to work on ai shooting. Possibly implementing new raycast system
Andrew: wants to randomize ai spawning locations and further ai spawning work
Quinn: this sprint, he would like to work on the movement and go further with his current decision tree work
Damian: we need a sprint goal.
Camron: sprint goal could relate to perception
[…] team discussion about raycast difficulties […]
Damian: We can work more on making stories on Thursday
Team: agrees
Quinn: yeah that will give us time to work on the the project over the weekend.
Damian: we did a good job about pull requests last sprint
Andrew: so what was our buzzword for the sprint goal? AI perception?
Damian: I think we have a decent idea on stories, let’s just bring more for Thursday
[…] team discussion about merging our dev branches […]

Action Items:

• Create new stories for sprint 2
• Begin work on sprint 2
• Fix current project branch structure

[Nathan-Turtleduck]

Sprint Planning
General Team Meeting Minutes 9/27/22

Present: Everyone

Summary:
We decided our sprint goals and began defining our user stories. We decided that we wanted Tavi to take care of the runner model mockup, Cameron is going to make the new class for runner stats, Nathan is going to adjust powerup behavior, and Annika is going to finish the model for the new map. Cameron is thinking we have a slow car with good traction thats larger then a fast one that has poor traction. Tavi is going to make models that reflect the look of cars that would behave like that. Cameron and Tavi are planning on meeting to discuss the specifics of those vehicles and their stats. Annika is going to make a custom mesh for the map. Based on the user story defined as “Powerup Polish”, Nathan will complete that.

[camronCollinsworth]

[ 9/28 ]
Excused: None
Absent: None

Summary: The main talking points of this meeting were regarding what we were working on for this sprint as well as what the current plan is for our development branch. There have been changes in the way our workflow is set up since the last sprint, so there was some necessary discussion about how we all plan to integrate changes for this sprint. There was also discussion about specific stories and and some time taken to have a general understanding of what we are all working on and how each of our work fits in with one another.

Action Points:

• Create Sprint Stories
• Clarify with general team about new branch structure
• Merge necessary branches and resolve conflicts
• Improve CI
• Begin work on sprint 2

[Nathan-Turtleduck]

General Team Meeting Minutes 9/29/22

Present: Everyone

Summary:
The purpose of this meeting was to get on the same page about the user stories that were going to be worked on this sprint. We decided that our meeting schedule for upcoming sprints will be that we'll meet the first week of the sprint and then if we got enough work done over the weekend, we'll meet on Tuesday. If we happen to not get that much done over the weekend, we'll use Tuesday as a day to work on the project and then meet on Thursday. We discussed the potential of using a different technology than Git LFS to store big files. Git LFS has no way to deal with merge conflicts, it just overwrites previous changes on that file. We decided to make a plan to avoid issues like this. We are going to be communicative about what files (non cpp files) we're currently working on. We need to merge quickly to ensure that bottlenecking doesn't happen on stories.

Action Items:

• Begin working on stories over the weekend
• Have commits done before next meeting
• Talk with team over discord about file communication
• Email Ben about Git LFS, how his team avoided overwriting issues

[Nathan-Turtleduck]

Meeting Minutes 10/4/22
Excused: None
Absent: None

Summary: We each discussed the progress we made on our user stories. We all were able to get a commit in except for Tavi so unfortunately we didn't complete that action item from the last game. Annika showed off the progress she made on the SUB map, Nathan discussed his findings with the powerup spawning, Tavi showed off the existing cars that have been made in the past semester and we discussed changes we wanted to make to them. We also created a discord channel to drop in inspiration photos for new cars.

Action Items:
Continue to work on assigned user stories - Everyone

[camronCollinsworth]

Meeting Minutes 10/6/22
Excused: None
Absent: None

Summary: The AI team discussed our current progress on our sprint as well as talked about certain issues that we have run into thus far. Main talking points included Quinn giving us updates on his docker and Jenkins pipeline. There was also a brief discussion about the new AI spawning system and AI decision making. It seems that we may need more time to iron out issues with decision making because it currently might be changing the action of the AI runner every frame. The team also floated the idea of having more collaborative work time. Possibly over the weekend.

Action Items:

• Continue work on sprint tasks
• Collaborate on AI decision making

[annika-mccain]

General Team Meeting Minutes 10/13/22
Excused: None
Absent: None

During this meeting, we wrote the specific user stories for the tasks this week and ensured that everyone was able to put in input for tasks needed for the different stories. Nathan will be doing the Runner Hit Effects which consists of a red flash and sound effect when hit and an explosion particle effect when the runner is destroyed. He will also be dealing with a powerup texture bug. Cameron will continue on the selector screen by connecting the runnerWheel class to it, allowing the user to change their runner, and moving it to the Main Menu. Tavi will continue on the creation of the new runner and the integration of it into Unreal. Annika is recreating the lost level and hopes to have that done by the 18th at the latest. She will also be dealing with creating the UI for the difficulty selection.

We also discussed where we want the scope of our next sprint to consist of we all agreed that we wanted to get a merge to master the next sprint in the second week after we had time to complete some more functional requirements. The AI team had also set up a scrum update that we had moved to the shared channels so that we all can be on the same page and be more unified in the whole group. We created a functional requirements channel to help the group refocus on our project goals and visually show when each is done.

Action Items:

• Create User Stories and tasks
• Begin working on stories over the weekend
• Have at least 1 commit done before the next meeting
• Discuss with AI team our thoughts for next Spint
• Add names to contributors in BroncoDrome

[annika-mccain]

General Team Meeting Minutes 10/18/22
Excused: None
Absent: None

For this meeting, we reviewed what we had accomplished in the last week, any blockages, if we had met the action items we wanted to at this time, and what we are doing for the next week. Nathan was able to fix the texture problems with the particle effects and make them more reliable. He had done this by moving the particles out of the Singleton Spawner and into PowerupSpawner Pedestal and created blueprint events that can be referenced in code. Tavi showed his progress on the current 3D model with no textures yet but is on track to get those together by the end of the sprint. Cam was able to start working on the selection screen and is currently dealing with debugging and is on track to get that done by the end of the sprint. Annika showed off the finished map and will be exporting the map into different formats such as OBJ, FBX, or 3DS to see which is the best to import the map into Unreal. Going forward after that she will be dealing with the difficulty selector. Currently, the only blockage we are facing is Unreal Engine is freezing on startup and can randomly crash. And we all had been able to met the action items we wanted to complete at this time.

Other things we addressed were feedback on the powerup particle effects for Nathan, such as making them smaller and the range they spread out. He was able to get them to a place we liked and got that merged during the meeting. We also created a shared calendar to keep track of team meetings for the remaining sprints.

[dameebsu]

AI Team Meeting Minutes 10/20/22
Excused: None
Absent: None

We each discussed our progress and our implementations. Quinn is continuing to work on the Docker but running into some issues. Quinn's also making progress with the movement system. Camron is also working on movement, trying to find a way to get the AI to get power ups. Andrew is working on the spawning system, specifically the player Runner spawn and using the AI spawning points for the player Runner to spawn at. Damian is working on AI Runner accuracy based on difficulty. We discussed as a group how to implement the accuracy and came up with some good ideas.

We also talked about staying on the same page for the AI decisions using Quinn's decision tree. Also talked through possible movement implementation ideas and thoughts.

[Tavi-Kohn]

General Team Meeting Minutes: 2022-10-15
Excused: None
Absent: None

Topic: Sprint 3 Planning

Cameron
Moving the selection screen to main menu
Test selection screen
Test different runner gameplay

Nathan
Fix pause menu to look like rest of UI
Add freeplay map selection mode
Play cycles maps automatically
Free play allows a map selection and will return the player to the main menu after playing that map

Annika
Bring map into Unreal
Update obstacles in the old map

Tavi
Two more car models, texturing and materials.

[timblegoorn]

Date: 10-25-22 (2:00pm-2:45PM)
Present: All

Team Roles For Sprint 4:

• Team Lead: Quinn
• Scribe (general): Tavi
• Scribe (AI): Andrew
• Product Owner: Cameron

Summary: Sprint 3 Retrospective & Sprint 4 Goal/Planning

Team meeting (AI):

We worked on our retrospective, assigned sprint 4 roles, and then talked about what we wanted to work on for sprint 4. Quinn and Camron determined that movement in its current form is more effort than its worth to try to fix, so Quinn is going to work on trying to implement an external movement/pathfinding library. Camron has had some experience with Docker and volunteered to try to build a Docker image for BroncoDrome. Damian is going to prioritize finding and fixing bugs this sprint and will try to spawn power ups at random locations on hard difficulty as a stretch goal. Andrew will work on implementing manual aiming but it will be configurable so that auto-aim will still be an option. Andrew will also work on redesigning the shot decision for AI, as the current system is somewhat suboptimal and has glaring blind spots. We will likely not have a full team meeting on Thursday as we were able to plan our sprint today, but will communicate and update on Discord as necessary.

Action Items

• Write out sprint 4 stories

[timblegoorn]

Date: 11-1-22 (1:30pm-2:20PM)
Present: All

Team Roles For Sprint 4:

• Team Lead: Quinn
• Scribe (general): Tavi
• Scribe (AI): Andrew
• Product Owner: Cameron

Summary: Sprint 4 Progress Meeting

Team meeting (AI):

Damian worked on a bug where the player lives wouldn't decrement on respawn. He is now working on random power up spawning and will also try to work on more bug fixes the rest of the sprint. Quinn has been working on a summary of the condition of the CI/CD pipeline. He and Camron are going to collaborate to implement the Jenkins Docker container to build an image of the game. Quinn also wants to get started working on implementing the movement library but has not yet started. Camron hasn't been able to get much done as he has been busy, but he will work together with Quinn on CI/CD and will try to polish some of the movement to show off a better looking demo to our sponsor. Andrew fixed a bug that was freezing the game on start, fully implemented mouse-controlled aiming, fixed the cutscene-skip to actually start the game when skipped, and fully implemented difficulty.

We then talked with general team (as they were having their meeting at the same time) and discussed sending a demo of the state of the game to our sponsor, general team brought up concerns of wanting to show off the new map so we will wait to showcase the demo till next week most likely. We also discussed some gameplay design decisions like changing the number of enemies required to kill from the current default and the idea of adding a survival gamemode where the player tries to survive as long as they can against an endless wave of enemies.

Action Items

• Send email to sponsor to touch base and schedule a demo

[Tavi-Kohn]

General Team Meeting Minutes 2022-11-01
Present: All

Progress Checkin

Nathan: Created and integrated level select menu
Note: used the widget editor to create an SOverlay, but not sure how to use it with a C++ widget
Annika: Lighting semi-working, map can be played, no obstacles. Screenshots for level selection can be done soon.
Cameron: Started moving runner selection over to main menu.
Tavi: Didn't meet the 1 commit goal.

General Team Discussion

Using C++ vs Widget editor to make UI elements in Unreal. Some menus are too complex to easily be designed using C++.
Reason for level selection having lines above and below the text: The font contains those lines.
The map was translated into a umap using datasmith so that it's now part of the project, and can be edited in the Unreal editor.
For our functional requirements, the highest priority should be better obstacles and textures.
Need three redesigned runners ASAP.
Please bother Tavi on Discord to get new runner models done.
Level selection may be moved to a new new scene, which may interrupt menu music. Reorganizing the menu music might be a good idea anyway.
Adding new UI elements to the main menu is tricky because it's written in C++, but it's not a significant problem.

Discussion with AI team

AI team would like to have AI runners search for and pick up powerups.
Damian or Andrew may be able to improve the lighting in the stadium scene.
How does data need to be recorded in the gamemode, like what difficulty was selected?
Andrew: Use the BroncoSaveGame to store it across different maps and access it from the level.
Work session over weekend to finish new runner models.
Better handling while driving should probably be punted.
Randomizing powerups can be enabled for specifically one difficulty or for all modes.
Survival mode? (Spawn waves one by one until you run out of lives). Email sponsor for approval, but both teams are on board.
Death explosion effect looks good.
The new hit effects greatly improve gameplay.

[Tavi-Kohn]

General Team Meeting Minutes 2022-11-07
Present: All

Sprint Review

Annika

• Finishing touches on SUB map
• Lighting improvements
• Created new obstacle models
• Feedback: more trees

Nathan

• Improved end of level UI
• Created free play mode and UI for selecting levels
• Manually tested all elements
• Can't reference sound cues from the main menu slate widget, planned to fix tonight

Cameron

• Implemented runner selection
• Added runner selection UI

Tavi

• Created and exported new racecar model

Sprint Goals Met

• Annika
• Nathan
• Cameron
• Tavi

[camronCollinsworth]

11/10 2:00 pm
Absent: [None]

Summary:
In this meeting, we discussed our plans for the coming sprint as well as some issues that team members have been having with the current build of the game. The meeting was fairly short as another meeting was scheduled later in the in day with the entire team.

Action Items:
All members committed to finding and fixing bugs in the current build of the game. Quinn and Andrew talked briefly about lighting issues and how they might be fixed. Andrew wished to redesign the general flow of the menus to make it less clunky. Quinn and Camron will both be working ai movement in order to fulfill the final technical requirement for the project. Damian took on some bug fixes and brought up the idea of merging the ai team with the general team.

[camronCollinsworth]

11/10 5:00 pm
Absent: [None]

Summary: First half of the meeting was between the entire team, second half was with just the general team and Andrew, which I did not attend. Meeting mostly consisted of the two teams catching up with one another as well as discussing some of the things that must be done for BroncoDrome in the coming weeks.

Action Items: Some action items include bug fixes, lighting fixes, testing the new map, adding obstacles to new map, creating two new music files for the new map, UI improvements, and fixing ai movement.

[annika-mccain]

General Team Meeting Minutes 11/10/22
Excused: None
Absent: Annika (Stranded without wifi and my phone was dead so had no way to join)

Summary: We had two meetings today first one was between the general team and we had decided on how to break up the tasks between us all. We had discussed this a bit before in our Sprint Review so we were able to plan regardless of me, Annika, not attending. Nathan will be in charge of finishing the SUB day map by adding the obstacles, AI and player spawning, as well as the powerup spawners. Cameron will take care of the same things but for the SUB night map as well as finishing up the model selection menu. Tavi will finish the new runner materials. Annika will be looking for and fixing bugs that we hadn't yet been able to address.

The second meeting was with the AI team and it was decided that they will be helping test out the new map and there was a discussion of the UI flow and how it might be good to change it a little. For the most part, this meeting consisted of the teams getting each other on the same page for our project and a discussion about reaching out to Ben to set up meetings for the approval and handoff. It was also decided it would be a good idea to do a merge to main to ensure new bugs don't pop up before we go to hand this off.

Action Items:

• Finish the three new runners
• Add finishing touches to the new maps
• Hook up the runner selection menu to the new runners
• Reach out to Ben to set up sign off meeting

[annika-mccain]

General Team Meeting Minutes 11/15/22
Excused: None
Absent: None

We reviewed the things that we had done in the last week and were catching up with the team on where we stood for our sprint goal. Nathan was not able to start on his goals yet as he was dealing with a lot of pain from his wisdom teeth removal. Cam has been working on trying to implement the new meshes on the cars and making sure that it is working correctly. Tavi worked on fixing the reversed faces on the newly revamped obstacles and showed off the new designs of the truck. Annika had fixed a collision problem with the new obstacles and has found and directed a few bugs getting fixed such as blocking volumes on the old maps that weren't implemented correctly so the runner could get outside the map.

It seems like over the break most of the team will have to do some work to make sure that we are able to complete all of our goals. Annika has volunteered to help Cam finish the night map so that the work is a little more distributed. We will be meeting the Monday before the end of the sprint to help ensure that we can get everything done and thoroughly tested. At this time none of our action items have been completed.

[camronCollinsworth]

AI Team Meeting Minutes 11/17/22
Excused: None
Absent: None

Summary:

Discussed our current progress in the sprint and made plans for the rest of the sprint as well as meeting over break. Team agrees that a meeting over Thanksgiving break would be good as this would allow us to catch up on some key features that are being implemented in the near future that will need testing before the end of the sprint. Each member gave a synopsis of what they were working on. This includes bug fixes, movement changes, and changes to the menu as well as a new game mode. The team agreed that we should make attempts to increase the documentation in the project. Both for us, and for future teams. There are some issues with the speed power up that have been causing some trouble aswell.

Action Items:

• Bug Fixes
• Movement Merged this weekend
• Speed power-up
• Documentation

[camronCollinsworth]

AI Team Meeting Minutes 11/22/22
Excused: None
Absent: None

Summary:

The team had a short meeting over the break to discuss our progress on new implementations as well as bug fixes. Some newly found bugs were discussed as well as some talk over the difficulty of recreating previously found bugs and deciding if it is worth trying to recreate a bug that may have been an odd occurrence. The speed powerup is still troubling to fix and movement towards powerups is still proving difficult. However, the rest of movement is implemented. The team agrees that we need to really wrap things up so that they can be tested before the end of the semester.

Action Items:

• Finish / merge movement
• Fix speed powerup
• Bug fixes
• Merge any other changes

[annika-mccain]

General Team Unofficial Meeting Minutes 11/28/22
Excused: None
Absent: None

Summary:
Making sure everyone was on track and checking to ensure that we can deliver our results on time. Nathan has finished his sprint and has merged the changes. Annika has finished her sprint and will be getting the PR up tonight. Cam and Tavi should be good to finish by tomorrow.

Action Items:

• Merge the finished SUB Night map into dev
• Merge dev to main to continue testing and make sure that doesn't break things
• Finish models and selection menu