Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Fastball locations for Glitch and Relic #83

Merged

Conversation

GeckoEidechse
Copy link
Member

Adds panel and BT locations for Glitch and Relic. Together with #70 and #76 all non-livefire maps should have panel locations and BT spawns now.

Locations where decided on together with @theroylee

GeckoEidechse and others added 2 commits January 7, 2022 12:13
Co-authored-by: theroylee <55896140+theroylee@users.noreply.github.com>
Co-authored-by: theroylee <55896140+theroylee@users.noreply.github.com>
@GeckoEidechse
Copy link
Member Author

Panel locations on Glitch

mp_glitch0002
mp_glitch0000
mp_glitch0001
mp_glitch0003

@GeckoEidechse
Copy link
Member Author

Panel locations on Relic
mp_relic020005
mp_relic020006
mp_relic020007
mp_relic020008

@GeckoEidechse
Copy link
Member Author

I also did some playtesting yesterday with these locations hosting a public server.
The general feedback/result was:

  • B on Glitch being too open
    -> Not solvable sadly. To keep the symmetry in Glitch there's only one spot we can put B that isn't out of bounds :/
  • A on Relic being too easy to trap
    -> No one mentioned it specifically but I found it rather easy to trap A with e-smoke, so we might reposition A later on if that becomes a major issue.

Otherwise there were no major complaints ^^

@theroylee
Copy link
Contributor

theroylee commented Jan 7, 2022

One idea that we had for B on Glitch was to put it on the support beam that sits high above the bridge, but unfortunately, that area is out of bounds. If every server had out of bounds disabled that area might work.

@Neoministein
Copy link
Contributor

  • B on Glitch being too open
    -> Not solvable sadly. To keep the symmetry in Glitch there's only one spot we can put B that isn't out of bounds :/

What about doing something like this with spawning some entities to stand on under the bridge

image

@theroylee
Copy link
Contributor

  • B on Glitch being too open
    -> Not solvable sadly. To keep the symmetry in Glitch there's only one spot we can put B that isn't out of bounds :/

What about doing something like this with spawning some entities to stand on under the bridge

image

Wouldn't that force all players to have to download a mod for this map? I think the idea is to have any server be able to host the mode without any mod changes.

@hummusbird
Copy link
Contributor

Wouldn't that force all players to have to download a mod for this map? I think the idea is to have any server be able to host the mode without any mod changes.

no. since this is getting pulled to the actual mods folder, players will already have the mod needed to do this

@GeckoEidechse
Copy link
Member Author

What about doing something like this with spawning some entities to stand on under the bridge

Oh I like this idea :D
We were considering doing something like this but decided not to as we thought it wouldn't work without needing some other form of additional mod, haha ^^

I'd keep the current PR regarding B as is atm to keep things clean and get all maps functional on Fastball ASAP. But we should definitely do a second PR updating the position and adding the entities as shown in the image.

@Neoministein
Copy link
Contributor

I'd keep the current PR regarding B as is atm to keep things clean and get all maps functional on Fastball ASAP. But we should definitely do a second PR updating the position and adding the entities as shown in the image.

Ok, I'll open a new PR when this is merged ^^

@BobTheBob9 BobTheBob9 merged commit ca0f206 into R2Northstar:main Jan 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

5 participants