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

Web override and respanwn spots categories #4

Open
kabyrage opened this issue May 11, 2015 · 0 comments
Open

Web override and respanwn spots categories #4

kabyrage opened this issue May 11, 2015 · 0 comments

Comments

@kabyrage
Copy link

There is a possibility to exec a web configs which is cool. I think we should also have a posibility to make web override working just in a same fasion: once uploaded and approved by league staff, overriding becomes a kind of 'official' and can be voted to be applied.

Override is a function that changes placement of items on a map and can be useful in tearms of ballancing maps which are cool by architecture but poor by items placement.

Another important feature to be applieble with web override is implementing different types for respawn spots. I believe that there should be categories for spots such as:

  • 0 - player never respawns here
  • 1 - this one can't be starting spot, otherwise player can respawn here
  • 2 - player can respawn here without any limitations

Differenting respawn spots obviously should be a part of web override as far as it's important in tearms of ballance and must be approved by staff and the majority of players. In fact, there should be a kind of 'EDL' override version just as there is EDL webconfig excisting.

How can it be used (examples):

  • I'd suggest to remove bottom machinegun and both room respawn spots as starting on q2dm1 (making them type 1)
  • Some cool maps from other quake's can be used in quake 2 with items relocated - spirit2dm2 or q3dm6tmp for example
  • There can be a room to relocate items for teamplay and duel modes (used in Q3 and Qlive)
@skullernet skullernet transferred this issue from skullernet/q2pro Dec 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant