11
2- # MVE - Map Vote Extended
2+ # MVE - Map Vote Extended
33
44[ ![ ci] ( ../../workflows/ci/badge.svg )] ( ../../actions/workflows/ci.yml )
55
@@ -8,33 +8,56 @@ MapVote lets players to choose the next gametype and map when a match ends.
88
99![ Screeshot of MapVote] ( ./docs/map-vote-screen.png )
1010
11+ ## Features
12+
13+ This mapvote is mainly focused on enabling multi-gametype servers. There was
14+ also a lot of work on compatibility so that it can load any gametype, mutator,
15+ package combination and mapvote itself can be run in multiple ways.
16+
17+ Important Features:
18+ - ServerPackages set per gametype -> Players only download what's needed for
19+ the current gametype, not the whole server.
20+ - Mutators, ServerActors, settings configurable per gametype
21+ - Map overrides allow map specific configuration (limited to a few configuration props)
22+
1123Map management:
12- - include /exclude filters
13- - map prefix filter
14- - map tags filter
15- - premade lists
24+ - Include /exclude filters
25+ - Map prefix filter
26+ - Map tags filter
27+ - Fixed order premade lists
1628
17- Compatible with:
29+ Compatible with gametypes :
1830 - Assault (including LeagueAssault)
1931 - Jailbreak (fixed spectator bug)
2032 - Coop campaigns with fixed map order
2133 - DeathMatch, CTF & Domination
2234 - MonsterHunt
2335 - BunnyTrack
2436
25- Important Features:
26- - ServerPackages set per gametype, players only download what's needed for
27- the current gametype.
28- - Mutators, ServerActors, settings are all configurable individually
29- for every gametype.
37+ For more info read the [ documentation] ( ./docs/feature-documentation.md ) .
38+ There also have a [ changelog] ( ./docs/changelog.md ) .
3039
3140
3241## Installation
3342
34- To install, grab one of the [ latest release] ( ../../releases/latest ) and follow the readme
35- from the that comes with the release. You should be able to find an
36- [ installation guide] ( ./ReleaseFiles/MVE2dev/Help/Map%20Vote%20Extended.txt )
37- inside the Help folder.
43+ To install, grab one of the [ latest release] ( ../../releases/latest ) and follow
44+ the [ quickstarter] ( ./docs/quickstart.txt ) readme. Which should be located in
45+ the Help folder of any release package.
46+
47+
48+ ## Bugs and feature requests
49+
50+ You can use github issues for this, it will be easy to track the issue that
51+ way. I may not be able to respond immediately. For server setup help please
52+ contact the UT99 community first as there are many admins familiar with this
53+ mapvote they may be able to help with your problem before I even read the
54+ message.
55+
56+ For bugs relevant log and configuration snippets are appreciated without which
57+ it can be hard to guess what's going on.
58+
59+ Feature requests will be weighted based on the fesability and usefulness and
60+ whether it makes sense for it to be withing mapvote.
3861
3962
4063## Development
@@ -46,6 +69,8 @@ To package a release, make the neccesay changes inside `./ReleaseFiles` then
4669copy the built * .u files to the System folder inside ` ./ReleaseFiles ` , package
4770this all together.
4871
72+ There is also [ release.sh] ( ./scripts/release.sh ) which automates this process.
73+
4974Recommended development environment:
5075 - editor [ VsCodium] ( https://vscodium.com/ ) or [ VsCode] ( https://code.visualstudio.com/ )
5176 - language support [ ucx] ( https://marketplace.visualstudio.com/search?term=ucx&target=VSCode )
@@ -55,15 +80,27 @@ Recommended development environment:
5580 - [ nodemon] ( https://nodemon.io/ ) is needed for watch tasks to work
5681
5782Alternatively what I recommend is to grab the release archive and extract the code
58- from the release packages. That way you can still modify and debug, but if you
59- plan on submittin a PR then you will have to re-apply your local changes on
60- top of this repository.
83+ from the release packages. That way you can still modify and debug.
6184
6285The project uses unit tests. These must always be green to ensure the correct
6386function of logic classes. The test code can be found in separate packages.
6487To run the tests you need to run [ TestMVE.TestAll.TestMain()] ( TestMVE/Classes/TestAll.uc )
6588This can be done by running ` ucc TestMVE.TestAll `
6689
67- MVE has a long history of development with contributions from many people.
6890
69- Each author retains copyright to their code.
91+ ## History, license and forks
92+
93+ MVE has a long history of development with contributions from many people.
94+ The project was copied, decompiled and modified by multiple people which is
95+ why the code itself is quite the spaghetti monster. I've been doing my best to
96+ clean things up and have rewritten major parts of this software already and I
97+ hope to continue cleaning it up.
98+
99+ Theoretically each author retains copyright to their code, but as with most
100+ UT99 mutators, things get copied and modified so feel free to do so yourself.
101+ I will not come with pitchfork after you and hopefully neither will my
102+ prececessors who built layed the foundation pieces for this mapvote. I can also
103+ neither provide any support or warranty of any sorts.
104+
105+ There are probably hundreds of forks floating around of the original mapvote
106+ anyways and I also know of a few forks of this mapvote too.
0 commit comments