Pactoria Wiki - User contributions [en]

Template:Quote/doc

2026-07-05T18:18:00Z

Silverpg017: Created page with "=== Examples === '''Basic use''': <code><nowiki>{{Quote|text=Quoted material.}}</nowiki></code> Gives: {{Quote|text=Quoted material.}} '''With attribution displayed''': <code><nowiki>{{Quote|text=Quoted material.|author=Quoted author.}}</nowiki></code> Gives: {{Quote|text=Quoted material.|author=Quoted author.}} '''With more attribution''': <code><nowiki>{{Quote|text=Quoted material.|author=First M. Last|title="Article Title"|source=''Book Title'' (date)}}</nowi..."

=== Examples ===
'''Basic use''':

<code><nowiki>{{Quote|text=Quoted material.}}</nowiki></code>

Gives:

{{Quote|text=Quoted material.}}

'''With attribution displayed''':

<code><nowiki>{{Quote|text=Quoted material.|author=Quoted author.}}</nowiki></code>

Gives:

{{Quote|text=Quoted material.|author=Quoted author.}}

'''With more attribution''':

<code><nowiki>{{Quote|text=Quoted material.|author=First M. Last|title="Article Title"|source=''Book Title'' (date)}}</nowiki></code>

Gives:

{{Quote|text=Quoted material.|author=First M. Last|title="Article Title"|source=''Book Title'' (date)}}

User:Silverpg017/Sandbox

2026-07-05T17:51:32Z

Silverpg017:

{{Infobox Boss
| name = Akram Boss
| image = Akram.jpg
| caption = super strong boss
| alt = you can't see this text? lol
| aliases = The Strongest Boss in the Pactverse
| HP = 600.000
| location = Akram Outpost
}}

This is before the quote
{{Quote
|text=Quoted material.
|author=First M. Last
}}
This is a text, next

Template:Quote

2026-07-05T17:51:09Z

Silverpg017:

<templatestyles src="Template:Quote/styles.css" /><blockquote class="templatequote {{{class|}}}" {{#if:{{{style|}}}|style="{{{style}}}"}}>{{{text|{{{content|{{{quotetext|{{{quote|{{{1|<includeonly>{{error|Error: No text given for quotation (or equals sign used in the actual argument to an unnamed parameter)}}{{main other|[[Category:Pages incorrectly using the quote template]]}}</includeonly><noinclude>{{lorem ipsum}}</noinclude>}}}}}}}}}}}}}}}{{#if:{{{multiline|}}}|<nowiki />
</blockquote>|</blockquote>}}{{#if:{{{sign|}}}{{{cite|}}}{{{author|}}}{{{by|}}}{{{personquoted|}}}{{{source|}}}{{{ts|}}}{{{title|}}}{{{publication|}}}{{{quotesource|}}}{{{char|}}}{{{character|}}}{{{2|}}}{{{3|}}}{{{4|}}}{{{5|}}}|
<div class="templatequotecite"><p style="display: inline; padding-left: 2.3em;">— {{#if:{{{char|{{{character|{{{5|}}}}}}}}}|{{{char|{{{character|{{{5|}}}}}}}}}, in }}{{Comma separated entries
| {{if empty|{{{sign|}}}|{{{cite|}}}|{{{author|}}}|{{{by|}}}|{{{personquoted|}}}|{{{2|}}}}}
| {{if empty|{{{title|}}}|{{{publication|}}}|{{{ts|}}}|{{{quotesource|}}}|{{{3|}}}}}
| {{if empty|{{{source|}}}|{{{4|}}}}}
}}</p></div>}}{{#invoke:Check for unknown parameters|check|unknown={{main other|[[Category:Pages using Quote template with unknown parameters|_VALUE_{{PAGENAME}}]]}}|preview=Page using [[Template:Quote]] with unknown parameter "_VALUE_"|ignoreblank=y| 1 | 2 | 3 | 4 | 5 | author | by | char | character | cite | class | content | multiline | personquoted | publication | quote | quotesource | quotetext | sign | source | style | text | title | ts }}<noinclude>
{{documentation}}
</noinclude>

Template:If empty/doc

2026-07-05T17:47:33Z

Silverpg017: Created page with "{{Documentation subpage}}  {{Template redirect |Ifempty |First nonempty |Use first nonempty}} {{Lua|Module:If empty}} {{High-use|all-pages = yes}} This is the {{tl|If empty}} template. *''Update 2014 Dec 23'': This template used to only take 9 parameters. This limit has been removed. This template is used inside other templates. It takes any number of parameters and returns the first found to b..."

{{Documentation subpage}}

{{Template redirect |Ifempty |First nonempty |Use first nonempty}}
{{Lua|Module:If empty}}
{{High-use|all-pages = yes}}

This is the {{tl|If empty}} template.

*''Update 2014 Dec 23'': This template used to only take 9 parameters. This limit has been removed.

This template is used inside other templates. It takes any number of parameters and returns the first found to be defined and non-empty. If none is found, nothing is returned. Typical usage is like this:
: <code><nowiki>{{If empty |{{{logo|}}} |{{{image|}}} |{{{picture|}}} |default.svg}}</nowiki></code>
: <nowiki>("Return {{{logo|}}} if it has a value; else {{{image|}}} if it has a value; else {{{picture|}}} if it has a value; else return "default.svg".")</nowiki>
This returns the first of the parameters ''logo'', ''image'' and ''picture'' that is defined and non-empty, otherwise "default.svg".

===Rationale===
The MediaWiki parameter default function doesn't return the default value for empty parameters. That is, <code><nowiki>{{{logo|default.svg}}}</nowiki></code> does not return "default.svg" if the template was called like this: <code><nowiki>{{template|logo=}}</nowiki></code>.

The usual workaround for a single parameter is:
: <code><nowiki>{{#if:{{{logo|}}} |{{{logo}}} |default.svg}}</nowiki></code>
: <nowiki>("If {{{logo}}} has a value, return it, else return "default.svg".")</nowiki>

But this becomes complex when several parameters are to be checked:
: <code><nowiki>{{#if:{{{logo|}}} |{{{logo}}} |{{#if:{{{image|}}} |{{{image}}} |{{#if:{{{picture|}}} |{{{picture}}} |default.svg}} }} }}</nowiki></code>
: <nowiki>("If {{{logo}}} has a value, return it; else if {{{image}}} has a value, return that; else if {{{picture}}} has a value, return that; else return "default.svg".")</nowiki>
In these cases, {{tlf|if empty}} produces the simpler syntax (as above):
: <code><nowiki>{{if empty |{{{logo|}}} |{{{image|}}} |{{{picture|}}} |default.svg}}</nowiki></code>

====Piping====
Parameters used with {{tlf|if empty}} must be [[Pipe (Unix)|pipe]]d – i.e. include the [[Vertical bar|vertical bar (pipe) symbol]] {{nowrap|("{{thin space}}|{{thin space}}")}} as a trailing character – so that empty or undefined parameters aren't treated as text and returned incorrectly. Hence, for example, <code><nowiki>{{{logo|}}}</nowiki></code>, <code><nowiki>{{{image|}}}</nowiki></code> and <code><nowiki>{{{picture|}}}</nowiki></code> rather than {{param|logo}}, {{param|image}} and {{param|picture}} in the above examples.

===Examples===
{{Aligned table |class=wikitable
|cols=3 |col1style=padding-right:1.0em; |col2style=padding-left:0.5em;padding-right:1.0em; |col3style=padding-left:0.5em;
|row1style=background:whitesmoke;padding-left:0.5em;font-weight:bold;
| Code | Result |
| {{tlc|if empty}} | {{if empty}} | Returns an empty string.
| {{tlc|if empty|one}} | {{if empty|one}} | Returns the first parameter that is defined and not empty.
| {{tlc|if empty|one|two}} | {{if empty|one|two}} |
| {{tlc|if empty|one|two|three|four}} | {{if empty|one|two|three|four}} |
| {{tlc|if empty||two}} | {{if empty||two}} | The first parameter is empty/undefined, so is passed over.
| {{tlc|if empty||two|three|four}} | {{if empty||two|three|four}} |
| {{tlc|if empty||two||four}} | {{if empty||two||four}} |
| <code><nowiki>{{if empty||||||||||ten}}</nowiki></code> | {{if empty||||||||||ten}} | Unlike in previous versions, this template is no longer limited by 9 parameters.
| {{tlc|if empty|}} | {{if empty|}} | The only parameter is empty or undefined, so returns an empty string.
| {{tlc|if empty||||}} | {{if empty||||}} | Returns an empty string.
| <code><nowiki>{{if empty|{{{1|}}}|{{{2|}}}|three}}</nowiki></code> | {{if empty|{{{1|}}}|{{{2|}}}|three}} |
| <code><nowiki>{{if empty|{{{1}}}|{{{2}}}|three}}</nowiki></code> | {{if empty|{{{1}}}|{{{2}}}|three}} | No pipe-characters following the names of the first two parameters ("1" and "2"), so the first of these returned as text ("{{{1}}}").
| <code><nowiki>{{if empty|{{{logo|}}}|two}}</nowiki></code> | {{if empty|{{{logo|}}}|two}} |
| <code><nowiki>{{if empty|{{{logo}}}|two}}</nowiki></code> | {{if empty|{{{logo}}}|two}} | No pipe-character following the parameter name "logo", so the text "{{{logo}}}" returned.
| <code><nowiki>{{if empty|p=q}}</nowiki></code> | {{if empty|p=q}} | The template identifies the parameters it receives as parameters 1 to 9, not using names such as "p", etc.
}}

===See also===
* {{tl|if all}}
* {{tl|if either}}
* [[Help:Parameter default]]

<includeonly>{{#ifeq:{{SUBPAGENAME}}|sandbox |
| 
[[Category:If-then-else templates]]
}}</includeonly>

Module:If empty

2026-07-05T17:47:14Z

Silverpg017: Created page with "local p = {} function p.main(frame) local args = require('Module:Arguments').getArgs(frame, {wrappers = 'Template:If empty', removeBlanks = false}) -- For backwards compatibility reasons, the first 8 parameters can be unset instead of being blank, -- even though there's really no legitimate use case for this. At some point, this will be removed. local lowestNil = math.huge for i = 8,1,-1 do if args[i] == nil then args[i] = '' lowestNil = i end end for..."

local p = {}

function p.main(frame)
local args = require('Module:Arguments').getArgs(frame, {wrappers = 'Template:If empty', removeBlanks = false})

-- For backwards compatibility reasons, the first 8 parameters can be unset instead of being blank,
-- even though there's really no legitimate use case for this. At some point, this will be removed.
local lowestNil = math.huge
for i = 8,1,-1 do
if args[i] == nil then
args[i] = ''
lowestNil = i
end
end

for k,v in ipairs(args) do
if v ~= '' then
if lowestNil < k then
-- If any uses of this template depend on the behavior above, add them to a tracking category.
-- This is a rather fragile, convoluted, hacky way to do it, but it ensures that this module's output won't be modified
-- by it.
frame:extensionTag('ref', '[[Category:Instances of Template:If_empty missing arguments]]', {group = 'TrackingCategory'})
frame:extensionTag('references', '', {group = 'TrackingCategory'})
end
return v
end
end
end

return p

Template:If empty

2026-07-05T17:46:54Z

Silverpg017: Created page with "{{<includeonly>safesubst:</includeonly>#invoke:If empty|main}}<noinclude>{{Documentation}}</noinclude>"

{{<includeonly>safesubst:</includeonly>#invoke:If empty|main}}<noinclude>{{Documentation}}</noinclude>

Module:Separated entries

2026-07-05T17:46:26Z

Silverpg017: Created page with "-- This module takes positional parameters as input and concatenates them with -- an optional separator. The final separator (the "conjunction") can be -- specified independently, enabling natural-language lists like -- "foo, bar, baz and qux". The starting parameter can also be specified. local compressSparseArray = require('Module:TableTools').compressSparseArray local p = {} function p._main(args) local dataPlural = args.dataPlural local separator = args.separator..."

-- This module takes positional parameters as input and concatenates them with
-- an optional separator. The final separator (the "conjunction") can be
-- specified independently, enabling natural-language lists like
-- "foo, bar, baz and qux". The starting parameter can also be specified.

local compressSparseArray = require('Module:TableTools').compressSparseArray
local p = {}

function p._main(args)
local dataPlural = args.dataPlural
local separator = args.separator
-- Decode (convert to Unicode) HTML escape sequences, such as " " for space.
and mw.text.decode(args.separator) or ''
local conjunction = args.conjunction and mw.text.decode(args.conjunction) or separator
-- Discard values before the starting parameter.
local start = tonumber(args.start)
if start then
for i = 1, start - 1 do args[i] = nil end
end
-- Discard named parameters.
local values = compressSparseArray(args)
local result = mw.text.listToText(values, separator, conjunction)
if dataPlural and #values > 0 and (#separator > 0 or #conjunction > 0) then
-- flag to [[Module:Detect singular]] whether this is a list with >1 element
result = result..'<span style="display:none" data-plural="'..(#values > 1 and '1' or '0')..'"></span>'
end
return result
end

local function makeInvokeFunction(separator, conjunction, first)
return function (frame)
local args = require('Module:Arguments').getArgs(frame, {frameOnly = (frame.args.frameOnly or '') ~= ''})
args.separator = separator or args.separator
args.conjunction = conjunction or args.conjunction
args.first = first or args.first
return p._main(args)
end
end

p.main = makeInvokeFunction()
p.br = makeInvokeFunction('<br />')
p.comma = makeInvokeFunction(mw.message.new('comma-separator'):plain())

return p

Template:Comma separated entries

2026-07-05T17:46:03Z

Silverpg017: Created page with "{{<includeonly>safesubst:</includeonly>#invoke:Separated entries|comma}}<noinclude> {{documentation}}  </noinclude>"

{{<includeonly>safesubst:</includeonly>#invoke:Separated entries|comma}}<noinclude>
{{documentation}}

</noinclude>

Module:Lorem ipsum/data

2026-07-05T17:44:53Z

Silverpg017: Created page with "--<nowiki> return { "{{safesubst:#if:%s|Lorem ipsum|Lorem ipsum}} dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserun..."

--<nowiki>
return {
"{{safesubst:#if:%s|[[Lorem ipsum]]|Lorem ipsum}} dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.",
"Curabitur pretium tincidunt lacus. Nulla gravida orci a odio. Nullam varius, turpis et commodo pharetra, est eros bibendum elit, nec luctus magna felis sollicitudin mauris. Integer in mauris eu nibh euismod gravida. Duis ac tellus et risus vulputate vehicula. Donec lobortis risus a elit. Etiam tempor. Ut ullamcorper, ligula eu tempor congue, eros est euismod turpis, id tincidunt sapien risus a quam. Maecenas fermentum consequat mi. Donec fermentum. Pellentesque malesuada nulla a mi. Duis sapien sem, aliquet nec, commodo eget, consequat quis, neque. Aliquam faucibus, elit ut dictum aliquet, felis nisl adipiscing sapien, sed malesuada diam lacus eget erat. Cras mollis scelerisque nunc. Nullam arcu. Aliquam consequat. Curabitur augue lorem, dapibus quis, laoreet et, pretium ac, nisi. Aenean magna nisl, mollis quis, molestie eu, feugiat in, orci. In hac habitasse platea dictumst.",
"Fusce convallis, mauris imperdiet gravida bibendum, nisl turpis suscipit mauris, sed placerat ipsum urna sed risus. In convallis tellus a mauris. Curabitur non elit ut libero tristique sodales. Mauris a lacus. Donec mattis semper leo. In hac habitasse platea dictumst. Vivamus facilisis diam at odio. Mauris dictum, nisi eget consequat elementum, lacus ligula molestie metus, non feugiat orci magna ac sem. Donec turpis. Donec vitae metus. Morbi tristique neque eu mauris. Quisque gravida ipsum non sapien. Proin turpis lacus, scelerisque vitae, elementum at, lobortis ac, quam. Aliquam dictum eleifend risus. In hac habitasse platea dictumst. Etiam sit amet diam. Suspendisse odio. Suspendisse nunc. In semper bibendum libero.",
"Proin nonummy, lacus eget pulvinar lacinia, pede felis dignissim leo, vitae tristique magna lacus sit amet eros. Nullam ornare. Praesent odio ligula, dapibus sed, tincidunt eget, dictum ac, nibh. Nam quis lacus. Nunc eleifend molestie velit. Morbi lobortis quam eu velit. Donec euismod vestibulum massa. Donec non lectus. Aliquam commodo lacus sit amet nulla. Cras dignissim elit et augue. Nullam non diam. Pellentesque habitant morbi tristique senectus et netus et malesuada fames ac turpis egestas. In hac habitasse platea dictumst. Aenean vestibulum. Sed lobortis elit quis lectus. Nunc sed lacus at augue bibendum dapibus.",
"Aliquam vehicula sem ut pede. Cras purus lectus, egestas eu, vehicula at, imperdiet sed, nibh. Morbi consectetuer luctus felis. Donec vitae nisi. Aliquam tincidunt feugiat elit. Duis sed elit ut turpis ullamcorper feugiat. Praesent pretium, mauris sed fermentum hendrerit, nulla lorem iaculis magna, pulvinar scelerisque urna tellus a justo. Suspendisse pulvinar massa in metus. Duis quis quam. Proin justo. Curabitur ac sapien. Nam erat. Praesent ut quam.",
"Vivamus commodo, augue et laoreet euismod, sem sapien tempor dolor, ac egestas sem ligula quis lacus. Donec vestibulum tortor ac lacus. Sed posuere vestibulum nisl. Curabitur eleifend fermentum justo. Nullam imperdiet. Integer sit amet mauris imperdiet risus sollicitudin rutrum. Ut vitae turpis. Nulla facilisi. Quisque tortor velit, scelerisque et, facilisis vel, tempor sed, urna. Vivamus nulla elit, vestibulum eget, semper et, scelerisque eget, lacus. Pellentesque viverra purus. Quisque elit. Donec ut dolor.",
"Duis volutpat elit et erat. In at nulla at nisl condimentum aliquet. Quisque elementum pharetra lacus. Nunc gravida arcu eget nunc. Nulla iaculis egestas magna. Aliquam erat volutpat. Sed pellentesque orci. Etiam lacus lorem, iaculis sit amet, pharetra quis, imperdiet sit amet, lectus. Integer quis elit ac mi aliquam pretium. Nullam mauris orci, porttitor eget, sollicitudin non, vulputate id, risus. Donec varius enim nec sem. Nam aliquam lacinia enim. Quisque eget lorem eu purus dignissim ultricies. Fusce porttitor hendrerit ante. Mauris urna diam, cursus id, mattis eget, tempus sit amet, risus. Curabitur eu felis. Sed eu mi. Nullam lectus mauris, luctus a, mattis ac, tempus non, leo. Cras mi nulla, rhoncus id, laoreet ut, ultricies id, odio.",
"Donec imperdiet. Vestibulum auctor tortor at orci. Integer semper, nisi eget suscipit eleifend, erat nisl hendrerit justo, eget vestibulum lorem justo ac leo. Integer sem velit, pharetra in, fringilla eu, fermentum id, felis. Vestibulum sed felis. In elit. Praesent et pede vel ante dapibus condimentum. Donec magna. Quisque id risus. Mauris vulputate pellentesque leo. Duis vulputate, ligula at venenatis tincidunt, orci nunc interdum leo, ac egestas elit sem ut lacus. Etiam non diam quis arcu egestas commodo. Curabitur nec massa ac massa gravida condimentum. Aenean id libero. Pellentesque vitae tellus. Fusce lectus est, accumsan ac, bibendum sed, porta eget, augue. Etiam faucibus. Quisque tempus purus eu ante.",
"Vestibulum sapien nisl, ornare auctor, consectetuer quis, posuere tristique, odio. Fusce ultrices ullamcorper odio. Ut augue nulla, interdum at, adipiscing non, tristique eget, neque. Pellentesque habitant morbi tristique senectus et netus et malesuada fames ac turpis egestas. Ut pede est, condimentum id, scelerisque ac, malesuada non, quam. Proin eu ligula ac sapien suscipit blandit. Suspendisse euismod. Ut accumsan, neque id gravida luctus, arcu pede sodales felis, vel blandit massa arcu eget ligula. Aenean sed turpis. Pellentesque habitant morbi tristique senectus et netus et malesuada fames ac turpis egestas. Donec sem eros, ornare ut, commodo eu, tempor nec, risus. Donec laoreet dapibus ligula. Praesent orci leo, bibendum nec, ornare et, nonummy in, elit. Donec interdum feugiat leo. Vestibulum ante ipsum primis in faucibus orci luctus et ultrices posuere cubilia Curae; Pellentesque feugiat ullamcorper ipsum. Donec convallis tincidunt urna.",
"Suspendisse et orci et arcu porttitor pellentesque. Sed lacus nunc, fermentum vel, vehicula in, imperdiet eget, urna. Nam consectetuer euismod nunc. Nulla dignissim posuere nulla. Integer iaculis lacinia massa. Nullam sapien augue, condimentum vel, venenatis id, rhoncus pellentesque, sapien. Donec sed ipsum ultrices turpis consectetuer imperdiet. Duis et ipsum ac nisl laoreet commodo. Mauris eu est. Suspendisse id turpis quis orci euismod consequat. Donec tellus mi, luctus sit amet, ultrices a, convallis eu, lorem. Proin faucibus convallis elit. Maecenas rhoncus arcu at arcu. Proin libero. Proin adipiscing. In quis lorem vitae elit consectetuer pretium. Nullam ligula urna, adipiscing nec, iaculis ut, elementum non, turpis. Fusce pulvinar.",

}
--</nowiki>

Module:Lorem ipsum

2026-07-05T17:44:06Z

Silverpg017: Created page with "local yn = require("Module:Yesno") return { main = function(frame) local args = require("Module:Arguments").getArgs(frame) local data = args["data"] and mw.loadData(args["data"]) or mw.loadData("Module:Lorem_ipsum/data") local paragraphs = {} for k,v in ipairs(data) do table.insert(paragraphs, v) end local out = '' local outTbl = {} local link = yn(args["link"]) or yn(args[4]) or false local join = yn(args["join"]) or false local joinprefixsuffix..."

local yn = require("Module:Yesno")
return {
main = function(frame)
local args = require("Module:Arguments").getArgs(frame)
local data = args["data"] and mw.loadData(args["data"]) or mw.loadData("Module:Lorem_ipsum/data")
local paragraphs = {}
for k,v in ipairs(data) do
table.insert(paragraphs, v)
end
local out = ''
local outTbl = {}
local link = yn(args["link"]) or yn(args[4]) or false
local join = yn(args["join"]) or false
local joinprefixsuffix = yn(args["joinprefixsuffix"]) or false
local cat = yn(args["cat"]) or true
local count = tonumber(args[1] or 1)
local i = 1
if join and (not joinprefixsuffix) then
table.insert(outTbl, (args["prefix"] or args[2] or ""))
end
while i <= count do
if (not join) or joinprefixsuffix then
table.insert(outTbl, (args["prefix"] or args[2] or "\n"))
end
table.insert(outTbl, mw.ustring.format(paragraphs[math.mod(i - 1, #paragraphs) + 1], (link and "link" or "")))
if not join then
table.insert(outTbl, (args["suffix"] or args[3] or "") .. "\n")
else
if joinprefixsuffix then
table.insert(outTbl, (args["suffix"] or args[3] or ""))
end
table.insert(outTbl, (i == count and "" or " "))
end
link = false
i = i + 1
end
if join and (not joinprefixsuffix) then
table.insert(outTbl, (args["suffix"] or args[3] or ""))
end
if cat and mw.title.getCurrentTitle().namespace == 0 and not mw.isSubsting() then
table.insert(outTbl, "[[Category:Wikipedia articles containing placeholders]]")
end
return frame:preprocess(table.concat(outTbl, ''))
end,
oneParagraph = function(frame)
local args = require("Module:Arguments").getArgs(frame)
local data = args["data"] and mw.loadData(args["data"]) or mw.loadData("Module:Lorem_ipsum/data")
local paragraphs = {}
for k,v in ipairs(data) do
table.insert(paragraphs, v)
end
local i = tonumber(args[1] or 1)
local link = yn(args["link"])
local paragraph = paragraphs[math.mod(i - 1, #paragraphs) + 1]
local out = ""
if cat and mw.title.getCurrentTitle().namespace == 0 and not mw.isSubsting() then
out = out .. "[[Category:Wikipedia articles containing placeholders]]"
end
out = out .. mw.ustring.format(paragraph, (link and "link" or ""))
out = frame:preprocess(out)
local maxLen = tonumber(args["max len"] or mw.ustring.len(out))
return mw.ustring.sub(out, 1, maxLen)
end
}

Template:Lorem ipsum

2026-07-05T17:43:29Z

Silverpg017: Created page with "{{{{{|safesubst:}}}#invoke:lorem ipsum|main}}<noinclude> {{Documentation}} </noinclude>"

{{{{{|safesubst:}}}#invoke:lorem ipsum|main}}<noinclude>
{{Documentation}}
</noinclude>

Template:Quote/styles.css

2026-07-05T17:42:58Z

Silverpg017: Created page with "/* {{pp-template}} Styling for Template:Quote */ .templatequote { overflow: hidden; margin: 1em 0; padding: 0 40px; } .templatequote .templatequotecite { line-height: 1.5em; /* @noflip */ text-align: left; /* @noflip */ padding-left: 1.6em; margin-top: 0; }"

/* {{pp-template}}
Styling for Template:Quote */
.templatequote {
overflow: hidden;
margin: 1em 0;
padding: 0 40px;
}
.templatequote .templatequotecite {
line-height: 1.5em;
/* @noflip */
text-align: left;
/* @noflip */
padding-left: 1.6em;
margin-top: 0;
}

Template:Quote

2026-07-05T17:42:41Z

Silverpg017: Created page with "<templatestyles src="Template:Quote/styles.css"/><blockquote class="templatequote" {{#if:{{{style|}}}|style="{{{style}}}"}}>{{{text|{{{content|{{{quotetext|{{{quote|{{{1|<includeonly>{{error|Error: No text given for quotation (or equals sign used in the actual argument to an unnamed parameter)}}Category:Pages incorrectly using the quote template</includeonly><noinclude>{{lorem ipsum}}</noinclude>}}}}}}}}}}}}}}}{{#if:{{{sign|}}}{{{cite|}}}{{{author|}}}{{{by|}}..."

<templatestyles src="Template:Quote/styles.css"/><blockquote class="templatequote" {{#if:{{{style|}}}|style="{{{style}}}"}}>{{{text|{{{content|{{{quotetext|{{{quote|{{{1|<includeonly>{{error|Error: No text given for quotation (or equals sign used in the actual argument to an unnamed parameter)}}[[Category:Pages incorrectly using the quote template]]</includeonly><noinclude>{{lorem ipsum}}</noinclude>}}}}}}}}}}}}}}}{{#if:{{{sign|}}}{{{cite|}}}{{{author|}}}{{{by|}}}{{{personquoted|}}}{{{source|}}}{{{ts|}}}{{{title|}}}{{{publication|}}}{{{quotesource|}}}{{{2|}}}{{{3|}}}{{{4|}}}{{{char|}}}{{{character|}}}|{{#if:{{{multiline|}}}|<nowiki />}}
<div class="templatequotecite">— <cite>{{#if:{{{char|{{{character|}}}}}}|{{{char|{{{character|}}}}}}, in }}{{Comma separated entries
| {{if empty|{{{sign|}}}|{{{cite|}}}|{{{author|}}}|{{{by|}}}|{{{personquoted|}}}|{{{2|}}}}}
| {{if empty|{{{title|}}}|{{{publication|}}}|{{{ts|}}}|{{{quotesource|}}}|{{{3|}}}}}
| {{if empty|{{{source|}}}|{{{4|}}}}}
}}</cite></div>
}}
</blockquote>{{#if:{{{class|}}}{{{id|}}}{{{diff|}}}{{{4|}}}{{{5|}}}|[[Category:Pages incorrectly using the quote template]]}}{{#invoke:Check for unknown parameters|check|unknown={{main other|[[Category:Pages using quote template with unknown parameters|_VALUE_{{PAGENAME}}]]}}|preview=Page using [[Template:Quote]] with unknown parameter "_VALUE_"|ignoreblank=y| 1 | 2 | 3 | 4 | 5 | author | by | char | character | cite | class | content | diff | id | multiline | personquoted | publication | quote | quotesource | quotetext | sign | source | style | text | title | ts }}<noinclude>
{{documentation}}
</noinclude>

Template:GettingStartedContainer

2026-07-05T17:32:18Z

Silverpg017:

{| style="width:100%; margin-top:7px"
| style="border:1px solid #cedff2; background-color:#f5faff; padding:5px 15px 15px 8px; vertical-align:top;" |

<h2 style="border-width:1px; border-style:solid; margin-top:3px; margin-bottom:0.5em; padding:0.2em 0.4em; font-size:120%; font-weight:bold; font-family:inherit; background:#1A1A1A; border-color: #3D3D3D;">Getting Started </h2>

<div style="display: flex; justify-content: space-between; gap: 10px; text-align:center;">

<div style="flex: 1;">[[File:Oaksign.png|100px|frameless|link=Category:Pactoria Content]]<br><br><span style="font-size:1.0em;">'''[[:Category:Pactoria Content|Gameplay & Features]]'''</span></div>

<div style="flex: 1;">[[File:Filledmap.png|100px|frameless|link=Dynmap]]<br><br><span style="font-size:1.0em;">'''Dynmap'''</span></div>

<div style="flex: 1;">[[File:Bookandquill.png|100px|frameless|link=Official Lore]]<br><br><span style="font-size:1.0em;">'''[[Official Lore]]'''</span></div>

<div style="flex: 1;">[[File:Book.png|100px|frameless|link=Rulebook]]<br><br><span style="font-size:1.0em;">'''[https://docs.google.com/document/d/1ylO4wE1T_kCvrcmyIwy0Q-3tHaBHGnteoipyKpd0pn0/edit?tab=t.0 Rulebook]'''</span></div>

<div style="flex: 1;">[[File:Hangingsign.png|100px|frameless|link=Server History]]<br><br><span style="font-size:1.0em;">'''[[:Category:Pactoria History|Pactoria History]]'''</span></div>
|}

File:Hangingsign.png

2026-07-05T17:28:13Z

Silverpg017: Silverpg017 uploaded a new version of File:Hangingsign.png

File:Hangingsign.png

2026-07-05T17:27:59Z

Silverpg017:

Template:GalleryContainer

2026-07-05T17:19:32Z

Silverpg017:

{| style="width:100%; margin-top:7px"
| style="border:1px solid #cedff2; background-color:#fff5f5; padding:5px 15px 15px 8px; vertical-align:top;" |
<h2 style="border-width:1px; border-style:solid; margin-top:3px; margin-bottom:0.5em; padding:0.2em 0.4em; font-size:120%; font-weight:bold; font-family:inherit; background:#1A1A1A; border-color: #3D3D3D;">Image Gallery</h2>

<gallery mode="packed" widths="270px" heights="270px">
File:Mp-bg-1.png
File:Mp-bg-2.png
File:Mp-bg-3.png
File:Mp-bg-4.png
File:Mp-bg-5.png
File:Mp-bg-6.png
File:Mp-bg-7.png
File:Mp-bg-8.png
File:Mp-bg-9.png
</gallery>
|}

Template:GettingStartedContainer

2026-07-05T17:19:01Z

Silverpg017:

{| style="width:100%; margin-top:7px"
| style="border:1px solid #cedff2; background-color:#f5faff; padding:5px 15px 15px 8px; vertical-align:top;" |

<h2 style="border-width:1px; border-style:solid; margin-top:3px; margin-bottom:0.5em; padding:0.2em 0.4em; font-size:120%; font-weight:bold; font-family:inherit; background:#1A1A1A; border-color: #3D3D3D;">Getting Started </h2>

<div style="display: flex; justify-content: space-between; gap: 20px; text-align:center;">

<div style="flex: 1;">[[File:Oaksign.png|100px|frameless|link=Category:Pactoria Content]]<br><br><span style="font-size:1.0em;">'''[[:Category:Pactoria Content|Gameplay & Features]]'''</span></div>

<div style="flex: 1;">[[File:Filledmap.png|100px|frameless|link=Dynmap]]<br><br><span style="font-size:1.0em;">'''Dynmap'''</span></div>

<div style="flex: 1;">[[File:Bookandquill.png|100px|frameless|link=Official Lore]]<br><br><span style="font-size:1.0em;">'''[[Official Lore]]'''</span></div>

<div style="flex: 1;">[[File:Book.png|100px|frameless|link=Rulebook]]<br><br><span style="font-size:1.0em;">'''[https://docs.google.com/document/d/1ylO4wE1T_kCvrcmyIwy0Q-3tHaBHGnteoipyKpd0pn0/edit?tab=t.0 Rulebook]'''</span></div>
|}

Template:AboutPactoriaContainer

2026-07-05T17:18:26Z

Silverpg017:

{| style="width:100%; margin-top:7px"
| style="border:1px solid #007334; color:#000000; background-color:#007334; padding:5px 15px 15px 8px; vertical-align:top;" |

<h2 style="border-width:1px; border-style:solid; margin-top:3px; margin-bottom:0.5em; padding:0.2em 0.4em; font-size:120%; font-weight:bold; font-family:inherit; background:#1A1A1A; border-color: #3D3D3D;">About Pactoria </h2>

'''Pactoria''' is a Minecraft medieval fantasy nations server built for deep worldbuilding and immersive roleplay. The world spans a '''15k x 15k handcrafted map''', designed specifically to offer depth and immersion at every turn.

The land is scarred by the past. You’ll find ancient ruins that tell forgotten stories and outposts that still carry the legacy of civilizations long gone. But watch your step because hidden across the world there are dangerous dungeons. If you stumble into one, you may find yourself facing monstrous bosses, ancient creatures that inhabit our world.

Those seasoned enough to defeat them are rewarded with custom armor and weapons themed after each boss, giving you the edge on the battlefield.

For those who prefer a more peaceful path, Pactoria offers a deep and rewarding economy. You can grow your nation into a major trade hub by mastering custom processes like steel making, cheese making, and advanced cooking. You can even become a master brewer or a legendary fisherman, catching custom fish and crafting unique drinks with their own effects. With new crops and crafting systems, daily life always feels busy and productive.

We document these servers, the mechanics that drive them, and the rise and fall of their players and civilizations.
|}

User:Silverpg017/Sandbox

2026-07-05T09:03:10Z

Silverpg017:

Template:Infobox Boss/doc

2026-07-05T09:00:45Z

Silverpg017: Created page with "{{Documentation subpage}} ==Usage== To use this template in an article, copy and paste the code below and fill it. Some spaces can be left blank and they won't show up on the final infobox. If you are using source editor, you can press on 'Show preview' to see a preview of your infobox. === Full === {{Parameter names example|_template=Infobox Boss|name|image|caption|alt|aliases|HP|location}} <nowiki>{{Infobox Boss | name = | image = | caption = | alt..."

{{Documentation subpage}}
==Usage==
To use this template in an article, copy and paste the code below and fill it. Some spaces can be left blank and they won't show up on the final infobox. If you are using source editor, you can press on 'Show preview' to see a preview of your infobox.
=== Full ===
{{Parameter names example|_template=Infobox Boss|name|image|caption|alt|aliases|HP|location}}
<nowiki>{{Infobox Boss
| name =
| image =
| caption =
| alt =
| aliases =
| HP =
| location =
}}
</nowiki>

Template:Infobox Boss

2026-07-05T08:59:55Z

Silverpg017: Created page with "<includeonly> {{Infobox | above = {{#if:{{{name|}}}|{{{name}}}|{{PAGENAMEBASE}}}} | autoheaders = y | image1 = {{#if:{{{image|}}}|upright=1}} | caption1 = <div style="text-align:center;">''{{{caption|}}}''</div> | captionstyle = | abovestyle = background:#eaecee;font-size:130%;padding:0.3em; | headerstyle = background:#eaecee; | header1 = Biographical information | label2 = <div style="text-align: left;">Al..."

<includeonly>
{{Infobox
| above = {{#if:{{{name|}}}|{{{name}}}|{{PAGENAMEBASE}}}}
| autoheaders = y

| image1 = {{#if:{{{image|}}}|[[File:{{{image}}}|frameless|border|center|alt={{{alt|}}}|upright=1]]}}
| caption1 = <div style="text-align:center;">''{{{caption|}}}''</div>

| captionstyle =

| abovestyle = background:#eaecee;font-size:130%;padding:0.3em;
| headerstyle = background:#eaecee;

| header1 = Biographical information

| label2 = <div style="text-align: left;">Aliases</div>
| data2 = {{{aliases|}}}

| label3 = <div style="text-align: left;">HP</div>
| data3 = {{{HP|}}}

| label4 = <div style="text-align: left;">Location</div>
| data4 = {{{location|}}}
}}
</includeonly>
<noinclude>
{{documentation}}
<templatedata>
{
"description": "An infobox template for displaying information about characters.",
"params": {
"name": {
"label": "Name",
"description": "The boss's name",
"type": "string",
"required": true,
"suggested": true
},
"image": {
"label": "Primary Image",
"description": "Name of the boss's portrait file",
"type": "string",
"example": "Boss Portrait.png",
"suggested": true
},
"alt": {
"label": "Alternative Image Text",
"description": "Alt text for image description",
"type": "string"
},
"caption": {
"label": "Image Caption",
"description": "Brief description of the image's content",
"type": "string",
"example": "This Boss in the Example Dungeon"
},
"aliases": {
"label": "Aliases",
"description": "Aliases of the boss. This can include noble titles, nicknames and so on",
"type": "string",
"example": "\"Super Strong Samurai\""
},
"HP": {
"label": "Health Points",
"description": "The boss' health points. For guidance, a player's base HP is 20.",
"type": "string",
"example": "600"
},
"location": {
"label": "Location",
"description": "Where the boss is located.",
"type": "string",
"example": "Akram Outpost"
}
},
"paramOrder": [
"name",
"image",
"caption",
"alt",
"aliases",
"HP",
"location"
],
"format": "block"
}
</templatedata>
</noinclude>
<includeonly>{{#ifeq:{{NAMESPACE}}|doc|[[Category:Bosses]]}}</includeonly>

Religion System

2026-07-04T19:01:28Z

Silverpg017:

Pactoria's '''religion system''' is one of the server's core features. It allows players to create their own religions and gain faith points as they complete daily quests and do sacrifices.

== Starting a religion ==
To create your own religion, type <code>/religion create <religion_name></code> in chat. You can invite other members typing <code>/religion invite <username></code>, or kick them (<code>/religion kick <username></code>).

== Ranks ==
There are five different ranks in a religion, in descending order:
* High Priest - Those who own the religion in-game.
* Priest - TBA
* Acolyte - TBA
* Devotee - TBA
* Initiate - Those who joined the religion and were not promoted.

== Events ==
Events are a core aspect in the religion system. There are three event tiers, depending on the attendee count:
* Tier 1: Minor Gathering (1-4 players)
* Tier 2: Sacred Assembly (5-9 players)
* Tier 3: Grand Conclave (10-∞ players)

To start a event, type <code>/religion event start</code>. For one of your members to join your event, they must type <code>/religion event join</code>. To end your event, you must type <code>/religion event end</code>.

Once your event ends, it will be sent to staff for evaluation and you may get reward points, which can be seen through <code>/religion reward</code>. You can either spend your reward points in a 1.5x Crop XP multiplier for thirty days, or you can get a Divine Intervention token.

== Offerings ==
Offerings are a core aspect in the religion system, and is the main way of getting faith points. Offerings may consist of either items (daily quests) or sacrifices (players), the latter giving you the most faith points. To make an offering or a sacrifice, the player will need to make an altar. Altars consist of a central water cauldron surrounded by four emerald blocks with lit candles on top of them.
[[File:Religion altar.png|thumb|Example of a working altar.]]

=== Daily quests ===
Daily quests can be browsed typing <code>/religion quest</code>, and they require certain items to offer. Once you have these items, drop them into an active altar cauldron and right-click the cauldron to complete the offering. You can also browse the remaining daily offerings by shift-right clicking the cauldron.

=== Sacrifices ===
Sacrifices work like offerings but said offering is a player. To do this, the sacrificed player must put position themselves inside the cauldron and another player must right-click the cauldron. This will kill the player and the religion will get 100 faith points. This can only be done once per day.

== Commands ==
* '''/religion create <religion_name>''' - Creates a religion
* '''/religion info <religion_name>''' - Show your religion's information. It shows your leader, your member count and your monthly and total faith points. This can also be used to browse other religions.
* '''/religion members <religion_name>''' - Show your (or another) religion's members, with their respective rank and individual faith points.
* '''/religion leaderboard <members/monthly/tiers>''' - Show a ranking of every religion based on either their all-time faith points (if no arguments are added), their monthly faith points, and you can also check the top member contributors and event tiers.
* '''/religion invite <username>''' - Invite a player to your religion
* '''/religion join <religion_name>''' - Join a religion. Requires invite.
* '''/religion rank <username> <high_priest/priest/acolyte/devotee/initiate>''' - Promotes or demotes a player within your religion.
* '''/religion kick <username>''' - Kick a member from your religion.
* '''/religion disband <religion_name>''' - Disbands your religion.
* '''/religion event <start/end/join/leave>''' - Choose to start or end an event, or as a member, choose to join or leave an event.
* '''/religion quest''' - Show your religion's daily quests.
* '''/religion reward <divine/expbuff>''' - Show your religion's reward points. By adding the <code><divine/expbuff></code> arguments, you can spend reward points to use either of them (see [[#Events]])

[[Category:Server Features]]

Religion System

2026-07-04T18:57:21Z

Silverpg017: Replaced system

Pactoria's '''religion system''' is one of the server's core features. It allows players to create their own religions and gain faith points as they complete daily quests and do sacrifices.

== Starting a religion ==
To create your own religion, type <code>/religion create <religion_name></code> in chat. You can invite other members typing <code>/religion invite <username></code>, or kick them (<code>/religion kick <username</code>).

== Ranks ==
There are five different ranks in a religion, in descending order:
* High Priest - Those who own the religion in-game.
* Priest - TBA
* Acolyte - TBA
* Devotee - TBA
* Initiate - Those who joined the religion and were not promoted.

== Events ==
Events are a core aspect in the religion system. There are three event tiers, depending on the attendee count:
* Tier 1: Minor Gathering (1-4 players)
* Tier 2: Sacred Assembly (5-9 players)
* Tier 3: Grand Conclave (10-∞ players)

To start a event, type <code>/religion event start</code>. For one of your members to join your event, they must type <code>/religion event join</code>. To end your event, you must type <code>/religion event end</code>.

Once your event ends, it will be sent to staff for evaluation and you may get reward points, which can be seen through <code>/religion reward</code>. You can either spend your reward points in a 1.5x Crop XP multiplier for thirty days, or you can get a Divine Intervention token.

== Offerings ==
Offerings are a core aspect in the religion system, and is the main way of getting faith points. Offerings may consist of either items (daily quests) or sacrifices (players), the latter giving you the most faith points. To make an offering or a sacrifice, the player will need to make an altar. Altars consist of a central water cauldron surrounded by four emerald blocks with lit candles on top of them.
[[File:Religion altar.png|thumb|Example of a working altar.]]

=== Daily quests ===
Daily quests can be browsed typing <code>/religion quest</code>, and they require certain items to offer. Once you have these items, drop them into an active altar cauldron and right-click the cauldron to complete the offering. You can also browse the remaining daily offerings by shift-right clicking the cauldron.

=== Sacrifices ===
Sacrifices work like offerings but said offering is a player. To do this, the sacrificed player must put position themselves inside the cauldron and another player must right-click the cauldron. This will kill the player and the religion will get 100 faith points. This can only be done once per day.

== Commands ==
* '''/religion create <religion_name>''' - Creates a religion
* '''/religion info <religion_name>''' - Show your religion's information. It shows your leader, your member count and your monthly and total faith points. This can also be used to browse other religions.
* '''/religion members <religion_name>''' - Show your (or another) religion's members, with their respective rank and individual faith points.
* '''/religion leaderboard <members/monthly/tiers>''' - Show a ranking of every religion based on either their all-time faith points (if no arguments are added), their monthly faith points, and you can also check the top member contributors and event tiers.
* '''/religion invite <username>''' - Invite a player to your religion
* '''/religion join <religion_name>''' - Join a religion. Requires invite.
* '''/religion rank <username> <high_priest/priest/acolyte/devotee/initiate>''' - Promotes or demotes a player within your religion.
* '''/religion kick <username>''' - Kick a member from your religion.
* '''/religion disband <religion_name>''' - Disbands your religion.
* '''/religion event <start/end/join/leave>''' - Choose to start or end an event, or as a member, choose to join or leave an event.
* '''/religion quest''' - Show your religion's daily quests.
* '''/religion reward <divine/expbuff>''' - Show your religion's reward points. By adding the <code><divine/expbuff></code> arguments, you can spend reward points to use either of them (see [[#Events]])

[[Category:Server Features]]

User:Silverpg017/Sandbox

2026-07-04T18:56:36Z

Silverpg017: Replaced content with "a"

User:Silverpg017/Sandbox

2026-07-04T18:56:26Z

Silverpg017:

Pactoria's '''religion system''' is one of the server's core features. It allows players to create their own religions and gain faith points as they complete daily quests and do sacrifices.

== Starting a religion ==
To create your own religion, type <code>/religion create <religion_name></code> in chat. You can invite other members typing <code>/religion invite <username></code>, or kick them (<code>/religion kick <username</code>).

== Ranks ==
There are five different ranks in a religion, in descending order:
* High Priest - Those who own the religion in-game.
* Priest - TBA
* Acolyte - TBA
* Devotee - TBA
* Initiate - Those who joined the religion and were not promoted.

== Events ==
Events are a core aspect in the religion system. There are three event tiers, depending on the attendee count:
* Tier 1: Minor Gathering (1-4 players)
* Tier 2: Sacred Assembly (5-9 players)
* Tier 3: Grand Conclave (10-∞ players)

To start a event, type <code>/religion event start</code>. For one of your members to join your event, they must type <code>/religion event join</code>. To end your event, you must type <code>/religion event end</code>.

Once your event ends, it will be sent to staff for evaluation and you may get reward points, which can be seen through <code>/religion reward</code>. You can either spend your reward points in a 1.5x Crop XP multiplier for thirty days, or you can get a Divine Intervention token.

== Offerings ==
Offerings are a core aspect in the religion system, and is the main way of getting faith points. Offerings may consist of either items (daily quests) or sacrifices (players), the latter giving you the most faith points. To make an offering or a sacrifice, the player will need to make an altar. Altars consist of a central water cauldron surrounded by four emerald blocks with lit candles on top of them.
[[File:Religion altar.png|thumb|Example of a working altar.]]

=== Daily quests ===
Daily quests can be browsed typing <code>/religion quest</code>, and they require certain items to offer. Once you have these items, drop them into an active altar cauldron and right-click the cauldron to complete the offering. You can also browse the remaining daily offerings by shift-right clicking the cauldron.

=== Sacrifices ===
Sacrifices work like offerings but said offering is a player. To do this, the sacrificed player must put position themselves inside the cauldron and another player must right-click the cauldron. This will kill the player and the religion will get 100 faith points. This can only be done once per day.

== Commands ==
* '''/religion create <religion_name>''' - Creates a religion
* '''/religion info <religion_name>''' - Show your religion's information. It shows your leader, your member count and your monthly and total faith points. This can also be used to browse other religions.
* '''/religion members <religion_name>''' - Show your (or another) religion's members, with their respective rank and individual faith points.
* '''/religion leaderboard <members/monthly/tiers>''' - Show a ranking of every religion based on either their all-time faith points (if no arguments are added), their monthly faith points, and you can also check the top member contributors and event tiers.
* '''/religion invite <username>''' - Invite a player to your religion
* '''/religion join <religion_name>''' - Join a religion. Requires invite.
* '''/religion rank <username> <high_priest/priest/acolyte/devotee/initiate>''' - Promotes or demotes a player within your religion.
* '''/religion kick <username>''' - Kick a member from your religion.
* '''/religion disband <religion_name>''' - Disbands your religion.
* '''/religion event <start/end/join/leave>''' - Choose to start or end an event, or as a member, choose to join or leave an event.
* '''/religion quest''' - Show your religion's daily quests.
* '''/religion reward <divine/expbuff>''' - Show your religion's reward points. By adding the <code><divine/expbuff></code> arguments, you can spend reward points to use either of them (see [[#Events]])

[[Category:Server Features]]

File:Religion altar.png

2026-07-04T18:20:42Z

Silverpg017:

Pactoria Wiki:Manual of Style

2026-07-01T17:30:52Z

Silverpg017: Created page with "The '''Manual of Style''' ('''MoS'''), also called '''formatting guidelines''' or just '''guidelines''' is the style manual for all articles in Pactoria Wiki. The purpose of these guidelines is to help the reader better read the wiki by having rules over its format, design and writing. Refer to [https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style Wikipedia's Manual of Style] for additional information. == Page names == * Page names are the title of every page or art..."

The '''Manual of Style''' ('''MoS'''), also called '''formatting guidelines''' or just '''guidelines''' is the style manual for all articles in Pactoria Wiki. The purpose of these guidelines is to help the reader better read the wiki by having rules over its format, design and writing. Refer to [https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style Wikipedia's Manual of Style] for additional information.

== Page names ==
* Page names are the title of every page or article* in the wiki. You may only create articles within the main and user [https://en.wikipedia.org/wiki/Wikipedia:Namespace namespaces].
** ''*Pages and articles aren't really the same, but for convenience's sake we'll interchangeably use these terms. [https://en.wikipedia.org/wiki/Wikipedia:The_difference_between_articles_and_pages Look up the difference between both terms if you're curious.]''
* Do not use articles (a, an, or the) as the first word in the page's title.
* Do not use punctuation or special characters in page names. This includes formatting i.e. italic or bold text, and page names must not be colored or include currency symbols or special characters.
* Use neutral titles for historical event articles. For example, instead of calling it "Nation's Totally Bad-Ass Deployment in Nation2", call it "Nation-Nation2 War". If you feel the need to use non-neutral names, you may include them in the article's [https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style/Lead_section lead section] as a secondary name.
* The page name should be precise and concise. Don't use vague wording and choose descriptive words.
* Every word in the page name must be capitalized.

== Page sections ==
* An article should start with a lead section. Infoboxes, images, and other related content should always be right-aligned. Message box templates such as [[Template:Lore|<nowiki>{{Lore}}</nowiki>]]
* An article's body must always be in third-person except for lore excerpts.
* In the article's body, use the present tense for entities that currently exist in the server's lore, and past tense for those that do not currently exist.
* In the article's body, always write out numbers that are less than three digits long. i.e. 99 = ninety-nine.

== Page headings ==
[[File:WP Table of contents.png|thumb|Table of contents are numbered]]
* A heading is an introductory title for a page section. They generally follow the same guidelines for page names.
* A heading must never be numbered or lettered as an outline. The table of contents already does such job.
* A heading must never reduntantly refer back to the article's subject. i.e. Instead of "Character's early life", use "Early life"
* Do not use links in headings.

== Markup ==
=== Italics ===
* Italics are used for emphasis, titles of creative works, foreign language terms or scientific plant, animal or race names.
* Avoid overusing italics to preserve the article's emphasis.

=== Boldface ===
* Boldface is commonly applied to the first occurrence of the page title's word or phrase in the lead, and most common synonyms.
* Avoid using boldface for emphasis, introducing new terms or expanding acronyms i.e. '''U'''nited '''C'''ollectivized '''L'''ands

== Punctuation ==
=== Apostrophes ===
* Use straight apostrophes (') instead of curvy apostrophes (’) or backticks (`)

=== Quotations ===
* Quotations may be used to illustrate points, establish context or attribute a point of view or idea.
* Do not put quotations in italics unless the quoted material would otherwise call for italics
* Quotations must always be clearly identified as such using double quotation marks ("quoted text") for quotations shorter than about 40 words.
* Quotations must always be identified using the double quote marks e.g. "example" for quotations shorter than 40 words. For quotations longer than 40 words, use the [[Template:Quote|<nowiki>{{Quote}}</nowiki>]] template.

=== Parentheses and brackets ===
* Use space before and after a bracket <code>[]</code> or a parenthesis <code>()</code>, but not inside either of them e.g. This [is] a sentence (that) exists. Do not use spaces next to parentheses and brackets if there is a colon, semicolon or a quotation mark.
* Brackets can be used inside quotes to indicate editorial replacements, insertions or grammatical corrections, but this should never alter the original meaning.
* Parentheses can be used inside quotes to indicate omissions, though this should never alter the original meaning.
* If an entire sentence is within brackets or parentheses, punctuation falls within the brackets.

=== Dashes ===
* Do not confuse hyphens (-) with dashes (– and —). There are two types of dashes: En dashes (–) and em dashes (—). They are both often used to mark divisions within a sentence and interruptions.
* To mark divisions within a sentence, both dashes can be used, but en dashes are spaced on both sides, while em dashes aren't. They can also be used to clarify a sentence's structure when parenthesis and commas are already being used. They should also be used sparingly to make reading easier.
* Use en dashes to express ranges that can be expressed with ''to'' or ''through'' e.g. 750–1000 people. Do not mix en dashes with ''between'' and ''from'' e.g. between 750 and 1000 people.
* Use en dashes for relationships between components i.e. boyfriend–girlfriend and compounds that include spaces, hyphens or dashes i.e. Pre–Matrix War.

== Infoboxes ==
* Do not create additional infoboxes; use the ones provided by the wiki team.
* Infoboxes always go to the right side of the page.
* Do not put 'none' or 'N/A' as data in an infobox unless necessary for the reader's experience. If not necessary, leave it blank.

== Links ==
* Always use hyperlinks. Do not use raw URLs in them. To use them, for example, use <code><nowiki>[[Main Page|this]]</nowiki></code> to show <code>[[Main Page|this]]</code>.
* Make links only relevant to the page's context, and only when necessary for the reader's understanding. Once you've put a hyperlink, do not overuse it throughout the article; use them once per heading (not sub-heading) at first occurrence. If you are having trouble, proofread your own article before creating it.
* To link to external pages, use <code><nowiki>[https://wiki-beta.pactoria.net/wiki/Main_Page this]</nowiki></code> to show <code>[https://wiki-beta.pactoria.net/wiki/Main_Page this]</code>. Do not use hyperlinks to external pages to redirect the reader to the wiki itself. External links should be accessible to the reader and used only in special occasions.

User:Silverpg017/Sandbox

2026-07-01T17:28:17Z

Silverpg017:

The '''Manual of Style''' ('''MoS'''), also called '''formatting guidelines''' or just '''guidelines''' is the style manual for all articles in Pactoria Wiki. The purpose of these guidelines is to help the reader better read the wiki by having rules over its format, design and writing. Refer to [https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style Wikipedia's Manual of Style] for additional information.

== Page names ==
* Page names are the title of every page or article* in the wiki. You may only create articles within the main and user [https://en.wikipedia.org/wiki/Wikipedia:Namespace namespaces].
** ''*Pages and articles aren't really the same, but for convenience's sake we'll interchangeably use these terms. [https://en.wikipedia.org/wiki/Wikipedia:The_difference_between_articles_and_pages Look up the difference between both terms if you're curious.]''
* Do not use articles (a, an, or the) as the first word in the page's title.
* Do not use punctuation or special characters in page names. This includes formatting i.e. italic or bold text, and page names must not be colored or include currency symbols or special characters.
* Use neutral titles for historical event articles. For example, instead of calling it "Nation's Totally Bad-Ass Deployment in Nation2", call it "Nation-Nation2 War". If you feel the need to use non-neutral names, you may include them in the article's [https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style/Lead_section lead section] as a secondary name.
* The page name should be precise and concise. Don't use vague wording and choose descriptive words.
* Every word in the page name must be capitalized.

== Page sections ==
* An article should start with a lead section. Infoboxes, images, and other related content should always be right-aligned. Message box templates such as [[Template:Lore|<nowiki>{{Lore}}</nowiki>]]
* An article's body must always be in third-person except for lore excerpts.
* In the article's body, use the present tense for entities that currently exist in the server's lore, and past tense for those that do not currently exist.
* In the article's body, always write out numbers that are less than three digits long. i.e. 99 = ninety-nine.

== Page headings ==
[[File:WP Table of contents.png|thumb|Table of contents are numbered]]
* A heading is an introductory title for a page section. They generally follow the same guidelines for page names.
* A heading must never be numbered or lettered as an outline. The table of contents already does such job.
* A heading must never reduntantly refer back to the article's subject. i.e. Instead of "Character's early life", use "Early life"
* Do not use links in headings.

== Markup ==
=== Italics ===
* Italics are used for emphasis, titles of creative works, foreign language terms or scientific plant, animal or race names.
* Avoid overusing italics to preserve the article's emphasis.

=== Boldface ===
* Boldface is commonly applied to the first occurrence of the page title's word or phrase in the lead, and most common synonyms.
* Avoid using boldface for emphasis, introducing new terms or expanding acronyms i.e. '''U'''nited '''C'''ollectivized '''L'''ands

== Punctuation ==
=== Apostrophes ===
* Use straight apostrophes (') instead of curvy apostrophes (’) or backticks (`)

=== Quotations ===
* Quotations may be used to illustrate points, establish context or attribute a point of view or idea.
* Do not put quotations in italics unless the quoted material would otherwise call for italics
* Quotations must always be clearly identified as such using double quotation marks ("quoted text") for quotations shorter than about 40 words.
* Quotations must always be identified using the double quote marks e.g. "example" for quotations shorter than 40 words. For quotations longer than 40 words, use the [[Template:Quote|<nowiki>{{Quote}}</nowiki>]] template.

=== Parentheses and brackets ===
* Use space before and after a bracket <code>[]</code> or a parenthesis <code>()</code>, but not inside either of them e.g. This [is] a sentence (that) exists. Do not use spaces next to parentheses and brackets if there is a colon, semicolon or a quotation mark.
* Brackets can be used inside quotes to indicate editorial replacements, insertions or grammatical corrections, but this should never alter the original meaning.
* Parentheses can be used inside quotes to indicate omissions, though this should never alter the original meaning.
* If an entire sentence is within brackets or parentheses, punctuation falls within the brackets.

=== Dashes ===
* Do not confuse hyphens (-) with dashes (– and —). There are two types of dashes: En dashes (–) and em dashes (—). They are both often used to mark divisions within a sentence and interruptions.
* To mark divisions within a sentence, both dashes can be used, but en dashes are spaced on both sides, while em dashes aren't. They can also be used to clarify a sentence's structure when parenthesis and commas are already being used. They should also be used sparingly to make reading easier.
* Use en dashes to express ranges that can be expressed with ''to'' or ''through'' e.g. 750–1000 people. Do not mix en dashes with ''between'' and ''from''.
* Use en dashes for relationships between components i.e. boyfriend–girlfriend and compounds that include spaces, hyphens or dashes i.e. Pre–Matrix War.

== Infoboxes ==
* Do not create additional infoboxes; use the ones provided by the wiki team.
* Infoboxes always go to the right side of the page.
* Do not put 'none' or 'N/A' as data in an infobox unless necessary for the reader's experience. If not necessary, leave it blank.

== Links ==
* Always use hyperlinks. Do not use raw URLs in them. To use them, for example, use <code><nowiki>[[Main Page|this]]</nowiki></code> to show <code>[[Main Page|this]]</code>.
* Make links only relevant to the page's context, and only when necessary for the reader's understanding. Once you've put a hyperlink, do not overuse it throughout the article; use them once per heading (not sub-heading) at first occurrence. If you are having trouble, proofread your own article before creating it.
* To link to external pages, use <code><nowiki>[https://wiki-beta.pactoria.net/wiki/Main_Page this]</nowiki></code> to show <code>[https://wiki-beta.pactoria.net/wiki/Main_Page this]</code>. Do not use hyperlinks to external pages to redirect the reader to the wiki itself. External links should be accessible to the reader and used only in special occasions.

User:Silverpg017/Sandbox

2026-07-01T17:26:07Z

Silverpg017:

The '''Manual of Style''' ('''MoS'''), also called '''formatting guidelines''' or just '''guidelines''' is the style manual for all articles in Pactoria Wiki. The purpose of these guidelines is to help the reader better read the wiki by having rules over its format, design and writing.

-Refer to https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style (i'll add most important MoS parts here tho)

== Page names ==
* Page names are the title of every page or article* in the wiki. You may only create articles within the main and user [https://en.wikipedia.org/wiki/Wikipedia:Namespace namespaces].
** ''*Pages and articles aren't really the same, but for convenience's sake we'll interchangeably use these terms. [https://en.wikipedia.org/wiki/Wikipedia:The_difference_between_articles_and_pages Look up the difference between both terms if you're curious.]''
* Do not use articles (a, an, or the) as the first word in the page's title.
* Do not use punctuation or special characters in page names. This includes formatting i.e. italic or bold text, and page names must not be colored or include currency symbols or special characters.
* Use neutral titles for historical event articles. For example, instead of calling it "Nation's Totally Bad-Ass Deployment in Nation2", call it "Nation-Nation2 War". If you feel the need to use non-neutral names, you may include them in the article's [https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style/Lead_section lead section] as a secondary name.
* The page name should be precise and concise. Don't use vague wording and choose descriptive words.
* Every word in the page name must be capitalized.

== Page sections ==
* An article should start with a lead section. Infoboxes, images, and other related content should always be right-aligned. Message box templates such as [[Template:Lore|<nowiki>{{Lore}}</nowiki>]]
* An article's body must always be in third-person except for lore excerpts.
* In the article's body, use the present tense for entities that currently exist in the server's lore, and past tense for those that do not currently exist.
* In the article's body, always write out numbers that are less than three digits long. i.e. 99 = ninety-nine.

== Page headings ==
[[File:WP Table of contents.png|thumb|Table of contents are numbered]]
* A heading is an introductory title for a page section. They generally follow the same guidelines for page names.
* A heading must never be numbered or lettered as an outline. The table of contents already does such job.
* A heading must never reduntantly refer back to the article's subject. i.e. Instead of "Character's early life", use "Early life"
* Do not use links in headings.

== Markup ==
=== Italics ===
* Italics are used for emphasis, titles of creative works, foreign language terms or scientific plant, animal or race names.
* Avoid overusing italics to preserve the article's emphasis.

=== Boldface ===
* Boldface is commonly applied to the first occurrence of the page title's word or phrase in the lead, and most common synonyms.
* Avoid using boldface for emphasis, introducing new terms or expanding acronyms i.e. '''U'''nited '''C'''ollectivized '''L'''ands

== Punctuation ==
=== Apostrophes ===
* Use straight apostrophes (') instead of curvy apostrophes (’) or backticks (`)

=== Quotations ===
* Quotations may be used to illustrate points, establish context or attribute a point of view or idea.
* Do not put quotations in italics unless the quoted material would otherwise call for italics
* Quotations must always be clearly identified as such using double quotation marks ("quoted text") for quotations shorter than about 40 words.
* Quotations must always be identified using the double quote marks e.g. "example" for quotations shorter than 40 words. For quotations longer than 40 words, use the [[Template:Quote|<nowiki>{{Quote}}</nowiki>]] template.

=== Parentheses and brackets ===
* Use space before and after a bracket <code>[]</code> or a parenthesis <code>()</code>, but not inside either of them e.g. This [is] a sentence (that) exists. Do not use spaces next to parentheses and brackets if there is a colon, semicolon or a quotation mark.
* Brackets can be used inside quotes to indicate editorial replacements, insertions or grammatical corrections, but this should never alter the original meaning.
* Parentheses can be used inside quotes to indicate omissions, though this should never alter the original meaning.
* If an entire sentence is within brackets or parentheses, punctuation falls within the brackets.

=== Dashes ===
* Do not confuse hyphens (-) with dashes (– and —). There are two types of dashes: En dashes (–) and em dashes (—). They are both often used to mark divisions within a sentence and interruptions.
* To mark divisions within a sentence, both dashes can be used, but en dashes are spaced on both sides, while em dashes aren't. They can also be used to clarify a sentence's structure when parenthesis and commas are already being used. They should also be used sparingly to make reading easier.
* Use en dashes to express ranges that can be expressed with ''to'' or ''through'' e.g. 750–1000 people. Do not mix en dashes with ''between'' and ''from''.
* Use en dashes for relationships between components i.e. boyfriend–girlfriend and compounds that include spaces, hyphens or dashes i.e. Pre–Matrix War.

== Infoboxes ==
* Do not create additional infoboxes; use the ones provided by the wiki team.
* Infoboxes always go to the right side of the page.
* Do not put 'none' or 'N/A' as data in an infobox unless necessary for the reader's experience. If not necessary, leave it blank.

== Links ==
* Always use hyperlinks. Do not use raw URLs in them. To use them, for example, use <code><nowiki>[[Main Page|this]]</nowiki></code> to show <code>[[Main Page|this]]</code>.
* Make links only relevant to the page's context, and only when necessary for the reader's understanding. Once you've put a hyperlink, do not overuse it throughout the article; use them once per heading (not sub-heading) at first occurrence. If you are having trouble, proofread your own article before creating it.
* To link to external pages, use <code><nowiki>[https://wiki-beta.pactoria.net/wiki/Main_Page this]</nowiki></code> to show <code>[https://wiki-beta.pactoria.net/wiki/Main_Page this]</code>. Do not use hyperlinks to external pages to redirect the reader to the wiki itself.

User:Silverpg017/Sandbox

2026-06-30T17:21:45Z

Silverpg017:

Template:GettingStartedContainer

2026-06-30T16:48:35Z

Silverpg017: Added link for Rulebook

{| style="width:100%; margin-top:7px"
| style="border:1px solid #cedff2; background-color:#f5faff; padding:5px 15px 15px 8px; vertical-align:top;" |

<h2 style="border-width:1px; border-style:solid; margin-top:3px; margin-bottom:0.5em; padding:0.2em 0.4em; font-size:120%; font-weight:bold; font-family:inherit; background:#cedff2; border-color: #a3b0bf;">Getting Started </h2>

<div style="display: flex; justify-content: space-between; gap: 20px; text-align:center;">

<div style="flex: 1;">[[File:Oaksign.png|100px|frameless|link=Category:Pactoria Content]]<br><br><span style="font-size:1.0em;">'''[[:Category:Pactoria Content|Gameplay & Features]]'''</span></div>

<div style="flex: 1;">[[File:Filledmap.png|100px|frameless|link=Dynmap]]<br><br><span style="font-size:1.0em;">'''Dynmap'''</span></div>

<div style="flex: 1;">[[File:Bookandquill.png|100px|frameless|link=Official Lore]]<br><br><span style="font-size:1.0em;">'''[[Official Lore]]'''</span></div>

<div style="flex: 1;">[[File:Book.png|100px|frameless|link=Rulebook]]<br><br><span style="font-size:1.0em;">'''[https://docs.google.com/document/d/1ylO4wE1T_kCvrcmyIwy0Q-3tHaBHGnteoipyKpd0pn0/edit?tab=t.0 Rulebook]'''</span></div>
|}

Template:MainPageContainer

2026-06-30T16:46:49Z

Silverpg017:

{| style="width:100%; margin-top:7px"
| style="border:1px solid #f0f0f0; background-color:#fafafa; padding:5px 15px 15px 8px; vertical-align:top; text-align: center;" |

[[File:Pactoria_logo.png|center|220px|link=Main Page]]<br />
<div style=font-size:20px; margin-bottom: 3px;">'''Welcome to the Pactoria Wiki!'''</div><br /><div style="margin-bottom: 10px;">This wiki has [[Special:Statistics|'''{{NUMBEROFACTIVEUSERS}} active users''']] maintaining [[Special:AllPages|'''{{NUMBEROFARTICLES}} articles''']] ([[Special:AllPages|'''{{NUMBEROFPAGES}} total pages''']]) and [[Special:ListFiles|'''{{NUMBEROFFILES}} images & videos''']].</div><br />
----<br />
<div style=font-size:20px; margin-bottom: 6px;">'''Social Media '''</div><br /><center>[https://discord.gg/jFP47huPx3 Discord] • [https://www.youtube.com/channel/UCAM5RvyUkL4IhQmdlgJBbxg Youtube] • [https://www.tiktok.com/@pactoriamc TikTok] • [Instagram (WIP)]</center> <br />
<center><big>'''Please read the [[Pactoria Wiki:Policies|Policies]] and [[Pactoria Wiki:Manual of Style|Manual of Style]] before editing and discussing!'''</big></center>
|}

Custom Recipes

2026-06-30T16:43:32Z

Silverpg017: Temporarily removing the inability to throw spears

Listed below, players can find all custom craftable recipes able to be used on Pactoria, including unique armor and sword variants, shields, spears, axes, rings, and (temp) the process of steelmaking.

== Armor Variants ==
In Pactoria, players are able to acquire custom cosmetic armor pieces via stonecutter.

Simply put an armor piece into the stonecutter to change the armor's cosmetic look. <gallery widths="250" heights="120" mode="packed" caption="'''Armor Variants'''">
File:Diamond helmet variant pact.png
File:Diamond chestplate variant pact.png
File:Diamond leggings variant pact.png
File:Diamond boots variant pact.png|alt=Diamond Armor Variants
File:Gold helm variant pact.png
File:Gold chestplate variant pact.png
File:Gold leggings variant pact.png
File:Gold boots variant pact.png
File:Iron helm variant pact.png
File:Iron chestplate variant pact.png
File:Iron leggings variant pact.png
File:Iron boots variant pact.png
</gallery>

== Sword Variants ==
Players can make custom sword variants via stonecutter.

Simply put a sword into the stonecutter.

Sword variants do not provide bonuses or negatives in attack damage or attack speed.

Names of swords listed in the stonecutter order below:

Ninjato, Kris, Katana, Longsword, Flambard, Falcata, Saber, Gladius, Shashka, Greatsword, Claymore, Cutlass, Falchion, Rapier, and Scimitar<gallery widths="365" heights="120" mode="packed" caption="'''Sword Variants'''">
File:Diamond sword variant pact.png
File:Gold sword variant pact.png
File:Iron sword variant pact.png
</gallery>

== Round Shield ==
Pactoria has 2 types of shields; Round Shields and Knight's Shields.

Round Shields are smaller and Knight's Shields are bigger, but they are both purely cosmetic and do not have added bonuses or negatives to each other.

Players can make them in the crafting table with 4 diamonds and a normal shield in the orders shown below.<gallery widths="365" heights="120" mode="packed" caption="Round and Knight's Shields">
File:Diamond round shield pact.png
File:Gold round shield pact.png
File:Iron round shield pact.png
File:Diamond knight shield pact.png
File:Gold knight shield pact.png
File:Iron knight shield pact.png
</gallery>

== Spear ==
Spears are different types of weapons available via crafting recipe in Pactoria.

<gallery widths="250" heights="120" mode="packed" caption="'''Spear Recipes'''">
File:Diamond spear pact.png
File:Gold spear pact.png
File:Iron spear pact.png
</gallery>

== Axe ==
Players can make custom axe variants via stonecutter.

Simply put an axe into the stonecutter.

Axe variants do not provide bonuses or negatives in attack damage or attack speed.

Names of axes listed in the stonecutter order below:

Morningstar, Flail, Club, Mace, Halberd, Glaive, Horseman's Axe, Battleaxe, and Warhammer<gallery widths="250" heights="120" mode="packed" caption="'''Axe Variants'''">
File:Diamond axe variant pact.png
File:Gold axe variant pact.png
File:Iron axe variant pact.png
</gallery>

== Rings ==
Rings are purely cosmetic items able to be crafted in the crafting table.

Rings can be used for roleplay or decoration.
[[File:Normal ring pact.png|left|thumb|'''Standard Ring Recipe''']]
<gallery widths="250" heights="120" mode="packed" caption="'''Ruby, Topaz, Emerald, and Aquamarine Rings'''">
File:Ruby ring pact.png
File:Topaz ring pact.png
File:Emerald ring pact.png
File:Aquamarine ring pact.png
</gallery>

== Steelmaking ==
{{See also|Steelmaking}}

<gallery widths="250" heights="120" mode="packed">
File:Coal coke pact.png|'''Coal coke (Smelting)'''
File:Steel pact.png|'''Steel Ingot'''
File:Steel block pact.png|'''Steel Block'''
File:Hammer pact.png|'''Hammer'''
</gallery>

User:Silverpg017/Sandbox

2026-06-30T16:38:18Z

Silverpg017:

File:WP Table of contents.png

2026-06-30T16:08:46Z

Silverpg017: From [https://en.wikipedia.org/wiki/File:WP_Table_of_contents.png]

== Summary ==
From [https://en.wikipedia.org/wiki/File:WP_Table_of_contents.png]

Pactoria Wiki:Policies

2026-06-21T15:17:26Z

Silverpg017: Created page with "===Common sense=== Breaking Pactoria Wiki's rules is easily avoidable if the editor has some common sense and knows not to disrupt the wiki's improvement and maintenance. Though, it is highly recommended to read all the rules to prevent any rule-breaks. ===Respect=== Any harassment, personal attacks, discrimination, insults, threats or any other behavior with the intent to disrespect or humiliate are prohibited. Constructive criticism and disagreements are allowed, but o..."

===Common sense===
Breaking Pactoria Wiki's rules is easily avoidable if the editor has some common sense and knows not to disrupt the wiki's improvement and maintenance. Though, it is highly recommended to read all the rules to prevent any rule-breaks.
===Respect===
Any harassment, personal attacks, discrimination, insults, threats or any other behavior with the intent to disrespect or humiliate are prohibited.
Constructive criticism and disagreements are allowed, but only if they speak about the matter at hand (an article, for example) and not the person themselves.
===Vandalism===
According to Wikipedia, vandalism is "editing a page in an intentionally disruptive or malicious manner.
Actions that are considered vandalism include, but are not limited to, deleting content without justification, adding nonsensical information, defacing pages, or intentionally disrupting the editing process.
===Enforcement===
One very important aspect of Pactoria Wiki's policies is that some of them are not firm. This means, they can change over time. But even when they are not firm, they are all enforced.
If a rule prevents you from improving or maintaining Pactoria Wiki's contents, ignore it. It is up to the Wiki Team's interpretation whether you have broken a rule or not.
===Non-original references===
Any references to events, people, entities and locations taken from real-life sources or other pieces of media will be immediately removed by the Wiki Team.
===Impartiality===
Accounts of lore, events, locations or people should be written from a neutral and balanced perspective. Contributors should present information fairly without promoting personal opinions, political views, commercial interests, or ideological positions.
In case of dispute i.e. edit wars, the wiki team is authorized to solve the dispute through the wiki's policies.
Edit wars occur when a repeated exchange of opposing edits are made to a contested article.
===Language===
The wiki's language and dialect is American English.
Any articles that are not mainly written in English will be deleted by the wiki team. Articles in other English dialects such as British or Australian English are allowed. The goal should be to make the article understandable for any English speaker, so avoid using terms that are only used by locals.
===Conflicts===
Disagreements between contributors should be resolved through discussion, evidence and consensus. Edit wars, personal disputes and retaliatory editing are prohibited. This includes repeatedly reverting edits without discussion, following another user to undo their contributions and escalating disagreements into personal attacks
===Staff decisions===
The wiki team is responsible for enforcing wiki policies and maintaining the wiki and its community. Deliberately and purposefully disrupting the team's work in the wiki will result in an immediate block.
Circumventing restrictions set by the wiki team is prohibited. Creating alt accounts to do so is also prohibited.
===Pactoria Rules===
Needless to say, the Pactoria Wiki is bound to Pactoria's rules, meaning the editor must adhere by its rules as well. While most of the rulebook does not overlap with the wiki's rules, some of them somewhat do and they should take priority.

Steelmaking

2026-06-13T17:16:32Z

Silverpg017:

'''Steelmaking''' is a core feature in Pactoria that allows players to make steel. Steel is used to craft siege weapons and utility items.

== Steelmaking process ==
#Smelt coal using lava in a blast furnace to obtain coal coke
#Mix (Drop) 4 iron ingots and 4 pieces of coal coke in a lava cauldron to obtain a hot steel ingot
##Make sure to drink a fire resistance potion as holding this item in your hand will burn you
#Shift and right-click on an anvil with the hot steel ingot in your hand and hammer down five items to get hot steel
#Drop the steel ingot on a water cauldron to cool it down and get a steel ingot

{{#ev:youtube|https://www.youtube.com/watch?v=7nAit4KmFxY}}

[[Category:Server Features]]

Custom Recipes

2026-06-13T17:15:35Z

Silverpg017: /* Steelmaking */

Listed below, players can find all custom craftable recipes able to be used on Pactoria, including unique armor and sword variants, shields, spears, axes, rings, and (temp) the process of steelmaking.

== Armor Variants ==
In Pactoria, players are able to acquire custom cosmetic armor pieces via stonecutter.

Simply put an armor piece into the stonecutter to change the armor's cosmetic look. <gallery widths="250" heights="120" mode="packed" caption="'''Armor Variants'''">
File:Diamond helmet variant pact.png
File:Diamond chestplate variant pact.png
File:Diamond leggings variant pact.png
File:Diamond boots variant pact.png|alt=Diamond Armor Variants
File:Gold helm variant pact.png
File:Gold chestplate variant pact.png
File:Gold leggings variant pact.png
File:Gold boots variant pact.png
File:Iron helm variant pact.png
File:Iron chestplate variant pact.png
File:Iron leggings variant pact.png
File:Iron boots variant pact.png
</gallery>

== Sword Variants ==
Players can make custom sword variants via stonecutter.

Simply put a sword into the stonecutter.

Sword variants do not provide bonuses or negatives in attack damage or attack speed.

Names of swords listed in the stonecutter order below:

Ninjato, Kris, Katana, Longsword, Flambard, Falcata, Saber, Gladius, Shashka, Greatsword, Claymore, Cutlass, Falchion, Rapier, and Scimitar<gallery widths="365" heights="120" mode="packed" caption="'''Sword Variants'''">
File:Diamond sword variant pact.png
File:Gold sword variant pact.png
File:Iron sword variant pact.png
</gallery>

== Round Shield ==
Pactoria has 2 types of shields; Round Shields and Knight's Shields.

Round Shields are smaller and Knight's Shields are bigger, but they are both purely cosmetic and do not have added bonuses or negatives to each other.

Players can make them in the crafting table with 4 diamonds and a normal shield in the orders shown below.<gallery widths="365" heights="120" mode="packed" caption="Round and Knight's Shields">
File:Diamond round shield pact.png
File:Gold round shield pact.png
File:Iron round shield pact.png
File:Diamond knight shield pact.png
File:Gold knight shield pact.png
File:Iron knight shield pact.png
</gallery>

== Spear ==
Spears are different types of weapons available via crafting recipe in Pactoria.

Spears do not provide more reach or any bonuses like other servers show. <gallery widths="250" heights="120" mode="packed" caption="'''Spear Recipes'''">
File:Diamond spear pact.png
File:Gold spear pact.png
File:Iron spear pact.png
</gallery>

== Axe ==
Players can make custom axe variants via stonecutter.

Simply put an axe into the stonecutter.

Axe variants do not provide bonuses or negatives in attack damage or attack speed.

Names of axes listed in the stonecutter order below:

Morningstar, Flail, Club, Mace, Halberd, Glaive, Horseman's Axe, Battleaxe, and Warhammer<gallery widths="250" heights="120" mode="packed" caption="'''Axe Variants'''">
File:Diamond axe variant pact.png
File:Gold axe variant pact.png
File:Iron axe variant pact.png
</gallery>

== Rings ==
Rings are purely cosmetic items able to be crafted in the crafting table.

Rings can be used for roleplay or decoration.
[[File:Normal ring pact.png|left|thumb|'''Standard Ring Recipe''']]
<gallery widths="250" heights="120" mode="packed" caption="'''Ruby, Topaz, Emerald, and Aquamarine Rings'''">
File:Ruby ring pact.png
File:Topaz ring pact.png
File:Emerald ring pact.png
File:Aquamarine ring pact.png
</gallery>

== Steelmaking ==
{{See also|Steelmaking}}

<gallery widths="250" heights="120" mode="packed">
File:Coal coke pact.png|'''Coal coke (Smelting)'''
File:Steel pact.png|'''Steel Ingot'''
File:Steel block pact.png|'''Steel Block'''
File:Hammer pact.png|'''Hammer'''
</gallery>

Steelmaking

2026-06-13T17:15:12Z

Silverpg017:

'''Steelmaking''' is a core feature in Pactoria that allows players to craft siege weapons and utility items.

== Steelmaking process ==
#Smelt coal using lava in a blast furnace to obtain coal coke
#Mix (Drop) 4 iron ingots and 4 pieces of coal coke in a lava cauldron to obtain a hot steel ingot
##Make sure to drink a fire resistance potion as holding this item in your hand will burn you
#Shift and right-click on an anvil with the hot steel ingot in your hand and hammer down five items to get hot steel
#Drop the steel ingot on a water cauldron to cool it down and get a steel ingot

{{#ev:youtube|https://www.youtube.com/watch?v=7nAit4KmFxY}}

[[Category:Server Features]]

Steelmaking

2026-06-13T17:14:57Z

Silverpg017: Created page with "'''Steelmaking''' is a core feature in Pactoria that allows players to craft siege weapons and utility items. == Steelmaking process == #Smelt coal using lava in a blast furnace to obtain coal coke #Mix (Drop) 4 iron ingots and 4 pieces of coal coke in a lava cauldron to obtain a hot steel ingot ##Make sure to drink a fire resistance potion as holding this item in your hand will burn you #Shift and right-click on an anvil with the hot steel ingot in your hand and hammer..."

Custom Recipes

2026-06-13T15:17:04Z

Silverpg017: Added hammer recipe

Listed below, players can find all custom craftable recipes able to be used on Pactoria, including unique armor and sword variants, shields, spears, axes, rings, and (temp) the process of steelmaking.

== Armor Variants ==
In Pactoria, players are able to acquire custom cosmetic armor pieces via stonecutter.

Simply put an armor piece into the stonecutter to change the armor's cosmetic look. <gallery widths="250" heights="120" mode="packed" caption="'''Armor Variants'''">
File:Diamond helmet variant pact.png
File:Diamond chestplate variant pact.png
File:Diamond leggings variant pact.png
File:Diamond boots variant pact.png|alt=Diamond Armor Variants
File:Gold helm variant pact.png
File:Gold chestplate variant pact.png
File:Gold leggings variant pact.png
File:Gold boots variant pact.png
File:Iron helm variant pact.png
File:Iron chestplate variant pact.png
File:Iron leggings variant pact.png
File:Iron boots variant pact.png
</gallery>

== Sword Variants ==
Players can make custom sword variants via stonecutter.

Simply put a sword into the stonecutter.

Sword variants do not provide bonuses or negatives in attack damage or attack speed.

Names of swords listed in the stonecutter order below:

Ninjato, Kris, Katana, Longsword, Flambard, Falcata, Saber, Gladius, Shashka, Greatsword, Claymore, Cutlass, Falchion, Rapier, and Scimitar<gallery widths="365" heights="120" mode="packed" caption="'''Sword Variants'''">
File:Diamond sword variant pact.png
File:Gold sword variant pact.png
File:Iron sword variant pact.png
</gallery>

== Round Shield ==
Pactoria has 2 types of shields; Round Shields and Knight's Shields.

Round Shields are smaller and Knight's Shields are bigger, but they are both purely cosmetic and do not have added bonuses or negatives to each other.

Players can make them in the crafting table with 4 diamonds and a normal shield in the orders shown below.<gallery widths="365" heights="120" mode="packed" caption="Round and Knight's Shields">
File:Diamond round shield pact.png
File:Gold round shield pact.png
File:Iron round shield pact.png
File:Diamond knight shield pact.png
File:Gold knight shield pact.png
File:Iron knight shield pact.png
</gallery>

== Spear ==
Spears are different types of weapons available via crafting recipe in Pactoria.

Spears do not provide more reach or any bonuses like other servers show. <gallery widths="250" heights="120" mode="packed" caption="'''Spear Recipes'''">
File:Diamond spear pact.png
File:Gold spear pact.png
File:Iron spear pact.png
</gallery>

== Axe ==
Players can make custom axe variants via stonecutter.

Simply put an axe into the stonecutter.

Axe variants do not provide bonuses or negatives in attack damage or attack speed.

Names of axes listed in the stonecutter order below:

Morningstar, Flail, Club, Mace, Halberd, Glaive, Horseman's Axe, Battleaxe, and Warhammer<gallery widths="250" heights="120" mode="packed" caption="'''Axe Variants'''">
File:Diamond axe variant pact.png
File:Gold axe variant pact.png
File:Iron axe variant pact.png
</gallery>

== Rings ==
Rings are purely cosmetic items able to be crafted in the crafting table.

Rings can be used for roleplay or decoration.
[[File:Normal ring pact.png|left|thumb|'''Standard Ring Recipe''']]
<gallery widths="250" heights="120" mode="packed" caption="'''Ruby, Topaz, Emerald, and Aquamarine Rings'''">
File:Ruby ring pact.png
File:Topaz ring pact.png
File:Emerald ring pact.png
File:Aquamarine ring pact.png
</gallery>

== Steelmaking ==
{{See also|Custom Brewing}}

<gallery widths="250" heights="120" mode="packed">
File:Coal coke pact.png|'''Coal coke (Smelting)'''
File:Steel pact.png|'''Steel Ingot'''
File:Steel block pact.png|'''Steel Block'''
File:Hammer pact.png|'''Hammer'''
</gallery>

Custom Recipes

2026-06-13T10:20:07Z

Silverpg017:

Listed below, players can find all custom craftable recipes able to be used on Pactoria, including unique armor and sword variants, shields, spears, axes, rings, and (temp) the process of steelmaking.

== Armor Variants ==
In Pactoria, players are able to acquire custom cosmetic armor pieces via stonecutter.

Simply put an armor piece into the stonecutter to change the armor's cosmetic look. <gallery widths="250" heights="120" mode="packed" caption="'''Armor Variants'''">
File:Diamond helmet variant pact.png
File:Diamond chestplate variant pact.png
File:Diamond leggings variant pact.png
File:Diamond boots variant pact.png|alt=Diamond Armor Variants
File:Gold helm variant pact.png
File:Gold chestplate variant pact.png
File:Gold leggings variant pact.png
File:Gold boots variant pact.png
File:Iron helm variant pact.png
File:Iron chestplate variant pact.png
File:Iron leggings variant pact.png
File:Iron boots variant pact.png
</gallery>

== Sword Variants ==
Players can make custom sword variants via stonecutter.

Simply put a sword into the stonecutter.

Sword variants do not provide bonuses or negatives in attack damage or attack speed.

Names of swords listed in the stonecutter order below:

Ninjato, Kris, Katana, Longsword, Flambard, Falcata, Saber, Gladius, Shashka, Greatsword, Claymore, Cutlass, Falchion, Rapier, and Scimitar<gallery widths="365" heights="120" mode="packed" caption="'''Sword Variants'''">
File:Diamond sword variant pact.png
File:Gold sword variant pact.png
File:Iron sword variant pact.png
</gallery>

== Round Shield ==
Pactoria has 2 types of shields; Round Shields and Knight's Shields.

Round Shields are smaller and Knight's Shields are bigger, but they are both purely cosmetic and do not have added bonuses or negatives to each other.

Players can make them in the crafting table with 4 diamonds and a normal shield in the orders shown below.<gallery widths="365" heights="120" mode="packed" caption="Round and Knight's Shields">
File:Diamond round shield pact.png
File:Gold round shield pact.png
File:Iron round shield pact.png
File:Diamond knight shield pact.png
File:Gold knight shield pact.png
File:Iron knight shield pact.png
</gallery>

== Spear ==
Spears are different types of weapons available via crafting recipe in Pactoria.

Spears do not provide more reach or any bonuses like other servers show. <gallery widths="250" heights="120" mode="packed" caption="'''Spear Recipes'''">
File:Diamond spear pact.png
File:Gold spear pact.png
File:Iron spear pact.png
</gallery>

== Axe ==
Players can make custom axe variants via stonecutter.

Simply put an axe into the stonecutter.

Axe variants do not provide bonuses or negatives in attack damage or attack speed.

Names of axes listed in the stonecutter order below:

Morningstar, Flail, Club, Mace, Halberd, Glaive, Horseman's Axe, Battleaxe, and Warhammer<gallery widths="250" heights="120" mode="packed" caption="'''Axe Variants'''">
File:Diamond axe variant pact.png
File:Gold axe variant pact.png
File:Iron axe variant pact.png
</gallery>

== Rings ==
Rings are purely cosmetic items able to be crafted in the crafting table.

Rings can be used for roleplay or decoration.
[[File:Normal ring pact.png|left|thumb|'''Standard Ring Recipe''']]
<gallery widths="250" heights="120" mode="packed" caption="'''Ruby, Topaz, Emerald, and Aquamarine Rings'''">
File:Ruby ring pact.png
File:Topaz ring pact.png
File:Emerald ring pact.png
File:Aquamarine ring pact.png
</gallery>

== Steelmaking ==
{{See also|Custom Brewing}}

<gallery widths="250" heights="120" mode="packed">
File:Coal coke pact.png|'''Coal coke (Smelting)'''
File:Steel pact.png|'''Steel Ingot'''
File:Steel block pact.png|'''Steel Block'''
</gallery>

File:Steel block pact.png
</gallery>

Module:Hatnote/styles.css

2026-06-13T10:17:48Z

Silverpg017: Created page with "/* {{pp|small=y}} */ .hatnote { font-style: italic; } /* Limit structure CSS to divs because of Module:Hatnote inline */ div.hatnote { /* @noflip */ padding-left: 1.6em; margin-bottom: 0.5em; } .hatnote i { font-style: normal; } /* The templatestyles causes an 'empty' span between hatnotes */ .hatnote + span.mw-empty-elt + .hatnote, /* remove this selector when Parsoid is the only parser, see also phab:T200206 */ .hatnote + link + .hatnote { margin-top:..."

/* {{pp|small=y}} */
.hatnote {
font-style: italic;
}

/* Limit structure CSS to divs because of [[Module:Hatnote inline]] */
div.hatnote {
/* @noflip */
padding-left: 1.6em;
margin-bottom: 0.5em;
}

.hatnote i {
font-style: normal;
}

/* The templatestyles causes an 'empty' span between hatnotes */
.hatnote + span.mw-empty-elt + .hatnote,
/* remove this selector when Parsoid is the only parser, see also [[phab:T200206]] */
.hatnote + link + .hatnote {
margin-top: -0.5em;
}

@media print {
body.ns-0 .hatnote {
display: none !important;
}
}

Module:Format link

2026-06-13T10:17:06Z

Silverpg017: Created page with "-------------------------------------------------------------------------------- -- Format link -- -- Makes a wikilink from the given link and display values. Links are escaped -- with colons if necessary, and links to sections are detected and displayed -- with " § " as a separator rather than the standard MediaWiki "#". Used in -- the {{format link}} template. -------------------------------------------------------------------------------- local libraryUtil = require(..."

--------------------------------------------------------------------------------
-- Format link
--
-- Makes a wikilink from the given link and display values. Links are escaped
-- with colons if necessary, and links to sections are detected and displayed
-- with " § " as a separator rather than the standard MediaWiki "#". Used in
-- the {{format link}} template.
--------------------------------------------------------------------------------
local libraryUtil = require('libraryUtil')
local checkType = libraryUtil.checkType
local checkTypeForNamedArg = libraryUtil.checkTypeForNamedArg
local mArguments -- lazily initialise [[Module:Arguments]]
local mError -- lazily initialise [[Module:Error]]
local yesno -- lazily initialise [[Module:Yesno]]

local p = {}

--------------------------------------------------------------------------------
-- Helper functions
--------------------------------------------------------------------------------

local function getArgs(frame)
-- Fetches the arguments from the parent frame. Whitespace is trimmed and
-- blanks are removed.
mArguments = require('Module:Arguments')
return mArguments.getArgs(frame, {parentOnly = true})
end

local function removeInitialColon(s)
-- Removes the initial colon from a string, if present.
return s:match('^:?(.*)')
end

local function maybeItalicize(s, shouldItalicize)
-- Italicize s if s is a string and the shouldItalicize parameter is true.
if s and shouldItalicize then
return '<i>' .. s .. '</i>'
else
return s
end
end

local function parseLink(link)
-- Parse a link and return a table with the link's components.
-- These components are:
-- - link: the link, stripped of any initial colon (always present)
-- - page: the page name (always present)
-- - section: the page name (may be nil)
-- - display: the display text, if manually entered after a pipe (may be nil)
link = removeInitialColon(link)

-- Find whether a faux display value has been added with the {{!}} magic
-- word.
local prePipe, display = link:match('^(.-)|(.*)$')
link = prePipe or link

-- Find the page, if it exists.
-- For links like [[#Bar]], the page will be nil.
local preHash, postHash = link:match('^(.-)#(.*)$')
local page
if not preHash then
-- We have a link like [[Foo]].
page = link
elseif preHash ~= '' then
-- We have a link like [[Foo#Bar]].
page = preHash
end

-- Find the section, if it exists.
local section
if postHash and postHash ~= '' then
section = postHash
end

return {
link = link,
page = page,
section = section,
display = display,
}
end

local function formatDisplay(parsed, options)
-- Formats a display string based on a parsed link table (matching the
-- output of parseLink) and an options table (matching the input options for
-- _formatLink).
local page = maybeItalicize(parsed.page, options.italicizePage)
local section = maybeItalicize(parsed.section, options.italicizeSection)
if (not section) then
return page
elseif (not page) then
return mw.ustring.format('§ %s', section)
else
return mw.ustring.format('%s § %s', page, section)
end
end

local function missingArgError(target)
mError = require('Module:Error')
return mError.error{message =
'Error: no link or target specified! ([[' .. target .. '#Errors|help]])'
}
end

--------------------------------------------------------------------------------
-- Main functions
--------------------------------------------------------------------------------

function p.formatLink(frame)
-- The formatLink export function, for use in templates.
yesno = require('Module:Yesno')
local args = getArgs(frame)
local link = args[1] or args.link
local target = args[3] or args.target
if not (link or target) then
return missingArgError('Template:Format link')
end

return p._formatLink{
link = link,
display = args[2] or args.display,
target = target,
italicizePage = yesno(args.italicizepage),
italicizeSection = yesno(args.italicizesection),
categorizeMissing = args.categorizemissing
}
end

function p._formatLink(options)
-- The formatLink export function, for use in modules.
checkType('_formatLink', 1, options, 'table')
local function check(key, expectedType) --for brevity
checkTypeForNamedArg(
'_formatLink', key, options[key], expectedType or 'string', true
)
end
check('link')
check('display')
check('target')
check('italicizePage', 'boolean')
check('italicizeSection', 'boolean')
check('categorizeMissing')

-- Normalize link and target and check that at least one is present
if options.link == '' then options.link = nil end
if options.target == '' then options.target = nil end
if not (options.link or options.target) then
return missingArgError('Module:Format link')
end

local parsed = parseLink(options.link)
local display = options.display or parsed.display
local catMissing = options.categorizeMissing
local category = ''

-- Find the display text
if not display then display = formatDisplay(parsed, options) end

-- Handle the target option if present
if options.target then
local parsedTarget = parseLink(options.target)
parsed.link = parsedTarget.link
parsed.page = parsedTarget.page
end

-- Test if page exists if a diagnostic category is specified
if catMissing and (mw.ustring.len(catMissing) > 0) then
local title = nil
if parsed.page then title = mw.title.new(parsed.page) end
if title and (not title.isExternal) then
local success, exists = pcall(function() return title.exists end)
if success and not exists then
category = mw.ustring.format('[[Category:%s]]', catMissing)
end
end
end

-- Format the result as a link
if parsed.link == display then
return mw.ustring.format('[[:%s]]%s', parsed.link, category)
else
return mw.ustring.format('[[:%s|%s]]%s', parsed.link, display, category)
end
end

--------------------------------------------------------------------------------
-- Derived convenience functions
--------------------------------------------------------------------------------

function p.formatPages(options, pages)
-- Formats an array of pages using formatLink and the given options table,
-- and returns it as an array. Nil values are not allowed.
local ret = {}
for i, page in ipairs(pages) do
ret[i] = p._formatLink{
link = page,
categorizeMissing = options.categorizeMissing,
italicizePage = options.italicizePage,
italicizeSection = options.italicizeSection
}
end
return ret
end

return p

Module:Hatnote list

2026-06-13T10:16:38Z

Silverpg017: Created page with "-------------------------------------------------------------------------------- -- Module:Hatnote list -- -- -- -- This module produces and formats lists for use in hatnotes. In particular, -- -- it implements the for-see list, i.e. lists of "For X, see Y" statements, -- -- as used in {{about}}, {{redirect}}, and their variants. Also introd..."

--------------------------------------------------------------------------------
-- Module:Hatnote list --
-- --
-- This module produces and formats lists for use in hatnotes. In particular, --
-- it implements the for-see list, i.e. lists of "For X, see Y" statements, --
-- as used in {{about}}, {{redirect}}, and their variants. Also introduced --
-- are andList & orList helpers for formatting lists with those conjunctions. --
--------------------------------------------------------------------------------

local mArguments --initialize lazily
local mFormatLink = require('Module:Format link')
local mHatnote = require('Module:Hatnote')
local libraryUtil = require('libraryUtil')
local checkType = libraryUtil.checkType
local p = {}

--------------------------------------------------------------------------------
-- List stringification helper functions
--
-- These functions are used for stringifying lists, usually page lists inside
-- the "Y" portion of "For X, see Y" for-see items.
--------------------------------------------------------------------------------

--default options table used across the list stringification functions
local stringifyListDefaultOptions = {
conjunction = "and",
separator = ",",
altSeparator = ";",
space = " ",
formatted = false
}

--Searches display text only
local function searchDisp(haystack, needle)
return string.find(
string.sub(haystack, (string.find(haystack, '|') or 0) + 1), needle
)
end

-- Stringifies a list generically; probably shouldn't be used directly
local function stringifyList(list, options)
-- Type-checks, defaults, and a shortcut
checkType("stringifyList", 1, list, "table")
if #list == 0 then return nil end
checkType("stringifyList", 2, options, "table", true)
options = options or {}
for k, v in pairs(stringifyListDefaultOptions) do
if options[k] == nil then options[k] = v end
end
local s = options.space
-- Format the list if requested
if options.formatted then
list = mFormatLink.formatPages(
{categorizeMissing = mHatnote.missingTargetCat}, list
)
end
-- Set the separator; if any item contains it, use the alternate separator
local separator = options.separator
for k, v in pairs(list) do
if searchDisp(v, separator) then
separator = options.altSeparator
break
end
end
-- Set the conjunction, apply Oxford comma, and force a comma if #1 has "§"
local conjunction = s .. options.conjunction .. s
if #list == 2 and searchDisp(list[1], "§") or #list > 2 then
conjunction = separator .. conjunction
end
-- Return the formatted string
return mw.text.listToText(list, separator .. s, conjunction)
end

--DRY function
function p.conjList (conj, list, fmt)
return stringifyList(list, {conjunction = conj, formatted = fmt})
end

-- Stringifies lists with "and" or "or"
function p.andList (...) return p.conjList("and", ...) end
function p.orList (...) return p.conjList("or", ...) end

--------------------------------------------------------------------------------
-- For see
--
-- Makes a "For X, see [[Y]]." list from raw parameters. Intended for the
-- {{about}} and {{redirect}} templates and their variants.
--------------------------------------------------------------------------------

--default options table used across the forSee family of functions
local forSeeDefaultOptions = {
andKeyword = 'and',
title = mw.title.getCurrentTitle().text,
otherText = 'other uses',
forSeeForm = 'For %s, see %s.',
}

--Collapses duplicate punctuation at end of string, ignoring italics and links
local function punctuationCollapse (text)
return text:match("[.?!]('?)%1(%]?)%2%.$") and text:sub(1, -2) or text
end

-- Structures arguments into a table for stringification, & options
function p.forSeeArgsToTable (args, from, options)
-- Type-checks and defaults
checkType("forSeeArgsToTable", 1, args, 'table')
checkType("forSeeArgsToTable", 2, from, 'number', true)
from = from or 1
checkType("forSeeArgsToTable", 3, options, 'table', true)
options = options or {}
for k, v in pairs(forSeeDefaultOptions) do
if options[k] == nil then options[k] = v end
end
-- maxArg's gotten manually because getArgs() and table.maxn aren't friends
local maxArg = 0
for k, v in pairs(args) do
if type(k) == 'number' and k > maxArg then maxArg = k end
end
-- Structure the data out from the parameter list:
-- * forTable is the wrapper table, with forRow rows
-- * Rows are tables of a "use" string & a "pages" table of pagename strings
-- * Blanks are left empty for defaulting elsewhere, but can terminate list
local forTable = {}
local i = from
local terminated = false
-- If there is extra text, and no arguments are given, give nil value
-- to not produce default of "For other uses, see foo (disambiguation)"
if options.extratext and i > maxArg then return nil end
-- Loop to generate rows
repeat
-- New empty row
local forRow = {}
-- On blank use, assume list's ended & break at end of this loop
forRow.use = args[i]
if not args[i] then terminated = true end
-- New empty list of pages
forRow.pages = {}
-- Insert first pages item if present
table.insert(forRow.pages, args[i + 1])
-- If the param after next is "and", do inner loop to collect params
-- until the "and"'s stop. Blanks are ignored: "1|and||and|3" → {1, 3}
while args[i + 2] == options.andKeyword do
if args[i + 3] then
table.insert(forRow.pages, args[i + 3])
end
-- Increment to next "and"
i = i + 2
end
-- Increment to next use
i = i + 2
-- Append the row
table.insert(forTable, forRow)
until terminated or i > maxArg

return forTable
end

-- Stringifies a table as formatted by forSeeArgsToTable
function p.forSeeTableToString (forSeeTable, options)
-- Type-checks and defaults
checkType("forSeeTableToString", 1, forSeeTable, "table", true)
checkType("forSeeTableToString", 2, options, "table", true)
options = options or {}
for k, v in pairs(forSeeDefaultOptions) do
if options[k] == nil then options[k] = v end
end
-- Stringify each for-see item into a list
local strList = {}
if forSeeTable then
for k, v in pairs(forSeeTable) do
local useStr = v.use or options.otherText
local pagesStr =
p.andList(v.pages, true) or
mFormatLink._formatLink{
categorizeMissing = mHatnote.missingTargetCat,
link = mHatnote.disambiguate(options.title)
}
local forSeeStr = string.format(options.forSeeForm, useStr, pagesStr)
forSeeStr = punctuationCollapse(forSeeStr)
table.insert(strList, forSeeStr)
end
end
if options.extratext then table.insert(strList, punctuationCollapse(options.extratext..'.')) end
-- Return the concatenated list
return table.concat(strList, ' ')
end

-- Produces a "For X, see [[Y]]" string from arguments. Expects index gaps
-- but not blank/whitespace values. Ignores named args and args < "from".
function p._forSee (args, from, options)
local forSeeTable = p.forSeeArgsToTable(args, from, options)
return p.forSeeTableToString(forSeeTable, options)
end

-- As _forSee, but uses the frame.
function p.forSee (frame, from, options)
mArguments = require('Module:Arguments')
return p._forSee(mArguments.getArgs(frame), from, options)
end

return p

Module:Hatnote

2026-06-13T10:16:16Z

Silverpg017: Created page with "-------------------------------------------------------------------------------- -- Module:Hatnote -- -- -- -- This module produces hatnote links and links to related articles. It -- -- implements the {{hatnote}} and {{format link}} meta-templates and includes -- -- helper functions for other Lua hatnote modules...."

--------------------------------------------------------------------------------
-- Module:Hatnote --
-- --
-- This module produces hatnote links and links to related articles. It --
-- implements the {{hatnote}} and {{format link}} meta-templates and includes --
-- helper functions for other Lua hatnote modules. --
--------------------------------------------------------------------------------

local libraryUtil = require('libraryUtil')
local checkType = libraryUtil.checkType
local checkTypeForNamedArg = libraryUtil.checkTypeForNamedArg
local mArguments -- lazily initialise [[Module:Arguments]]
local yesno -- lazily initialise [[Module:Yesno]]
local formatLink -- lazily initialise [[Module:Format link]] ._formatLink

local p = {}

--------------------------------------------------------------------------------
-- Helper functions
--------------------------------------------------------------------------------

local function getArgs(frame)
-- Fetches the arguments from the parent frame. Whitespace is trimmed and
-- blanks are removed.
mArguments = require('Module:Arguments')
return mArguments.getArgs(frame, {parentOnly = true})
end

local function removeInitialColon(s)
-- Removes the initial colon from a string, if present.
return s:match('^:?(.*)')
end

function p.defaultClasses(inline)
-- Provides the default hatnote classes as a space-separated string; useful
-- for hatnote-manipulation modules like [[Module:Hatnote group]].
return
(inline == 1 and 'hatnote-inline' or 'hatnote') .. ' ' ..
'navigation-not-searchable'
end

function p.disambiguate(page, disambiguator)
-- Formats a page title with a disambiguation parenthetical,
-- i.e. "Example" → "Example (disambiguation)".
checkType('disambiguate', 1, page, 'string')
checkType('disambiguate', 2, disambiguator, 'string', true)
disambiguator = disambiguator or 'disambiguation'
return mw.ustring.format('%s (%s)', page, disambiguator)
end

function p.findNamespaceId(link, removeColon)
-- Finds the namespace id (namespace number) of a link or a pagename. This
-- function will not work if the link is enclosed in double brackets. Colons
-- are trimmed from the start of the link by default. To skip colon
-- trimming, set the removeColon parameter to false.
checkType('findNamespaceId', 1, link, 'string')
checkType('findNamespaceId', 2, removeColon, 'boolean', true)
if removeColon ~= false then
link = removeInitialColon(link)
end
local namespace = link:match('^(.-):')
if namespace then
local nsTable = mw.site.namespaces[namespace]
if nsTable then
return nsTable.id
end
end
return 0
end

function p.makeWikitextError(msg, helpLink, addTrackingCategory, title)
-- Formats an error message to be returned to wikitext. If
-- addTrackingCategory is not false after being returned from
-- [[Module:Yesno]], and if we are not on a talk page, a tracking category
-- is added.
checkType('makeWikitextError', 1, msg, 'string')
checkType('makeWikitextError', 2, helpLink, 'string', true)
yesno = require('Module:Yesno')
title = title or mw.title.getCurrentTitle()
-- Make the help link text.
local helpText
if helpLink then
helpText = ' ([[' .. helpLink .. '|help]])'
else
helpText = ''
end
-- Make the category text.
local category
if not title.isTalkPage -- Don't categorise talk pages
and title.namespace ~= 2 -- Don't categorise userspace
and yesno(addTrackingCategory) ~= false -- Allow opting out
then
category = 'Hatnote templates with errors'
category = mw.ustring.format(
'[[%s:%s]]',
mw.site.namespaces[14].name,
category
)
else
category = ''
end
return mw.ustring.format(
'<strong class="error">Error: %s%s.</strong>%s',
msg,
helpText,
category
)
end

local curNs = mw.title.getCurrentTitle().namespace
p.missingTargetCat =
--Default missing target category, exported for use in related modules
((curNs == 0) or (curNs == 14)) and
'Articles with hatnote templates targeting a nonexistent page' or nil

function p.quote(title)
--Wraps titles in quotation marks. If the title starts/ends with a quotation
--mark, kerns that side as with {{-'}}
local quotationMarks = {
["'"]=true, ['"']=true, ['“']=true, ["‘"]=true, ['”']=true, ["’"]=true
}
local quoteLeft, quoteRight = -- Test if start/end are quotation marks
quotationMarks[string.sub(title, 1, 1)],
quotationMarks[string.sub(title, -1, -1)]
if quoteLeft or quoteRight then
title = mw.html.create("span"):wikitext(title)
end
if quoteLeft then title:css("padding-left", "0.15em") end
if quoteRight then title:css("padding-right", "0.15em") end
return '"' .. tostring(title) .. '"'
end

--------------------------------------------------------------------------------
-- Hatnote
--
-- Produces standard hatnote text. Implements the {{hatnote}} template.
--------------------------------------------------------------------------------
p[''] = function (frame) return p.hatnote(frame:newChild{ title = "Template:Hatnote" }) end

function p.hatnote(frame)
local args = getArgs(frame)
local s = args[1]
if not s then
return p.makeWikitextError(
'no text specified',
'Template:Hatnote#Errors',
args.category
)
end
return p._hatnote(s, {
extraclasses = args.extraclasses,
selfref = args.selfref
})
end

function p._hatnote(s, options)
checkType('_hatnote', 1, s, 'string')
checkType('_hatnote', 2, options, 'table', true)
options = options or {}
local inline = options.inline
local hatnote = mw.html.create(inline == 1 and 'span' or 'div')
local extraclasses
if type(options.extraclasses) == 'string' then
extraclasses = options.extraclasses
end

hatnote
:attr('role', 'note')
:addClass(p.defaultClasses(inline))
:addClass(extraclasses)
:addClass(options.selfref and 'selfref' or nil)
:wikitext(s)

return mw.getCurrentFrame():extensionTag{
name = 'templatestyles', args = { src = 'Module:Hatnote/styles.css' }
} .. tostring(hatnote)
end

return p

Module:Labelled list hatnote

2026-06-13T10:15:43Z

Silverpg017: Created page with "-------------------------------------------------------------------------------- -- Labelled list -- -- -- -- This module does the core work of creating a hatnote composed of a list -- -- prefixed by a colon-terminated label, i.e. "LABEL: [andList of pages]", -- -- for {{see also}} and similar templates...."

--------------------------------------------------------------------------------
-- Labelled list --
-- --
-- This module does the core work of creating a hatnote composed of a list --
-- prefixed by a colon-terminated label, i.e. "LABEL: [andList of pages]", --
-- for {{see also}} and similar templates. --
--------------------------------------------------------------------------------

local mHatnote = require('Module:Hatnote')
local mHatlist = require('Module:Hatnote list')
local mArguments --initialize lazily
local yesno --initialize lazily
local p = {}

-- Defaults global to this module
local defaults = {
label = 'See also', --Final fallback for label argument
labelForm = '%s: %s',
prefixes = {'label', 'label ', 'l'},
template = 'Module:Labelled list hatnote'
}

-- Localizable message strings
local msg = {
errorSuffix = '#Errors',
noInputWarning = 'no page names specified',
noOutputWarning =
"'''[[%s]] — no output: none of the target pages exist.'''"
}

-- Helper function that pre-combines display parameters into page arguments.
-- Also compresses sparse arrays, as a desirable side-effect.
function p.preprocessDisplays (args, prefixes)
-- Prefixes specify which parameters, in order, to check for display options
-- They each have numbers auto-appended, e.g. 'label1', 'label 1', & 'l1'
prefixes = prefixes or defaults.prefixes
local indices = {}
local sparsePages = {}
for k, v in pairs(args) do
if type(k) == 'number' then
indices[#indices + 1] = k
local display
for i = 1, #prefixes do
display = args[prefixes[i] .. k]
if display then break end
end
sparsePages[k] = display and
string.format('%s|%s', string.gsub(v, '|.*$', ''), display) or v
end
end
table.sort(indices)
local pages = {}
for k, v in ipairs(indices) do pages[#pages + 1] = sparsePages[v] end
return pages
end

--Helper function to get a page target from a processed page string
--e.g. "Page|Label" → "Page" or "Target" → "Target"
local function getTarget(pagename)
local pipe = string.find(pagename, '|')
return string.sub(pagename, 0, pipe and pipe - 1 or nil)
end

-- Produces a labelled pages-list hatnote.
-- The main frame (template definition) takes 1 or 2 arguments, for a singular
-- and (optionally) plural label respectively:
-- * {{#invoke:Labelled list hatnote|labelledList|Singular label|Plural label}}
-- The resulting template takes pagename & label parameters normally.
function p.labelledList (frame)
mArguments = require('Module:Arguments')
yesno = require('Module:Yesno')
local labels = {frame.args[1] or defaults.label}
labels[2] = frame.args[2] or labels[1]
labels[3] = frame.args[3] --no defaulting
labels[4] = frame.args[4] --no defaulting
local template = frame:getParent():getTitle()
local args = mArguments.getArgs(frame, {parentOnly = true})
local pages = p.preprocessDisplays(args)
local options = {
category = yesno(args.category),
extraclasses = frame.args.extraclasses,
ifexists = yesno(frame.args.ifexists),
namespace = frame.args.namespace or args.namespace,
selfref = yesno(frame.args.selfref or args.selfref),
template = template
}
return p._labelledList(pages, labels, options)
end
local function exists(title)
local success, result = pcall(function() return title.exists end)
if success then
return result
else
return true
end
end

function p._labelledList (pages, labels, options)
local removednonexist = false
if options.ifexists then
for k = #pages, 1, -1 do --iterate backwards to allow smooth removals
local v = pages[k]
if mw.ustring.sub(mw.text.trim(v), 1, 1) ~= "#" then
local title = mw.title.new(getTarget(v), namespace)
if (v == '') or (title == nil) or not exists(title) then
table.remove(pages, k)
removednonexist = true
end
end
end
end
labels = labels or {}
label = (#pages == 1 and labels[1] or labels[2]) or defaults.label
for k, v in pairs(pages) do
if mHatnote.findNamespaceId(v) ~= 0 then
label =
(
#pages == 1 and
(labels[3] or labels[1] or defaults.label) or
(labels[4] or labels[2] or defaults.label)
) or defaults.label
end
end
if #pages == 0 then
if removednonexist then
mw.addWarning(
string.format(
msg.noOutputWarning, options.template or defaults.template
)
)
return ''
else
return mHatnote.makeWikitextError(
msg.noInputWarning,
(options.template or defaults.template) .. msg.errorSuffix,
options.category
)
end
end
local text = string.format(
options.labelForm or defaults.labelForm,
label,
mHatlist.andList(pages, true)
)
local hnOptions = {
extraclasses = options.extraclasses,
selfref = options.selfref
}
return mHatnote._hatnote(text, hnOptions)
end

return p

Template:See also

2026-06-13T10:14:40Z

Silverpg017: Created page with "<includeonly>{{#invoke:Labelled list hatnote|labelledList|See also|ifexists={{{ifexists|true}}}}}</includeonly><noinclude> {{documentation}}  </noinclude>"

<includeonly>{{#invoke:Labelled list hatnote|labelledList|See also|ifexists={{{ifexists|true}}}}}</includeonly><noinclude>
{{documentation}}

</noinclude>

Custom Recipes

2026-05-10T19:46:45Z

Silverpg017: Undo revision 738 by Pickleation (talk)

Listed below, players can find all custom craftable recipes able to be used on Pactoria, including unique armor and sword variants, shields, spears, axes, rings, and (temp) the process of steelmaking.

== Armor Variants ==
In Pactoria, players are able to acquire custom cosmetic armor pieces via stonecutter.

Simply put an armor piece into the stonecutter to change the armor's cosmetic look. <gallery widths="365" heights="365" mode="packed" caption="'''Armor Variants'''">
File:Diamond helmet variant pact.png
File:Diamond chestplate variant pact.png
File:Diamond leggings variant pact.png
File:Diamond boots variant pact.png|alt=Diamond Armor Variants
File:Gold helm variant pact.png
File:Gold chestplate variant pact.png
File:Gold leggings variant pact.png
File:Gold boots variant pact.png
File:Iron helm variant pact.png
File:Iron chestplate variant pact.png
File:Iron leggings variant pact.png
File:Iron boots variant pact.png
</gallery>

== Sword Variants ==
Players can make custom sword variants via stonecutter.

Simply put a sword into the stonecutter.

Sword variants do not provide bonuses or negatives in attack damage or attack speed.

Names of swords listed in the stonecutter order below:

Ninjato, Kris, Katana, Longsword, Flambard, Falcata, Saber, Gladius, Shashka, Greatsword, Claymore, Cutlass, Falchion, Rapier, and Scimitar<gallery widths="512" heights="512" mode="packed" caption="'''Sword Variants'''">
File:Diamond sword variant pact.png
File:Gold sword variant pact.png
File:Iron sword variant pact.png
</gallery>

== Round Shield ==
Pactoria has 2 types of shields; Round Shields and Knight's Shields.

Round Shields are smaller and Knight's Shields are bigger, but they are both purely cosmetic and do not have added bonuses or negatives to each other.

Players can make them in the crafting table with 4 diamonds and a normal shield in the orders shown below.<gallery widths="470" heights="470" mode="packed" caption="Round and Knight's Shields">
File:Diamond round shield pact.png
File:Gold round shield pact.png
File:Iron round shield pact.png
File:Diamond knight shield pact.png
File:Gold knight shield pact.png
File:Iron knight shield pact.png
</gallery>

== Spear ==
Spears are different types of weapons available via crafting recipe in Pactoria.

Spears do not provide more reach or any bonuses like other servers show. <gallery widths="512" heights="512" mode="packed" caption="'''Spear Recipes'''">
File:Diamond spear pact.png
File:Gold spear pact.png
File:Iron spear pact.png
</gallery>

== Axe ==
Players can make custom axe variants via stonecutter.

Simply put an axe into the stonecutter.

Axe variants do not provide bonuses or negatives in attack damage or attack speed.

Names of axes listed in the stonecutter order below:

Morningstar, Flail, Club, Mace, Halberd, Glaive, Horseman's Axe, Battleaxe, and Warhammer<gallery widths="512" heights="512" mode="packed" caption="'''Axe Variants'''">
File:Diamond axe variant pact.png
File:Gold axe variant pact.png
File:Iron axe variant pact.png
</gallery>

== Rings ==
Rings are purely cosmetic items able to be crafted in the crafting table.

Rings can be used for roleplay or decoration.
[[File:Normal ring pact.png|left|thumb|'''Standard Ring Recipe''']]
<gallery widths="215" heights="215" caption="'''Ruby, Topaz, Emerald, and Aquamarine Rings'''">
File:Ruby ring pact.png
File:Topaz ring pact.png
File:Emerald ring pact.png
File:Aquamarine ring pact.png
</gallery>

== Steelmaking ==
Steelmaking article is WIP.

Steel process below.

Smelt Coal into Coal Coke, Coal Coke becomes Steel (this process is WIP), Steel can be turned into blocks.<gallery widths="512" heights="512" mode="packed" caption="'''Steelmaking WIP'''">
File:Coal coke pact.png
File:Steel pact.png
File:Steel block pact.png
</gallery>