What's a Blog?
Published on October 19, 2007 By Mumblefratz In Metaverse

This is where we will keep all the rules used for the Metaverse League (MVL). The point is to have a single place where all rules are defined and so there's a single place where people can refer to resolve all question.

I will continually update this OP to reflect the current state of rules that we have all agreed to. The point is to make this as simple and concise as possible. As we have seen argument and upset occurs when different people have different interpretations of what has been agreed. Keeping these rules as simple and short as possible will help reduce potential conflict.



Rule 1) Rule changes are not allowed in the middle of a round. If an unanticipated situation develops in the middle of a round all effort should be made to deal with it as consistently as possible based on current rules and precedent. In the hopefully rare cases this is not possible the Commissioner will make an arbitrary ruling on how the matter will be resolved for the current round. Once the round is over then the issue can be revisited and a more permanent solution can be decided by the members of the League. Note that this arbitrary ruling can only be made by the Commissioner. Also the Commissioner is the only person that can grant an exception to any rule, but this power should be used judiciously.

Rule 2) Team Size. People may join the League and start playing at pretty much anytime. In the middle of a round a new player should be randomly assigned a new team by either the Commissioner or Vice Commissioner. The only limitation is that at any point in time no team should have more than one more player than any other team.

Also people may have to announce that they can't submit during a round. This can be treated using the scoring rules related to non-submission or if it's early in the round the teams could be re-balanced by the Commissioner. The decision to re-balance or not, and if so who to move, is soley the decision of the Commissioner.

The ideal team size is 5 since it provides some protection against an unforeseen non-submittal without being too unweildly. Team size at the beginning of a round should never be less than 4 or more than 6.

Rule 3) Honor System. Each round of play consists of a game (or games) of randomly selected settings and victory conditions. Very few of the required settings can be verified, namely galaxy size and victory condition. The fact that all other settings cannot be verified requires the league to operate on the honor system.

From time to time various versions of the game may exhibit a bug that temporarily allows some particular exploit. When and if this happens people should make sure the league is aware of the situation but no rule will be made to prohibit the particular exploit other than the same honor system that ensures everyone is playing the same game.

A final point about the honor system is that abuse of the honor system doesn't debase a single game played by a single player but debases every game played by every player. When seen in this light I'm sure that no one would be tempted to risk shaking the foundation of the league just to gain a miniscule benefit by intentionally bending a setting or rule. Also everyone should realize that honest mistakes do happen and if occasionally someone makes a mistake in a required game setting that it's no real big deal.

A corollary to the fact that only galaxy size and victory condition can be verified, along with the practice of taking a game submitted to the metaverse but not submitted to the league as a persons "intended" league submission, results in the rule that people should not have games submitted to the metaverse under their league character that might be confused with a legitimate league game. Note that clearly once a player has made a submission for the current round there can be no such confusion.

Honor System Addendum

The deliberate and determined use by a Player, with full knowledge and intent, of repeatedly and excessively, exploiting bugs, quirks, or other miscellanea in a game to achieve an outcome not normally possible is hereby prohibited in the MVL.

Rule 4) Reported Difficulty Levels and Race Customization in MVL Games

Every MVL player is honor bound to ensure that the effective difficulty of any game they submit is accurately represented by the games posted difficulty. To support this requirement the following guidance is provided.

External modification of any game related files are prohibited in MVL games.

In-game modification of opponent characteristics is prohibited in MVL games. The only choices allowed are the selection of opponents from among the default standard races and default custom race and the selection of their difficulty levels.

All opponent starting relations must be set to "Unknown".

DA games must be set to Allow Surrenders.

Rule 5) MVL Member Behavior

In the case where a MVL member has been found to be cheating, being overly disruptive, or detrimental to the League in some form, the commissioner is free to levy the following punishments as he deems necessary and appropriate. Such punishments may include; the loss of a team Captaincy or other MVL Administrative Position, the loss of the Player's points earned in a particular Round, forcing the Player to sit out a Round, or any other temporary punishment deemed appropriate.

For anything deemed worthy of a permanent ban from the league then besides the recommendation of the commissioner it should also require the consensus of the captains and other MVL administrators to make the ban permanent. Once banned then continued disruption of MVL threads and activities will be appropriately reported to forum authorities.



Scoring

A team's score consists of the sum of "base" scores plus individual and team bonus points.

Base Score

A player's base score is simply 2 points for a win of the designated type, 1 point for a win of the wrong type and 0 points otherwise. A team’s base score is the sum of the four top player base scores submitted. This is done so that a team having more players has no advantage over a team with fewer players.

There are two types of rounds that are treated slightly differently. One is a “Single Victory” type round where all players play for the same victory condition. The other is an “All Victories” type round where each team must submit at least one game of each of the 4 different victory types.

Non-Submission

In the Single Victory round if a player neglects to submit a game then there is no issue as long as the team still has at least four other players that submitted a game. However, if the team only had four players to begin with then they would be missing one potential contribution to the team’s base score. If this non-submission is pre-announced (this is highly encouraged), then either the Commissioner or Vice Commissioner may randomly select another member of the team to submit another game to count towards the teams base score.

In the case where no notice is given, if the player has a single game that fits the rounds criteria as to date, galaxy size and victory condition posted to the Metaverse but not yet submitted to the league then that game will be presumed to be submitted "automatically" to the league during the last minute of the round. If there are more than one qualifying game posted to the metaverse under the players MVL character than the game with the highest score/year ratio will be the game submitted to the league. If two or more games have identical score/year ratios then the submitted game shall be randomly selected from these games by the commissioner or vice commissioner whichever is not a memeber of the team in question. Note that players should make sure that any games that "appear" to match the current rounds criteria posted to the MV do indeed satisfy all the current rounds criteria. This can always be accomplished by simply waiting until your official has been made before posting a game to the MV that might otherwise be confused with the current MVL game.

In the case where no notice is given, and if other members of the team have other games that satisfy the round’s criteria that have already been submitted to the metaverse then either the Commissioner or Vice Commissioner may randomly select one of these games to count towards the teams base score. In this case the team should identify *all* such games that satisfy the round’s criteria for possible selection not simply the *best* such game.

If the non-submission is not pre-announced and the team has no “extra” qualifying games then the team gets credit only for the number of base scores properly submitted.

Note that a team of 5 players with two players that failed to submit a game would be in a similar situation as described above and the same rules apply. The same is true with 6 players and 3 non-submissions, etc. It is also possible for a team to be more than one submission short of the required total of 4 in which case the same rules can be applied to possibly allow the team to make up for more than one non-submission.

Finally these same rules apply in the case of an All Victories round but with an extra qualification. This extra requirement is that in an All Victories round each team is required to submit at least one game of each victory type. In this case the team may be required to use an “extra” game as described by the rules above that duplicates the victory type of an already submitted game. In this case for base scoring purposes that game would have to be considered a 1 point victory of the wrong type. Note that such a game could still receive individual and team bonus points based on the correct victory category.

Individual Bonus Points

In the case of a Single Victory round a single bonus point is granted for the 4 top scoring games and the 4 fastest games.

In the case of an All Victory round a single bonus point is given to the top score and the fastest game in each of the 4 different victory conditions.

The fastest games are determined by the number of years reported by the metaverse. Game speed ties are broken by score and score ties are broken by speed. Any games tied in both speed and score will be left unbroken and both players will receive the identical bonus.

Team Bonus Points

All team bonus points are based on the average of the team’s submitted games. Just as in the individual bonus point case only wins of the correct type are counted. The 1st place team receives 2 points and the 2nd place team receives 1 point in the following categories.

Team Score

Team Speed (speed of game reported by metaverse)

Team Submission (number of days into the round before game is submitted to the league)

Any teams tied in any team bonus category receive the same bonus. However, any fractional result is not subject to rounding and any tie must be exact.



MVL Voting Rules

1. Any MVL member can call for a vote among any number of competing proposals which must be seconded by two other MVL members to be considered official.

2. All votes will occur in the Galciv II Metaverse Leagues forum at the Core and notice must also be given in the current MVL Round thread.

3. All votes should run for a period of time specified in the OP of the voting thread. This period should be no shorter than 1 week or longer than 3 weeks. It's encouraged but not required that votes should be completed before the start of the next round of play if at all possible.

4. A valid vote requires participation by at least 50% of active MVL members. An abstention counts as participation. A proposal requires 60% or more of the cast ballots to be accepted. If less than 60% is achieved by any one proposal there will be a runoff between the two most popular options. The winner of the runoff will be the proposal that achieves a simple majority of votes cast with no quorum requirement.

5. Editing of your vote is allowed although any changes should be made in such a way as to make it obvious that a change has occured.

6. Once the time specified for the vote expires the thread will be locked to maintain an accurate record of the vote. The results of any vote are final and can only be changed by a subsequent official MVL vote.

Rules accepted by Consensus

From time to time minor issues may crop up that may not warrent the full attention of the League. In such cases a limited number of members may discuss the issue and come to some agreement. As long as no member of the league voices any objection to such an agreement and as long as such an agreement has been posted in a prominent thread (the current round thread or the MVL Rule thread) for a period of one week then that rule will be considered to be "official" by the league.

Besides any MVL member voicing an objection to the proposed rule, thereby invalidating the proposal, any member could also move to have a vote taken on the proposal which, as specified in our voting rules, requires a vote be taken as long as the motion is seconded by two other MVL members.



Last update Mar 28, 2008. Added Race Configuration Rule and Honor System Addendum

 


Comments (Page 28)
31 PagesFirst 26 27 28 29 30  Last
on Mar 16, 2008
ARC, or Advanced Race Customization, refers to altering the Dark Avatar xml files out of the game to change abilities, alignment and starting planets. For overall balance the use of ARC xml customization is banned in MVL competition, whether altering enemy races or the player race.

"Straw dogs" refers to a variety of practices, done either through the in-game interface or with out of game xml customization, that artificially weakens an AI player below the true difficulty setting. Choosing "straw dog" enemies or deliberately handicapping your opponents during setup is banned in MVL competition. "Straw dog" practices include, but are not limited to, lowering aggression ratings, removing super abilities, removing starting tech, choosing "lame duck" abilities and super abilities, changing enemy starting worlds, lowering enemy income and resource sliders, and setting weak enemy political parties.

Both ARC and "straw dog" prohibitions are to be enforced by the honor code. Every player has an obligation to themselves, their teammates and the league as a whole not to engage in either of these practices for official MVL games.

Other practices, not explicitly included herein, which have the general effect of artificially boosting the abilities normally available to a player race in-game, or that unfairly handicap AI players, are also prohibited by the honor code until such time as they are discovered and can be specifically banned by the MVL community.

Not quite what I was looking for although perhaps people will like it better than what I have to offer. My tendency is to go with something like the following.

Reported Difficulty Levels and Race Customization in MVL Games

Every MVL player is honor bound to ensure that the effective difficulty of any game they submit is accurately represented by the games posted difficulty. To support this requirement the following guidence is provided.

Modification of any game related files are prohibited in MVL games.

Custom races are prohibited for use in MVL games either for the player or as an opponent.

In-game modification of opponent characteristics is prohibited in MVL games. The only opponent choices allowed are the selection among the standard races and their difficulty level.


I am kind of fishing here because I'm not sure that this really covers everything on the one hand and on the other hand doesn't go too far by prohibiting more than intended.

Comments please.
on Mar 16, 2008
Custom races are prohibited for use in MVL games either for the player or as an opponent.


I cant say i agree with that. There is a difference between an ARC and a normal custom race.
We have not been discussing the canned custom race so i feel we should not include it in any rule. If anything they are weaker.

on Mar 16, 2008
I agree with Neilo on this, Normal custom races should be excluded from the ARC rule.
on Mar 16, 2008
Yeah, custom races are balanced within DA if used as a player race. I have no problem with custom races.

~ Wyndstar
on Mar 16, 2008
Yeah, custom races are balanced within DA if used as a player race. I have no problem with custom races.

Great, this is the kind of input I need.

Is it safe to say "Modification of any game related files are prohibited in MVL games" covers everything we wish to exclude related to ARC? If so then this makes the rule even simpler, and simpler is better.

Also you specifically mention custom races as balanced for the player. Does that mean they should be excluded as an opponent or are "normal" (i.e. unmodified by external means) custom races OK for opponents as well?

Finally how about the clause related to opponents, does this cover everything we think should be covered? Or does this also exclude things that we think should be allowed?
on Mar 16, 2008
Basically how I worded the rule was that my initial proposal essentially became a statement of intent. The overall intent of everything we've been talking about here boils down to maintaining the validity of the reported difficulty level.

The next clause seems to me to be the simplest expression of how to exclude ARC as allowed behavior. This clause has the additional benefit of disallowing the modification of any game related files which is probably a good general rule to have regardless of ARC and Straw men opponents.

The final clause about opponents merely reduces the options to the same options that are available in DL and of course I'd like to hear if folks feel this is either too restrictive or not restrictive enough (doubtful since I can't imagine it being any more restrictive than it is).
on Mar 17, 2008
A player using a custom race doesn't strike me as very problematic; if anything, the player may be shooting herself in the foot by using less points than she would by using a stock race.

At the same time, a custom race showing up as an opponent also doesn't strike me as problematic; they are far more likely to be a straw dog for another opponent than they are for the player. Rarely do I see custom races do well when controlled by an AI. This is not a problem, so long as all of your opponents are not custom ones, I suppose, which would not be dissimilar from ARC use.

Have we heard anything from Stardock about ARC use yet? Surprised nobody has commented in either MVL thread yet...
on Mar 17, 2008
I think custom races as opponents CAN do very well, as long as they are not severely handicapped. I've seen custom races put up a tougher fight than some stock races. But it is a pretty gray area. A couple of the things Wyndstar mentioned would lower the difficulty level by adjusting anyway. I personally think that as long as you don't remove starting techs and you let the AI pick it's own abilities, custom opponents are as difficult as any, especially at high difficulty levels.

Now setting SA, that could be tricky, since their are obviosly weak and strong ones, and I don't believe there is a "random" option.
on Mar 17, 2008
Reported Difficulty Levels and Race Customization in MVL Games

Every MVL player is honor bound to ensure that the effective difficulty of any game they submit is accurately represented by the games posted difficulty. To support this requirement the following guidence is provided.

Modification of any game related files are prohibited in MVL games.

In-game modification of opponent characteristics is prohibited in MVL games. The only opponent choices allowed are the selection among the standard races and their difficulty level.


OK so how about this. Is this sufficient? Does it go too far?

The thing is that to be effective a rule must be clear. It must be obvious to all precisely what is allowed and what isn't. We can't have rules with kind of, sort of, or maybe.
on Mar 17, 2008
OK, with my exams almost over I finally have enough free time to try the round 7 settings... too late for this discussion though(and it took me an hour to catch up too!).

Reported Difficulty Levels and Race Customization in MVL Games

Every MVL player is honor bound to ensure that the effective difficulty of any game they submit is accurately represented by the games posted difficulty. To support this requirement the following guidance is provided.

Modification of any game related files are prohibited in MVL games.

In-game modification of opponent characteristics is prohibited in MVL games. The only opponent choices allowed are the selection among the standard races and their difficulty level.


Fair enough. But to make a slightly guilty admission, I'll miss customizing my race...

@Wyndstar: Most of the uses for ARC that you noticed(rigging the map, etc), I don't think I'd ever have spotted them. In fact, I might just have to start a non-MVL game to test it out. ARC seems so much more when you look at it.
on Mar 17, 2008
I agree with the proposed rules as they are worded.

Kzinti empire2.JPG Sentient species taste better...

on Mar 17, 2008
i concur
on Mar 17, 2008
The one thing I'm a bit concerned about is if the wording is OK in regard to the custom race. Neilo, Playjeff, Wyndstar, Ghostwes and Elwood all seemed fine with custom races for either the player or an opponent as long as:

1) for either player or opponent, there is no modification of files outside of the game.

2) for opponent there is no "crippling" by the selection of crappy abilities, super abilities, etc.

Since the second clause of the rule as stated precludes 1) and the third clause precludes 2) then I think the rule is fine for the "custom race" on the basis that the custom race is also a standard race.

As an opponent this would limit the custom race to simply being selected and it's difficulty level specified but the abilities, super abilities, techs, etc. would need to be unmodified. As a player race the player would be able to select whatever they want.

However this is still kind of dangerous isn't it? Suppose the person used the custom race for himself which allowed him to setup everthing as he wanted. Doesn't this configuration stay around and wouldn't that be the new "default" if the player selected the custom race as an opponent?

I actually find this case rather fitting for the player to play against the same custom race configuration that they themseleves played but this is a bit of a hole in the rule as to what constitues the "default" custom race configuration that is suitable for use as an opponent.

Do people understand what I'm getting at here and does anyone see a clean and simple way to define what's OK for a custom race opponent and what's not?
on Mar 17, 2008
i know what you are trying to say. Its a lil harder cuz yer trying to explain DA stuff with only DL knowledge, no easy task.

If you make an opponent a custom race in DA, it starts out with:

+6% Logistics
15 Ability Points (which the AI will spend if you don't)
No Super Ability
Generic AI Personality
Neutral Alignment
Techs: Hyperdrive, Gal. Warfare, Xeno Engineering, and Stellar Cartography.

In this sense, I think its ok to make a custom race to whatever you want, cuz it is a custom race still.

The concern is, that making a bunch of walkovers.

You can't take away all the techs I don't think, I am fairly confident (90%) that if the AI has tech points left to spend it does, just like it does with the leftover ability points.

So a Stock Custom Race is pretty weak. Actually, really weak in overall comparison.

I also believe that its too easy for us to bind a player's hand and limit creativity in the MVL if we try to govern custom races too much.

So...


Reported Difficulty Levels and Race Customization in MVL Games

Every MVL player is honor bound to ensure that the effective difficulty of any game they submit is accurately represented by the games posted difficulty. To support this requirement the following guidance is provided.

Modification of any game related files are prohibited in MVL games.

Custom races and opponents are allowed in the MVL but in-game modification that severely handicaps the AI, affects the reported difficulty level, or gives an unfair advantage to the player is not allowed.

on Mar 17, 2008
Custom races and opponents are allowed in the MVL but in-game modification that severely handicaps the AI, affects the reported difficulty level, or gives an unfair advantage to the player is not allowed.

This is still ambiguous. The point of my initial statement pretty much covers this but the complaint against that was that is was too subjective.

Still leaving the subjective intent is OK assuming that it's further defined by something not so subjective. This clause seems to me to merely be trying to redefine a subjective statement by adding another subjective statement.

I think we're cool with the ARC part since that did require file modification and that is cleanly handled.

Whats left is how to deal with opponents (or straw men) and that issue comes in two flavors. The first flavor is merely taking the standard races and selecting bad abilities, super abilities and techs in the DA race configuration screen. This is the problem that Iztok reported and this problem seems to be cleanly addressed by the "In-game modification of opponent characteristics is prohibited in MVL games. The only opponent choices allowed are the selection among the standard races and their difficulty level" clause. I believe removing this clause is a mistake for the issues that Iztok pointed out.

However my concern is that the above clause does not necessarily cover the custom opponent case sufficiently. It seems your added clause is meant to deal with custom race opponents and that's fine but can it be made more explicit as to how custom opponents can be configured without requiring a judgement call by the player to determine what handicaps the AI or gives an unfair advantage to the player?
31 PagesFirst 26 27 28 29 30  Last