GithubHelp home page GithubHelp logo

website's People

Contributors

alejo112 avatar applenick avatar cowinkkeydinkinc avatar cswhite2000 avatar dependabot[bot] avatar electroid avatar ericzeiberg avatar guillevn avatar harvanchik avatar indicardo avatar ohpointfive avatar pablete1234 avatar picajoluna avatar pugzy avatar szboy avatar therealpear avatar zzufx avatar

Stargazers

 avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar

website's Issues

Document permissions

Currently there is no way to find the different permission nodes except going into the source code, a little segment covering all the default stuff would be nice!

Document <king> module

<king> is a module that despite being depreciated is still used by a large number of maps, especially KotH maps made originally for competitive use due to mapmakers copying the standardised hill XML used by maps such as Smoke and Cobalt. The control points page currently lists some info specific to the module under it's KotH defaults header, but the page makes no direct mention of what <king> actually is.

The main difference between <king> and <control-points> is simply the different default values that the points have. <king> also allows usage of </king> under score, which originally prevented kills from giving points on a KotH map but now has no function despite still existing within PGM as kills no longer give points by default.

The original documentation related to <king> can be found within these two archived pages of docs.oc.tc

Most recent archive that still lists info about <king>

Older archive that has less info but lists the purpose of </king> before it was depreciated

Document internal workings of PGM

Something mentioned in #2 was that @rafibaum may have had an interest in documenting how the underlying PGM code works together. We could still get others to do this, as afaik a lot is self explanatory.

Document specific objective filters

<completed> and <captured> filters are not documented.

PGMDev/PGM#939
chidddy/PGM@2d4f331
http://docs.oc.tc/modules/filters#objectiveFilter

We have which is a more generic version that has any="true/false", and a team (only allowed to be set if any=false). The completed and captured filters are the versions of objective with any="true" and any="false" respectively, the first one allowing for a team to be specified.

The current documentation doesn't present them:
https://pgm.dev/docs/modules/mechanics/filters/#objective-filter

Projectiles modules docs broken

The projectiles module for the projectile feature is broken... It refers to https://pgm.dev/docs/reference/entities/entity-types
as all the entities a projectile can be but half of the names listed there don't work or have to be changed to work

e.g. Primed TNT -> TNTprimed

Ender pearl > Enderpearl
Wither Skull > Witherskull
Creeper -> ?
[this one doesn't work]

On top that no entities fired can't have nbt attached to them... oversight?

Control point recovery rate defaults

The default recovery-rate and decay-rate for control points is defined by the incremental flag. Even if deprecated, incremental = true/false still defines the other rates.

If incremental is true, recovery rate is 1, decay rate is 0, and owned-decay-rate is also 0
If incremental is false, recovery rate and decay rate are both infinite, and owned-decay-rate is 0

Additionally, the explanations on recovery-rate and decay-rate are a bit lacking, it should say that both recovery-rate and decay-rate apply when a point is naturally going back to its current state, and one applies when the owner team is dominating (having their players on the point) while the other applies when no one is dominating (either multiple teams or no team), and that capture rules are what determine this

Document other missing filters (rank and countdown, fill action, subtitle typo)

  • <rank> Match if the player or team's rank is within the specified range.

<rank> and <score> can also have an team attribute.

https://docs.oc.tc/modules/filters#rank_score
https://github.com/PGMDev/PGM/blob/dev/core/src/main/java/tc/oc/pgm/filters/parse/FilterParser.java#L539-L543

  • <countdown>

https://docs.oc.tc/modules/filters#countdown
https://github.com/PGMDev/PGM/blob/dev/core/src/main/java/tc/oc/pgm/filters/parse/FilterParser.java#L519-L527

  • <fill> Fill action

https://github.com/PGMDev/PGM/blob/dev/core/src/main/java/tc/oc/pgm/action/ActionParser.java#L283-L290

  • subtitle attribute of <message> action is called subtitle and not text.

https://github.com/PGMDev/PGM/blob/dev/core/src/main/java/tc/oc/pgm/action/ActionParser.java#L225

  • spread-teammates attribute of spawn Spawn players as far away as possible from any players, event teammates.

  • <holding/>, <carrying/> and <wearing/> are dynamic filters.

  • exposed If true an action can be triggered using /action trigger [action]

PGMDev/PGM#1102

Document overtime

<time overtime="1m" max-overtime="15m">12m</time>

The match will last 12 minutes, if when timelimit reaches 0 the teams are tied, a one-minute overtime starts. If the tie is broken and no team makes a comeback, the 1m ticks down. The overtime will last a maximum of 15 minutes, when approaching 15 minutes it will tick down and will end regardless.

Document match phase filters

<match-started/> Filter if the match has started (running or finished).
<match-running/> Filter if the match is running.
<match-finished/> Filter if the match is over.

There is also <match-phase> match phases are: running, finished, started, starting and idle. Users should be informed to use the above more specific filters rather then <match-phase>.

https://docs.oc.tc/modules/filters#matcherelements
https://github.com/PGMDev/PGM/blob/dev/core/src/main/java/tc/oc/pgm/filters/parse/FilterParser.java#L551-L587

Add translated rules set

Back in the OCN website there was an addition that allowed players to translate the rule set so that Spanish speakers and other linguistic communities will be able to better understand the rules in their own language. We should restore this feature so that we can get back a more international audience.

Score filter example for ranges is wrong

The docs use the example: <score>[5-10]</score>, this is incorrect, you must use <score>[5,10]</score>, it could probably also use an example for infinity: <score>[5, oo)</score> (5 or more)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.