http://wiki.warfactory.co/api.php?action=feedcontributions&feedformat=atom&user=Mr.NorwoodWarfactory Wiki - User contributions [en]2026-05-12T05:40:19ZUser contributionsMediaWiki 1.43.0http://wiki.warfactory.co/index.php?title=Warfactory_2_design&diff=230Warfactory 2 design2025-11-14T08:31:58Z<p>Mr.Norwood: </p>
<hr />
<div>Warfactory is a 1.12 Modpack made specifically for large faction server SMPs,<br />
based around HBM:NTM and Gregtech, using Modular Warfare Shining and possibly<br />
Mcheli for combat. The Modpack features an in-house fork of the Warforge claim mod,<br />
adjusted for a more dynamic, fair and exciting faction experience.<br />
<br />
== General Principles ==<br />
The pack must be accommodating to both veterans and new players, offering experience that is well documented and easily inferred from context clues. The progression will be tailored towards a much faster and dynamic style, compared to vanilla GT.<br />
<br />
Resources will be given very generously and infrastructure will be easy to set up, and in-game challenges will be tailored towards quick-thinking and high performance instead of endurance (grind). <br />
Combat balance is very important to us. Every item and system will be designed and improved with more tactical combat experience in mind. We take a hard stance against creative flight, buff stacking, teleportation, insane armor values and other game breaking features that have commonly been seen in other commonly used packs. Guile gives far greater rewards than material advantages.<br />
<br />
=== “Shoulders of Giants” Approach ===<br />
Having certain “milestone” machines maintain their relevance across several tiers, undergoing only incremental upgrades. This will incentivize staying in one place. Moreover, as long as a team has good risk management, they’ll have backups of these machines to get them up and running easily, making progression faster and more rewarding.<br />
Say a ULV reworked blast furnace has no coils. As we progress, we give it coil upgrades and incrementally approve what it can cook.<br />
<br />
To encourage different play styles, we will have 3 different win conditions:<br />
* Wonder winner – The team which has the nicest buildings and wonders.<br />
* Domination victory – The team that topples the most bases.<br />
* Progression victory – The most technologically advanced team.<br />
<br />
== Combat ==<br />
This is the section for the combat for WF2.<br />
<br />
==== Infantry combat ====<br />
The most exciting part of the game is perhaps the infantry combat. From our experience, players want a more tactical and grounded combat that still indeed feels like infantry combat. In the past, the traditional packs, which were not made with combat in mind, would give players access to overpowered tools. The combat would be more similar to fights from DragonBall , where the goal is to use the most overpowered and cheaty method of inflicitng damage while causing game to have trouble registering hits on you. In our modpack, players will need to be aware of their positioning, make strategic pushes, build forward operating bases, manage their inventory to avoid slowdowns, like in other conventional shooters<br />
<br />
==== Guns ====<br />
Just like warfactory 1.0, we will have guns in the pack. Our current mod of choice is modular warfare shining, allowing us to have a framework for constantly expanding arsenal. We will also make use of new and improved HBM guns and turrets. We will integrate the guns with <br />
NTM armor system, that will make for interesting combat, devoid of bullet sponges and cheap one-shot tactics.<br />
<br />
==== Weight system ====<br />
Using likes of Iguana tweaks, we will introduce a simple weight system that prevents players from becoming a walking armory. Those limits will only apply to combat-related things, as to not slow down progression inside of the modpack. Furthermore, we will add inventory limits that will prevent players from stashing too many things such as medicine, to prevent drawn out combat and encourage team play. Vehicles will not be possible for players to pick up either, making them a lot more precious and encourage proper handling of them, instead of it being a pocket weapon of mass destruction. Vehicles will be deployed using special assembling multiblocks, that one will need to deploy on the field.<br />
<br />
==== Medical system ====<br />
To spice up gameplay, a simple medical system will be introduced. There are 2 types of damage: "Light" damage and "Hard" damage. Light damage will damage player normally, allowing players to use simple healing methods such as bandages, pain killers. Hard damage decreases player's health pool making them unable to recover without use of more sophisticated means. For such cases, more potent drugs will be introduced, such as opiates. Those are very potent, but dangerous drugs, which can heal, but have many drawbacks and should be handled with caution. Reckless use may cause instant death, or strong debuffs. Last class are stimulants, which are the source of buffs. They also can come with drawbacks. The system may grow with time, however this groundwork goes a long way and makes healing a bit more interesting compared to vanilla<br />
<br />
=== Base raiding ===<br />
Raiding should be as difficult as defending yourself. As veterans of the modded landscape, we have noticed the general meta to be:<br />
<br />
You make cobble box underground and push progression mindlessly<br />
Make cheapest throwable explosive to destroy claims (if they exist)<br />
Use psyops or bruteforce to find other cobble boxes<br />
Raid the cobble box to get some loot<br />
Hope you won't get found, or you need to move the entire base in about an hour<br />
<br />
We completely disagree with this meta, it makes attacking too powerful and impossible to defend against due to the nature of minecraft. Base planning makes no sense when, after your base is found, the entire team will be occupied with defending itself against the lowest tier explosives.<br />
The only real way to defend yourself is to never get found, which is not an engaging and fun game loop. Attacking teams also spend most of their time traveling around the map, trying to find the base via bruteforce, which is not a fun experience either. Which encourages cheating, in the form of BlockESP to make the experience bearable.<br />
Our mod: Warforge factions will make players rethink the way they play faction servers. Bases will require time demanding strategic sieges that will take strategic effort from the attacker. With extended defensive tooling from mods such as NTM, base design, defenses, and automation will hopefully become an important aspect of the game.<br />
The land you will settle down on will also be very significant, giving teams advantages for settling down in resource rich areas. Some exclusive rare materials that will make specific subbranches of military and industry more viable. Those will not be required for progression, but offer tactical resource advantage.<br />
<br />
=== Early Combat ===<br />
The first combat will be done using the Large Metal Press multi, which works similar to the burner press from HBM. This will be used to obtain the first guns. The Gear Foundry will be the way you make armor, weapons and advanced tools. It will be upgradable similar to the Chemplant from GTNH.<br />
<br />
==== Radar ====<br />
We will feature tools like the radar to make finding bases viable in the early midgame of the tech progression tree. Allowing for base finding to be much more streamlined, and making hiding strategies much less viable. Radar will require computation, power, and be placed relatively high up with access to the skyline. Quite cumbersome and fragile, yet game changing when it comes to recon. It will find an average point of enemy bases and index them according to how big and populous the base is. Meaning, the teams that are more ahead will have more eyes on them.<br />
<br />
==== Factions progression ====<br />
Factions will be at the heart of your factory, they provide as your source of chunk claiming and chunk loading. However, to expand the area you can control the strength of your defenses. Your factions will have limited possible chunks they can claim, to expand their limit, teams must provide special resources to the faction, in order to increase their claim power.<br />
<br />
==== Suppliers ====<br />
Special multiblocks called suppliers will allow bases to bolster their defenses. Multiblocks will require a steady supply of quality food to increase the defense factor of a certain area, about 3x3 chunk area (will only work on claimed chunks). For a buff to be applied, it must be done while not under siege. The machine will refuse to buff the base if it was turned on after the siege started. Machines will increase their strength depending on the amount of food supplied. Type of food item will be determined by faction tier, lower tier factions will require lower tier foods, while high tier factions will require high quality foodstuffs. The amount of claimed chunks will also increase the amount of food required. <br />
<br />
==== MC-heli ====<br />
We want to make use of a custom fork of MCHELI, developed to integrate into our pack. Vehicles will help players to move around the map and conduct sieges. It may not come with WF2, as it will be a challenge to refactor.<br />
Vehicle balance issues come from availability, ease of deployment, and effectiveness against infantry. Traditionally, vehicles in Minecraft modpacks tended to allow any player to deploy multiple vehicles from their inventory, allowing for chaotic sprawls of combat vehicles right before the enemy. Furthermore, vehicles can be damaged by infantry far too easily, making players treat them as a nuisance rather than a threat. There is a large gap in less flashy and more tactical vehicle types, such as artillery or mortars. Due to Minecraft's terrible inventory system, logistic vehicles or IFVs are rarely considered, as due to access to superb (overpowered) forms of transportation or teleportation for both personnel and items, they are not as highly desired as tanks or fighter jets.<br />
<br />
Our goal is to make vehicles both expensive and powerful in warfare, especially in the tactical aspect. To address vehicle sprawl and the treatment of vehicles as a get-out-of-jail ace card, **players won't be able to place or hold vehicles in their inventories**. Instead, they will be required to build specialized assembly machines for the assembly of vehicles. The vehicle assembly will not only require a lot of high-quality materials and energy, just like a real vehicle assembly does, but it will also require a blueprint that will require research. The blueprints are reusable and duplicable for a moderate price. Vehicles assembled will simply be put onto an assembly platform. This means that the only way of transporting a vehicle to the front line must be done with the vehicle in its physical form. Such as driving or chaining/stashing it in a bigger vehicle. This rule will apply to most vehicles, except some smaller emplacements that are meant to be deployed by infantry, such as mounted machine guns. Those emplacements, however, will still pose a challenge to transport due to weight. We may provide some solutions for stashing vehicles in the form of vehicle depots that will allow players to safely stash vehicles in neat multiblocks, saving space (and performance).<br />
<br />
Depending on vehicle type, they may require different types of effort in order to take down. Light APCs may be possible to be taken down by a heavy machine gun, while heavy battle tanks may require sustained barrage or expensive high-tech infantry weaponry, assuming that a team can execute a proper anti-tank assult.<br />
<br />
Vehicles will have a rudimentary maintenance and parts system in which certain parts of a vehicle can be damaged, which will inflict different amounts of damage, as well as be able to disable certain systems. Those damages will range from field-serviceable to requiring specialized tooling and machines in order to fix. The general rule is that light and most medium damage can be serviced in the field to a limited degree, but still allow for the vehicle to be operational, while heavy damage will require a proper site to repair. This, while a difficult system to execute, will make vehicle combat a lot more tactical, rather than just an endurance run who can shoot the most rockets at the other party.<br />
Because teleportation is made difficult, if not completely unavailable, and items carry weight, transport and logistic vehicles will play a role in supplying both personnel and resources to the front line. The inventory system of vehicles will be rewritten to remove all of its limitations. <br />
<br />
Uavs will also be extremely important in warfare. We plan to featue a wide set of drones, from small civilian grade disposable drones to heavy expensive military drones. Currently drones have limited use due to range restictions, though this will be resoved.<br />
<br />
<br />
== Progression ==<br />
The 2 Main mods carrying progression will be Gregtech and HBM, with focus on Gregtech and HBM filling in with what we theme is the "highlight" content.<br />
<br />
=== Asymmetric progression ===<br />
To make progression and battles more dynamic, we want to introduce specific branches of progression depending on player's access to resources. For example, player has access to renewable large source of uranium. This allows player to start nuclear research early, giving access things such as early nuclear power, low yield nuclear weapons. Another example would be access to a specific resource that would allow player to produce energy weapons, which while not explicitly better than standard weapons, would be more effective against standard bullet-proof armor. Such design decisions would be sprinkled around the modpack. To enforce uniqueness of those resources, the map would have a limited amount of such resources, regulated by the administrator. This would encourage turf wars, to make players fight over strategic resources across the map. <br />
<br />
=== Faster progression ===<br />
Our goal is to make progression mesh well with the fast landscape that modded faction wars is. Let's be honest, GregTech's call to fame came from it's "immersive" (slow) gameplay. While we do want to retain the complexity and logistical challenge that GregTech provides, we want to remove the tedious, repetitive parts that are present in the mod. This ranges from large sweeping changes, to small optimizations. Here is a list of things that we want to introduce in order to archive this:<br />
<br />
* Early, but limited access to AE2<br />
* Recursive pipe shuttering<br />
* Multiblock blueprints<br />
* Complete rework of early game in order to decrease micro-crafting<br />
* Early centralized power and more streamlined powergrid handling<br />
<br />
=== Powergrid handling ===<br />
From experience in management of large bases, power management in GregTech is poorly designed. In early game, it is a chore. Low voltages make your expansion limited, it is impossible to have a properly designed, centralized power system that players can expand. Lategame however, it becomes overtly reliant on storing massive amounts of EU inside different kinds of EU storages. By the time you are in lategame, many interesting solutions are presented to the player, which in my opinion is a lost opportunity when it comes to game design. This does not even take into account AE2's EU/RF p2p's which trivialize power grid planning, to a point that all other tools become almost obsolete. We plan to mend this issue, using few simple machines and design choices.<br />
<br />
===== Large transformers =====<br />
To make power grid managment easier, players will get access to large transformers, which are simple multiblock structures that allow player to place energy hatches and dynamos, that will transform power. They would be tiered, with first tier allowing player to transform power from LV to HV and another one that would be able to tranform power for all of the tiers (up to UV). Goal is to make power grid managment much more streamlined, less reliant on hacky transformer chains or separate power grids.<br />
<br />
===== AC power =====<br />
To help players transfer power between different points. An "AC" power converter machine would be introduced. "AC" power would be a voltage type that would be unusable with machines, however would not suffer the same per-block loss like the "DC" power. Some kind of loss would still be at play, either passive loss on conversion between voltages or a loss proportional to amount of current drawn through the system. The AC power is there to ease dealing with power transfer in the early game to midgame, having less of an impact as games progresses into lategame. <br />
<br />
===== Removal of the power "cheese" =====<br />
To make power menagment matter in lategame stages. We will curb the amount of EU player can store. We will also restrict ways player can transfer EU, to avoid things such as AE2 completely breaking the game meta.<br />
<br />
=== Steam Age Rework ===<br />
Steam age is the biggest thorn in GT's design. It suffers from issues that we specifically want to avoid in our modpack. We opt into redesigning the steam age to focus on player to quickly be able to reach LV, while allowing player to make use of extra machines, that will stay relevant well into the midgame.<br />
[[File:Steam age progression chart.png|thumb|Chart for the steam age progression, showcasing the flow and key resources required to progress. (May change at any time)]]<br />
<br />
=== Steam power overhaul ===<br />
Steam is a rather underutilized power source in later stages of GregTech, due to its unremarkable power density. It is a shame that this power source gets completely outshined by the the time you get to LV. We want to introduce higher density steam types, which paired with high pressure pipes allow for scalable throughput beyond earlygame. With NTM there are also even more interesting way to boil water, using many different reactors.<br />
<br />
Other current ideas for new ways to generate steam are:<br />
* The Boiler Tower, a multi which gives higher yields exponentially the taller it is.<br />
* The Heat Exchanger, a multi which turns lava and water into steam.<br />
* A reworked Large Boiler system to overcome its flaws and to make them relevant again.<br />
<br />
In a parallel to the real world’s development, petrochemistry is unlocked very early on. High-pressure steam is used to extract oil and refine it. Of course, these early methods are not nearly as successful as more advanced systems, and we cannot refine advanced petrochemicals like HOG this way. Bunker fuel, kerosene, etc is unlocked around this time.<br />
<br />
With this, we can construct power systems that will sustain us far into the electrical tiers.<br />
<br />
==== Early Combustion ====<br />
In alignment with the “shoulders of giants” philosophy, the player will be given crude combustion engines in late ULV. These engines, through incremental upgrade, can sustain them well into the LV-EV tiers. To begin, you will only be able to produce crude kerosene and bunker fuel, and suffer poor efficiency and very crude engines that can only really sustain you for a while.<br />
<br />
Early petro fuels won’t produce power, but will power boilers to produce oodles of steam. Direct combustion engines (and steam turbines) are unlocked in LV, but can be made easily by retrofitting your early boiler systems. <br />
=== Lv-Ev Tenets ===<br />
<br />
=== Low Voltage ===<br />
Low voltage will unlock AE2 as we recognize that this mod is inseparable with GT due to its Gregtech’s complexity ramping up as soon as player gets to later stages. Early AE2 will empower the team to produce larger and more complex factories, as they won’t feel they need to wait until they reach AE2 (common issue with GTNH). This may make people think this will kill complexity, which is why we opt to enable keep channels enabled. <br />
<br />
Players will unlock plethora of basic self defence guns and infrastructure, such as barbed wire, concrete.<br />
<br />
===== AE2's common pitfall: oversimplification of bases =====<br />
AE2 is a powerful tool, which can do many many things. This is what makes it great. However, AE2 can actually oversimplify a lot of systems, via its powerful ondemand crafting system. We want to give players access to the powerful tools, though stray away from introducing AE2s full overpowered suite of tools that make game become AE2 trivia simulator.<br />
<br />
=== Medium Voltage ===<br />
=== High Voltage ===<br />
<br />
=== Ev-Luv Tenets ===<br />
<br />
=== Extreme Voltage ===<br />
<br />
=== Insane Voltage ===<br />
<br />
=== Ludicrous Voltage ===<br />
<br />
=== ZPM Voltage ===<br />
I doubt we need to go this far, only one team will most likely even make it to ZPM or beyond it<br />
<br />
=== Multi Rework ===<br />
<br />
For WF2 we want to move away from GCYM, as it has some intrinsic problems with it, as well as it doesn’t fit into what we want for a pvp pack.<br />
<br />
<br />
We will implement new multis, either through an external mod or through WFCore. And the consensus is that the first round of multis will be available in early HV to incentivise the creation of large scale automation early on.<br />
<br />
<br />
The Parallels will most likely be akin to how GT++ calculates parallels.<br />
<br />
=== NTM Space ===<br />
Since we are also porting the NTM space content, we are looking into integrating it into Warfactory, and as it's such a major part of the progression it will get it's own section.<br />
<br />
== Takeaways and lessons from WF1 ==<br />
* All movement options within Warfactory 2, have to be evaluated and checked for if they are too overpowered, not to have a repeat of the hooks situation from Warfactory 1.<br />
* Ensure armor and weapons are tested THOROUGHLY (to prevent a repeat of the redstone arsenal incident)<br />
* Make sure to do small scale tests with testers who are intentionally made to cause as much lag as possible to then make a spark profile to find sources of lag to prevent another visual ores situation.<br />
* We will also be cutting down on the amount of mods to prevent interactions in-between the mods.<br />
<br />
<br />
== The Dev Test ==<br />
A Dev Test will be orchestrated as a way of engaging the community before WF2, while still using it as a platform to see if the more experimental features work in a event setting.<br />
<br />
The devtest will be done as follows, first the top 2 people of each team<ref>Would likely be the Leader and Co-Leader of each respective team</ref> would be invited to a discord. This is to discuss the rules and to make any last minute alterations to the pack before the devtest takes place.<br />
<br />
After everything is sorted out, all the members of each respective team will be added, and if there are still server slots there will be a google form setup for invitations.<br />
<br />
The prevailing idea is that once the pack reaches LuV, the devtest will occur. As it is not a traditional event, the server will have very specific win conditions. Those being finishing LuV and obtaining the Crystal Mainframe. This will be akin to the "Science Victory" in Civ6.</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=Warforge&diff=229Warforge2025-08-31T15:02:47Z<p>Mr.Norwood: </p>
<hr />
<div>Warforge is a mod created by jamioflan, creator of FlansMod. The mod was PVP centric claim mod made specifically for now defunct Flan's modded. 1.12.2 SMP. During development of Warfactory 1, the mod was forked and rewritten by Mr. Norwood and EightXOR8, introducing many additional features.<br />
<br />
General overview<br />
The mod allows players to create factions, which grant them the ability to claim chunks as well as get passive resources from claimed chunks. Factions can raid other factions, allowing them to destroy enemy claims and take over bases.<br />
<br />
== Guide ==<br />
<br />
=== Creating a faction ===<br />
<br />
To create a faction, a player must first obtain a '''citadel'''. Citadels can be placed on any '''unclaimed chunk''' and can be picked up by '''sneak-interacting''' with them, provided the citadel is unclaimed. <br />
[[File:UnclaimedCitadelGui.png|thumb|UI presented on freshly placed citadel]]<br />
<br />
A factionless player can create a faction by placing a citadel, interacting with it, and clicking the '''“Create”''' button. They can then '''name the faction''' and choose its '''color'''.<br />
<br />
* '''Faction name''' is permanent and cannot be changed.<br />
* '''Faction color''' can be changed later via the citadel menu.<br />
<br />
Every claimed chunk displays a '''colored border''' corresponding to its faction. These borders cannot be disabled globally but can be toggled on or off individually by pressing '''B''' (default) or using the <code>/f borders</code> command.<br />
<br />
The player who creates the faction is automatically set as the '''leader'''.<br />
=== Inviting players, ranks transferring, ownership, leaving ===<br />
Every faction has a '''leader''', who is the faction’s owner. Beyond the leader, factions can have '''officers''' and '''regular members'''.<br />
<br />
* '''Officers''' can perform additional actions, such as inviting or expelling players and placing claims.<br />
* '''Members''' can be promoted to officers or demoted using <code>/f promote</code> and <code>/f demote</code>.<br />
* The '''leader''' can transfer leadership to another member with <code>/f setleader</code>.<br />
<br />
All faction members have an '''extra name tag field''' that displays their faction affiliation.<br />
----<br />
<br />
=== Chunk veins and passive yields ===<br />
Chunks can contain valuable resource '''veins'''. Players can view veins by '''sneaking''', which displays a UI indicator for the vein in the chunks they are currently in. <br />
<br />
[[File:Vein.png|Chunk vein of Rich Gold-Diamond, with 100% chance of 80 gold ores, 80% of extra 10 gold ores, and 100% of 3 diamonds, with 60% possibility for an extra diamond. |center|thumb|500x500px]]<br />
<br />
Veins have '''three quality levels''' — Poor, Fair, and Rich — which affect the total yield. The display shows:<br />
<br />
* The '''item'''.<br />
* The '''number of items''' you will receive (in square brackets).<br />
* Up to '''two percentages''':<br />
*# The first percentage indicates the chance of obtaining the listed items.<br />
*# The second percentage indicates the chance of getting '''one extra item'''.<br />
<br />
<blockquote>Note: An item can have multiple independent drop chances within the same vein.</blockquote>Veins can occur at different rates depending on the '''dimension''', and all vein-specific settings can be adjusted in <code>warforge/veins.cfg</code>.<br />
<br />
'''Yield collection:''' Items from veins are automatically deposited into the chunk’s claim at set intervals, configurable in the main configuration file.<br />
<br />
=== Expanding Claim area and citadel upgrading ===<br />
To expand your faction’s claim area, players with the rank of officer or higher can place claim blocks. Currently, there are two types: basic and reinforced, which differ in strength. Strength determines how many points attackers must gain to win a siege.<br />
<br />
If the citadel level system is enabled, it restricts the number of claims a faction can have, preventing players from placing extra claims once the limit is reached.<br />
<br />
[[File:UpgradeUI.png|thumb|Citadel Upgrade UI|left]]<br />
<br />
To level up a citadel, an officer or higher must interact with it and click the “Upgrade Citadel” button. This opens a GUI showing the required items for the upgrade. If the player has the items and confirms by pressing “Upgrade”, the items are removed from the player’s inventory and the citadel levels up.<br />
<br />
The number of levels, their claim limits, and the required items can be configured in the file: <code>warforge/upgrade_levels.cfg</code>.<br />
<br />
<br />
<br />
<br />
=== Sieges ===<br />
Sieges allow factions to attack other factions, unclaiming their chunks, preventing them from being reclaimed, or even taking over their territory. A faction can start a siege by placing a siege structure next to the enemy’s land, opening the siege menu, and selecting the chunk to target. The siege will only begin if the attacking faction is not under a losing penalty.<br />
[[File:Siege camp UI.png|thumb|Siege camp UI, with attacker's siege camp in the center, with enemy claim chunk to the north|center]]<br />
During an active siege, both attackers and defenders see an overhead display showing siege progress. The siege functions as a '''tug-of-war''': killing enemies grants points to the respective side. The siege timer is influenced by the attacker’s '''momentum''' – gained from winning previous sieges and lost when a siege is lost.<br />
[[File:SiegeBar.png|frameless|center|891x891px]]<br />
<br />
* When the timer reaches 0, attackers earn a point and the timer resets.<br />
* Timer values based on momentum can be configured in the main configuration file.<br />
* Each attacker win grants an extra momentum point, which lasts for a configurable duration. If the momentum expires or the siege is lost, it resets to 0.<br />
* If attackers start a siege with 0 momentum, a siege penalty is applied.<br />
A siege is considered '''abandoned''' if all members of one side leave the siege area. By default, this area includes a '''2-chunk radius around the siege chunk''' (configurable in the main config) and the '''entire claim area of the defenders'''.<br />
<br />
* If defenders were offline when the siege began, they are not considered abandoned until a defender logs in and then leaves the siege area.<br />
* The deserting side has a limited amount of time to return to the siege area before the siege is marked as failed.<br />
* Factions are notified via chat whenever a siege is at risk of being abandoned.<br />
<br />
The point ranges depend on defender's claim type, surrounding claims and claim reinforces that may be present on or around their claimed chunks.<br />
<br />
<br />
===Player commands===<br />
<br />
* <code>/f invite <playerName></code> – Invite a player to join your faction.<br />
* <code>/f accept</code> – Accept a pending faction invitation.<br />
* <code>/f disband</code> – Disband your faction permanently (leader only).<br />
* <code>/f expel <playerName></code> – Remove a member from your faction (officer or leader).<br />
* <code>/f leave</code> – Leave your current faction.<br />
* <code>/f time</code> – Check the amount of time your faction has been active or remaining siege/claim timers.<br />
* <code>/f info <factionName></code> – View information about a specific faction (members, claims, stats).<br />
* <code>/f top</code> – Show a leaderboard of top factions (by wealth, kills, or other metrics).<br />
* <code>/f wealth</code> – Check your faction’s total wealth.<br />
* <code>/f legacy</code> – View your faction’s legacy.<br />
* <code>/f notoriety</code> – Check your faction’s notoriety or reputation in the world, affected by amount of kills they get.<br />
* <code>/f borders</code> – Toggle the display of faction claim borders.</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=File:SiegeBar.png&diff=228File:SiegeBar.png2025-08-31T14:59:37Z<p>Mr.Norwood: </p>
<hr />
<div>siege bar</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=Warforge&diff=227Warforge2025-08-31T14:30:25Z<p>Mr.Norwood: /* Chunk veins and passive yields */</p>
<hr />
<div>Warforge is a mod created by jamioflan, creator of FlansMod. Mod was PVP centric claim mod made specifically for now defunct Flan's modded. 1.12.2 SMP. During development of Warfactory 1, the mod was forked and rewritten by Mr. Norwood and EightXOR8, introducing many additional features.<br />
<br />
General overview<br />
The mod allows players to create factions, which grant them the ability to claim chunks as well as get passive resources from claimed chunks. Factions can raid other factions, allowing them to destroy enemy claims and take over bases.<br />
<br />
== Guide ==<br />
<br />
=== Creating a faction ===<br />
<br />
To create a faction, a player must first obtain a '''citadel'''. Citadels can be placed on any '''unclaimed chunk''' and can be picked up by '''sneak-interacting''' with them, provided the citadel is unclaimed. <br />
[[File:UnclaimedCitadelGui.png|thumb|UI presented on freshly placed citadel]]<br />
<br />
A factionless player can create a faction by placing a citadel, interacting with it, and clicking the '''“Create”''' button. They can then '''name the faction''' and choose its '''color'''.<br />
<br />
* '''Faction name''' is permanent and cannot be changed.<br />
* '''Faction color''' can be changed later via the citadel menu.<br />
<br />
Every claimed chunk displays a '''colored border''' corresponding to its faction. These borders cannot be disabled globally but can be toggled on or off individually by pressing '''B''' (default) or using the <code>/f borders</code> command.<br />
<br />
The player who creates the faction is automatically set as the '''leader'''.<br />
=== Inviting players, ranks transferring, ownership, leaving ===<br />
Every faction has a '''leader''', who is the faction’s owner. Beyond the leader, factions can have '''officers''' and '''regular members'''.<br />
<br />
* '''Officers''' can perform additional actions, such as inviting or expelling players and placing claims.<br />
* '''Members''' can be promoted to officers or demoted using <code>/f promote</code> and <code>/f demote</code>.<br />
* The '''leader''' can transfer leadership to another member with <code>/f setleader</code>.<br />
<br />
All faction members have an '''extra name tag field''' that displays their faction affiliation.<br />
----<br />
<br />
=== Chunk veins and passive yields ===<br />
Chunks can contain valuable resource '''veins'''. Players can view veins by '''sneaking''', which displays a UI indicator for the vein in the chunks they are currently in. <br />
<br />
[[File:Vein.png|frame|Chunk vein of Rich Gold-Diamond, with 100% chance of 80 gold ores, 80% of extra 10 gold ores, and 100% of 3 diamonds, with 60% possibility for an extra diamond. ]]<br />
<br />
Veins have '''three quality levels''' — Poor, Fair, and Rich — which affect the total yield. The display shows:<br />
<br />
* The '''item'''.<br />
* The '''number of items''' you will receive (in square brackets).<br />
* Up to '''two percentages''':<br />
*# The first percentage indicates the chance of obtaining the listed items.<br />
*# The second percentage indicates the chance of getting '''one extra item'''.<br />
<br />
<blockquote>Note: An item can have multiple independent drop chances within the same vein.</blockquote>Veins can occur at different rates depending on the '''dimension''', and all vein-specific settings can be adjusted in <code>warforge/veins.cfg</code>.<br />
<br />
'''Yield collection:''' Items from veins are automatically deposited into the chunk’s claim at set intervals, configurable in the main configuration file.<br />
<br />
=== Expanding Claim area and citadel upgrading ===<br />
To expand your faction’s claim area, players with the rank of officer or higher can place claim blocks. Currently, there are two types: basic and reinforced, which differ in strength. Strength determines how many points attackers must gain to win a siege.<br />
<br />
If the citadel level system is enabled, it restricts the number of claims a faction can have, preventing players from placing extra claims once the limit is reached.<br />
<br />
[[File:UpgradeUI.png|thumb|Citadel Upgrade UI]]<br />
<br />
To level up a citadel, an officer or higher must interact with it and click the “Upgrade Citadel” button. This opens a GUI showing the required items for the upgrade. If the player has the items and confirms by pressing “Upgrade”, the items are removed from the player’s inventory and the citadel levels up.<br />
<br />
The number of levels, their claim limits, and the required items can be configured in the file: <code>warforge/upgrade_levels.cfg</code>.<br />
<br />
=== Sieges ===<br />
Sieges allow factions to attack other factions, unclaiming their chunks, preventing them from being reclaimed, or even taking over their territory. A faction can start a siege by placing a siege structure next to the enemy’s land, opening the siege menu, and selecting the chunk to target. The siege will only begin if the attacking faction is not under a losing penalty.<br />
[[File:Siege camp UI.png|thumb|Siege camp UI, with attacker's siege camp in the center, with enemy claim chunk to the north]]<br />
During an active siege, both attackers and defenders see an overhead display showing siege progress. The siege functions as a '''tug-of-war''': killing enemies grants points to the respective side. The siege timer is influenced by the attacker’s '''momentum''' – gained from winning previous sieges and lost when a siege is lost.<br />
<br />
* When the timer reaches 0, attackers earn a point and the timer resets.<br />
* Timer values based on momentum can be configured in the main configuration file.<br />
* Each attacker win grants an extra momentum point, which lasts for a configurable duration. If the momentum expires or the siege is lost, it resets to 0.<br />
* If attackers start a siege with 0 momentum, a siege penalty is applied.<br />
A siege is considered '''abandoned''' if all members of one side leave the siege area. By default, this area includes a '''2-chunk radius around the siege chunk''' (configurable in the main config) and the '''entire claim area of the defenders'''.<br />
<br />
* If defenders were offline when the siege began, they are not considered abandoned until a defender logs in and then leaves the siege area.<br />
* The deserting side has a limited amount of time to return to the siege area before the siege is marked as failed.<br />
* Factions are notified via chat whenever a siege is at risk of being abandoned.<br />
<br />
The point ranges depend on defender's claim type, surrounding claims and claim reinforces that may be present on or around their claimed chunks.<br />
<br />
<br />
===Player commands===<br />
<br />
* <code>/f invite <playerName></code> – Invite a player to join your faction.<br />
* <code>/f accept</code> – Accept a pending faction invitation.<br />
* <code>/f disband</code> – Disband your faction permanently (leader only).<br />
* <code>/f expel <playerName></code> – Remove a member from your faction (officer or leader).<br />
* <code>/f leave</code> – Leave your current faction.<br />
* <code>/f time</code> – Check the amount of time your faction has been active or remaining siege/claim timers.<br />
* <code>/f info <factionName></code> – View information about a specific faction (members, claims, stats).<br />
* <code>/f top</code> – Show a leaderboard of top factions (by wealth, kills, or other metrics).<br />
* <code>/f wealth</code> – Check your faction’s total wealth.<br />
* <code>/f legacy</code> – View your faction’s legacy.<br />
* <code>/f notoriety</code> – Check your faction’s notoriety or reputation in the world, affected by amount of kills they get.<br />
* <code>/f borders</code> – Toggle the display of faction claim borders.</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=Warforge&diff=226Warforge2025-08-31T14:29:29Z<p>Mr.Norwood: Images</p>
<hr />
<div>Warforge is a mod created by jamioflan, creator of FlansMod. Mod was PVP centric claim mod made specifically for now defunct Flan's modded. 1.12.2 SMP. During development of Warfactory 1, the mod was forked and rewritten by Mr. Norwood and EightXOR8, introducing many additional features.<br />
<br />
General overview<br />
The mod allows players to create factions, which grant them the ability to claim chunks as well as get passive resources from claimed chunks. Factions can raid other factions, allowing them to destroy enemy claims and take over bases.<br />
<br />
== Guide ==<br />
<br />
=== Creating a faction ===<br />
<br />
To create a faction, a player must first obtain a '''citadel'''. Citadels can be placed on any '''unclaimed chunk''' and can be picked up by '''sneak-interacting''' with them, provided the citadel is unclaimed. <br />
[[File:UnclaimedCitadelGui.png|thumb|UI presented on freshly placed citadel]]<br />
<br />
A factionless player can create a faction by placing a citadel, interacting with it, and clicking the '''“Create”''' button. They can then '''name the faction''' and choose its '''color'''.<br />
<br />
* '''Faction name''' is permanent and cannot be changed.<br />
* '''Faction color''' can be changed later via the citadel menu.<br />
<br />
Every claimed chunk displays a '''colored border''' corresponding to its faction. These borders cannot be disabled globally but can be toggled on or off individually by pressing '''B''' (default) or using the <code>/f borders</code> command.<br />
<br />
The player who creates the faction is automatically set as the '''leader'''.<br />
=== Inviting players, ranks transferring, ownership, leaving ===<br />
Every faction has a '''leader''', who is the faction’s owner. Beyond the leader, factions can have '''officers''' and '''regular members'''.<br />
<br />
* '''Officers''' can perform additional actions, such as inviting or expelling players and placing claims.<br />
* '''Members''' can be promoted to officers or demoted using <code>/f promote</code> and <code>/f demote</code>.<br />
* The '''leader''' can transfer leadership to another member with <code>/f setleader</code>.<br />
<br />
All faction members have an '''extra name tag field''' that displays their faction affiliation.<br />
----<br />
<br />
=== Chunk veins and passive yields ===<br />
Chunks can contain valuable resource '''veins'''. Players can view veins by '''sneaking''', which displays a UI indicator for the vein in the chunks they are currently in. <br />
<br />
[[File:Vein.png|thumb]]<br />
<br />
Veins have '''three quality levels''' — Poor, Fair, and Rich — which affect the total yield. The display shows:<br />
<br />
* The '''item'''.<br />
* The '''number of items''' you will receive (in square brackets).<br />
* Up to '''two percentages''':<br />
*# The first percentage indicates the chance of obtaining the listed items.<br />
*# The second percentage indicates the chance of getting '''one extra item'''.<br />
<br />
<blockquote>Note: An item can have multiple independent drop chances within the same vein.</blockquote>Veins can occur at different rates depending on the '''dimension''', and all vein-specific settings can be adjusted in <code>warforge/veins.cfg</code>.<br />
<br />
'''Yield collection:''' Items from veins are automatically deposited into the chunk’s claim at set intervals, configurable in the main configuration file.<br />
<br />
=== Expanding Claim area and citadel upgrading ===<br />
To expand your faction’s claim area, players with the rank of officer or higher can place claim blocks. Currently, there are two types: basic and reinforced, which differ in strength. Strength determines how many points attackers must gain to win a siege.<br />
<br />
If the citadel level system is enabled, it restricts the number of claims a faction can have, preventing players from placing extra claims once the limit is reached.<br />
<br />
[[File:UpgradeUI.png|thumb|Citadel Upgrade UI]]<br />
<br />
To level up a citadel, an officer or higher must interact with it and click the “Upgrade Citadel” button. This opens a GUI showing the required items for the upgrade. If the player has the items and confirms by pressing “Upgrade”, the items are removed from the player’s inventory and the citadel levels up.<br />
<br />
The number of levels, their claim limits, and the required items can be configured in the file: <code>warforge/upgrade_levels.cfg</code>.<br />
<br />
=== Sieges ===<br />
Sieges allow factions to attack other factions, unclaiming their chunks, preventing them from being reclaimed, or even taking over their territory. A faction can start a siege by placing a siege structure next to the enemy’s land, opening the siege menu, and selecting the chunk to target. The siege will only begin if the attacking faction is not under a losing penalty.<br />
[[File:Siege camp UI.png|thumb|Siege camp UI, with attacker's siege camp in the center, with enemy claim chunk to the north]]<br />
During an active siege, both attackers and defenders see an overhead display showing siege progress. The siege functions as a '''tug-of-war''': killing enemies grants points to the respective side. The siege timer is influenced by the attacker’s '''momentum''' – gained from winning previous sieges and lost when a siege is lost.<br />
<br />
* When the timer reaches 0, attackers earn a point and the timer resets.<br />
* Timer values based on momentum can be configured in the main configuration file.<br />
* Each attacker win grants an extra momentum point, which lasts for a configurable duration. If the momentum expires or the siege is lost, it resets to 0.<br />
* If attackers start a siege with 0 momentum, a siege penalty is applied.<br />
A siege is considered '''abandoned''' if all members of one side leave the siege area. By default, this area includes a '''2-chunk radius around the siege chunk''' (configurable in the main config) and the '''entire claim area of the defenders'''.<br />
<br />
* If defenders were offline when the siege began, they are not considered abandoned until a defender logs in and then leaves the siege area.<br />
* The deserting side has a limited amount of time to return to the siege area before the siege is marked as failed.<br />
* Factions are notified via chat whenever a siege is at risk of being abandoned.<br />
<br />
The point ranges depend on defender's claim type, surrounding claims and claim reinforces that may be present on or around their claimed chunks.<br />
<br />
<br />
===Player commands===<br />
<br />
* <code>/f invite <playerName></code> – Invite a player to join your faction.<br />
* <code>/f accept</code> – Accept a pending faction invitation.<br />
* <code>/f disband</code> – Disband your faction permanently (leader only).<br />
* <code>/f expel <playerName></code> – Remove a member from your faction (officer or leader).<br />
* <code>/f leave</code> – Leave your current faction.<br />
* <code>/f time</code> – Check the amount of time your faction has been active or remaining siege/claim timers.<br />
* <code>/f info <factionName></code> – View information about a specific faction (members, claims, stats).<br />
* <code>/f top</code> – Show a leaderboard of top factions (by wealth, kills, or other metrics).<br />
* <code>/f wealth</code> – Check your faction’s total wealth.<br />
* <code>/f legacy</code> – View your faction’s legacy.<br />
* <code>/f notoriety</code> – Check your faction’s notoriety or reputation in the world, affected by amount of kills they get.<br />
* <code>/f borders</code> – Toggle the display of faction claim borders.</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=File:Vein.png&diff=225File:Vein.png2025-08-31T14:29:06Z<p>Mr.Norwood: </p>
<hr />
<div>Chunk vein of Rich Gold-Diamond, with 100% chance of 80 gold ores, 80% of extra 10 gold ores, and 100% of 3 diamonds, with 60% possibility for an extra diamond.</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=File:UpgradeUI.png&diff=224File:UpgradeUI.png2025-08-31T14:21:30Z<p>Mr.Norwood: </p>
<hr />
<div>Upgrade UI</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=File:Siege_camp_UI.png&diff=223File:Siege camp UI.png2025-08-31T14:16:35Z<p>Mr.Norwood: </p>
<hr />
<div>Siege camp UI, showing the attacker's siege camp in the center, surrounding chunks around it, with enemy siege camps to the north.</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=Warforge&diff=222Warforge2025-08-31T13:48:17Z<p>Mr.Norwood: Writing the rest of it + pictures</p>
<hr />
<div>Warforge is a mod created by jamioflan, creator of FlansMod. Mod was PVP centric claim mod made specifically for now defunct Flan's modded. 1.12.2 SMP. During development of Warfactory 1, the mod was forked and rewritten by Mr. Norwood and EightXOR8, introducing many additional features.<br />
<br />
General overview<br />
The mod allows players to create factions, which grant them the ability to claim chunks as well as get passive resources from claimed chunks. Factions can raid other factions, allowing them to destroy enemy claims and take over bases.<br />
<br />
== Guide ==<br />
<br />
=== Creating a faction ===<br />
<br />
To create a faction, a player must first obtain a citadel. Citadels can be placed on any unclaimed chunk, and picked up by sneak-interacting with them, if they don't belong to any faction. To create a faction, a factionless player must place a citadel, interact with it and click “Create” button. From there, the player is allowed to name the faction and choose a color. It's important to note that the faction's '''name is immutable''', while color can always be changed from the citadel's menu. Every claimed chunk has a border drawn around it with the color of the faction and cannot be disabled. Players can toggle borders by pressing B by default or using the <code>/f borders</code> command. Creators of the faction will always be set as the leaders. <br />
[[File:UnclaimedCitadelGui.png|thumb|UI presented on freshly placed citadel]]<br />
<br />
=== Inviting players, ranks transferring, ownership, leaving ===<br />
Every faction has to have a leader, who is the owner of the faction. From there, factions have officers and regular members. Officers are able to do additional things within the faction's context, such as: inviting, expelling or placing claims. Members can be promoted and demoted with <code>/f promote</code> and <code>/f demote</code>, respectively. Leader can change the leader of the faction using <code>/f setleader</code> command. Members of the factions will have an additional name tag field that displays their faction affiliation.<br />
<br />
=== Chunk veins and passive yields ===<br />
Chunks can hold valuable resource yields. Players can view veins by sneaking, which will give them a UI indicator of the vein in the chunks they are currently in. Veins can have 3 different qualities: Poor, Fair and Rich, the quality affects the total yield. The display shows you the item, amount of items that you will get, within square brackets and up 2 percentages. First percentage shows the chance of you getting the items. A second percentage value is responsible for an extra item, which displays a chance for getting a single extra item. It's important to note that the same item can have multiple chances to drop, as it's possible for an item to have multiple drop chances, with each chance having their percentage. Certain veins can occur at different rates in different dimensions. All vein-specific settings can be adjusted within the <code>warforge/veins.cfg</code> config file. <br />
<br />
Yield items will be deposited into the chunk's claim on set intervals, configured within the main configuration file.<br />
<br />
<br />
<br />
=== Expanding Claim area and citadel upgrading ===<br />
To expand your claim area, players with rank officer or higher can place claim blocks. Currently, there are 2 claim blocks: basic and reinforced. They differ in strength, which decides the amount of points that attackers need to gain in order to win a siege. Depending on the configuration, you may have citadel level system enabled. Level system restricts the amount of claims that a faction can have. Preventing players placing extra claims if the limit is reached. To level up your citadel, an officer or higher needs to go into the citadel and press the “Upgrade Citadel” button. This will open a GUI that will ask the player for specific items in order to advance. If the player has the requested items and presses the “Upgrade” button, the items will be deducted from the player's inventory and the citadel will level up. Amount of levels, their claim limits and required items can be configured in <code>warforge/upgrade_levels.cfg</code> config file.<br />
<br />
=== Sieges ===<br />
Sieges allow factions to attack other factions, unclaiming their chunks and preventing them from being claimed, or even taking over the claim. Sieges can be started by a faction by placing a siege next to the enemy faction, opening the menu, and selecting the chunk that you want to siege. If the faction is not having a losing penalty active, the siege will begin.<br />
<br />
During active siege, attackers, and defender will have an overhead display about the progress of the siege. The siege is a tug of war between attackers and defenders, where killing the enemy gives points to their respective side. The timer is set based on attacker's momentum, which is gained via winning sieges, and lost on losing a siege. Whenever timer ticks down to 0, a point is awarded to attackers and the timer restarts. Timer's values based on momentum is configurable in the main configuration file. On each attacker win, they get extra momentum point that is valid for a certain amount of time, based on the configuration file, if it expires or a siege is lost, the value is set back to 0. If attackers while having 0 momentum, they will be given a siege penalty.<br />
<br />
The point ranges depend on defender's claim type, surrounding claims and claim reinforces that may be present on or around their claimed chunks.</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=File:UnclaimedCitadelGui.png&diff=221File:UnclaimedCitadelGui.png2025-08-31T13:46:39Z<p>Mr.Norwood: </p>
<hr />
<div>Unclaimed Citadel Gui</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=Warforge&diff=220Warforge2025-08-31T12:38:02Z<p>Mr.Norwood: </p>
<hr />
<div>Warforge is a mod created by jamioflan, creator of FlansMod. Mod was PVP centric claim mod made specifically for now defunct Flan's modded. 1.12.2 SMP. During development of Warfactory 1, the mod was forked and rewritten by Mr. Norwood and EightXOR8, introducing many additional features.<br />
<br />
General overview<br />
The mod allows players to create factions, which grant them the ability to claim chunks as well as get passive resources from claimed chunks. Factions can raid other factions, allowing them to destroy enemy claims and take over bases.<br />
<br />
== Guide ==<br />
<br />
=== Creating a faction ===<br />
<br />
To create a faction, a player must first obtain a citadel. Citadels can be placed on any unclaimed chunk, and picked up by sneak-interacting with them, if they don't belong to any faction. To create a faction, a factionless player must place a citadel, interact with it and click “Create” button. From there, the player is allowed to name the faction and choose a color. It's important to note that the faction's '''name is immutable''', while color can always be changed from the citadel's menu. Every claimed chunk has a border drawn around it with the color of the faction and cannot be disabled. Players can toggle borders by pressing B by default or using the <code>/f borders</code> command. Creators of the faction will always be set as the leaders. <br />
<br />
=== Inviting players, ranks transferring, ownership, leaving ===<br />
Every faction has to have a leader, who is the owner of the faction. From there, factions have officers and regular members. Officers are able to do additional things within the faction's context, such as: inviting, expelling or placing claims. Members can be promoted and demoted with <code>/f promote</code> and <code>/f demote</code>, respectively. Leader can change the leader of the faction using <code>/f setleader</code> command. Members of the factions will have an additional name tag field that displays their faction affiliation.<br />
<br />
=== Chunk veins and passive yields ===<br />
Chunks can hold valuable resource yields. Players can view veins by sneaking, which will give them a UI indicator of the vein in the chunks they are currently in. Veins can have 3 different qualities: Poor, Fair and Rich, the quality affects the total yield. The display shows you the item, amount of items that you will get, within square brackets and up 2 percentages. First percentage shows the chance of you getting the items. A second percentage value is responsible for an extra item, which displays a chance for getting a single extra item. It's important to note that the same item can have multiple chances to drop, as it's possible for an item to have multiple drop chances, with each chance having their percentage. Certain veins can occur at different rates in different dimensions. All vein-specific settings can be adjusted within the <code>warforge/veins.cfg</code> config file. <br />
<br />
Yield items will be deposited into the chunk's claim on set intervals, configured within the main configuration file.<br />
<br />
<br />
<br />
=== Expanding Claim area and citadel upgrading ===<br />
To expand your claim area, players with rank officer or higher can place claim blocks. Currently, there are 2 claim blocks: basic and reinforced. They differ in strength, which decides the amount of points that attackers need to gain in order to win a siege. Depending on the configuration, you may have citadel level system enabled. Level system restricts the amount of claims that a faction can have. Preventing players placing extra claims if the limit is reached. To level up your citadel, an officer or higher needs to go into the citadel and press the “Upgrade Citadel” button. This will open a GUI that will ask the player for specific items in order to advance. If the player has the requested items and presses the “Upgrade” button, the items will be deducted from the player's inventory and the citadel will level up. Amount of levels, their claim limits and required items can be configured in <code>warforge/upgrade_levels.cfg</code> config file.<br />
<br />
=== Sieges ===<br />
Sieges allow factions to attack other factions, unclaiming their chunks and preventing them from being claimed, or even taking over the claim. Sieges can be started by a faction by placing a siege next to the enemy faction, opening the menu, and selecting the chunk that you want to siege. If the faction is not having a losing penalty active, the siege will begin.<br />
<br />
During active siege, attackers, and defender will have an overhead display about the progress of the siege. The siege is a tug of war between attackers and defenders, where killing the enemy gives points to their respective side. The timer ticks down</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=Warforge&diff=219Warforge2025-08-31T11:52:15Z<p>Mr.Norwood: Created page with "Warforge is a mod created by jamioflan, creator of FlansMod. Mod was pvp centric claim mod made specifically for now defunct Flan's modded. 1.12.2 SMP. During development of Warfactory 1, the mod was forked and rewritten by Mr.Norwood and EightXOR8, introducing many additional features. General overview The mod allows players to create factions, which grant them the ability to claim chunks as well as get passive resources from claimed chunks. Factions can raid other fac..."</p>
<hr />
<div>Warforge is a mod created by jamioflan, creator of FlansMod. Mod was pvp centric claim mod made specifically for now defunct Flan's modded. 1.12.2 SMP. During development of Warfactory 1, the mod was forked and rewritten by Mr.Norwood and EightXOR8, introducing many additional features.<br />
<br />
General overview<br />
The mod allows players to create factions, which grant them the ability to claim chunks as well as get passive resources from claimed chunks. Factions can raid other factions, allowing them to destroy enemy claims and take over bases.<br />
<br />
== Guide ==<br />
<br />
=== Creating a faction ===<br />
<br />
To create a faction, a player must first obtain a citadel. Citadels can be placed on any unclaimed chunk, and picked up by sneak-interacting with them, if they don't belong to any faction. To create a faction, a factionless player must place a citadel, interact with it and click “Create” button. From there, the player is allowed to name the faction and choose a color. It's important to note that the faction's '''name is immutable''', while color can always be changed from the citadel's menu. Every claimed chunk has a border drawn around it with the color of the faction and cannot be disabled. Players can toggle borders by pressing B by default or using the <code>/f borders</code> command. Creators of the faction will always be set as the leaders. <br />
<br />
=== Inviting players, ranks transferring, ownership, leaving ===<br />
Every faction has to have a leader, who is the owner of the faction. From there, factions have officers and regular members. Officers are able to do additional things within the faction's context, such as: inviting, expelling or placing claims. Members can be promoted and demoted with <code>/f promote</code> and <code>/f demote</code>, respectively. Leader can change the leader of the faction using <code>/f setleader</code> command. Members of the factions will have an additional name tag field that displays their faction affiliation.<br />
<br />
=== Chunk veins and passive yields ===<br />
Chunks can hold valuable resource yields. Players can view veins by sneaking, which will give them a UI indicator of the vein in the chunks they are currently in. Veins can have 3 different qualities: Poor, Fair and Rich, the quality affects the total yield. The display shows you the item, amount of items that you will get, within square brackets and up 2 percentages. First percentage shows the chance of you getting the items. A second percentage value is responsible for an extra item, which displays a chance for getting a single extra item. It's important to note that the same item can have multiple chances to drop, as it's possible for an item to have multiple drop chances, with each chance having their percentage. Certain veins can occur at different rates in different dimensions. All vein-specific settings can be adjusted within the <code>warforge/veins.cfg</code> config file.<br />
<br />
<br />
<br />
=== Expanding Claim area and citadel upgrading ===<br />
To expand your claim area, players with rank officer or higher can place claim blocks. Currently, there are 2 claim blocks: basic and reinforced. They differ in strength, which decides the amount of points that attackers need to gain in order to win a siege. Depending on the configuration, you may have citadel level system enabled. Level system restricts the amount of claims that a faction can have. Preventing players placing extra claims if the limit is reached. To level up your citadel, an officer or higher needs to go into the citadel and press the “Upgrade Citadel” button. This will open a GUI that will ask the player for specific items in order to advance. If the player has the requested items and presses the “Upgrade” button, the items will be deducted from the player's inventory and the citadel will level up. Amount of levels, their claim limits and required items can be configured in <code>warforge/upgrade_levels.cfg</code> config file.<br />
<br />
=== Sieges ===</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=Warfactory_2_design&diff=218Warfactory 2 design2025-07-30T20:39:34Z<p>Mr.Norwood: Medical, infantry</p>
<hr />
<div>Warfactory is a 1.12 Modpack made specifically for large faction server SMPs,<br />
based around HBM:NTM and Gregtech, using Modular Warfare Shining and possibly<br />
Mcheli for combat. The Modpack features an in-house fork of the Warforge claim mod,<br />
adjusted for a more dynamic, fair and exciting faction experience.<br />
<br />
== General Principles ==<br />
The pack must be accommodating to both veterans and new players, offering experience that is well documented and easily inferred from context clues. The progression will be tailored towards a much faster and dynamic style, compared to vanilla GT.<br />
<br />
Resources will be given very generously and infrastructure will be easy to set up, and in-game challenges will be tailored towards quick-thinking and high performance instead of endurance (grind). <br />
Combat balance is very important to us. Every item and system will be designed and improved with more tactical combat experience in mind. We take a hard stance against creative flight, buff stacking, teleportation, insane armor values and other game breaking features that have commonly been seen in other commonly used packs. Guile gives far greater rewards than material advantages.<br />
<br />
=== “Shoulders of Giants” Approach ===<br />
Having certain “milestone” machines maintain their relevance across several tiers, undergoing only incremental upgrades. This will incentivize staying in one place. Moreover, as long as a team has good risk management, they’ll have backups of these machines to get them up and running easily, making progression faster and more rewarding.<br />
Say a ULV reworked blast furnace has no coils. As we progress, we give it coil upgrades and incrementally approve what it can cook.<br />
<br />
To encourage different play styles, we will have 3 different win conditions:<br />
* Wonder winner – The team which has the nicest buildings and wonders.<br />
* Domination victory – The team that topples the most bases.<br />
* Progression victory – The most technologically advanced team.<br />
<br />
== Combat ==<br />
This is the section for the combat for WF2.<br />
<br />
==== Infantry combat ====<br />
The most exciting part of the game is perhaps the infantry combat. From our experience, players want a more tactical and grounded combat that still indeed feels like infantry combat. In the past, the traditional packs, which were not made with combat in mind, would give players access to overpowered tools. The combat would be more similar to fights from DragonBall , where the goal is to use the most overpowered and cheaty method of inflicitng damage while causing game to have trouble registering hits on you. In our modpack, players will need to be aware of their positioning, make strategic pushes, build forward operating bases, manage their inventory to avoid slowdowns, like in other conventional shooters<br />
<br />
==== Guns ====<br />
Just like warfactory 1.0, we will have guns in the pack. Our current mod of choice is modular warfare shining, allowing us to have a framework for constantly expanding arsenal. We will also make use of new and improved HBM guns and turrets. We will integrate the guns with <br />
NTM armor system, that will make for interesting combat, devoid of bullet sponges and cheap one-shot tactics.<br />
<br />
==== Weight system ====<br />
Using likes of Iguana tweaks, we will introduce a simple weight system that prevents players from becoming a walking armory. Those limits will only apply to combat-related things, as to not slow down progression inside of the modpack. Furthermore, we will add inventory limits that will prevent players from stashing too many things such as medicine, to prevent drawn out combat and encourage team play. Vehicles will not be possible for players to pick up either, making them a lot more precious and encourage proper handling of them, instead of it being a pocket weapon of mass destruction. Vehicles will be deployed using special assembling multiblocks, that one will need to deploy on the field.<br />
<br />
==== Medical system ====<br />
To spice up gameplay, a simple medical system will be introduced. There are 2 types of damage: "Light" damage and "Hard" damage. Light damage will damage player normally, allowing players to use simple healing methods such as bandages, pain killers. Hard damage decreases player's health pool making them unable to recover without use of more sophisticated means. For such cases, more potent drugs will be introduced, such as opiates. Those are very potent, but dangerous drugs, which can heal, but have many drawbacks and should be handled with caution. Reckless use may cause instant death, or strong debuffs. Last class are stimulants, which are the source of buffs. They also can come with drawbacks. The system may grow with time, however this groundwork goes a long way and makes healing a bit more interesting compared to vanilla<br />
<br />
=== Base raiding ===<br />
Raiding should be as difficult as defending yourself. As veterans of the modded landscape, we have noticed the general meta to be:<br />
<br />
You make cobble box underground and push progression mindlessly<br />
Make cheapest throwable explosive to destroy claims (if they exist)<br />
Use psyops or bruteforce to find other cobble boxes<br />
Raid the cobble box to get some loot<br />
Hope you won't get found, or you need to move the entire base in about an hour<br />
<br />
We completely disagree with this meta, it makes attacking too powerful and impossible to defend against due to the nature of minecraft. Base planning makes no sense when, after your base is found, the entire team will be occupied with defending itself against the lowest tier explosives.<br />
The only real way to defend yourself is to never get found, which is not an engaging and fun game loop. Attacking teams also spend most of their time traveling around the map, trying to find the base via bruteforce, which is not a fun experience either. Which encourages cheating, in the form of BlockESP to make the experience bearable.<br />
Our mod: Warforge factions will make players rethink the way they play faction servers. Bases will require time demanding strategic sieges that will take strategic effort from the attacker. With extended defensive tooling from mods such as NTM, base design, defenses, and automation will hopefully become an important aspect of the game.<br />
The land you will settle down on will also be very significant, giving teams advantages for settling down in resource rich areas. Some exclusive rare materials that will make specific subbranches of military and industry more viable. Those will not be required for progression, but offer tactical resource advantage.<br />
<br />
=== Early Combat ===<br />
The first combat will be done using the Large Metal Press multi, which works similar to the burner press from HBM. This will be used to obtain the first guns. The Gear Foundry will be the way you make armor, weapons and advanced tools. It will be upgradable similar to the Chemplant from GTNH.<br />
<br />
==== Radar ====<br />
We will feature tools like the radar to make finding bases viable in the early midgame of the tech progression tree. Allowing for base finding to be much more streamlined, and making hiding strategies much less viable. Radar will require computation, power, and be placed relatively high up with access to the skyline. Quite cumbersome and fragile, yet game changing when it comes to recon. It will find an average point of enemy bases and index them according to how big and populous the base is. Meaning, the teams that are more ahead will have more eyes on them.<br />
<br />
==== Factions progression ====<br />
Factions will be at the heart of your factory, they provide as your source of chunk claiming and chunk loading. However, to expand the area you can control the strength of your defenses. Your factions will have limited possible chunks they can claim, to expand their limit, teams must provide special resources to the faction, in order to increase their claim power.<br />
<br />
==== Suppliers ====<br />
Special multiblocks called suppliers will allow bases to bolster their defenses. Multiblocks will require a steady supply of quality food to increase the defense factor of a certain area, about 3x3 chunk area (will only work on claimed chunks). For a buff to be applied, it must be done while not under siege. The machine will refuse to buff the base if it was turned on after the siege started. Machines will increase their strength depending on the amount of food supplied. Type of food item will be determined by faction tier, lower tier factions will require lower tier foods, while high tier factions will require high quality foodstuffs. The amount of claimed chunks will also increase the amount of food required. <br />
<br />
==== MC-heli ====<br />
We want to make use of a custom fork of MCHELI, developed to integrate into our pack. Vehicles will help players to move around the map and conduct sieges. It may not come with WF2, as it will be a challenge to refactor.<br />
<br />
== Progression ==<br />
The 2 Main mods carrying progression will be Gregtech and HBM, with focus on Gregtech and HBM filling in with what we theme is the "highlight" content.<br />
<br />
=== Asymmetric progression ===<br />
To make progression and battles more dynamic, we want to introduce specific branches of progression depending on player's access to resources. For example, player has access to renewable large source of uranium. This allows player to start nuclear research early, giving access things such as early nuclear power, low yield nuclear weapons. Another example would be access to a specific resource that would allow player to produce energy weapons, which while not explicitly better than standard weapons, would be more effective against standard bullet-proof armor. Such design decisions would be sprinkled around the modpack. To enforce uniqueness of those resources, the map would have a limited amount of such resources, regulated by the administrator. This would encourage turf wars, to make players fight over strategic resources across the map. <br />
<br />
=== Faster progression ===<br />
Our goal is to make progression mesh well with the fast landscape that modded faction wars is. Let's be honest, GregTech's call to fame came from it's "immersive" (slow) gameplay. While we do want to retain the complexity and logistical challenge that GregTech provides, we want to remove the tedious, repetitive parts that are present in the mod. This ranges from large sweeping changes, to small optimizations. Here is a list of things that we want to introduce in order to archive this:<br />
<br />
* Early, but limited access to AE2<br />
* Recursive pipe shuttering<br />
* Multiblock blueprints<br />
* Complete rework of early game in order to decrease micro-crafting<br />
* Early centralized power and more streamlined powergrid handling<br />
<br />
=== Powergrid handling ===<br />
From experience in management of large bases, power management in GregTech is poorly designed. In early game, it is a chore. Low voltages make your expansion limited, it is impossible to have a properly designed, centralized power system that players can expand. Lategame however, it becomes overtly reliant on storing massive amounts of EU inside different kinds of EU storages. By the time you are in lategame, many interesting solutions are presented to the player, which in my opinion is a lost opportunity when it comes to game design. This does not even take into account AE2's EU/RF p2p's which trivialize power grid planning, to a point that all other tools become almost obsolete. We plan to mend this issue, using few simple machines and design choices.<br />
<br />
===== Large transformers =====<br />
To make power grid managment easier, players will get access to large transformers, which are simple multiblock structures that allow player to place energy hatches and dynamos, that will transform power. They would be tiered, with first tier allowing player to transform power from LV to HV and another one that would be able to tranform power for all of the tiers (up to UV). Goal is to make power grid managment much more streamlined, less reliant on hacky transformer chains or separate power grids.<br />
<br />
===== AC power =====<br />
To help players transfer power between different points. An "AC" power converter machine would be introduced. "AC" power would be a voltage type that would be unusable with machines, however would not suffer the same per-block loss like the "DC" power. Some kind of loss would still be at play, either passive loss on conversion between voltages or a loss proportional to amount of current drawn through the system. The AC power is there to ease dealing with power transfer in the early game to midgame, having less of an impact as games progresses into lategame. <br />
<br />
===== Removal of the power "cheese" =====<br />
To make power menagment matter in lategame stages. We will curb the amount of EU player can store. We will also restrict ways player can transfer EU, to avoid things such as AE2 completely breaking the game meta.<br />
<br />
=== Steam Age Rework ===<br />
Steam age is the biggest thorn in GT's design. It suffers from issues that we specifically want to avoid in our modpack. We opt into redesigning the steam age to focus on player to quickly be able to reach LV, while allowing player to make use of extra machines, that will stay relevant well into the midgame.<br />
[[File:Steam age progression chart.png|thumb|Chart for the steam age progression, showcasing the flow and key resources required to progress. (May change at any time)]]<br />
<br />
=== Steam power overhaul ===<br />
Steam is a rather underutilized power source in later stages of GregTech, due to its unremarkable power density. It is a shame that this power source gets completely outshined by the the time you get to LV. We want to introduce higher density steam types, which paired with high pressure pipes allow for scalable throughput beyond earlygame. With NTM there are also even more interesting way to boil water, using many different reactors.<br />
<br />
Other current ideas for new ways to generate steam are:<br />
* The Boiler Tower, a multi which gives higher yields exponentially the taller it is.<br />
* The Heat Exchanger, a multi which turns lava and water into steam.<br />
* A reworked Large Boiler system to overcome its flaws and to make them relevant again.<br />
<br />
In a parallel to the real world’s development, petrochemistry is unlocked very early on. High-pressure steam is used to extract oil and refine it. Of course, these early methods are not nearly as successful as more advanced systems, and we cannot refine advanced petrochemicals like HOG this way. Bunker fuel, kerosene, etc is unlocked around this time.<br />
<br />
With this, we can construct power systems that will sustain us far into the electrical tiers.<br />
<br />
==== Early Combustion ====<br />
In alignment with the “shoulders of giants” philosophy, the player will be given crude combustion engines in late ULV. These engines, through incremental upgrade, can sustain them well into the LV-EV tiers. To begin, you will only be able to produce crude kerosene and bunker fuel, and suffer poor efficiency and very crude engines that can only really sustain you for a while.<br />
<br />
Early petro fuels won’t produce power, but will power boilers to produce oodles of steam. Direct combustion engines (and steam turbines) are unlocked in LV, but can be made easily by retrofitting your early boiler systems. <br />
=== Lv-Ev Tenets ===<br />
<br />
=== Low Voltage ===<br />
Low voltage will unlock AE2 as we recognize that this mod is inseparable with GT due to its Gregtech’s complexity ramping up as soon as player gets to later stages. Early AE2 will empower the team to produce larger and more complex factories, as they won’t feel they need to wait until they reach AE2 (common issue with GTNH). This may make people think this will kill complexity, which is why we opt to enable keep channels enabled. <br />
<br />
Players will unlock plethora of basic self defence guns and infrastructure, such as barbed wire, concrete.<br />
<br />
===== AE2's common pitfall: oversimplification of bases =====<br />
AE2 is a powerful tool, which can do many many things. This is what makes it great. However, AE2 can actually oversimplify a lot of systems, via its powerful ondemand crafting system. We want to give players access to the powerful tools, though stray away from introducing AE2s full overpowered suite of tools that make game become AE2 trivia simulator.<br />
<br />
=== Medium Voltage ===<br />
=== High Voltage ===<br />
<br />
=== Ev-Luv Tenets ===<br />
<br />
=== Extreme Voltage ===<br />
<br />
=== Insane Voltage ===<br />
<br />
=== Ludicrous Voltage ===<br />
<br />
=== ZPM Voltage ===<br />
I doubt we need to go this far, only one team will most likely even make it to ZPM or beyond it<br />
<br />
=== Multi Rework ===<br />
<br />
For WF2 we want to move away from GCYM, as it has some intrinsic problems with it, as well as it doesn’t fit into what we want for a pvp pack.<br />
<br />
<br />
We will implement new multis, either through an external mod or through WFCore. And the consensus is that the first round of multis will be available in early HV to incentivise the creation of large scale automation early on.<br />
<br />
<br />
The Parallels will most likely be akin to how GT++ calculates parallels.<br />
<br />
=== NTM Space ===<br />
Since we are also porting the NTM space content, we are looking into integrating it into Warfactory, and as it's such a major part of the progression it will get it's own section.<br />
<br />
== Takeaways and lessons from WF1 ==<br />
* All movement options within Warfactory 2, have to be evaluated and checked for if they are too overpowered, not to have a repeat of the hooks situation from Warfactory 1.<br />
* Ensure armor and weapons are tested THOROUGHLY (to prevent a repeat of the redstone arsenal incident)<br />
* Make sure to do small scale tests with testers who are intentionally made to cause as much lag as possible to then make a spark profile to find sources of lag to prevent another visual ores situation.<br />
* We will also be cutting down on the amount of mods to prevent interactions in-between the mods.<br />
<br />
<br />
== The Dev Test ==<br />
A Dev Test will be orchestrated as a way of engaging the community before WF2, while still using it as a platform to see if the more experimental features work in a event setting.<br />
<br />
The devtest will be done as follows, first the top 2 people of each team<ref>Would likely be the Leader and Co-Leader of each respective team</ref> would be invited to a discord. This is to discuss the rules and to make any last minute alterations to the pack before the devtest takes place.<br />
<br />
After everything is sorted out, all the members of each respective team will be added, and if there are still server slots there will be a google form setup for invitations.<br />
<br />
The prevailing idea is that once the pack reaches LuV, the devtest will occur. As it is not a traditional event, the server will have very specific win conditions. Those being finishing LuV and obtaining the Crystal Mainframe. This will be akin to the "Science Victory" in Civ6.</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=Warfactory_2_design&diff=217Warfactory 2 design2025-07-30T20:01:18Z<p>Mr.Norwood: The great rewrite of progression part 2</p>
<hr />
<div>Warfactory is a 1.12 Modpack made specifically for large faction server SMPs,<br />
based around HBM:NTM and Gregtech, using Modular Warfare Shining and possibly<br />
Mcheli for combat. The Modpack features an in-house fork of the Warforge claim mod,<br />
adjusted for a more dynamic, fair and exciting faction experience.<br />
<br />
== General Principles ==<br />
The pack must be accommodating to both veterans and new players, offering experience that is well documented and easily inferred from context clues. The progression will be tailored towards a much faster and dynamic style, compared to vanilla GT.<br />
<br />
Resources will be given very generously and infrastructure will be easy to set up, and in-game challenges will be tailored towards quick-thinking and high performance instead of endurance (grind). <br />
Combat balance is very important to us. Every item and system will be designed and improved with more tactical combat experience in mind. We take a hard stance against creative flight, buff stacking, teleportation, insane armor values and other game breaking features that have commonly been seen in other commonly used packs. Guile gives far greater rewards than material advantages.<br />
Another idea in the works is the idea of “Time Gated Progression”. This is a measure to nerf large teams and allow smaller teams to survive. This will be executed with the use of RecipeStages, where each passing day unlocks a new voltage tier that people can progress into, Steam Day 1, Lv Day 2, Mv Day 3 Etc.<br />
<br />
=== “Shoulders of Giants” Approach ===<br />
Having certain “milestone” machines maintain their relevance across several tiers, undergoing only incremental upgrades. This will incentivize staying in one place. Moreover, as long as a team has good risk management, they’ll have backups of these machines to get them up and running easily, making progression faster and more rewarding.<br />
Say a ULV reworked blast furnace has no coils. As we progress, we give it coil upgrades and incrementally approve what it can cook.<br />
<br />
To encourage different play styles, we will have 3 different win conditions:<br />
* Wonder winner – The team which has the nicest buildings and wonders.<br />
* Domination victory – The team that topples the most bases.<br />
* Progression victory – The most technologically advanced team.<br />
<br />
== Combat ==<br />
This is the section for the combat for WF2.<br />
<br />
=== Base raiding ===<br />
Raiding should be as difficult as defending yourself. As veterans of the modded landscape, we have noticed the general meta to be:<br />
<br />
You make cobble box underground and push progression mindlessly<br />
Make cheapest throwable explosive to destroy claims (if they exist)<br />
Use psyops or bruteforce to find other cobble boxes<br />
Raid the cobble box to get some loot<br />
Hope you won't get found, or you need to move the entire base in about an hour<br />
<br />
We completely disagree with this meta, it makes attacking too powerful and impossible to defend against due to the nature of minecraft. Base planning makes no sense when, after your base is found, the entire team will be occupied with defending itself against the lowest tier explosives.<br />
The only real way to defend yourself is to never get found, which is not an engaging and fun game loop. Attacking teams also spend most of their time traveling around the map, trying to find the base via bruteforce, which is not a fun experience either. Which encourages cheating, in the form of BlockESP to make the experience bearable.<br />
Our mod: Warforge factions will make players rethink the way they play faction servers. Bases will require time demanding strategic sieges that will take strategic effort from the attacker. With extended defensive tooling from mods such as NTM, base design, defenses, and automation will hopefully become an important aspect of the game.<br />
The land you will settle down on will also be very significant, giving teams advantages for settling down in resource rich areas. Some exclusive rare materials that will make specific subbranches of military and industry more viable. Those will not be required for progression, but offer tactical resource advantage.<br />
<br />
=== Early Combat ===<br />
The first combat will be done using the Large Metal Press multi, which works similar to the burner press from HBM. This will be used to obtain the first guns. The Gear Foundry will be the way you make armor, weapons and advanced tools. It will be upgradable similar to the Chemplant from GTNH.<br />
<br />
==== Radar ====<br />
We will feature tools like the radar to make finding bases viable in the early midgame of the tech progression tree. Allowing for base finding to be much more streamlined, and making hiding strategies much less viable. Radar will require computation, power, and be placed relatively high up with access to the skyline. Quite cumbersome and fragile, yet game changing when it comes to recon. It will find an average point of enemy bases and index them according to how big and populous the base is. Meaning, the teams that are more ahead will have more eyes on them.<br />
<br />
==== Factions progression ====<br />
Factions will be at the heart of your factory, they provide as your source of chunk claiming and chunk loading. However, to expand the area you can control the strength of your defenses. Your factions will have limited possible chunks they can claim, to expand their limit, teams must provide special resources to the faction, in order to increase their claim power.<br />
<br />
==== Suppliers ====<br />
Special multiblocks called suppliers will allow bases to bolster their defenses. Multiblocks will require a steady supply of quality food to increase the defense factor of a certain area, about 3x3 chunk area (will only work on claimed chunks). For a buff to be applied, it must be done while not under siege. The machine will refuse to buff the base if it was turned on after the siege started. Machines will increase their strength depending on the amount of food supplied. Type of food item will be determined by faction tier, lower tier factions will require lower tier foods, while high tier factions will require high quality foodstuffs. The amount of claimed chunks will also increase the amount of food required. <br />
<br />
==== Guns ====<br />
Just like warfactory 1.0, we will have guns in the pack. Our current mod of choice is modular warfare shining, allowing us to have a framework for constantly expanding arsenal. We will also make use of new and improved HBM guns and turrets. We will integrate the guns with <br />
NTM armor system, that will make for interesting combat, devoid of bullet sponges and cheap one-shot tactics.<br />
<br />
==== MC-heli ====<br />
We want to make use of a custom fork of MCHELI, developed to integrate into our pack. Vehicles will help players to move around the map and conduct sieges. It may not come with WF2, as it will be a challenge to refactor.<br />
<br />
== Progression ==<br />
The 2 Main mods carrying progression will be Gregtech and HBM, with focus on Gregtech and HBM filling in with what we theme is the "highlight" content.<br />
<br />
=== Asymmetric progression ===<br />
To make progression and battles more dynamic, we want to introduce specific branches of progression depending on player's access to resources. For example, player has access to renewable large source of uranium. This allows player to start nuclear research early, giving access things such as early nuclear power, low yield nuclear weapons. Another example would be access to a specific resource that would allow player to produce energy weapons, which while not explicitly better than standard weapons, would be more effective against standard bullet-proof armor. Such design decisions would be sprinkled around the modpack. To enforce uniqueness of those resources, the map would have a limited amount of such resources, regulated by the administrator. This would encourage turf wars, to make players fight over strategic resources across the map. <br />
<br />
=== Faster progression ===<br />
Our goal is to make progression mesh well with the fast landscape that modded faction wars is. Let's be honest, GregTech's call to fame came from it's "immersive" (slow) gameplay. While we do want to retain the complexity and logistical challenge that GregTech provides, we want to remove the tedious, repetitive parts that are present in the mod. This ranges from large sweeping changes, to small optimizations. Here is a list of things that we want to introduce in order to archive this:<br />
<br />
* Early, but limited access to AE2<br />
* Recursive pipe shuttering<br />
* Multiblock blueprints<br />
* Complete rework of early game in order to decrease micro-crafting<br />
* Early centralized power and more streamlined powergrid handling<br />
<br />
=== Powergrid handling ===<br />
From experience in management of large bases, power management in GregTech is poorly designed. In early game, it is a chore. Low voltages make your expansion limited, it is impossible to have a properly designed, centralized power system that players can expand. Lategame however, it becomes overtly reliant on storing massive amounts of EU inside different kinds of EU storages. By the time you are in lategame, many interesting solutions are presented to the player, which in my opinion is a lost opportunity when it comes to game design. This does not even take into account AE2's EU/RF p2p's which trivialize power grid planning, to a point that all other tools become almost obsolete. We plan to mend this issue, using few simple machines and design choices.<br />
<br />
===== Large transformers =====<br />
To make power grid managment easier, players will get access to large transformers, which are simple multiblock structures that allow player to place energy hatches and dynamos, that will transform power. They would be tiered, with first tier allowing player to transform power from LV to HV and another one that would be able to tranform power for all of the tiers (up to UV). Goal is to make power grid managment much more streamlined, less reliant on hacky transformer chains or separate power grids.<br />
<br />
===== AC power =====<br />
To help players transfer power between different points. An "AC" power converter machine would be introduced. "AC" power would be a voltage type that would be unusable with machines, however would not suffer the same per-block loss like the "DC" power. Some kind of loss would still be at play, either passive loss on conversion between voltages or a loss proportional to amount of current drawn through the system. The AC power is there to ease dealing with power transfer in the early game to midgame, having less of an impact as games progresses into lategame. <br />
<br />
===== Removal of the power "cheese" =====<br />
To make power menagment matter in lategame stages. We will curb the amount of EU player can store. We will also restrict ways player can transfer EU, to avoid things such as AE2 completely breaking the game meta.<br />
<br />
=== Steam Age Rework ===<br />
Steam age is the biggest thorn in GT's design. It suffers from issues that we specifically want to avoid in our modpack. We opt into redesigning the steam age to focus on player to quickly be able to reach LV, while allowing player to make use of extra machines, that will stay relevant well into the midgame.<br />
[[File:Steam age progression chart.png|thumb|Chart for the steam age progression, showcasing the flow and key resources required to progress. (May change at any time)]]<br />
<br />
=== Steam power overhaul ===<br />
Steam is a rather underutilized power source in later stages of GregTech, due to its unremarkable power density. It is a shame that this power source gets completely outshined by the the time you get to LV. We want to introduce higher density steam types, which paired with high pressure pipes allow for scalable throughput beyond earlygame. With NTM there are also even more interesting way to boil water, using many different reactors.<br />
<br />
Other current ideas for new ways to generate steam are:<br />
* The Boiler Tower, a multi which gives higher yields exponentially the taller it is.<br />
* The Heat Exchanger, a multi which turns lava and water into steam.<br />
* A reworked Large Boiler system to overcome its flaws and to make them relevant again.<br />
<br />
In a parallel to the real world’s development, petrochemistry is unlocked very early on. High-pressure steam is used to extract oil and refine it. Of course, these early methods are not nearly as successful as more advanced systems, and we cannot refine advanced petrochemicals like HOG this way. Bunker fuel, kerosene, etc is unlocked around this time.<br />
<br />
With this, we can construct power systems that will sustain us far into the electrical tiers.<br />
<br />
==== Early Combustion ====<br />
In alignment with the “shoulders of giants” philosophy, the player will be given crude combustion engines in late ULV. These engines, through incremental upgrade, can sustain them well into the LV-EV tiers. To begin, you will only be able to produce crude kerosene and bunker fuel, and suffer poor efficiency and very crude engines that can only really sustain you for a while.<br />
<br />
Early petro fuels won’t produce power, but will power boilers to produce oodles of steam. Direct combustion engines (and steam turbines) are unlocked in LV, but can be made easily by retrofitting your early boiler systems. <br />
=== Lv-Ev Tenets ===<br />
<br />
=== Low Voltage ===<br />
Low voltage will unlock AE2 as we recognize that this mod is inseparable with GT due to its Gregtech’s complexity ramping up as soon as player gets to later stages. Early AE2 will empower the team to produce larger and more complex factories, as they won’t feel they need to wait until they reach AE2 (common issue with GTNH). This may make people think this will kill complexity, which is why we opt to enable keep channels enabled. <br />
<br />
Players will unlock plethora of basic self defence guns and infrastructure, such as barbed wire, concrete.<br />
<br />
===== AE2's common pitfall: oversimplification of bases =====<br />
AE2 is a powerful tool, which can do many many things. This is what makes it great. However, AE2 can actually oversimplify a lot of systems, via its powerful ondemand crafting system. We want to give players access to the powerful tools, though stray away from introducing AE2s full overpowered suite of tools that make game become AE2 trivia simulator.<br />
<br />
=== Medium Voltage ===<br />
=== High Voltage ===<br />
<br />
=== Ev-Luv Tenets ===<br />
<br />
=== Extreme Voltage ===<br />
<br />
=== Insane Voltage ===<br />
<br />
=== Ludicrous Voltage ===<br />
<br />
=== ZPM Voltage ===<br />
I doubt we need to go this far, only one team will most likely even make it to ZPM or beyond it<br />
<br />
=== Multi Rework ===<br />
<br />
For WF2 we want to move away from GCYM, as it has some intrinsic problems with it, as well as it doesn’t fit into what we want for a pvp pack.<br />
<br />
<br />
We will implement new multis, either through an external mod or through WFCore. And the consensus is that the first round of multis will be available in early HV to incentivise the creation of large scale automation early on.<br />
<br />
<br />
The Parallels will most likely be akin to how GT++ calculates parallels.<br />
<br />
=== NTM Space ===<br />
Since we are also porting the NTM space content, we are looking into integrating it into Warfactory, and as it's such a major part of the progression it will get it's own section.<br />
<br />
== Takeaways and lessons from WF1 ==<br />
* All movement options within Warfactory 2, have to be evaluated and checked for if they are too overpowered, not to have a repeat of the hooks situation from Warfactory 1.<br />
* Ensure armor and weapons are tested THOROUGHLY (to prevent a repeat of the redstone arsenal incident)<br />
* Make sure to do small scale tests with testers who are intentionally made to cause as much lag as possible to then make a spark profile to find sources of lag to prevent another visual ores situation.<br />
* We will also be cutting down on the amount of mods to prevent interactions in-between the mods.<br />
<br />
<br />
== The Dev Test ==<br />
A Dev Test will be orchestrated as a way of engaging the community before WF2, while still using it as a platform to see if the more experimental features work in a event setting.<br />
<br />
The devtest will be done as follows, first the top 2 people of each team<ref>Would likely be the Leader and Co-Leader of each respective team</ref> would be invited to a discord. This is to discuss the rules and to make any last minute alterations to the pack before the devtest takes place.<br />
<br />
After everything is sorted out, all the members of each respective team will be added, and if there are still server slots there will be a google form setup for invitations.<br />
<br />
The prevailing idea is that once the pack reaches LuV, the devtest will occur. As it is not a traditional event, the server will have very specific win conditions. Those being finishing LuV and obtaining the Crystal Mainframe. This will be akin to the "Science Victory" in Civ6.</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=File:Steam_age_progression_chart.png&diff=216File:Steam age progression chart.png2025-07-30T19:51:14Z<p>Mr.Norwood: </p>
<hr />
<div>field for steam age progression</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=Warfactory_2_design&diff=215Warfactory 2 design2025-07-30T19:43:21Z<p>Mr.Norwood: Removing MTNS crap</p>
<hr />
<div>Warfactory is a 1.12 Modpack made specifically for large faction server SMPs,<br />
based around HBM:NTM and Gregtech, using Modular Warfare Shining and possibly<br />
Mcheli for combat. The Modpack features an in-house fork of the Warforge claim mod,<br />
adjusted for a more dynamic, fair and exciting faction experience.<br />
<br />
== General Principles ==<br />
The pack must be accommodating to both veterans and new players, offering experience that is well documented and easily inferred from context clues. The progression will be tailored towards a much faster and dynamic style, compared to vanilla GT.<br />
<br />
Resources will be given very generously and infrastructure will be easy to set up, and in-game challenges will be tailored towards quick-thinking and high performance instead of endurance (grind). <br />
Combat balance is very important to us. Every item and system will be designed and improved with more tactical combat experience in mind. We take a hard stance against creative flight, buff stacking, teleportation, insane armor values and other game breaking features that have commonly been seen in other commonly used packs. Guile gives far greater rewards than material advantages.<br />
Another idea in the works is the idea of “Time Gated Progression”. This is a measure to nerf large teams and allow smaller teams to survive. This will be executed with the use of RecipeStages, where each passing day unlocks a new voltage tier that people can progress into, Steam Day 1, Lv Day 2, Mv Day 3 Etc.<br />
<br />
=== “Shoulders of Giants” Approach ===<br />
Having certain “milestone” machines maintain their relevance across several tiers, undergoing only incremental upgrades. This will incentivize staying in one place. Moreover, as long as a team has good risk management, they’ll have backups of these machines to get them up and running easily, making progression faster and more rewarding.<br />
Say a ULV reworked blast furnace has no coils. As we progress, we give it coil upgrades and incrementally approve what it can cook.<br />
<br />
To encourage different play styles, we will have 3 different win conditions:<br />
* Wonder winner – The team which has the nicest buildings and wonders.<br />
* Domination victory – The team that topples the most bases.<br />
* Progression victory – The most technologically advanced team.<br />
<br />
== Combat ==<br />
This is the section for the combat for WF2.<br />
<br />
=== Base raiding ===<br />
Raiding should be as difficult as defending yourself. As veterans of the modded landscape, we have noticed the general meta to be:<br />
<br />
You make cobble box underground and push progression mindlessly<br />
Make cheapest throwable explosive to destroy claims (if they exist)<br />
Use psyops or bruteforce to find other cobble boxes<br />
Raid the cobble box to get some loot<br />
Hope you won't get found, or you need to move the entire base in about an hour<br />
<br />
We completely disagree with this meta, it makes attacking too powerful and impossible to defend against due to the nature of minecraft. Base planning makes no sense when, after your base is found, the entire team will be occupied with defending itself against the lowest tier explosives.<br />
The only real way to defend yourself is to never get found, which is not an engaging and fun game loop. Attacking teams also spend most of their time traveling around the map, trying to find the base via bruteforce, which is not a fun experience either. Which encourages cheating, in the form of BlockESP to make the experience bearable.<br />
Our mod: Warforge factions will make players rethink the way they play faction servers. Bases will require time demanding strategic sieges that will take strategic effort from the attacker. With extended defensive tooling from mods such as NTM, base design, defenses, and automation will hopefully become an important aspect of the game.<br />
The land you will settle down on will also be very significant, giving teams advantages for settling down in resource rich areas. Some exclusive rare materials that will make specific subbranches of military and industry more viable. Those will not be required for progression, but offer tactical resource advantage.<br />
<br />
=== Early Combat ===<br />
The first combat will be done using the Large Metal Press multi, which works similar to the burner press from HBM. This will be used to obtain the first guns. The Gear Foundry will be the way you make armor, weapons and advanced tools. It will be upgradable similar to the Chemplant from GTNH.<br />
<br />
==== Radar ====<br />
We will feature tools like the radar to make finding bases viable in the early midgame of the tech progression tree. Allowing for base finding to be much more streamlined, and making hiding strategies much less viable. Radar will require computation, power, and be placed relatively high up with access to the skyline. Quite cumbersome and fragile, yet game changing when it comes to recon. It will find an average point of enemy bases and index them according to how big and populous the base is. Meaning, the teams that are more ahead will have more eyes on them.<br />
<br />
==== Factions progression ====<br />
Factions will be at the heart of your factory, they provide as your source of chunk claiming and chunk loading. However, to expand the area you can control the strength of your defenses. Your factions will have limited possible chunks they can claim, to expand their limit, teams must provide special resources to the faction, in order to increase their claim power.<br />
<br />
==== Suppliers ====<br />
Special multiblocks called suppliers will allow bases to bolster their defenses. Multiblocks will require a steady supply of quality food to increase the defense factor of a certain area, about 3x3 chunk area (will only work on claimed chunks). For a buff to be applied, it must be done while not under siege. The machine will refuse to buff the base if it was turned on after the siege started. Machines will increase their strength depending on the amount of food supplied. Type of food item will be determined by faction tier, lower tier factions will require lower tier foods, while high tier factions will require high quality foodstuffs. The amount of claimed chunks will also increase the amount of food required. <br />
<br />
==== Guns ====<br />
Just like warfactory 1.0, we will have guns in the pack. Our current mod of choice is modular warfare shining, allowing us to have a framework for constantly expanding arsenal. We will also make use of new and improved HBM guns and turrets. We will integrate the guns with <br />
NTM armor system, that will make for interesting combat, devoid of bullet sponges and cheap one-shot tactics.<br />
<br />
==== MC-heli ====<br />
We want to make use of a custom fork of MCHELI, developed to integrate into our pack. Vehicles will help players to move around the map and conduct sieges. It may not come with WF2, as it will be a challenge to refactor.<br />
<br />
== Progression ==<br />
The 2 Main mods carrying progression will be Gregtech and HBM, with focus on Gregtech and HBM filling in with what we theme is the "highlight" content.<br />
<br />
=== Asymmetric progression ===<br />
To make progression and battles more dynamic, we want to introduce specific branches of progression depending on player's access to resources. For example, player has access to renewable large source of uranium. This allows player to start nuclear research early, giving access things such as early nuclear power, low yield nuclear weapons. Another example would be access to a specific resource that would allow player to produce energy weapons, which while not explicitly better than standard weapons, would be more effective against standard bullet-proof armor. Such design decisions would be sprinkled around the modpack. To enforce uniqueness of those resources, the map would have a limited amount of such resources, regulated by the administrator. This would encourage turf wars, to make players fight over strategic resources across the map. <br />
<br />
=== Faster progression ===<br />
Our goal is to make progression mesh well with the fast landscape that modded faction wars is. Let's be honest, gregtech's call to fame came from it's "immersive" (slow) gameplay. While we do want to retain the complexity and logistical challenge that gregtech provides, we want to remove the tedious, repetitive parts that are present in the mod. This ranges from large sweeping changes, to small optimizations. Here is a list of things that we want to introduce in order to archive this:<br />
<br />
* Early, but limited access to AE2<br />
* Recursive pipe shuttering<br />
* Multiblock blueprints<br />
* Complete rework of early game in order to decrease micro-crafting<br />
* Early centralized power and more streamlined powergrid handling<br />
<br />
=== Powergrid handling ===<br />
From experience in management of large bases, power management in GregTech is poorly designed. In early game, it is a chore. Low voltages make your expansion limited, it is impossible to have a properly designed, centralized power system that players can expand. Lategame however, it becomes overtly reliant on storing massive amounts of EU inside different kinds of EU storages. By the time you are in lategame, many interesting solutions are presented to the player, which in my opinion is a lost opportunity when it comes to game design. This does not even take into account AE2's EU/RF p2p's which trivialize power grid planning, to a point that all other tools become almost obsolete. We plan to mend this issue, using few simple machines and design choices.<br />
<br />
===== Large transformers =====<br />
To make power grid managment easier, players will get access to large transformers, which are simple multiblock structures that allow player to place energy hatches and dynamos, that will transform power. They would be tiered, with first tier allowing player to transform power from LV to HV and another one that would be able to tranform power for all of the tiers (up to UV). Goal is to make power grid managment much more streamlined, less reliant on hacky transformer chains or separate power grids.<br />
<br />
===== AC power =====<br />
To help players transfer power between different points. An "AC" power converter machine would be introduced. "AC" power would be a voltage type that would be unusable with machines, however would not suffer the same per-block loss like the "DC" power. Some kind of loss would still be at play, either passive loss on conversion between voltages or a loss proportional to amount of current drawn through the system. The AC power is there to ease dealing with power transfer in the early game to midgame, having less of an impact as games progresses into lategame. <br />
<br />
===== Removal of the power "cheese" =====<br />
To make power menagment matter in lategame stages. We will curb the amount of EU player can store. We will also restrict ways player can transfer EU, to avoid things such as AE2 completely breaking the game meta.<br />
<br />
=== Steam Age Rework ===<br />
Steam age is the biggest thorn in GT's design. It suffers from issues that we specifically want to avoid in our modpack<br />
<br />
=== Low pressure ===<br />
The first Subtier will be “Low Pressure” which are the standard bronze steam machines, and the main goal will be to obtain Steel, which is the material for the next tier.<br />
<br />
==== New Steel line ====<br />
This features the reworked Blast Furnace, which instead of outputting steel in solid form, outputs it in liquid form. This idea was ripped straight from GT:Mega, as it works quite well there as an early way to incentivize automation.<br />
<br />
Strandcaster<ref><br />
The Strandcaster becomes obsolete fast, being replaced with the fluid solidifier<br />
<br />
Fixes: Remove the Fluid Solidifier recipe and make a new multi for this purpose, Bite the bullet and give into power creep, nerf the Fluid Solidifier recipe<br />
</ref>, which inputs water to cool the ingots and outputs steam, and the way players will transport liquid steel is using the new Brick pipes. The result is a beefy array of large multis that will last the player for a long time. Perhaps it could accept simple incremental upgrades as the tier advances? (Recall, IRL blast furnaces have not changed considerably in the last century.) <br />
<br />
<br />
<nowiki>*</nowiki>Note: having large multiblocks disincentives moving <br />
==== New Rubber line ====<br />
The idea behind this is to make rubber a chain that is done early on in the game, and also works forever with zero inputs other than sulphur.<br />
This is needed, as the blast furnace does not have a Gui and needs the hatches to function.<br />
<small>[More theory crafting needed]</small><br />
<br />
* Automated Rubber Plantation?<br />
* What tree-interaction systems are added by GT? HBM?<br />
* Is a custom multi needed?<br />
* Perhaps this multi should require a view of the sky.<br />
<br />
<br />
=== High pressure ===<br />
<br />
The main goal of this tier is to obtain the Crucible from HBM, which is used to make the mat for the next subtier, “Advanced Alloy”, and it also brings forth the idea of “Hot gas reclaim” for Blast furnaces.<br />
<br />
==== Crucible ====<br />
<br />
It will be based on the HBM Crucible and will be extremely steel heavy, to incentivise people to use the gas preheating system. The crucible will be used to obtain Advanced alloy, which is a staple material through the Steam age and up until late Mv.<br />
<br />
==== Gas Preheating ====<br />
This system will use Hot Blast Stoves, that will turn air into Preheated Air, that can then be inputted into a Colossal Blast Furnace, to get extra parallels and speed that will remain unrivalled until far later in the game.<br />
<br />
<br />
Another thing is that the EBF Steel recipe will be removed, as it brings unwanted power creep into the game, and will be replaced with a more involved and interesting way to create steel, other than just inputting oxygen and wrought iron in an EBF.<br />
<br />
==== Pressure Pipes ====<br />
One of the many power rebalances to steam brought by Warfactory 2, these are pipes that have immense throughput, while only being able to transfer steam. Allowing for the throughput problems that make steam unviable to be rectified.<br />
<br />
<br />
The first tier ones will be made with steel and advanced alloy.<br />
<br />
==== Mining Explosives ====<br />
<br />
Mining is a tedious process in default GT. Doubly so in vanilla. While big mining vehicles are clearly out of the question, the next best thing is planting explosives and gnawing away at big veins that way. <br />
<br />
=== Ultra High Pressure?? Unsure on the name ===<br />
The goal of this tier is to obtain electronic circuits, which will be used to progress to Lv. This tier will be very steel heavy in the new multis for creating the circuits. The main concept is that the amount of steps will be increased but the cost of a circuit will go down dramatically to incentivize automation.<br />
<br />
==== New PCB line ====<br />
Early petrochem equals early plastics. Simple Bakelite and whatnot can be used as an effective base for circuits. Sure, you can make wooden circuits with GT’s base prices. But an ENIAC-style crude plastic circuit is far cheaper if you have the time to automate it.<br />
<br />
=== Steam power overhaul ===<br />
Steam is a rather underutilized power source in later stages of gregtech, due to its unremarkable power density.<br />
It is a shame that this power source gets completely outshined by the the time you get to LV. We want to introduce<br />
higher density steam types, which paired with high pressure pipes allow for scalable throughput beyond earlygame. <br />
With NTM there are also even more interesting way to boil water, using many different reactors.<br />
<br />
Other current ideas for new ways to generate steam are:<br />
* The Boiler Tower, a multi which gives higher yields exponentially the taller it is.<br />
* The Heat Exchanger, a multi which turns lava and water into steam.<br />
* A reworked Large Boiler system to overcome its flaws and to make them relevant again.<br />
<br />
This isn't confirmed as we haven't thought of a concrete system for it<br />
<br />
<br />
Main reason for it's inclusion is that It can give players in the time gates more stuff to do, for an easier allocation of tasks while still implementing a genuinely cool system<br />
<br />
In a parallel to the real world’s development, petrochemistry is unlocked very early on. High-pressure steam is used to extract oil and refine it. Of course, these early methods are not nearly as successful as more advanced systems, and we cannot refine advanced petrochemicals like HOG this way. Bunker fuel, kerosene, etc is unlocked around this time.<br />
<br />
<br />
With this, we can construct power systems that will sustain us far into the electrical tiers.<br />
<br />
==== Early Combustion ====<br />
In alignment with the “shoulders of giants” philosophy, the player will be given crude combustion engines in late ULV. These engines, through incremental upgrade, can sustain them well into the LV-EV tiers. To begin, you will only be able to produce crude kerosene and bunker fuel, and suffer poor efficiency and very crude engines that can only really sustain you for a while.<br />
<br />
<br />
Early petro fuels won’t produce power, but will power boilers to produce oodles of steam. Direct combustion engines (and steam turbines) are unlocked in LV, but can be made easily by retrofitting your early boiler systems. <br />
<br />
<br />
The question is: how meta do we make steam turbines? Will they sustain us far into higher tiers?<br />
=== Lv-Ev Tenets ===<br />
<br />
=== Low Voltage ===<br />
Low voltage will unlock AE2 as we recognize that this mod is inseparable with GT due to its Gregtech’s complexity ramping up as soon as player gets to later stages. Early AE2 will empower the team to produce larger and more complex factories, as they won’t feel they need to wait until they reach AE2 (common issue with GTNH). This may make people think this will kill complexity, which is why we opt to enable keep channels enabled.<br />
<br />
Players will unlock plethora of basic self defence guns and infrastructure, such as barbed wire, concrete.<br />
<br />
=== Medium Voltage ===<br />
Not much needs to be changed in MV, I do believe it's probably one of the most fun tiers in GT. Adding on, GCYL doesn't make many changes to it main ones being the circuit manufacturing and the gold line. There will also not be any HBM content in this tier, aside from potentially a very low yield SEMTEX recipe.<br />
<br />
=== High Voltage ===<br />
<br />
=== Ev-Luv Tenets ===<br />
<br />
=== Extreme Voltage ===<br />
<br />
=== Insane Voltage ===<br />
<br />
=== Ludicrous Voltage ===<br />
<br />
=== Luv-Uhv Tenets ===<br />
I doubt we need to go this far, only one team will most likely even make it to ZPM or beyond it<br />
<br />
=== Uhv+ Progression ===<br />
<br />
=== Multi Rework ===<br />
<br />
For WF2 we want to move away from GCYM, as it has some intrinsic problems with it, as well as it doesn’t fit into what we want for a pvp pack.<br />
<br />
<br />
We will implement new multis, either through an external mod or through WFCore. And the consensus is that the first round of multis will be available in early HV to incentivise the creation of large scale automation early on.<br />
<br />
<br />
The Parallels will most likely be akin to how GT++ calculates parallels.<br />
<br />
=== GCYL Balancing ===<br />
While GCYL does have it's short comings, I<ref>Lrdmtns</ref> do believe that it suites a pvp pack. This is due to the fact that, due to the abundance of lines that are made, it makes it easier for teams to allocate simple tasks.<br />
<br />
As in each tier, there are maybe 2-3 large lines and 5-7 smaller lines, that can be allocated quite easily to a large group of people.<br />
<br />
Not much has to be changed as, a large chunk of the more insufferable parts of GCYL are in the late game. Most prominent examples of which are things such as Bromine and Indium. Which only become a major concern around the time of Luv+.<br />
<br />
A concern when it comes to GCYL is that, due to the large amount of tile-entities present. This will hopefully be addressed in the devtest, which will give further insight on what to do when it comes to conserving tick time.<br />
<br />
An idea to solves this would be, after someone makes a line, said line can be done on a single multi akin to what GTNH does with it's Quantum Force Transformer or what GCYL does lategame with it's chemplant.<br />
<br />
== NTM Space ==<br />
Since we are also porting the NTM space content, we are looking into integrating it into Warfactory, and as it's such a major part of the progression it will get it's own section.<br />
<br />
== Takeaways and lessons from WF1 ==<br />
* All movement options within Warfactory 2, have to be evaluated and checked for if they are too overpowered, not to have a repeat of the hooks situation from Warfactory 1.<br />
* Ensure armor and weapons are tested THOROUGHLY (to prevent a repeat of the redstone arsenal incident)<br />
* Make sure to do small scale tests with testers who are intentionally made to cause as much lag as possible to then make a spark profile to find sources of lag to prevent another visual ores situation.<br />
* We will also be cutting down on the amount of mods to prevent interactions in-between the mods.<br />
<br />
<br />
== The Dev Test ==<br />
A Dev Test will be orchestrated as a way of engaging the community before WF2, while still using it as a platform to see if the more experimental features work in a event setting.<br />
<br />
The devtest will be done as follows, first the top 2 people of each team<ref>Would likely be the Leader and Co-Leader of each respective team</ref> would be invited to a discord. This is to discuss the rules and to make any last minute alterations to the pack before the devtest takes place.<br />
<br />
After everything is sorted out, all the members of each respective team will be added, and if there are still server slots there will be a google form setup for invitations.<br />
<br />
The prevailing idea is that once the pack reaches LuV, the devtest will occur. As it is not a traditional event, the server will have very specific win conditions. Those being finishing LuV and obtaining the Crystal Mainframe. This will be akin to the "Science Victory" in Civ6.</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=MediaWiki:Citizen.css&diff=195MediaWiki:Citizen.css2025-07-17T22:07:21Z<p>Mr.Norwood: Created page with "/* All CSS here will be loaded for users of the Citizen skin */ :root { --citizen-color-accent: #d40000; /* orange example */ }"</p>
<hr />
<div>/* All CSS here will be loaded for users of the Citizen skin */<br />
:root {<br />
--citizen-color-accent: #d40000; /* orange example */<br />
}</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=Template:InfoboxWar/styles.css&diff=137Template:InfoboxWar/styles.css2025-04-09T13:05:51Z<p>Mr.Norwood: </p>
<hr />
<div>.infobox {<br />
width: 300px;<br />
border-radius: 6px;<br />
border: 2px solid white;<br />
padding: 12px;<br />
margin: 15px 20px 20px 25px;<br />
float: right;<br />
clear: right;<br />
font-size: 90%;<br />
line-height: 1.3;<br />
}<br />
.ib-data-title {<br />
font-weight: bold;<br />
width: 85px;<br />
padding-left: 5px;<br />
vertical-align: top;<br />
}<br />
.ib-data {<br />
max-width: 170px;<br />
vertical-align: top;<br />
}<br />
.ib-image img {<br />
border: 1px solid !important;<br />
margin: 5px auto !important;<br />
}<br />
.ib-credits {<br />
text-align: center;<br />
font-size: 90%;<br />
}<br />
.pi-data {<br />
border-width: 0;<br />
padding: 0.625em 1em;<br />
padding-left: 0.500em;<br />
width: auto;<br />
text-align: center;<br />
}</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=Template:InfoboxWar/styles.css&diff=136Template:InfoboxWar/styles.css2025-04-09T13:05:23Z<p>Mr.Norwood: Created page with "/* probably for other infoboxes */ .infobox { width: 300px; border-radius: 6px; border: 2px solid white; padding: 12px; margin: 15px 20px 20px 25px; float: right; clear: right; font-size: 90%; line-height: 1.3; } .ib-data-title { font-weight: bold; width: 85px; padding-left: 5px; vertical-align: top; } .ib-data { max-width: 170px; vertical-align: top; } .ib-image img { border: 1px solid !important; margin: 5px auto !important; } .ib-credits { text-align..."</p>
<hr />
<div>/* probably for other infoboxes */<br />
.infobox {<br />
width: 300px;<br />
border-radius: 6px;<br />
border: 2px solid white;<br />
padding: 12px;<br />
margin: 15px 20px 20px 25px;<br />
float: right;<br />
clear: right;<br />
font-size: 90%;<br />
line-height: 1.3;<br />
}<br />
.ib-data-title {<br />
font-weight: bold;<br />
width: 85px;<br />
padding-left: 5px;<br />
vertical-align: top;<br />
}<br />
.ib-data {<br />
max-width: 170px;<br />
vertical-align: top;<br />
}<br />
.ib-image img {<br />
border: 1px solid !important;<br />
margin: 5px auto !important;<br />
}<br />
.ib-credits {<br />
text-align: center;<br />
font-size: 90%;<br />
}<br />
.pi-data {<br />
border-width: 0;<br />
padding: 0.625em 1em;<br />
padding-left: 0.500em;<br />
width: auto;<br />
text-align: center;<br />
}<br />
/* infoboxwar specifics */<br />
/* source from soft cell wiki (cc.by-sa 4.0) */<br />
/* creds to allaze_eroler for subtitle alignment help */</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=Warfactory_2_design&diff=127Warfactory 2 design2025-04-07T15:23:32Z<p>Mr.Norwood: </p>
<hr />
<div>== Warfactory 2 ==<br />
<br />
Warfactory is a 1.12 Modpack made specifically for large faction server SMPs,<br />
based around HBM:NTM and Gregtech, using Modular Warfare Shining and possibly<br />
Mcheli for combat. The Modpack features an in-house fork of the Warforge claim mod,<br />
adjusted for a more dynamic, fair and exciting faction experience.<br />
<br />
=== General Principles ===<br />
The pack must be accommodating to both veterans and new players, offering experience that is well documented and easily inferred from context clues. The progression will be tailored towards a much faster and dynamic style, compared to vanilla GT.<br />
<br />
Resources will be given very generously and infrastructure will be easy to set up, and in-game challenges will be tailored towards quick-thinking and high performance instead of endurance (grind). <br />
Combat balance is very important to us. Every item and system will be designed and improved with more tactical combat experience in mind. We take a hard stance against creative flight, buff stacking, teleportation, insane armor values and other game breaking features that have commonly been seen in other commonly used packs. Guile gives far greater rewards than material advantages.<br />
Another idea in the works is the idea of “Time Gated Progression”. This is a measure to nerf large teams and allow smaller teams to survive. This will be executed with the use of RecipeStages, where each passing day unlocks a new voltage tier that people can progress into, Steam Day 1, Lv Day 2, Mv Day 3 Etc.<br />
<br />
<br />
==== “Shoulders of Giants” Approach ====<br />
<br />
Having certain “milestone” machines maintain their relevance across several tiers, undergoing only incremental upgrades. This will incentivize staying in one place. Moreover, as long as a team has good risk management, they’ll have backups of these machines to get them up and running easily, making progression faster and more rewarding.<br />
Say a ULV reworked blast furnace has no coils. As we progress, we give it coil upgrades and incrementally approve what it can cook.<br />
<br />
<br />
To encourage different play styles, we will have 3 different win conditions:<br />
* Wonder winner – The team which has the nicest buildings and wonders.<br />
* Domination victory – The team that topples the most bases.<br />
* Progression victory – The most technologically advanced team.<br />
<br />
<br />
<br />
== Combat ==<br />
<br />
=== Base raiding ===<br />
Raiding should be as difficult as defending yourself. As veterans of the modded landscape, we have noticed the general meta to be:<br />
<br />
You make cobble box underground and push progression mindlessly<br />
Make cheapest throwable explosive to destroy claims (if they exist)<br />
Use psyops or bruteforce to find other cobble boxes<br />
Raid the cobble box to get some loot<br />
Hope you won't get found, or you need to move the entire base in about an hour<br />
<br />
We completely disagree with this meta, it makes attacking too powerful and impossible to defend against due to the nature of minecraft. Base planning makes no sense when, after your base is found, the entire team will be occupied with defending itself against the lowest tier explosives.<br />
The only real way to defend yourself is to never get found, which is not an engaging and fun game loop. Attacking teams also spend most of their time traveling around the map, trying to find the base via bruteforce, which is not a fun experience either. Which encourages cheating, in the form of BlockESP to make the experience bearable.<br />
Our mod: Warforge factions will make players rethink the way they play faction servers. Bases will require time demanding strategic sieges that will take strategic effort from the attacker. With extended defensive tooling from mods such as NTM, base design, defenses, and automation will hopefully become an important aspect of the game.<br />
The land you will settle down on will also be very significant, giving teams advantages for settling down in resource rich areas. Some exclusive rare materials that will make specific subbranches of military and industry more viable. Those will not be required for progression, but offer tactical resource advantage.<br />
<br />
=== Early Combat ===<br />
<br />
The first combat will be done using the Large Metal Press multi, which works similar to the burner press from HBM. This will be used to obtain the first guns. The Gear Foundry will be the way you make armor, weapons and advanced tools. It will be upgradable similar to the Chemplant from GTNH.<br />
<br />
==== Radar ====<br />
<br />
We will feature tools like the radar to make finding bases viable in the early midgame of the tech progression tree. Allowing for base finding to be much more streamlined, and making hiding strategies much less viable. Radar will require computation, power, and be placed relatively high up with access to the skyline. Quite cumbersome and fragile, yet game changing when it comes to recon. It will find an average point of enemy bases and index them according to how big and populous the base is. Meaning, the teams that are more ahead will have more eyes on them.<br />
<br />
==== Factions progression ====<br />
<br />
Factions will be at the heart of your factory, they provide as your source of chunk claiming and chunk loading. However, to expand the area you can control the strength of your defenses. Your factions will have limited possible chunks they can claim, to expand their limit, teams must provide special resources to the faction, in order to increase their claim power.<br />
<br />
==== Suppliers ====<br />
<br />
Special multiblocks called suppliers will allow bases to bolster their defenses. Multiblocks will require a steady supply of quality food to increase the defense factor of a certain area, about 3x3 chunk area (will only work on claimed chunks). For a buff to be applied, it must be done while not under siege. The machine will refuse to buff the base if it was turned on after the siege started. Machines will increase their strength depending on the amount of food supplied. Type of food item will be determined by faction tier, lower tier factions will require lower tier foods, while high tier factions will require high quality foodstuffs. The amount of claimed chunks will also increase the amount of food required. <br />
<br />
==== Guns ====<br />
<br />
Just like warfactory 1.0, we will have guns in the pack. Our current mod of choice is modular warfare shining, allowing us to have a framework for constantly expanding arsenal. We will also make use of new and improved HBM guns and turrets. We will integrate the guns with <br />
NTM armor system, that will make for interesting combat, devoid of bullet sponges and cheap one-shot tactics.<br />
<br />
==== MC-heli ====<br />
<br />
We want to make use of a custom fork of MCHELI, developed to integrate into our pack. Vehicles will help players to move around the map and conduct sieges. It may not come with WF2, as it will be a challenge to refactor.<br />
<br />
== Progression ==<br />
<br />
The 2 Main mods carrying progression will be gregtech CEU with the GCYL:CEU add-on The original mod progression will be modified to fit our pack’s principles. This is needed as, GCYL is not beginner-friendly nor multiplayer friendly. A restructure of the progression is needed to overcome its shortcomings, and allow for an experience that can be approached by anyone regardless of their skill level.<br />
<br />
==== Steam Age Rework ====<br />
<br />
The main idea behind the Steam Age is the idea of “Subtiers”. Within the age which are used to bring new mechanics and ideas to the table to differentiate it from other packs. As the Steam age is notoriously boring and in Warfactory 1 we completely avoided it, opting for a removal of the steam age.<br />
<br />
==== Low pressure ====<br />
<br />
The first Subtier will be “Low Pressure” which are the standard bronze steam machines, and the main goal will be to obtain Steel, which is the material for the next tier.<br />
<br />
==== New Steel line ====<br />
<br />
This features the reworked Blast Furnace, which instead of outputting steel in solid form, outputs it in liquid form. This idea was ripped straight from GT:Mega, as it works quite well there as an early way to incentivize automation.<br />
<br />
Strandcaster<ref>,<br />
The Strandcaster becomes obsolete fast, being replaced with the fluid solidifier<br />
<br />
Fixes: Remove the Fluid Solidifier recipe and make a new multi for this purpose, Bite the bullet and give into power creep, nerf the Fluid Solidifier recipe<br />
</ref>which inputs water to cool the ingots and outputs steam, and the way players will transport liquid steel is using the new Brick pipes. The result is a beefy array of large multis that will last the player for a long time. Perhaps it could accept simple incremental upgrades as the tier advances? (Recall, IRL blast furnaces have not changed considerably in the last century.) <br />
<br />
<br />
<nowiki>*</nowiki>Note: having large multiblocks disincentivizes moving <br />
==== New Rubber line ====<br />
The idea behind this is to make rubber a chain that is done early on in the game, and also works forever with zero inputs other than sulfur.<br />
This is needed, as the blast furnace does not have a Gui and needs the hatches to function.<br />
<small>[More theory crafting needed]</small><br />
<br />
* Automated Rubber Plantation?<br />
* What tree-interaction systems are added by GT? HBM?<br />
* Is a custom multi needed?<br />
* Perhaps this multi should require a view of the sky.<br />
<br />
<br />
==== High pressure ====<br />
<br />
The main goal of this tier is to obtain the Crucible from HBM, which is used to make the mat for the next subtier, “Advanced Alloy”, and it also brings forth the idea of “Hot gas reclaim” for Blast furnaces.<br />
<br />
==== Crucible ====<br />
<br />
It will be based on the HBM Crucible and will be extremely steel heavy, to incentivise people to use the gas preheating system. The crucible will be used to obtain Advanced alloy, which is a staple material through the Steam age and up until late Mv.<br />
<br />
==== Gas Preheating ====<br />
This system will use Hot Blast Stoves, that will turn air into Preheated Air, that can then be inputted into a Colossal Blast Furnace, to get extra parallels and speed that will remain unrivaled until far later in the game.<br />
<br />
<br />
Another thing is that the EBF Steel recipe will be removed, as it brings unwanted power creep into the game, and will be replaced with a more involved and interesting way to create steel, other than just inputting oxygen and wrought iron in an EBF.<br />
<br />
==== Pressure Pipes ====<br />
One of the many power rebalances to steam brought by Warfactory 2, these are pipes that have immense throughput, while only being able to transfer steam. Allowing for the throughput problems that make steam unviable to be rectified.<br />
<br />
<br />
The first tier ones will be made with steel and advanced alloy.<br />
<br />
==== Mining Explosives ====<br />
<br />
Mining is a tedious process in default GT. Doubly so in vanilla. While big mining vehicles are clearly out of the question, the next best thing is planting explosives and gnawing away at big veins that way. <br />
<br />
==== Ultra High Pressure?? Unsure on the name ====<br />
<br />
The goal of this tier is to obtain electronic circuits, which will be used to progress to Lv. This tier will be very steel heavy in the new multis for creating the circuits. The main concept is that the amount of steps will be increased but the cost of a circuit will go down dramatically to incentivize automation.<br />
<br />
==== New PCB line ====<br />
<br />
Early petrochem equals early plastics. Simple bakelite and whatnot can be used as an effective base for circuits. Sure, you can make wooden circuits with GT’s base prices. But an ENIAC-style crude plastic circuit is far cheaper if you have the time to automate it.<br />
<br />
=== Steam power overhaul ===<br />
Steam is a rather underutilized power source in later stages of gregtech, due to its unremarkable power density.<br />
It is a shame that this power source gets completely outshined by the the time you get to LV. We want to introduce<br />
higher density steam types, which paired with high pressure pipes allow for scalable throughput beyond earlygame. <br />
With NTM there are also even more interesting way to boil water, using many different reactors.<br />
<br />
Other current ideas for new ways to generate steam are:<br />
* The Boiler Tower, a multi which gives higher yields exponentially the taller it is.<br />
* The Heat Exchanger, a multi which turns lava and water into steam.<br />
* A reworked Large Boiler system to overcome its flaws and to make them relevant again.<br />
<br />
This isn't confirmed as we haven't thought of a concrete system for it<br />
<br />
<br />
<span style="background-color:transparent;color:#000000;">Main reason for it's inclusion is that It can give players in the time gates more stuff to do, for an easier allocation of tasks while still implementing a genuinely&nbsp;cool system</span>Black Gold</div><br />
<br />
In a parallel to the real world’s development, petrochemistry is unlocked very early on. High-pressure steam is used to extract oil and refine it. Of course, these early methods are not nearly as successful as more advanced systems, and we cannot refine advanced petrochemicals like HOG this way. Bunker fuel, kerosene, etc is unlocked around this time.<br />
<br />
<br />
With this, we can construct power systems that will sustain us far into the electrical tiers.<br />
<br />
==== Early Combustion ====<br />
<br />
In alignment with the “shoulders of giants” philosophy, the player will be given crude combustion engines in late ULV. These engines, through incremental upgrade, can sustain them well into the LV-EV tiers. To begin, you will only be able to produce crude kerosene and bunker fuel, and suffer poor efficiency and very crude engines that can only really sustain you for a while.<br />
<br />
<br />
Early petro fuels won’t produce power, but will power boilers to produce oodles of steam. Direct combustion engines (and steam turbines) are unlocked in LV, but can be made easily by retrofitting your early boiler systems. <br />
<br />
<br />
The question is: how meta do we make steam turbines? Will they sustain us far into higher tiers?<br />
<br />
==== Lv-Ev Progression ====<br />
<br />
[More Theorycrafting needed]<br />
<br />
=== Low Voltage ===<br />
<br />
Low voltage will unlock AE2 as we recognize that this mod is inseparable with gt due to its gregtech’s complexity ramping up as soon as player gets to later stages. Early AE2 will empower the team to produce larger and more complex factories, as they won’t feel they need to wait until they reach AE2 (common issue with GTHN). This may make people think this will kill complexity, which is why we opt to enable keep channels enabled.<br />
<br />
Players will unlock plethera of basic self defense guns and infrastructure, such as barbed wire, concrete.<br />
<br />
<br />
<div style="color:#434343;">Medium Voltage</div><br />
<br />
<div style="color:#434343;">High Voltage</div><br />
<br />
Ev-Luv Progression<br />
<br />
<div style="color:#434343;">Extreme Voltage</div>* <div style="margin-left:0.5in;"></div><br />
<br />
<br />
<br />
Luv-Uhv Progression<br />
<br />
I doubt we need to go this far, only one team will most likely even make it to ZPM or beyond it<br />
<br />
== NTM Space ==<br />
Since we are also porting the NTM space content, we are looking into integrating it into warfactory<br />
<br />
<br />
<br />
<br />
Uhv+ Progression<br />
<br />
Multi Rework<br />
<br />
For WF2 we want to move away from GCYL, as it has some intrinsic problems with it, as well as it doesn’t fit into what we want for a pvp pack.<br />
<br />
<br />
We will implement new multis, either through an external mod or through WFCore. And the consensus is that the first round of multis will be available in early HV to incentivise the creation of large scale automation early on.<br />
<br />
<br />
The Parallels will most likely be akin to how GT++ calculates parallels.<br />
<br />
Takeaways and lessons from WF1* <div style="margin-left:0.5in;">All movement options within Warfactory 2, have to be evaluated and checked for if they are too overpowered, not to have a repeat of the hooks situation from Warfactory 1.</div><br />
* <div style="margin-left:0.5in;">Ensure armor and weapons are tested THOROUGHLY (to prevent a repeat of the redstone arsenal incident)</div><br />
* <div style="margin-left:0.5in;">Make sure to do small scale tests with testers who are intentionally made to cause as much lag as possible to then make a spark profile to find sources of lag to prevent another visual ores situation.</div><br />
* <div style="margin-left:0.5in;">We will also be cutting down on the amount of mods to prevent interactions in-between the mods.</div><br />
<br />
<br />
==== The Dev Test ====<br />
<br />
A Dev Test will be orchestrated as a way of engaging the community before WF2, while still using it as a platform to see if the more experimental features work in a mock event setting.<br />
<br />
We will shorten the progression to only really test the stuff we care about, as well as raiding other teams would need permission from an admin to go ahead.<br />
<br />
As of now there is no consensus on how the dev test will be performed, it will either be done where we invite the most active people in the discord or open a google form.</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=Warfactory_2_design&diff=126Warfactory 2 design2025-04-07T14:14:36Z<p>Mr.Norwood: fixing the formatting</p>
<hr />
<div>== Warfactory 2 ==<br />
<br />
Warfactory is a 1.12 Modpack made specifically for large faction server SMPs,<br />
based around HBM:NTM and Gregtech, using Modular Warfare Shining and possibly<br />
Mcheli for combat. The Modpack features an in-house fork of the Warforge claim mod,<br />
adjusted for a more dynamic, fair and exciting faction experience.<br />
<br />
=== General Principles ===<br />
The pack must be accommodating to both veterans and new players, offering experience that is well documented and easily inferred from context clues. The progression will be tailored towards a much faster and dynamic style, compared to vanilla GT.<br />
<br />
Resources will be given very generously and infrastructure will be easy to set up, and in-game challenges will be tailored towards quick-thinking and high performance instead of endurance (grind). <br />
Combat balance is very important to us. Every item and system will be designed and improved with more tactical combat experience in mind. We take a hard stance against creative flight, buff stacking, teleportation, insane armor values and other game breaking features that have commonly been seen in other commonly used packs. Guile gives far greater rewards than material advantages.<br />
Another idea in the works is the idea of “Time Gated Progression”. This is a measure to nerf large teams and allow smaller teams to survive. This will be executed with the use of RecipeStages, where each passing day unlocks a new voltage tier that people can progress into, Steam Day 1, Lv Day 2, Mv Day 3 Etc.<br />
<br />
<br />
==== “Shoulders of Giants” Approach ====<br />
<br />
Having certain “milestone” machines maintain their relevance across several tiers, undergoing only incremental upgrades. This will incentivize staying in one place. Moreover, as long as a team has good risk management, they’ll have backups of these machines to get them up and running easily, making progression faster and more rewarding.<br />
Say a ULV reworked blast furnace has no coils. As we progress, we give it coil upgrades and incrementally approve what it can cook.<br />
<br />
<br />
To encourage different play styles, we will have 3 different win conditions:<br />
* Wonder winner – The team which has the nicest buildings and wonders.<br />
* Domination victory – The team that topples the most bases.<br />
* Progression victory – The most technologically advanced team.<br />
<br />
<br />
<br />
== Combat ==<br />
<br />
=== Base raiding ===<br />
Raiding should be as difficult as defending yourself. As veterans of the modded landscape, we have noticed the general meta to be:<br />
<br />
You make cobble box underground and push progression mindlessly<br />
Make cheapest throwable explosive to destroy claims (if they exist)<br />
Use psyops or bruteforce to find other cobble boxes<br />
Raid the cobble box to get some loot<br />
Hope you won't get found, or you need to move the entire base in about an hour<br />
<br />
We completely disagree with this meta, it makes attacking too powerful and impossible to defend against due to the nature of minecraft. Base planning makes no sense when, after your base is found, the entire team will be occupied with defending itself against the lowest tier explosives.<br />
The only real way to defend yourself is to never get found, which is not an engaging and fun game loop. Attacking teams also spend most of their time traveling around the map, trying to find the base via bruteforce, which is not a fun experience either. Which encourages cheating, in the form of BlockESP to make the experience bearable.<br />
Our mod: Warforge factions will make players rethink the way they play faction servers. Bases will require time demanding strategic sieges that will take strategic effort from the attacker. With extended defensive tooling from mods such as NTM, base design, defenses, and automation will hopefully become an important aspect of the game.<br />
The land you will settle down on will also be very significant, giving teams advantages for settling down in resource rich areas. Some exclusive rare materials that will make specific subbranches of military and industry more viable. Those will not be required for progression, but offer tactical resource advantage.<br />
<br />
=== Early Combat ===<br />
<br />
The first combat will be done using the Large Metal Press multi, which works similar to the burner press from HBM. This will be used to obtain the first guns. The Gear Foundry will be the way you make armor, weapons and advanced tools. It will be upgradable similar to the Chemplant from GTNH.<br />
<br />
==== Radar ====<br />
<br />
We will feature tools like the radar to make finding bases viable in the early midgame of the tech progression tree. Allowing for base finding to be much more streamlined, and making hiding strategies much less viable. Radar will require computation, power, and be placed relatively high up with access to the skyline. Quite cumbersome and fragile, yet game changing when it comes to recon. It will find an average point of enemy bases and index them according to how big and populous the base is. Meaning, the teams that are more ahead will have more eyes on them.<br />
<br />
==== Factions progression ====<br />
<br />
Factions will be at the heart of your factory, they provide as your source of chunk claiming and chunk loading. However, to expand the area you can control the strength of your defenses. Your factions will have limited possible chunks they can claim, to expand their limit, teams must provide special resources to the faction, in order to increase their claim power.<br />
<br />
==== Suppliers ====<br />
<br />
Special multiblocks called suppliers will allow bases to bolster their defenses. Multiblocks will require a steady supply of quality food to increase the defense factor of a certain area, about 3x3 chunk area (will only work on claimed chunks). For a buff to be applied, it must be done while not under siege. The machine will refuse to buff the base if it was turned on after the siege started. Machines will increase their strength depending on the amount of food supplied. Type of food item will be determined by faction tier, lower tier factions will require lower tier foods, while high tier factions will require high quality foodstuffs. The amount of claimed chunks will also increase the amount of food required. <br />
<br />
==== Guns ====<br />
<br />
Just like warfactory 1.0, we will have guns in the pack. Our current mod of choice is modular warfare shining, allowing us to have a framework for constantly expanding arsenal. We will also make use of new and improved HBM guns and turrets. We will integrate the guns with <br />
NTM armor system, that will make for interesting combat, devoid of bullet sponges and cheap one-shot tactics.<br />
<br />
==== MC-heli ====<br />
<br />
We want to make use of a custom fork of MCHELI, developed to integrate into our pack. Vehicles will help players to move around the map and conduct sieges. It may not come with WF2, as it will be a challenge to refactor.<br />
<br />
==== Progression ====<br />
<br />
The 2 Main mods carrying progression will be gregtech CEU with the GCYL:CEU add-on The original mod progression will be modified to fit our pack’s principles. This is needed as, GCYL is not beginner-friendly nor multiplayer friendly. A restructure of the progression is needed to overcome its shortcomings, and allow for an experience that can be approached by anyone regardless of their skill level.<br />
<br />
==== Steam Age Rework ====<br />
<br />
The main idea behind the Steam Age is the idea of “Subtiers”. Within the age which are used to bring new mechanics and ideas to the table to differentiate it from other packs. As the Steam age is notoriously boring and in Warfactory 1 we completely avoided it, opting for a removal of the steam age.<br />
<br />
==== Low pressure ====<br />
<br />
The first Subtier will be “Low Pressure” which are the standard bronze steam machines, and the main goal will be to obtain Steel, which is the material for the next tier.<br />
<br />
==== New Steel line ====<br />
<br />
This features the reworked Blast Furnace, which instead of outputting steel in solid form, outputs it in liquid form. This idea was ripped straight from GT:Mega, as it works quite well there as an early way to incentivize automation.<br />
<br />
Strandcaster, which inputs water to cool the ingots and outputs steam, and the way players will transport liquid steel is using the new Brick pipes. The result is a beefy array of large multis that will last the player for a long time. Perhaps it could accept simple incremental upgrades as the tier advances? (Recall, IRL blast furnaces have not changed considerably in the last century.) <br />
<br />
<nowiki>*</nowiki>Note: having large multiblocks disincentivizes moving <br />
==== New Rubber line ====<br />
The idea behind this is to make rubber a chain that is done early on in the game, and also works forever with zero inputs other than sulfur.<br />
This is needed, as the blast furnace does not have a Gui and needs the hatches to function.<br />
<small>[More theory crafting needed]</small><br />
<br />
* Automated Rubber Plantation?<br />
* What tree-interaction systems are added by GT? HBM?<br />
* Is a custom multi needed?<br />
* Perhaps this multi should require a view of the sky.<br />
<br />
<br />
==== High pressure ====<br />
<br />
The main goal of this tier is to obtain the Crucible from HBM, which is used to make the mat for the next subtier, “Advanced Alloy”, and it also brings forth the idea of “Hot gas reclaim” for Blast furnaces.<br />
<br />
==== Crucible ====<br />
<br />
It will be based on the HBM Crucible and will be extremely steel heavy, to incentivise people to use the gas preheating system. The crucible will be used to obtain Advanced alloy, which is a staple material through the Steam age and up until late Mv.<br />
<br />
<div style="color:#666666;">Gas Preheating</div><br />
<br />
This system will use Hot Blast Stoves, that will turn air into Preheated Air, that can then be inputted into a Colossal Blast Furnace, to get extra parallels and speed that will remain unrivaled until far later in the game.<br />
<br />
<br />
Another thing is that the EBF Steel recipe will be removed, as it brings unwanted power creep into the game, and will be replaced with a more involved and interesting way to create steel, other than just inputting oxygen and wrought iron in an EBF.<br />
<br />
==== Pressure Pipes ====<br />
One of the many power rebalances to steam brought by Warfactory 2, these are pipes that have immense throughput, while only being able to transfer steam. Allowing for the throughput problems that make steam unviable to be rectified.<br />
<br />
<br />
The first tier ones will be made with steel and advanced alloy.<br />
<br />
==== Mining Explosives ====<br />
<br />
Mining is a tedious process in default GT. Doubly so in vanilla. While big mining vehicles are clearly out of the question, the next best thing is planting explosives and gnawing away at big veins that way. <br />
<br />
<br />
<br />
<br />
<div style="color:#434343;">Ultra High Pressure?? Unsure on the name</div><br />
<br />
The goal of this tier is to obtain electronic circuits, which will be used to progress to Lv. This tier will be very steel heavy in the new multis for creating the circuits. The main concept is that the amount of steps will be increased but the cost of a circuit will go down dramatically to incentivize automation.<br />
<br />
<div style="color:#666666;">New PCB line</div><br />
<br />
Early petrochem equals early plastics. Simple bakelite and whatnot can be used as an effective base for circuits. Sure, you can make wooden circuits with GT’s base prices. But an ENIAC-style crude plastic circuit is far cheaper if you have the time to automate it.<br />
<br />
<div style="color:#666666;">New Steam Powergen Ideas</div><br />
<br />
This comes in the form of giving the player access to multiblock generators, early on in the game. As well as trying to either improve, or phase out the <span style="background-color:transparent;color:#000000;">We can do a myriad of different ideas:</span><br />
<br />
<br />
<span style="background-color:transparent;color:#000000;">Make a tier of Rotor Holder available in each tier</span><br />
<br />
<br />
<span style="background-color:transparent;color:#000000;">Remove the system overall and replace it with a more tailored version for the pack</span><br />
<br />
<br />
<span style="background-color:transparent;color:#000000;">Redo the way the bonuses are given, likely based on the fuel inputted</span>rotor system as it is riddled with flaws.<br />
<br />
<br />
Another idea is to double the Eu/t of steam making it easier to make power calculations and making steam more viable throughout the game.<br />
<br />
<br />
The current ideas for new ways to generate steam are:* <div style="margin-left:0.5in;">The Boiler Tower, a multi which gives higher yields exponentially the taller it is.</div><br />
* <div style="margin-left:0.5in;">The Heat Exchanger, a multi which turns lava and water into steam.</div><br />
* <div style="margin-left:0.5in;">A reworked Large Boiler system to overcome its flaws and to make them relevant again.</div><br />
<br />
<br />
<br />
<br />
<br />
<div style="color:#666666;"><span style="background-color:transparent;color:#000000;">This isn't confirmed as we haven't thought of a concrete system for it</span><br />
<br />
<br />
<span style="background-color:transparent;color:#000000;">Main reason for it's inclusion is that It can give players in the time gates more stuff to do, for an easier allocation of tasks while still implementing a genuinely&nbsp;cool system</span>Black Gold</div><br />
<br />
In a parallel to the real world’s development, petrochemistry is unlocked very early on. High-pressure steam is used to extract oil and refine it. Of course, these early methods are not nearly as successful as more advanced systems, and we cannot refine advanced petrochemicals like HOG this way. Bunker fuel, kerosene, etc is unlocked around this time.<br />
<br />
<br />
With this, we can construct power systems that will sustain us far into the electrical tiers.<br />
<br />
==== Early Combustion ====<br />
<br />
In alignment with the “shoulders of giants” philosophy, the player will be given crude combustion engines in late ULV. These engines, through incremental upgrade, can sustain them well into the LV-EV tiers. To begin, you will only be able to produce crude kerosene and bunker fuel, and suffer poor efficiency and very crude engines that can only really sustain you for a while.<br />
<br />
<br />
Early petro fuels won’t produce power, but will power boilers to produce oodles of steam. Direct combustion engines (and steam turbines) are unlocked in LV, but can be made easily by retrofitting your early boiler systems. <br />
<br />
<br />
The question is: how meta do we make steam turbines? Will they sustain us far into higher tiers?<br />
<br />
==== Lv-Ev Progression ====<br />
<br />
[More Theorycrafting needed]<br />
<br />
Low Voltage<br />
<br />
Low voltage will unlock AE2 as we recognize that this mod is inseparable with gt due to its gregtech’s complexity ramping up as soon as player gets to later stages. Early AE2 will empower the team to produce larger and more complex factories, as they won’t feel they need to wait until they reach AE2 (common issue with GTHN). This may make people think this will kill complexity, which is why we opt to enable keep channels enabled.<br />
<br />
<br />
<div style="color:#434343;">Medium Voltage</div><br />
<br />
<div style="color:#434343;">High Voltage</div><br />
<br />
Ev-Luv Progression<br />
<br />
<div style="color:#434343;">Extreme Voltage</div>* <div style="margin-left:0.5in;"></div><br />
<br />
<br />
<br />
Luv-Uhv Progression<br />
<br />
I doubt we need to go this far, only one team will most likely even make it to ZPM or beyond it<br />
<br />
<br />
<div style="color:#434343;">On Space </div><br />
<br />
Space throws much of our design decisions out of the window. Also, massive amount of work to port it (true, imo we scrap it (if it wasn't so cool 😭))* <div style="margin-left:0.5in;">How do we handle space stations in a PVP environment?</div><br />
** <div style="margin-left:1in;">Space piracy? </div><br />
** <div style="margin-left:1in;">Perhaps a new function for docks</div><br />
*** <div style="margin-left:1.5in;">If your station has equal (or greater) thrust as another, you can conduct a boarding action with the dock. </div><br />
*** <div style="margin-left:1.5in;">Basically, you get their station’s Station Drive if you are both orbiting the same body, allowing a hostile rendezvous</div><br />
<br />
<br />
<br />
<br />
<br />
Uhv+ Progression<br />
<br />
Multi Rework<br />
<br />
For WF2 we want to move away from GCYL, as it has some intrinsic problems with it, as well as it doesn’t fit into what we want for a pvp pack.<br />
<br />
<br />
We will implement new multis, either through an external mod or through WFCore. And the consensus is that the first round of multis will be available in early HV to incentivise the creation of large scale automation early on.<br />
<br />
<br />
The Parallels will most likely be akin to how GT++ calculates parallels.<br />
<br />
Takeaways and lessons from WF1* <div style="margin-left:0.5in;">All movement options within Warfactory 2, have to be evaluated and checked for if they are too overpowered, not to have a repeat of the hooks situation from Warfactory 1.</div><br />
* <div style="margin-left:0.5in;">Ensure armor and weapons are tested THOROUGHLY (to prevent a repeat of the redstone arsenal incident)</div><br />
* <div style="margin-left:0.5in;">Make sure to do small scale tests with testers who are intentionally made to cause as much lag as possible to then make a spark profile to find sources of lag to prevent another visual ores situation.</div><br />
* <div style="margin-left:0.5in;">We will also be cutting down on the amount of mods to prevent interactions in-between the mods.</div><br />
<br />
<br />
==== The Dev Test ====<br />
<br />
A Dev Test will be orchestrated as a way of engaging the community before WF2, while still using it as a platform to see if the more experimental features work in a mock event setting.<br />
<br />
We will shorten the progression to only really test the stuff we care about, as well as raiding other teams would need permission from an admin to go ahead.<br />
<br />
As of now there is no consensus on how the dev test will be performed, it will either be done where we invite the most active people in the discord or open a google form.</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=Warfactory_2_design&diff=125Warfactory 2 design2025-04-07T14:12:25Z<p>Mr.Norwood: Created page with "== Warfactory 2 == Warfactory is a 1.12 Modpack made specifically for large faction server SMPs, based around HBM:NTM and Gregtech, using Modular Warfare Shining and possibly Mcheli for combat. The Modpack features an in-house fork of the Warforge claim mod, adjusted for a more dynamic, fair and exciting faction experience. === General Principles === The pack must be accommodating to both veterans and new players, offering experience that is well documented and easily..."</p>
<hr />
<div>== Warfactory 2 ==<br />
<br />
Warfactory is a 1.12 Modpack made specifically for large faction server SMPs,<br />
based around HBM:NTM and Gregtech, using Modular Warfare Shining and possibly<br />
Mcheli for combat. The Modpack features an in-house fork of the Warforge claim mod,<br />
adjusted for a more dynamic, fair and exciting faction experience.<br />
<br />
=== General Principles ===<br />
The pack must be accommodating to both veterans and new players, offering experience that is well documented and easily inferred from context clues. The progression will be tailored towards a much faster and dynamic style, compared to vanilla GT.<br />
<br />
Resources will be given very generously and infrastructure will be easy to set up, and in-game challenges will be tailored towards quick-thinking and high performance instead of endurance (grind). <br />
Combat balance is very important to us. Every item and system will be designed and improved with more tactical combat experience in mind. We take a hard stance against creative flight, buff stacking, teleportation, insane armor values and other game breaking features that have commonly been seen in other commonly used packs. Guile gives far greater rewards than material advantages.<br />
Another idea in the works is the idea of “Time Gated Progression”. This is a measure to nerf large teams and allow smaller teams to survive. This will be executed with the use of RecipeStages, where each passing day unlocks a new voltage tier that people can progress into, Steam Day 1, Lv Day 2, Mv Day 3 Etc.<br />
<br />
<br />
==== “Shoulders of Giants” Approach ====<br />
<br />
Having certain “milestone” machines maintain their relevance across several tiers, undergoing only incremental upgrades. This will incentivize staying in one place. Moreover, as long as a team has good risk management, they’ll have backups of these machines to get them up and running easily, making progression faster and more rewarding.<br />
Say a ULV reworked blast furnace has no coils. As we progress, we give it coil upgrades and incrementally approve what it can cook.<br />
<br />
<br />
To encourage different play styles, we will have 3 different win conditions:<br />
* Wonder winner – The team which has the nicest buildings and wonders.<br />
* Domination victory – The team that topples the most bases.<br />
* Progression victory – The most technologically advanced team.<br />
<br />
<br />
=== Combat ===<br />
<br />
==== Base raiding ====<br />
<br />
Raiding should be as difficult as defending yourself. As veterans of the modded landscape, we have noticed the general meta to be:<br />
<br />
You make cobble box underground and push progression mindlessly<br />
Make cheapest throwable explosive to destroy claims (if they exist)<br />
Use psyops or bruteforce to find other cobble boxes<br />
Raid the cobble box to get some loot<br />
Hope you won't get found, or you need to move the entire base in about an hour<br />
<br />
We completely disagree with this meta, it makes attacking too powerful and impossible to defend against due to the nature of minecraft. Base planning makes no sense when, after your base is found, the entire team will be occupied with defending itself against the lowest tier explosives.<br />
The only real way to defend yourself is to never get found, which is not an engaging and fun game loop. Attacking teams also spend most of their time traveling around the map, trying to find the base via bruteforce, which is not a fun experience either. Which encourages cheating, in the form of BlockESP to make the experience bearable.<br />
Our mod: Warforge factions will make players rethink the way they play faction servers. Bases will require time demanding strategic sieges that will take strategic effort from the attacker. With extended defensive tooling from mods such as NTM, base design, defenses, and automation will hopefully become an important aspect of the game.<br />
The land you will settle down on will also be very significant, giving teams advantages for settling down in resource rich areas. Some exclusive rare materials that will make specific subbranches of military and industry more viable. Those will not be required for progression, but offer tactical resource advantage.<br />
<br />
=== Early Combat ===<br />
<br />
The first combat will be done using the Large Metal Press multi, which works similar to the burner press from HBM. This will be used to obtain the first guns. The Gear Foundry will be the way you make armor, weapons and advanced tools. It will be upgradable similar to the Chemplant from GTNH.<br />
<br />
==== Radar ====<br />
<br />
We will feature tools like the radar to make finding bases viable in the early midgame of the tech progression tree. Allowing for base finding to be much more streamlined, and making hiding strategies much less viable. Radar will require computation, power, and be placed relatively high up with access to the skyline. Quite cumbersome and fragile, yet game changing when it comes to recon. It will find an average point of enemy bases and index them according to how big and populous the base is. Meaning, the teams that are more ahead will have more eyes on them.<br />
<br />
==== Factions progression ====<br />
<br />
Factions will be at the heart of your factory, they provide as your source of chunk claiming and chunk loading. However, to expand the area you can control the strength of your defenses. Your factions will have limited possible chunks they can claim, to expand their limit, teams must provide special resources to the faction, in order to increase their claim power.<br />
<br />
==== Suppliers ====<br />
<br />
Special multiblocks called suppliers will allow bases to bolster their defenses. Multiblocks will require a steady supply of quality food to increase the defense factor of a certain area, about 3x3 chunk area (will only work on claimed chunks). For a buff to be applied, it must be done while not under siege. The machine will refuse to buff the base if it was turned on after the siege started. Machines will increase their strength depending on the amount of food supplied. Type of food item will be determined by faction tier, lower tier factions will require lower tier foods, while high tier factions will require high quality foodstuffs. The amount of claimed chunks will also increase the amount of food required. <br />
<br />
==== Guns ====<br />
<br />
Just like warfactory 1.0, we will have guns in the pack. Our current mod of choice is modular warfare shining, allowing us to have a framework for constantly expanding arsenal. We will also make use of new and improved HBM guns and turrets. We will integrate the guns with <br />
NTM armor system, that will make for interesting combat, devoid of bullet sponges and cheap one-shot tactics.<br />
<br />
==== MC-heli ====<br />
<br />
We want to make use of a custom fork of MCHELI, developed to integrate into our pack. Vehicles will help players to move around the map and conduct sieges. It may not come with WF2, as it will be a challenge to refactor.<br />
<br />
==== Progression ====<br />
<br />
The 2 Main mods carrying progression will be gregtech CEU with the GCYL:CEU add-on The original mod progression will be modified to fit our pack’s principles. This is needed as, GCYL is not beginner-friendly nor multiplayer friendly. A restructure of the progression is needed to overcome its shortcomings, and allow for an experience that can be approached by anyone regardless of their skill level.<br />
<br />
==== Steam Age Rework ====<br />
<br />
The main idea behind the Steam Age is the idea of “Subtiers”. Within the age which are used to bring new mechanics and ideas to the table to differentiate it from other packs. As the Steam age is notoriously boring and in Warfactory 1 we completely avoided it, opting for a removal of the steam age.<br />
<br />
==== Low pressure ====<br />
<br />
The first Subtier will be “Low Pressure” which are the standard bronze steam machines, and the main goal will be to obtain Steel, which is the material for the next tier.<br />
<br />
==== New Steel line ====<br />
<br />
This features the reworked Blast Furnace, which instead of outputting steel in solid form, outputs it in liquid form. This idea was ripped straight from GT:Mega, as it works quite well there as an early way to incentivize automation.<br />
<br />
Strandcaster, which inputs water to cool the ingots and outputs steam, and the way players will transport liquid steel is using the new Brick pipes. The result is a beefy array of large multis that will last the player for a long time. Perhaps it could accept simple incremental upgrades as the tier advances? (Recall, IRL blast furnaces have not changed considerably in the last century.)* <div style="margin-left:0.5in;">Note: having large multiblocks disincentivizes moving</div><br />
<br />
<br />
<br />
<br />
==== New Rubber line ====<br />
The idea behind this is to make rubber a chain that is done early on in the game, and also works forever with zero inputs other than sulfur.<br />
This is needed, as the blast furnace does not have a Gui and needs the hatches to function.<br />
<small>[More theory crafting needed]</small><br />
<br />
* Automated Rubber Plantation?<br />
* What tree-interaction systems are added by GT? HBM?<br />
* Is a custom multi needed?<br />
* Perhaps this multi should require a view of the sky.<br />
<br />
<br />
==== High pressure ====<br />
<br />
The main goal of this tier is to obtain the Crucible from HBM, which is used to make the mat for the next subtier, “Advanced Alloy”, and it also brings forth the idea of “Hot gas reclaim” for Blast furnaces.<br />
<br />
==== Crucible ====<br />
<br />
It will be based on the HBM Crucible and will be extremely steel heavy, to incentivise people to use the gas preheating system. The crucible will be used to obtain Advanced alloy, which is a staple material through the Steam age and up until late Mv.<br />
<br />
<div style="color:#666666;">Gas Preheating</div><br />
<br />
This system will use Hot Blast Stoves, that will turn air into Preheated Air, that can then be inputted into a Colossal Blast Furnace, to get extra parallels and speed that will remain unrivaled until far later in the game.<br />
<br />
<br />
Another thing is that the EBF Steel recipe will be removed, as it brings unwanted power creep into the game, and will be replaced with a more involved and interesting way to create steel, other than just inputting oxygen and wrought iron in an EBF.<br />
<br />
==== Pressure Pipes ====<br />
One of the many power rebalances to steam brought by Warfactory 2, these are pipes that have immense throughput, while only being able to transfer steam. Allowing for the throughput problems that make steam unviable to be rectified.<br />
<br />
<br />
The first tier ones will be made with steel and advanced alloy.<br />
<br />
==== Mining Explosives ====<br />
<br />
Mining is a tedious process in default GT. Doubly so in vanilla. While big mining vehicles are clearly out of the question, the next best thing is planting explosives and gnawing away at big veins that way. <br />
<br />
<br />
<br />
<br />
<div style="color:#434343;">Ultra High Pressure?? Unsure on the name</div><br />
<br />
The goal of this tier is to obtain electronic circuits, which will be used to progress to Lv. This tier will be very steel heavy in the new multis for creating the circuits. The main concept is that the amount of steps will be increased but the cost of a circuit will go down dramatically to incentivize automation.<br />
<br />
<div style="color:#666666;">New PCB line</div><br />
<br />
Early petrochem equals early plastics. Simple bakelite and whatnot can be used as an effective base for circuits. Sure, you can make wooden circuits with GT’s base prices. But an ENIAC-style crude plastic circuit is far cheaper if you have the time to automate it.<br />
<br />
<div style="color:#666666;">New Steam Powergen Ideas</div><br />
<br />
This comes in the form of giving the player access to multiblock generators, early on in the game. As well as trying to either improve, or phase out the <span style="background-color:transparent;color:#000000;">We can do a myriad of different ideas:</span><br />
<br />
<br />
<span style="background-color:transparent;color:#000000;">Make a tier of Rotor Holder available in each tier</span><br />
<br />
<br />
<span style="background-color:transparent;color:#000000;">Remove the system overall and replace it with a more tailored version for the pack</span><br />
<br />
<br />
<span style="background-color:transparent;color:#000000;">Redo the way the bonuses are given, likely based on the fuel inputted</span>rotor system as it is riddled with flaws.<br />
<br />
<br />
Another idea is to double the Eu/t of steam making it easier to make power calculations and making steam more viable throughout the game.<br />
<br />
<br />
The current ideas for new ways to generate steam are:* <div style="margin-left:0.5in;">The Boiler Tower, a multi which gives higher yields exponentially the taller it is.</div><br />
* <div style="margin-left:0.5in;">The Heat Exchanger, a multi which turns lava and water into steam.</div><br />
* <div style="margin-left:0.5in;">A reworked Large Boiler system to overcome its flaws and to make them relevant again.</div><br />
<br />
<br />
<br />
<br />
<br />
<div style="color:#666666;"><span style="background-color:transparent;color:#000000;">This isn't confirmed as we haven't thought of a concrete system for it</span><br />
<br />
<br />
<span style="background-color:transparent;color:#000000;">Main reason for it's inclusion is that It can give players in the time gates more stuff to do, for an easier allocation of tasks while still implementing a genuinely&nbsp;cool system</span>Black Gold</div><br />
<br />
In a parallel to the real world’s development, petrochemistry is unlocked very early on. High-pressure steam is used to extract oil and refine it. Of course, these early methods are not nearly as successful as more advanced systems, and we cannot refine advanced petrochemicals like HOG this way. Bunker fuel, kerosene, etc is unlocked around this time.<br />
<br />
<br />
With this, we can construct power systems that will sustain us far into the electrical tiers.<br />
<br />
==== Early Combustion ====<br />
<br />
In alignment with the “shoulders of giants” philosophy, the player will be given crude combustion engines in late ULV. These engines, through incremental upgrade, can sustain them well into the LV-EV tiers. To begin, you will only be able to produce crude kerosene and bunker fuel, and suffer poor efficiency and very crude engines that can only really sustain you for a while.<br />
<br />
<br />
Early petro fuels won’t produce power, but will power boilers to produce oodles of steam. Direct combustion engines (and steam turbines) are unlocked in LV, but can be made easily by retrofitting your early boiler systems. <br />
<br />
<br />
The question is: how meta do we make steam turbines? Will they sustain us far into higher tiers?<br />
<br />
==== Lv-Ev Progression ====<br />
<br />
[More Theorycrafting needed]<br />
<br />
Low Voltage<br />
<br />
Low voltage will unlock AE2 as we recognize that this mod is inseparable with gt due to its gregtech’s complexity ramping up as soon as player gets to later stages. Early AE2 will empower the team to produce larger and more complex factories, as they won’t feel they need to wait until they reach AE2 (common issue with GTHN). This may make people think this will kill complexity, which is why we opt to enable keep channels enabled.<br />
<br />
<br />
<div style="color:#434343;">Medium Voltage</div><br />
<br />
<div style="color:#434343;">High Voltage</div><br />
<br />
Ev-Luv Progression<br />
<br />
<div style="color:#434343;">Extreme Voltage</div>* <div style="margin-left:0.5in;"></div><br />
<br />
<br />
<br />
Luv-Uhv Progression<br />
<br />
I doubt we need to go this far, only one team will most likely even make it to ZPM or beyond it<br />
<br />
<br />
<div style="color:#434343;">On Space </div><br />
<br />
Space throws much of our design decisions out of the window. Also, massive amount of work to port it (true, imo we scrap it (if it wasn't so cool 😭))* <div style="margin-left:0.5in;">How do we handle space stations in a PVP environment?</div><br />
** <div style="margin-left:1in;">Space piracy? </div><br />
** <div style="margin-left:1in;">Perhaps a new function for docks</div><br />
*** <div style="margin-left:1.5in;">If your station has equal (or greater) thrust as another, you can conduct a boarding action with the dock. </div><br />
*** <div style="margin-left:1.5in;">Basically, you get their station’s Station Drive if you are both orbiting the same body, allowing a hostile rendezvous</div><br />
<br />
<br />
<br />
<br />
<br />
Uhv+ Progression<br />
<br />
Multi Rework<br />
<br />
For WF2 we want to move away from GCYL, as it has some intrinsic problems with it, as well as it doesn’t fit into what we want for a pvp pack.<br />
<br />
<br />
We will implement new multis, either through an external mod or through WFCore. And the consensus is that the first round of multis will be available in early HV to incentivise the creation of large scale automation early on.<br />
<br />
<br />
The Parallels will most likely be akin to how GT++ calculates parallels.<br />
<br />
Takeaways and lessons from WF1* <div style="margin-left:0.5in;">All movement options within Warfactory 2, have to be evaluated and checked for if they are too overpowered, not to have a repeat of the hooks situation from Warfactory 1.</div><br />
* <div style="margin-left:0.5in;">Ensure armor and weapons are tested THOROUGHLY (to prevent a repeat of the redstone arsenal incident)</div><br />
* <div style="margin-left:0.5in;">Make sure to do small scale tests with testers who are intentionally made to cause as much lag as possible to then make a spark profile to find sources of lag to prevent another visual ores situation.</div><br />
* <div style="margin-left:0.5in;">We will also be cutting down on the amount of mods to prevent interactions in-between the mods.</div><br />
<br />
<br />
==== The Dev Test ====<br />
<br />
A Dev Test will be orchestrated as a way of engaging the community before WF2, while still using it as a platform to see if the more experimental features work in a mock event setting.<br />
<br />
We will shorten the progression to only really test the stuff we care about, as well as raiding other teams would need permission from an admin to go ahead.<br />
<br />
As of now there is no consensus on how the dev test will be performed, it will either be done where we invite the most active people in the discord or open a google form.</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=Warfactory_One&diff=124Warfactory One2025-02-24T14:32:50Z<p>Mr.Norwood: </p>
<hr />
<div>{{Modpack<br />
|name = Warfactory Legacy<br />
|image = [[File:Warfactory 1 Logo.png|thumb]]<br />
|release-date = 31 July 2024<br />
|devs = <br />
* [[Mr.Norwood]]<br />
* GrayGloo<br />
* Trainvoi<br />
* XorEight<br />
* Corydora<br />
* WanderingHero (QA)<br />
| servers =<br />
# Warfactory offical server <br> (31st July 2024 – August 8th 2024)<br />
# Minecraft Centralized Civilizations (MMC)<br />
| status = discontinued in favor of Warfactory 2<br />
}}<br />
'''Warfactory Legacy''' (Also know as WF or warfactory 1 or just warfactory) is a 1.12.2 pack created in summer 2024 by [[Mr.Norwood]]. Pack was accompanied by a factions' server that was active for a week in August 2024. Pack was a fork of nomifactory 1.7, which added a lot of balance adjustment and combat mods like Modern Warfare Cubed and MCheli 1.12.2. Reception was rather positive, however due to rushed development and bloated base, it had many exploits and stability issues. Due to those problems, it was abandoned soon after its release in favor of [[Warfactory 2]], which as of 24th of February 2025 is still in development.<br />
== Origin ==<br />
Pack was created due to dissatisfaction with the dire state of the modded faction servers. After IGoByLotsOfNames' departure from the event community due to the Supersymmetry event server burnout, a lot of new developers and hosts have attempted to replicate the success of the SuSy faction server. One of the major attempts were done by [[Hecuba]] with his [[ChaosTech]] event that occurred on May 18th 2024 and lasted until 22th of same month. [[Mr.Norwood]] excited with the development of a new faction server with a custom modpack (which was quite rare at that time), attempting at helping [[Hecuba]] with the modpack development and hosting of the event. However, [[Hecuba]] refused to listen to [[Mr.Norwood]], which has caused many common beginner mistakes, crashes, performance issues, duplication exploits. Hecuba also clearly has been biased towards the Albania team, in which [[IGoByLotsOfNames]] has played. Frustrated with lack of cooperation with [[Hecuba]] and clearly biased moderation, [[Norwood]] decided to gather a few known veterans from older events and set out to create his own modpack and host his own event. He notably partnered with [https://hexium.host/ Hexium Hosting], a startup hosting company which offered to help with hosting of Warfactory. <br />
==== Notable features ====<br />
Pack notably featured fork of Warforge by Flans Mod's, A mod which adds a pvp-friendly claim system, which allows for pvp balanced PVP battles. For combat, modpack featured Modern Warfare cubed, MCheli and its coremod: WFcore, adjusting armor values. Nomifactory 1.7 was used as a base for the pack, ensuring fleshed out, yet casual progression.<br />
===== Status =====<br />
The pack has been discontinued shortly after it's release, due to overbearing bloat, causing duplication glitches, instability, and general balance issues. It is still available for download [https://github.com/MisterNorwood/Warfactory-Legacy/releases here].</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=Warfactory_One&diff=123Warfactory One2025-02-24T02:40:15Z<p>Mr.Norwood: </p>
<hr />
<div>{{Modpack<br />
|name = Warfactory Legacy<br />
|image = [[File:Warfactory 1 Logo.png|thumb]]<br />
|release-date = 31 July 2024<br />
|devs = <br />
* [[Mr.Norwood]]<br />
* GrayGloo<br />
* Trainvoi<br />
* XorEight<br />
* Corydora<br />
* WanderingHero (QA)<br />
| servers =<br />
# Warfactory offical server <br> (31st July 2024 – August 8th 2024)<br />
# Minecraft Centralized Civilizations (MMC)<br />
| status = discontinued in favor of Warfactory 2<br />
}}<br />
'''Warfactory Legacy''' (Also know as WF or warfactory 1 or just warfactory) is a 1.12.2 pack created in summer 2024 by [[Mr.Norwood]]. Pack was accompanied by a factions' server that was active for a week in August 2024. Pack was a fork of nomifactory 1.7, which added a lot of balance adjustment and combat mods like Modern Warfare Cubed and MCheli 1.12.2. Reception was rather positive, however due to rushed development and bloated base, it had many exploits and stability issues. Due to those problems, it was abandoned soon after its release in favor of [[Warfactory 2]], which as of 24th of February 2025 is still in development.<br />
== Origin ==<br />
Pack was created due to dissatisfaction with the dire state of the modded faction servers. After IGoByLotsOfNames' departure from the event community due to the Supersymmetry event server burnout, a lot of new developers and hosts have attempted to replicate the success of the SuSy faction server. One of the major attempts were done by [[Hecuba]] with his [[ChaosTech]] event that occurred on May 18th 2024 and lasted until 22th of same month. [[Mr.Norwood]] excited with the development of a new faction server with a custom modpack (which was quite rare at that time), attempting at helping [[Hecuba]] with the modpack development and hosting of the event. However, [[Hecuba]] refused to listen to [[Mr.Norwood]], which has caused many common beginner mistakes, crashes, performance issues, duplication exploits. Hecuba also clearly has been biased towards the Albania team, in which [[IGoByLotsOfNames]] has played. Frustrated with lack of cooperation with [[Hecuba]] and clearly biased moderation, [[Norwood]] decided to gather a few known veterans from older events and set out to create his own modpack and host his own event. He notably partnered with [Hexium Hosting https://hexium.host/], a startup hosting company which offered to help with hosting of Warfactory. <br />
==== Notable features ====<br />
Pack notably featured fork of Warforge by Flans Mod's, A mod which adds a pvp-friendly claim system, which allows for pvp balanced PVP battles. For combat, modpack featured Modern Warfare cubed, MCheli and its coremod: WFcore, adjusting armor values. Nomifactory 1.7 was used as a base for the pack, ensuring fleshed out, yet casual progression.<br />
===== Status =====<br />
The pack has been discontinued shortly after it's release, due to overbearing bloat, causing duplication glitches, instability and general balance issues. It is still available for download [https://github.com/MisterNorwood/Warfactory-Legacy/releases here].</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=Warfactory_One&diff=122Warfactory One2025-02-24T02:39:45Z<p>Mr.Norwood: /* Origin */</p>
<hr />
<div>{{Modpack<br />
|name = Warfactory Legacy<br />
|image = [[File:Warfactory 1 Logo.png|thumb]]<br />
|release-date = "31 July 2024"<br />
|devs = <br />
* [[Mr.Norwood]]<br />
* GrayGloo<br />
* Trainvoi<br />
* XorEight<br />
* Corydora<br />
* WanderingHero (QA)<br />
| servers =<br />
# Warfactory offical server <br> (31st July 2024 – August 8th 2024)<br />
# Minecraft Centralized Civilizations (MMC)<br />
| status = discontinued in favor of Warfactory 2<br />
}}<br />
'''Warfactory Legacy''' (Also know as WF or warfactory 1 or just warfactory) is a 1.12.2 pack created in summer 2024 by [[Mr.Norwood]]. Pack was accompanied by a factions' server that was active for a week in August 2024. Pack was a fork of nomifactory 1.7, which added a lot of balance adjustment and combat mods like Modern Warfare Cubed and MCheli 1.12.2. Reception was rather positive, however due to rushed development and bloated base, it had many exploits and stability issues. Due to those problems, it was abandoned soon after its release in favor of [[Warfactory 2]], which as of 24th of February 2025 is still in development.<br />
== Origin ==<br />
Pack was created due to dissatisfaction with the dire state of the modded faction servers. After IGoByLotsOfNames' departure from the event community due to the Supersymmetry event server burnout, a lot of new developers and hosts have attempted to replicate the success of the SuSy faction server. One of the major attempts were done by [[Hecuba]] with his [[ChaosTech]] event that occurred on May 18th 2024 and lasted until 22th of same month. [[Mr.Norwood]] excited with the development of a new faction server with a custom modpack (which was quite rare at that time), attempting at helping [[Hecuba]] with the modpack development and hosting of the event. However, [[Hecuba]] refused to listen to [[Mr.Norwood]], which has caused many common beginner mistakes, crashes, performance issues, duplication exploits. Hecuba also clearly has been biased towards the Albania team, in which [[IGoByLotsOfNames]] has played. Frustrated with lack of cooperation with [[Hecuba]] and clearly biased moderation, [[Norwood]] decided to gather a few known veterans from older events and set out to create his own modpack and host his own event. He notably partnered with [Hexium Hosting https://hexium.host/], a startup hosting company which offered to help with hosting of Warfactory. <br />
==== Notable features ====<br />
Pack notably featured fork of Warforge by Flans Mod's, A mod which adds a pvp-friendly claim system, which allows for pvp balanced PVP battles. For combat, modpack featured Modern Warfare cubed, MCheli and its coremod: WFcore, adjusting armor values. Nomifactory 1.7 was used as a base for the pack, ensuring fleshed out, yet casual progression.<br />
===== Status =====<br />
The pack has been discontinued shortly after it's release, due to overbearing bloat, causing duplication glitches, instability and general balance issues. It is still available for download [https://github.com/MisterNorwood/Warfactory-Legacy/releases here].</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=Warfactory_One&diff=121Warfactory One2025-02-24T02:36:37Z<p>Mr.Norwood: </p>
<hr />
<div>{{Modpack<br />
|name = Warfactory Legacy<br />
|image = [[File:Warfactory 1 Logo.png|thumb]]<br />
|release-date = "31 July 2024"<br />
|devs = <br />
* [[MrNorwood]]<br />
* GrayGloo<br />
* Trainvoi<br />
* XorEight<br />
* Corydora<br />
* WanderingHero (QA)<br />
| servers =<br />
# Warfactory offical server <br> (31st July 2024 – August 8th 2024)<br />
# Minecraft Centralized Civilizations (MMC)<br />
| status = discontinued in favor of Warfactory 2<br />
}}<br />
'''Warfactory Legacy''' (Also know as WF or warfactory 1 or just warfactory) is a 1.12.2 pack created in summer 2024 by [[Mr.Norwood]]. Pack was accompanied by a factions' server that was active for a week in August 2024. Pack was a fork of nomifactory 1.7, which added a lot of balance adjustment and combat mods like Modern Warfare Cubed and MCheli 1.12.2. Reception was rather positive, however due to rushed development and bloated base, it had many exploits and stability issues. Due to those problems, it was abandoned soon after its release in favor of [[Warfactory 2]], which as of 24th of February 2025 is still in development.<br />
== Origin ==<br />
Pack was created due to dissatisfaction with the dire state of the modded faction servers. After IGoByLotsOfNames' departure from the event community due to the Supersymmetry event server burnout, a lot of new developers and hosts have attempted to replicate the success of the SuSy faction server. One of the major attempts were done by [[Hecuba]] with his [[ChaosTech]] event that occurred on May 18th 2024 and lasted until 22th of same month. [[Mr.Norwood]] excited with the development of a new faction server with a custom modpack (which was quite rare at that time), attempting at helping [[Hecuba]] with the modpack development and hosting of the event. However, [[Hecuba]] refused to listen to [[MrNorwood]], which has caused many common beginner mistakes, crashes, performance issues, duplication exploits. Hecuba also clearly has been biased towards the Albania team, in which [[IGoByLotsOfNames]] has played. Frustrated with lack of cooperation with [[Hecuba]] and clearly biased moderation, [[Norwood]] decided to gather a few known veterans from older events and decided to create his own modpack and host his own event. He notably partnered with [Hexium Hosting https://hexium.host/], a startup hosting company which offered to help with hosting of warfactory. <br />
==== Notable features ====<br />
Pack notably featured fork of Warforge by Flans Mod's, A mod which adds a pvp-friendly claim system, which allows for pvp balanced PVP battles. For combat, modpack featured Modern Warfare cubed, MCheli and its coremod: WFcore, adjusting armor values. Nomifactory 1.7 was used as a base for the pack, ensuring fleshed out, yet casual progression.<br />
===== Status =====<br />
The pack has been discontinued shortly after it's release, due to overbearing bloat, causing duplication glitches, instability and general balance issues. It is still available for download [https://github.com/MisterNorwood/Warfactory-Legacy/releases here].</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=Warfactory_One&diff=120Warfactory One2025-02-24T02:30:04Z<p>Mr.Norwood: </p>
<hr />
<div>{{Modpack<br />
|name = Warfactory Legacy<br />
|image = [[File:Warfactory 1 Logo.png|thumb]]<br />
|release-date = "31 July 2024"<br />
|devs = <br />
* MrNorwood<br />
* GrayGloo<br />
* Trainvoi<br />
* XorEight<br />
* Corydora<br />
* WanderingHero (QA)<br />
| servers =<br />
# Warfactory offical server <br> (31st July 2024 – August 8th 2024)<br />
# Minecraft Centralized Civilizations (MMC)<br />
| status = discontinued in favor of Warfactory 2<br />
}}<br />
'''Warfactory Legacy''' (Also know as WF or warfactory 1 or just warfactory) is a 1.12.2 pack created in summer 2024 by Mr.Norwood. Pack was accompanied by a factions' server that was active for a week in August 2024. Pack was a fork of nomifactory 1.7, which added a lot of banalce adjustment and combat mods like Modern Warfare Cubed and MCheli 1.12.2. Reception was rather positive, however due to rushed development and bloated base, it had many exploits and stability issues. Due to those problems, it was abandoned soon after its release in favor of Warfactory 2, which as of 24th of February 2025 is still in development.<br />
== Origin ==<br />
Pack was created due to dissatisfaction with the dire state of the modded faction servers. After IGoByLotsOfNames' departure from the event community due to the Supersymmetry event server burnout, a lot of new developers and hosts have attempted to replicate the success of the SuSy faction server. One of the major attempts were done by [[Hecuba]] with his [[ChaosTech]] event that occurred on May 18th 2024 and lasted until 22th of same month. Mr.Norwood excited with the development of a new faction server with a custom modpack (which was quite rare at that time), attempting at helping hecuba with the modpack development and hosting of the event. However, Hecuba refused to listen to MrNorwood, which has caused many common beginner mistakes, crashes, performance issues, duplication exploits. Hecuba also clearly has been biased towards the Albania team, in which IGoByLotsOfNames has played. Frustrated with lack of cooperation with Hecuba, Norwood decided to gather a few known veterans from older events and decided to create his own modpack and host his own event. He notably partnered with Hexium Hosting, a startup hosting company which offered to help with hosting of warfactory. <br />
==== Notable features ====<br />
Pack notably featured fork of Warforge by Flans Mod's, A mod which adds a pvp-friendly claim system, which allows for pvp balanced PVP battles. For combat, modpack featured Modern Warfare cubed, MCheli and its coremod: WFcore, adjusting armor values. Nomifactory 1.7 was used as a base for the pack, ensuring fleshed out, yet casual progression.<br />
===== Status =====<br />
The pack has been discontinued shortly after it's release, due to overbearing bloat, causing duplication glitches, instability and general balance issues. It is still available for download [[https://github.com/MisterNorwood/Warfactory-Legacy/releases | here]].</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=File:Warfactory_1_Logo.png&diff=119File:Warfactory 1 Logo.png2025-02-24T01:55:23Z<p>Mr.Norwood: </p>
<hr />
<div>Warfactory 1 logo</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=Warfactory_One&diff=118Warfactory One2025-02-24T01:51:48Z<p>Mr.Norwood: Created page with "'''Warfactory 1''' (Also know as WF or warfactory 1) is a 1.12.2 pack created in summer 2024 by Mr.Norwood. Pack was accompanied by a factions' server that was active for a week in August 2024. Pack was a fork of nomifactory 1.7, which added a lot of banalce adjustment and combat mods like Modern Warfare Cubed and MCheli 1.12.2. Reception was rather positive, however due to rushed development and bloated base, it had many exploits and stability issues. Due to those probl..."</p>
<hr />
<div>'''Warfactory 1''' (Also know as WF or warfactory 1) is a 1.12.2 pack created in summer 2024 by Mr.Norwood. Pack was accompanied by a factions' server that was active for a week in August 2024. Pack was a fork of nomifactory 1.7, which added a lot of banalce adjustment and combat mods like Modern Warfare Cubed and MCheli 1.12.2. Reception was rather positive, however due to rushed development and bloated base, it had many exploits and stability issues. Due to those problems, it was abandoned soon after its release in favor of Warfactory 2, which as of 24th of February 2025 is still in development.</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=Template:Modpack&diff=117Template:Modpack2025-02-24T01:48:57Z<p>Mr.Norwood: Infobox created with infobox builder.</p>
<hr />
<div><infobox><title source="title"><default>{{PAGENAME}}</default></title><image source="image"/><header>General information</header><data source="release-date"><label>Release date</label></data><data source="version"><label>Minecraft version</label><default>1.12.2</default></data><data source="devs"><label>Developer(s)</label></data><data source="servers"><label>Associated servers</label><default>None</default></data><data source="status"><label>Status</label><default>Active</default></data></infobox></div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=Main_Page&diff=62Main Page2025-02-22T20:30:44Z<p>Mr.Norwood: </p>
<hr />
<div>__NOTOC__<br />
[[File:Warfactory Logo.png|800px|center]]<br />
<br />
== Welcome to WarFactory Wiki! ==<br />
This independent wiki site serves as a place to document anything that has to do with the WarFactory modded faction server, modpack and any team lore that surrounds that space. It is a soft reboot of the infamous [https://greglore.miraheze.org/wiki/Main_Page Greglore wiki], which has become unmaintained and bloated with shitposts. Here is what you may find here:<br />
* Information about the WarFactory pack, as well as strategies, progression tips and anything that may come in handy to the player<br />
* Detailed write-ups of the faction events history<br />
* Biographies about key figures and teams (within the context of the modded faction space)<br />
* Any other information that can be considered important to the players in the modded faction space<br />
As of now, the site is only editable by a hand-picked selection of writers, but this may change as the page grows.<br />
<br />
=== Rules ===<br />
# <strong>No personal information / Doxxing</strong> – While generic information such as nationalities is fine, editors who spread personal information without consent of the person the page concerns will be banned.<br />
# <strong>Keep it on topic</strong> – We already have Greglore for lighthearted ironic posts, keep this on topic. While editors of those pages won't be banned in most cases, pages may be hidden, tagged as off-topic, or outright removed.<br />
<br />
=== Contact ===<br />
Our community is active on [https://discord.gg/eKFrH7P5ZR Discord]. If you need to contact the owner directly, please message user '''mr.norwood''' on discord.</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=MediaWiki:Common.css&diff=61MediaWiki:Common.css2025-02-22T20:24:31Z<p>Mr.Norwood: Blanked the page</p>
<hr />
<div></div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=MediaWiki:Common.css&diff=45MediaWiki:Common.css2025-02-20T23:17:58Z<p>Mr.Norwood: </p>
<hr />
<div>/* CSS placed here will be applied to all skins */<br />
:root {<br />
--lt-color-background-default: #37383e;<br />
--background-color-base: #37383e;<br />
--background-color-darker: #2b2b2f;<br />
--font-color: #fff;<br />
--color-progressive: #a4b9d6;<br />
--border-color-base: #b92727;<br />
}<br />
<br />
/* Change background color */<br />
body {<br />
background-color: #730c0c !important;<br />
color: var(--font-color) !important;<br />
}<br />
<br />
h1, h2, h3, h4, h5, h6, li {<br />
color: var(--font-color);<br />
}<br />
<br />
table {<br />
color: var(--font-color);<br />
background-color: var(--background-color-darker);<br />
}<br />
<br />
/* Set background image */<br />
body {<br />
/*background-image: url('/images/custom-background.png');*/<br />
background-size: cover;<br />
background-attachment: fixed;<br />
}<br />
#searchInput {<br />
background-color: var(--background-color-darker);<br />
color: #fff;<br />
border: none !important; <br />
}<br />
<br />
#searchInput:focus {<br />
outline: none; <br />
box-shadow: 0 0 5px rgba(0, 0, 0, 0.2); <br />
}<br />
<br />
.vector-button, button, input[type="submit"], input[type="button"] {<br />
background-color: var(--background-color-darker);<br />
color: #fff;<br />
border: none;<br />
}<br />
<br />
.vector-button:hover, button:hover, input[type="submit"]:hover, input[type="button"]:hover {<br />
background-color: var(--background-color);<br />
}</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=MediaWiki:Common.css&diff=44MediaWiki:Common.css2025-02-20T22:47:42Z<p>Mr.Norwood: </p>
<hr />
<div>/* CSS placed here will be applied to all skins */<br />
:root {<br />
--lt-color-background-default: #37383e;<br />
--background-color-base: #37383e;<br />
--background-color-darker: #2b2b2f;<br />
--font-color: #fff;<br />
--color-progressive: #a4b9d6;<br />
--border-color-base: #b92727;<br />
}<br />
<br />
/* Change background color */<br />
body {<br />
background-color: #730c0c !important;<br />
color: var(--font-color) !important;<br />
}<br />
<br />
h1, h2, h3, h4, h5, h6, li {<br />
color: var(--font-color);<br />
}<br />
<br />
/* Set background image */<br />
body {<br />
/*background-image: url('/images/custom-background.png');*/<br />
background-size: cover;<br />
background-attachment: fixed;<br />
}<br />
#searchInput {<br />
background-color: var(--background-color-darker);<br />
color: #fff;<br />
border: none !important; <br />
}<br />
<br />
#searchInput:focus {<br />
outline: none; <br />
box-shadow: 0 0 5px rgba(0, 0, 0, 0.2); <br />
}<br />
<br />
.vector-button, button, input[type="submit"], input[type="button"] {<br />
background-color: var(--background-color-darker);<br />
color: #fff;<br />
border: none;<br />
}<br />
<br />
.vector-button:hover, button:hover, input[type="submit"]:hover, input[type="button"]:hover {<br />
background-color: var(--background-color);<br />
}</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=MediaWiki:Common.css&diff=43MediaWiki:Common.css2025-02-20T22:12:39Z<p>Mr.Norwood: </p>
<hr />
<div>/* CSS placed here will be applied to all skins */<br />
:root {<br />
--lt-color-background-default: #37383e;<br />
--background-color-base: #37383e;<br />
--background-color-darker: #2b2b2f;<br />
--font-color: #fff;<br />
--color-progressive: #a4b9d6;<br />
--border-color-base: #b92727;<br />
}<br />
<br />
/* Change background color */<br />
body {<br />
background-color: #730c0c !important;<br />
color: var(--font-color) !important;<br />
}<br />
<br />
h1, h2, h3, h4, h5, h6 {<br />
color: var(--font-color);<br />
}<br />
<br />
/* Set background image */<br />
body {<br />
/*background-image: url('/images/custom-background.png');*/<br />
background-size: cover;<br />
background-attachment: fixed;<br />
}<br />
#searchInput {<br />
background-color: var(--background-color-darker);<br />
color: #fff;<br />
border: none !important; <br />
}<br />
<br />
#searchInput:focus {<br />
outline: none; <br />
box-shadow: 0 0 5px rgba(0, 0, 0, 0.2); <br />
}<br />
<br />
.vector-button, button, input[type="submit"], input[type="button"] {<br />
background-color: var(--background-color-darker);<br />
color: #fff;<br />
border: none;<br />
}<br />
<br />
.vector-button:hover, button:hover, input[type="submit"]:hover, input[type="button"]:hover {<br />
background-color: var(--background-color);<br />
}</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=MediaWiki:Common.css&diff=42MediaWiki:Common.css2025-02-20T22:11:01Z<p>Mr.Norwood: </p>
<hr />
<div>/* CSS placed here will be applied to all skins */<br />
:root {<br />
--lt-color-background-default: #37383e;<br />
--background-color-base: #37383e;<br />
--background-color-darker: #2b2b2f;<br />
--font-color: #fff;<br />
--color-progressive: #a4b9d6;<br />
--border-color-base: #b92727;<br />
}<br />
<br />
/* Change background color */<br />
body {<br />
background-color: #730c0c !important;<br />
color: var(--font-color) !important;<br />
}<br />
<br />
h1, h2, h3, h4, h5, h6 {<br />
color: var(--font-color);<br />
}<br />
<br />
/* Set background image */<br />
body {<br />
/*background-image: url('/images/custom-background.png');*/<br />
background-size: cover;<br />
background-attachment: fixed;<br />
}<br />
#searchInput {<br />
background-color: var(--background-color-darker);<br />
color: #fff;<br />
border: none !important; <br />
}<br />
<br />
#searchInput:focus {<br />
outline: none; <br />
box-shadow: 0 0 5px rgba(0, 0, 0, 0.2); <br />
}<br />
<br />
.vector-button {<br />
background-color: var(--background-color-darker);<br />
color: #fff;<br />
border: none;<br />
}<br />
<br />
.vector-button:hover {<br />
background-color: var(--background-color);<br />
}</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=MediaWiki:Common.css&diff=41MediaWiki:Common.css2025-02-20T22:08:44Z<p>Mr.Norwood: </p>
<hr />
<div>/* CSS placed here will be applied to all skins */<br />
:root {<br />
--lt-color-background-default: #37383e;<br />
--background-color-base: #37383e;<br />
--background-color-darker: #2b2b2f;<br />
--font-color: #fff;<br />
--color-progressive: #a4b9d6;<br />
--border-color-base: #b92727;<br />
}<br />
<br />
/* Change background color */<br />
body {<br />
background-color: #730c0c !important;<br />
color: var(--font-color) !important;<br />
}<br />
<br />
h1, h2, h3, h4, h5, h6 {<br />
color: var(--font-color);<br />
}<br />
<br />
/* Set background image */<br />
body {<br />
/*background-image: url('/images/custom-background.png');*/<br />
background-size: cover;<br />
background-attachment: fixed;<br />
}<br />
#searchInput {<br />
background-color: var(--background-color-darker);<br />
color: #fff;<br />
border: none !important; <br />
}<br />
<br />
#searchInput:focus {<br />
outline: none; /* Remove the blue focus outline */<br />
box-shadow: 0 0 5px rgba(0, 0, 0, 0.2); /* Optional: subtle shadow */<br />
}</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=MediaWiki:Common.css&diff=40MediaWiki:Common.css2025-02-20T22:07:30Z<p>Mr.Norwood: </p>
<hr />
<div>/* CSS placed here will be applied to all skins */<br />
:root {<br />
--lt-color-background-default: #37383e;<br />
--background-color-base: #37383e;<br />
--background-color-darker: #2b2b2f;<br />
--font-color: #fff;<br />
--color-progressive: #a4b9d6;<br />
--border-color-base: #b92727;<br />
}<br />
<br />
/* Change background color */<br />
body {<br />
background-color: #730c0c !important;<br />
color: var(--font-color) !important;<br />
}<br />
<br />
h1, h2, h3, h4, h5, h6 {<br />
color: var(--font-color);<br />
}<br />
<br />
/* Set background image */<br />
body {<br />
/*background-image: url('/images/custom-background.png');*/<br />
background-size: cover;<br />
background-attachment: fixed;<br />
}<br />
#searchInput {<br />
background-color: #f8f9fa; /* Change the background color */<br />
color: #333; /* Change the text color */<br />
border: none !important; /* Remove the border */<br />
padding: 6px; /* Adjust padding */<br />
border-radius: 5px; /* Optional: round the corners */<br />
}<br />
<br />
#searchInput:focus {<br />
outline: none; /* Remove the blue focus outline */<br />
box-shadow: 0 0 5px rgba(0, 0, 0, 0.2); /* Optional: subtle shadow */<br />
}</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=MediaWiki:Common.css&diff=39MediaWiki:Common.css2025-02-20T22:06:36Z<p>Mr.Norwood: </p>
<hr />
<div>/* CSS placed here will be applied to all skins */<br />
:root {<br />
--lt-color-background-default: #37383e;<br />
--background-color-base: #37383e;<br />
--background-color-darker: #2b2b2f;<br />
--font-color: #fff;<br />
--color-progressive: #a4b9d6;<br />
--border-color-base: #b92727;<br />
}<br />
<br />
/* Change background color */<br />
body {<br />
background-color: #730c0c !important;<br />
color: var(--font-color) !important;<br />
}<br />
<br />
h1, h2, h3, h4, h5, h6 {<br />
color: var(--font-color);<br />
}<br />
<br />
/* Set background image */<br />
body {<br />
/*background-image: url('/images/custom-background.png');*/<br />
background-size: cover;<br />
background-attachment: fixed;<br />
}<br />
#vector-typeahead-search-container {<br />
border: none;<br />
background-color: var(--background-color-darker);<br />
}</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=MediaWiki:Common.css&diff=38MediaWiki:Common.css2025-02-20T22:04:45Z<p>Mr.Norwood: </p>
<hr />
<div>/* CSS placed here will be applied to all skins */<br />
:root {<br />
--lt-color-background-default: #37383e;<br />
--background-color-base: #37383e;<br />
--background-color-darker: #2b2b2f;<br />
--font-color: #fff;<br />
--color-progressive: #a4b9d6;<br />
--border-color-base: #b92727;<br />
}<br />
<br />
#vector-appearance {<br />
display: none;<br />
}<br />
<br />
/* Change background color */<br />
body {<br />
background-color: #730c0c !important;<br />
color: var(--font-color) !important;<br />
}<br />
<br />
h1, h2, h3, h4, h5, h6 {<br />
color: var(--font-color);<br />
}<br />
<br />
/* Set background image */<br />
body {<br />
/*background-image: url('/images/custom-background.png');*/<br />
background-size: cover;<br />
background-attachment: fixed;<br />
}<br />
searchform {<br />
border: none;<br />
background-color: var(--background-color-darker);<br />
}</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=MediaWiki:Common.css&diff=37MediaWiki:Common.css2025-02-20T22:04:32Z<p>Mr.Norwood: </p>
<hr />
<div>/* CSS placed here will be applied to all skins */<br />
:root {<br />
--lt-color-background-default: #37383e;<br />
--background-color-base: #37383e;<br />
--background-color-darker: #2b2b2f;<br />
--font-color: #fff;<br />
--color-progressive: #a4b9d6;<br />
--border-color-base: #b92727;<br />
}<br />
<br />
#vector-appearance {<br />
display: none;<br />
}<br />
<br />
/* Change background color */<br />
body {<br />
background-color: #730c0c !important;<br />
color: var(--font-color) !important;<br />
}<br />
<br />
h1, h2, h3, h4, h5, h6 {<br />
color: var(--font-color);<br />
}<br />
<br />
/* Set background image */<br />
body {<br />
/*background-image: url('/images/custom-background.png');*/<br />
background-size: cover;<br />
background-attachment: fixed;<br />
}<br />
searchform {<br />
border: none;<br />
color: var(--background-color-darker);<br />
}</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=MediaWiki:Common.css&diff=36MediaWiki:Common.css2025-02-20T21:26:03Z<p>Mr.Norwood: </p>
<hr />
<div>/* CSS placed here will be applied to all skins */<br />
:root {<br />
--lt-color-background-default: #37383e;<br />
--background-color-base: #37383e;<br />
--background-color-darker: #2b2b2f;<br />
--font-color: #fff;<br />
--color-progressive: #a4b9d6;<br />
--border-color-base: #b92727;<br />
}<br />
<br />
#vector-appearance {<br />
display: none;<br />
}<br />
<br />
/* Change background color */<br />
body {<br />
background-color: #730c0c !important;<br />
color: var(--font-color) !important;<br />
}<br />
<br />
h1, h2, h3, h4, h5, h6 {<br />
color: var(--font-color);<br />
}<br />
<br />
/* Set background image */<br />
body {<br />
/*background-image: url('/images/custom-background.png');*/<br />
background-size: cover;<br />
background-attachment: fixed;<br />
}<br />
vector-typeahead-search-container {<br />
border: none;<br />
color: var(--background-color-darker);<br />
}</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=MediaWiki:Common.css&diff=35MediaWiki:Common.css2025-02-20T21:21:34Z<p>Mr.Norwood: </p>
<hr />
<div>/* CSS placed here will be applied to all skins */<br />
:root {<br />
--lt-color-background-default: #37383e;<br />
--background-color-base: #37383e;<br />
--background-color-darker: #2b2b2f;<br />
--font-color: #fff;<br />
--color-progressive: #a4b9d6;<br />
--border-color-base: #b92727;<br />
}<br />
<br />
#vector-appearance {<br />
display: none;<br />
}<br />
<br />
/* Change background color */<br />
body {<br />
background-color: #730c0c !important;<br />
color: var(--font-color) !important;<br />
}<br />
<br />
h1, h2, h3, h4, h5, h6 {<br />
color: var(--font-color);<br />
}<br />
<br />
/* Set background image */<br />
body {<br />
/*background-image: url('/images/custom-background.png');*/<br />
background-size: cover;<br />
background-attachment: fixed;<br />
}<br />
cdx-text-input__input {<br />
border: none;<br />
color: var(--background-color-darker);<br />
}</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=MediaWiki:Common.css&diff=34MediaWiki:Common.css2025-02-20T21:21:08Z<p>Mr.Norwood: </p>
<hr />
<div>/* CSS placed here will be applied to all skins */<br />
:root {<br />
--lt-color-background-default: #37383e;<br />
--background-color-base: #37383e;<br />
--background-color-darker: #2b2b2f;<br />
--font-color: #fff;<br />
--color-progressive: #a4b9d6;<br />
--border-color-base: #b92727;<br />
}<br />
<br />
#vector-appearance {<br />
display: none;<br />
}<br />
<br />
/* Change background color */<br />
body {<br />
background-color: #730c0c !important;<br />
color: var(--font-color) !important;<br />
}<br />
<br />
h1, h2, h3, h4, h5, h6 {<br />
color: var(--font-color);<br />
}<br />
<br />
/* Set background image */<br />
body {<br />
/*background-image: url('/images/custom-background.png');*/<br />
background-size: cover;<br />
background-attachment: fixed;<br />
}<br />
cdx-text-input__input {<br />
border: none;<br />
background-color: var(--background-color-darker);<br />
}</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=MediaWiki:Common.css&diff=33MediaWiki:Common.css2025-02-20T21:16:56Z<p>Mr.Norwood: </p>
<hr />
<div>/* CSS placed here will be applied to all skins */<br />
:root {<br />
--lt-color-background-default: #37383e;<br />
--background-color-base: #37383e;<br />
--font-color: #fff;<br />
--color-progressive: #a4b9d6;<br />
--border-color-base: #b92727;<br />
}<br />
<br />
#vector-appearance {<br />
display: none;<br />
}<br />
<br />
/* Change background color */<br />
body {<br />
background-color: #730c0c !important;<br />
color: var(--font-color) !important;<br />
}<br />
<br />
h1, h2, h3, h4, h5, h6 {<br />
color: var(--font-color);<br />
}<br />
<br />
/* Set background image */<br />
body {<br />
/*background-image: url('/images/custom-background.png');*/<br />
background-size: cover;<br />
background-attachment: fixed;<br />
}<br />
<br />
/* Hide some stuff on main page */<br />
.page-Main_page .toc {<br />
display: none;<br />
}</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=Main_Page&diff=32Main Page2025-02-20T21:03:33Z<p>Mr.Norwood: </p>
<hr />
<div>__NOTOC__<br />
[[File:Warfactory Logo.png|800px|frameless|center]]<br />
<br />
== Welcome to WarFactory Wiki! ==<br />
This independent wiki site serves as a place to document anything that has to do with the WarFactory modded faction server, modpack and any team lore that surrounds that space. It is a soft reboot of the infamous [https://greglore.miraheze.org/wiki/Main_Page Greglore wiki], which has become unmaintained and bloated with shitposts. Here is what you may find here:<br />
* Information about the WarFactory pack, as well as strategies, progression tips and anything that may come in handy to the player<br />
* Detailed write-ups of the faction events history<br />
* Biographies about key figures and teams (within the context of the modded faction space)<br />
* Any other information that can be considered important to the players in the modded faction space<br />
As of now, the site is only editable by a hand-picked selection of writers, but this may change as the page grows.<br />
<br />
=== Rules ===<br />
# <strong>No personal information / Doxxing</strong> – While generic information such as nationalities is fine, editors who spread personal information without consent of the person the page concerns will be banned.<br />
# <strong>Keep it on topic</strong> – We already have Greglore for lighthearted ironic posts, keep this on topic. While editors of those pages won't be banned in most cases, pages may be hidden, tagged as off-topic, or outright removed.<br />
<br />
=== Contact ===<br />
Our community is active on [https://discord.gg/eKFrH7P5ZR Discord]. If you need to contact the owner directly, please message user '''mr.norwood''' on discord.</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=MediaWiki:Common.css&diff=31MediaWiki:Common.css2025-02-20T20:11:55Z<p>Mr.Norwood: Undo revision 30 by Mr.Norwood (talk)</p>
<hr />
<div>/* CSS placed here will be applied to all skins */<br />
:root {<br />
--lt-color-background-default: #37383e;<br />
--background-color-base: #37383e;<br />
--font-color: #fff;<br />
--color-progressive: #a4b9d6;<br />
}<br />
<br />
#vector-appearance {<br />
display: none;<br />
}<br />
<br />
/* Change background color */<br />
body {<br />
background-color: #730c0c !important;<br />
color: var(--font-color) !important;<br />
}<br />
<br />
h1, h2, h3, h4, h5, h6 {<br />
color: var(--font-color);<br />
}<br />
<br />
/* Set background image */<br />
body {<br />
/*background-image: url('/images/custom-background.png');*/<br />
background-size: cover;<br />
background-attachment: fixed;<br />
}<br />
<br />
/* Hide some stuff on main page */<br />
.page-Main_page .toc {<br />
display: none;<br />
}</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=MediaWiki:Common.css&diff=30MediaWiki:Common.css2025-02-20T20:11:11Z<p>Mr.Norwood: </p>
<hr />
<div>/*<br />
* This is the CSS common to all desktop skins on en.Wikipedia.<br />
* Styling inside .mw-parser-output should generally use TemplateStyles.<br />
*/<br />
<br />
/* Minecraft font<br />
* [[File:Minecraft.woff2]] [[File:Minecraft.woff]]<br />
*/<br />
@font-face {<br />
font-family: Minecraft;<br />
src: url('/w/images/2/21/Minecraft.woff2') format('woff2'),<br />
url('/w/images/1/1a/Minecraft.woff') format('woff');<br />
}<br />
<br />
/* Reset italic styling set by user agent */<br />
cite,<br />
dfn {<br />
font-style: inherit;<br />
}<br />
<br />
/* Straight quote marks for <q> */<br />
q {<br />
quotes: '"' '"' "'" "'";<br />
}<br />
<br />
/* Avoid collision of blockquote with floating elements by swapping margin and padding */<br />
blockquote {<br />
overflow: hidden;<br />
margin: 1em 0;<br />
padding: 0 40px;<br />
}<br />
<br />
/* Consistent size for <small>, <sub> and <sup> */<br />
small {<br />
font-size: 85%;<br />
}<br />
<br />
.mw-body-content sub,<br />
.mw-body-content sup {<br />
font-size: 80%;<br />
}<br />
<br />
/* Same spacing for indented and unindented paragraphs on talk pages */<br />
.ns-talk .mw-body-content dd {<br />
margin-top: 0.4em;<br />
margin-bottom: 0.4em;<br />
}<br />
<br />
/* Reduce page jumps by hiding collapsed/dismissed content */<br />
.client-js .collapsible:not( .mw-made-collapsible).collapsed > tbody > tr:not(:first-child),<br />
<br />
/* Avoid FOUC/reflows on collapsed elements. */<br />
/* This copies MediaWiki's solution for T42812 to apply to innercollapse/outercollapse (T325115). */<br />
/* TODO: Use :is() selector at some reasonable future when support is good for Most Clients */<br />
/* Reference: https://gerrit.wikimedia.org/g/mediawiki/core/+/ecda06cb2aef55b77c4b4d7ecda492d634419ead/resources/src/jquery/jquery.makeCollapsible.styles.less#75 */<br />
.client-js .outercollapse .innercollapse.mw-collapsible:not( .mw-made-collapsible ) > p,<br />
.client-js .outercollapse .innercollapse.mw-collapsible:not( .mw-made-collapsible ) > table,<br />
.client-js .outercollapse .innercollapse.mw-collapsible:not( .mw-made-collapsible ) > thead + tbody,<br />
.client-js .outercollapse .innercollapse.mw-collapsible:not( .mw-made-collapsible ) tr:not( :first-child ),<br />
.client-js .outercollapse .innercollapse.mw-collapsible:not( .mw-made-collapsible ) .mw-collapsible-content,<br />
<br />
/* Hide charinsert base for those not using the gadget */<br />
#editpage-specialchars {<br />
display: none;<br />
}<br />
<br />
/* Make the list of references smaller<br />
* Keep in sync with Template:Refbegin/styles.css<br />
* And Template:Reflist/styles.css<br />
*/<br />
ol.references {<br />
font-size: 90%;<br />
margin-bottom: 0.5em;<br />
}<br />
<br />
/* Cite customizations for Parsoid<br />
* Once everything uses the one true parser these are just customizations<br />
*/<br />
span[ rel="mw:referencedBy" ] {<br />
counter-reset: mw-ref-linkback 0;<br />
}<br />
<br />
span[ rel='mw:referencedBy' ] > a::before {<br />
content: counter( mw-ref-linkback, lower-alpha );<br />
font-size: 80%;<br />
font-weight: bold;<br />
font-style: italic;<br />
}<br />
<br />
a[ rel="mw:referencedBy" ]::before {<br />
font-weight: bold;<br />
content: "^";<br />
}<br />
<br />
span[ rel="mw:referencedBy" ]::before {<br />
content: "^ ";<br />
}<br />
<br />
.mw-ref > a[data-mw-group=lower-alpha]::after {<br />
content: '[' counter( mw-Ref, lower-alpha ) ']';<br />
}<br />
<br />
.mw-ref > a[data-mw-group=upper-alpha]::after {<br />
content: '[' counter( mw-Ref, upper-alpha ) ']';<br />
}<br />
<br />
.mw-ref > a[data-mw-group=decimal]::after {<br />
content: '[' counter( mw-Ref, decimal ) ']';<br />
}<br />
<br />
.mw-ref > a[data-mw-group=lower-roman]::after {<br />
content: '[' counter( mw-Ref, lower-roman ) ']';<br />
}<br />
<br />
.mw-ref > a[data-mw-group=upper-roman]::after {<br />
content: '[' counter( mw-Ref, upper-roman ) ']';<br />
}<br />
<br />
.mw-ref > a[data-mw-group=lower-greek]::after {<br />
content: '[' counter( mw-Ref, lower-greek ) ']';<br />
}<br />
<br />
/* Styling for jQuery makeCollapsible, matching that of collapseButton */<br />
.mw-parser-output .mw-collapsible-toggle:not(.mw-ui-button) {<br />
font-weight: normal;<br />
padding-right: 0.2em;<br />
padding-left: 0.2em;<br />
}<br />
<br />
.mw-collapsible-leftside-toggle .mw-collapsible-toggle {<br />
/* @noflip */<br />
float: left;<br />
}<br />
<br />
/* Lists in wikitable data cells are always left-aligned */<br />
.wikitable td ul,<br />
.wikitable td ol,<br />
.wikitable td dl {<br />
/* @noflip */<br />
text-align: left;<br />
}<br />
<br />
/* Change the external link icon to a PDF icon for all PDF files */<br />
.mw-parser-output a[href$=".pdf"].external,<br />
.mw-parser-output a[href*=".pdf?"].external,<br />
.mw-parser-output a[href*=".pdf#"].external,<br />
.mw-parser-output a[href$=".PDF"].external,<br />
.mw-parser-output a[href*=".PDF?"].external,<br />
.mw-parser-output a[href*=".PDF#"].external {<br />
background: url("//upload.wikimedia.org/wikipedia/commons/4/4d/Icon_pdf_file.png") no-repeat right;<br />
/* @noflip */<br />
padding: 8px 18px 8px 0;<br />
}<br />
<br />
/* System messages styled similarly to fmbox */<br />
/* for .mw-warning-with-logexcerpt, behavior of this line differs between<br />
* the edit-protected notice and the special:Contribs for blocked users<br />
* The latter has specificity of 3 classes so we have to triple up here.<br />
*/<br />
.mw-warning-with-logexcerpt.mw-warning-with-logexcerpt.mw-warning-with-logexcerpt,<br />
div.mw-lag-warn-high,<br />
div.mw-cascadeprotectedwarning,<br />
div#mw-protect-cascadeon {<br />
clear: both;<br />
margin: 0.2em 0;<br />
border: 1px solid #bb7070;<br />
background-color: #ffdbdb;<br />
padding: 0.25em 0.9em;<br />
box-sizing: border-box;<br />
}<br />
<br />
/* default colors for partial block message */<br />
/* gotta get over the hump introduced by the triple class above */<br />
.mw-contributions-blocked-notice-partial .mw-warning-with-logexcerpt.mw-warning-with-logexcerpt {<br />
border-color: #fc3;<br />
background-color: #fef6e7;<br />
}<br />
<br />
/* Minimum thumb width */<br />
figure[typeof~='mw:File/Thumb'],<br />
figure[typeof~='mw:File/Frame'],<br />
.thumbinner {<br />
min-width: 100px;<br />
}<br />
<br />
/* Prevent floating boxes from overlapping any category listings,<br />
file histories, edit previews, and edit [Show changes] views. */<br />
#mw-subcategories,<br />
#mw-pages,<br />
#mw-category-media,<br />
#filehistory,<br />
#wikiPreview,<br />
#wikiDiff {<br />
clear: both;<br />
}<br />
<br />
/* Styling for tags in changes pages */<br />
.mw-tag-markers {<br />
font-style: italic;<br />
font-size: 90%;<br />
}<br />
<br />
/* Hide stuff meant for accounts with special permissions. Made visible again in<br />
[[MediaWiki:Group-checkuser.css]], [[MediaWiki:Group-sysop.css]], [[MediaWiki:Group-abusefilter.css]],<br />
[[MediaWiki:Group-abusefilter-helper.css]], [[MediaWiki:Group-patroller.css]],<br />
[[MediaWiki:Group-templateeditor.css]], [[MediaWiki:Group-extendedmover.css]],<br />
[[MediaWiki:Group-extendedconfirmed.css]], and [[Mediawiki:Group-autoconfirmed.css]]. */<br />
.checkuser-show,<br />
.sysop-show,<br />
.abusefilter-show,<br />
.abusefilter-helper-show,<br />
.patroller-show,<br />
.templateeditor-show,<br />
.extendedmover-show,<br />
.extendedconfirmed-show,<br />
.autoconfirmed-show,<br />
.user-show {<br />
display: none;<br />
}<br />
<br />
/* Hide the redlink generated by {{Editnotice}},<br />
this overrides the ".sysop-show { display: none; }" above that applies<br />
to the same link as well. See [[phab:T45013]]<br />
<br />
Hide the images in editnotices to keep them readable in VE view.<br />
Long term, editnotices should become a core feature so that they can be designed responsive. */<br />
.ve-ui-mwNoticesPopupTool-item .editnotice-redlink,<br />
.ve-ui-mwNoticesPopupTool-item .mbox-image,<br />
.ve-ui-mwNoticesPopupTool-item .mbox-imageright {<br />
display: none !important;<br />
}<br />
<br />
/* Remove bullets when there are multiple edit page warnings */<br />
ul.permissions-errors {<br />
margin: 0;<br />
}<br />
<br />
ul.permissions-errors > li {<br />
list-style: none;<br />
}<br />
<br />
/* larger inline math */<br />
span.mwe-math-mathml-inline {<br />
font-size: 118%;<br />
}<br />
<br />
/* Make <math display="block"> be left aligned with one space indent for <br />
* compatibility with style conventions<br />
*/<br />
.mwe-math-fallback-image-display,<br />
.mwe-math-mathml-display {<br />
margin-left: 1.6em !important;<br />
margin-top: 0.6em;<br />
margin-bottom: 0.6em;<br />
}<br />
<br />
.mwe-math-mathml-display math {<br />
display: inline;<br />
}<br />
<br />
@media screen {<br />
/* Put a chequered background behind images, only visible if they have transparency,<br />
* except on main, user, and portal namespaces<br />
*/<br />
body:not(.ns-0):not(.ns-2):not(.ns-100) .gallerybox .thumb img {<br />
background: #fff url(//upload.wikimedia.org/wikipedia/commons/5/5d/Checker-16x16.png) repeat;<br />
}<br />
<br />
/* Display "From Wikipedia, the free encyclopedia" in skins that support it,<br />
do not apply to print mode */<br />
#siteSub {<br />
display: block;<br />
}<br />
}<br />
<br />
/* Hide FlaggedRevs notice UI when there are no pending changes */<br />
.flaggedrevs_draft_synced,<br />
.flaggedrevs_stable_synced,<br />
/* "Temporary" to remove links in sidebar T255381 */<br />
/*#t-upload,*/<br />
/* Hide broken download box on Special:Book pending T285400 */<br />
.mw-special-Book #coll-downloadbox {<br />
display: none;<br />
}<br />
<br />
.img-pixelated,<br />
.img-pixelated img,<br />
.cdx-thumbnail__image,<br />
.mw-datatable img {<br />
image-rendering: pixelated;<br />
}<br />
<br />
.img-512 img {<br />
width: 512px;<br />
height: unset;<br />
}<br />
.img-256 img {<br />
width: 256px;<br />
height: unset;<br />
}<br />
.img-128 img {<br />
width: 128px;<br />
height: unset;<br />
}<br />
.img-64 img {<br />
width: 64px;<br />
height: unset;<br />
}<br />
<br />
/*<br />
* BELOW HERE THERE BE SOONTOBE TEMPLATESTYLES THINGS;<br />
* SEE [[MediaWiki talk:Common.css/to do]]<br />
*/<br />
<br />
/* Infobox template style */<br />
.infobox {<br />
border: 1px solid #a2a9b1;<br />
border-spacing: 3px;<br />
background-color: #f8f9fa;<br />
color: black;<br />
/* @noflip */<br />
margin: 0.5em 0 0.5em 1em;<br />
padding: 0.25em;<br />
/* @noflip */<br />
float: right;<br />
/* @noflip */<br />
clear: right;<br />
font-size: 88%;<br />
line-height: 1.5em;<br />
width: 22em;<br />
}<br />
<br />
.infobox-header,<br />
.infobox-label,<br />
.infobox-above,<br />
.infobox-full-data,<br />
.infobox-data,<br />
.infobox-below,<br />
.infobox-subheader,<br />
.infobox-image,<br />
.infobox-navbar,<br />
/* Remove element selector when every .infobox thing is using the standard module/templates */<br />
.infobox th,<br />
.infobox td {<br />
vertical-align: top;<br />
}<br />
<br />
.infobox-label,<br />
.infobox-data,<br />
/* Remove element selector when every .infobox thing is using the standard module/templates */<br />
.infobox th,<br />
.infobox td {<br />
/* @noflip */<br />
text-align: left;<br />
}<br />
<br />
/* Remove .infobox when element selectors above are removed */<br />
.infobox .infobox-above,<br />
.infobox .infobox-title,<br />
/* Remove element selector when every .infobox thing is using the standard module/templates */<br />
.infobox caption {<br />
font-size: 125%;<br />
font-weight: bold;<br />
text-align: center;<br />
}<br />
<br />
.infobox-title,<br />
/* Remove element selector when every .infobox thing is using the standard module/templates */<br />
.infobox caption {<br />
padding: 0.2em;<br />
}<br />
<br />
/* Remove .infobox when element selectors above are removed */<br />
.infobox .infobox-header,<br />
.infobox .infobox-subheader,<br />
.infobox .infobox-image,<br />
.infobox .infobox-full-data,<br />
.infobox .infobox-below {<br />
text-align: center;<br />
}<br />
<br />
/* Remove .infobox when element selectors above are removed */<br />
.infobox .infobox-navbar {<br />
/* @noflip */<br />
text-align: right;<br />
}<br />
<br />
/* Normal font styling for wikitable row headers with scope="row" tag */<br />
.wikitable.plainrowheaders th[scope=row],<br />
.wikitable.plainrowheaders th[scope=rowgroup] {<br />
font-weight: normal;<br />
/* @noflip */<br />
text-align: left;<br />
}<br />
<br />
/* Remove underlines from certain links */<br />
.nounderlines a,<br />
.IPA a:link,<br />
.IPA a:visited {<br />
text-decoration: none !important;<br />
}<br />
<br />
/* Prevent line breaks in silly places where desired (nowrap)<br />
and links when we don't want them to (nowraplinks a) */<br />
.nowrap,<br />
.nowraplinks a {<br />
white-space: nowrap;<br />
}<br />
<br />
/* But allow wrapping where desired: */<br />
.wrap,<br />
.wraplinks a {<br />
white-space: normal;<br />
}<br />
<br />
/* texhtml class for inline math (based on generic times-serif class) */<br />
span.texhtml {<br />
font-family: "Nimbus Roman No9 L", "Times New Roman", Times, serif;<br />
font-size: 118%;<br />
line-height: 1;<br />
white-space: nowrap;<br />
/* Force tabular and lining display for texhtml */<br />
font-variant-numeric: lining-nums tabular-nums;<br />
font-kerning: none;<br />
}<br />
<br />
span.texhtml span.texhtml {<br />
font-size: 100%;<br />
}<br />
<br />
@media screen {<br />
.nochecker .gallerybox .thumb img {<br />
background-image: none;<br />
}<br />
}<br />
<br />
/* Generic Minecraft interface styling */<br />
.mcui {<br />
display: inline-block;<br />
position: relative;<br />
background-color: #C6C6C6;<br />
color: black;<br />
border: 2px solid;<br />
border-color: #DBDBDB #5B5B5B #5B5B5B #DBDBDB;<br />
padding: 6px;<br />
text-align: left;<br />
white-space: nowrap;<br />
vertical-align: bottom;<br />
image-rendering: pixelated;<br />
}<br />
.wikitable .mcui {<br />
width: 100%;<br />
box-sizing: border-box;<br />
text-align: center;<br />
}<br />
<br />
.mcui-input, .mcui-output {<br />
display: inline-block;<br />
vertical-align: middle;<br />
}<br />
.mcui-input {<br />
text-align: right;<br />
}<br />
<br />
.mcui-arrow {<br />
margin:0 16px;<br />
position: relative;<br />
display: inline-block;<br />
vertical-align: middle;<br />
}<br />
.mcui-arrow-overlay {<br />
position: absolute;<br />
left: 0;<br />
overflow: hidden;<br />
width: 0;<br />
}<br />
<br />
.mcui-action {<br />
position: relative;<br />
display: inline-block;<br />
vertical-align: middle;<br />
}<br />
.mcui-action-overlay {<br />
animation: 3.6s steps(18) infinite mcui-height;<br />
position: absolute;<br />
left: 0;<br />
overflow: hidden;<br />
height: 0;<br />
}<br />
<br />
.mcui-info {<br />
display: block;<br />
text-align: center;<br />
font-family: Minecraft, sans-serif !important;<br />
height: 0; /* Info shouldn't cause reflow */<br />
}<br />
<br />
.mcui-arrow-slot .invslot {<br />
margin: auto;<br />
display: block;<br />
}<br />
<br />
.mcui-arrow-slot:first-child {<br />
margin-bottom: 4px;<br />
}<br />
<br />
.mcui-arrow-slot:last-child {<br />
margin-top: 4px;<br />
}<br />
<br />
.mcui-inter {<br />
display: inline-block;<br />
vertical-align: middle;<br />
}<br />
<br />
.mcui-anvil .mcui-inter {<br />
vertical-align: top;<br />
}<br />
<br />
.mcui-animated > :not(.mcui-animated-active) {<br />
display: none;<br />
}<br />
<br />
.mcui-icon {<br />
position: absolute;<br />
top: 0;<br />
right: 6px;<br />
cursor: help;<br />
}<br />
<br />
@keyframes mcui-width {<br />
0% {<br />
width: 0%;<br />
}<br />
80% {<br />
width: 100%;<br />
}<br />
100% {<br />
width: 100%;<br />
}<br />
}<br />
<br />
@keyframes mcui-height {<br />
0% {<br />
height: 0%;<br />
}<br />
80% {<br />
height: 100%;<br />
}<br />
100% {<br />
height: 100%;<br />
}<br />
}<br />
<br />
<br />
/* [[Template:Inventory slot]] */<br />
.invslot,<br />
.fluidslot-id,<br />
.fluidslot-tank,<br />
.crucibleslot {<br />
position: relative;<br />
display: inline-block;<br />
background: #8B8B8B no-repeat center center / 32px 32px;<br />
border: 2px solid;<br />
border-color: #373737 #FFF #FFF #373737;<br />
width: 32px;<br />
height: 32px;<br />
font-size: 16px;<br />
line-height: 1;<br />
text-align: left;<br />
vertical-align: bottom;<br />
}<br />
.invslot::before,<br />
.invslot::after {<br />
content: "";<br />
position: absolute;<br />
background-color: #8B8B8B;<br />
height: 2px;<br />
width: 2px;<br />
/*pointer-events: none;*/<br />
}<br />
.invslot::before {<br />
bottom: -2px;<br />
left: -2px;<br />
}<br />
.invslot::after {<br />
top: -2px;<br />
right: -2px;<br />
}<br />
<br />
.invslot-item {<br />
position: relative;<br />
display: block;<br />
margin: -2px;<br />
padding: 2px;<br />
}<br />
<br />
.invslot-large {<br />
padding: 8px;<br />
}<br />
<br />
.invslot-stacksize {<br />
position: absolute;<br />
right: 0;<br />
bottom: 0;<br />
font-family: Minecraft, sans-serif !important;<br />
font-weight: normal !important;<br />
color: #FFF !important;<br />
text-shadow: 2px 2px 0 #3F3F3F;<br />
filter: dropshadow(color=#3F3F3F, offx=2, offy=2);<br />
z-index: 2;<br />
}<br />
<br />
.invslot-highlight {<br />
position: absolute;<br />
left: 0;<br />
right: 0;<br />
top: 0;<br />
bottom: 0;<br />
background-color: rgba(255, 255, 255, 0.5);<br />
pointer-events: none;<br />
display: none;<br />
}<br />
<br />
.invslot:not(.invslot-disable-highlight):hover .invslot-highlight,<br />
.fluidslot-id:not(.invslot-disable-highlight):hover .invslot-highlight {<br />
display: block;<br />
}<br />
<br />
<br />
/* Fluid slots, like inventory slots, but wet */<br />
.fluidslot-id {<br />
background: none;<br />
border-color: transparent;<br />
}<br />
<br />
.fluidslot-tank,<br />
.crucibleslot {<br />
width: 104px;<br />
}<br />
<br />
.fluidslot-fluid,<br />
.crucibleslot-fluid {<br />
display: block;<br />
height: 100%;<br />
cursor: default;<br />
background-blend-mode: multiply;<br />
background-size: 50%;<br />
animation: fluid-translate 4s linear infinite;<br />
}<br />
<br />
.fluidslot-fluid {<br />
background-image: url("https://nucleartech.wiki/w/images/e/ec/Tank_Fluid.png");<br />
}<br />
<br />
.crucibleslot-fluid {<br />
background-image: url("https://nucleartech.wiki/w/images/d/d3/Crucible_Fluid.png");<br />
}<br />
<br />
@keyframes fluid-translate {<br />
0% {<br />
background-position-x: 0%;<br />
}<br />
100% {<br />
background-position-x: 100%;<br />
}<br />
}<br />
<br />
.fluidslot-fluid::after {<br />
content: '';<br />
display: block;<br />
position: absolute;<br />
width: 100%;<br />
height: 100%;<br />
}<br />
<br />
.fluidslot-tank::after {<br />
content: '';<br />
background-image: url(/w/images/a/a4/Tank_Marks.png);<br />
position: absolute;<br />
top: 0;<br />
bottom: 0;<br />
left: 0;<br />
right: 0;<br />
pointer-events: none;<br />
}<br />
<br />
.fluidslot-vertical {<br />
display: inline-block;<br />
width: 36px;<br />
height: 144px;<br />
}<br />
<br />
.fluidslot-vertical .fluidslot-id {<br />
display: block;<br />
}<br />
<br />
.fluidslot-vertical .invslot-stacksize {<br />
right: unset;<br />
}<br />
<br />
.fluidslot-vertical .fluidslot-tank {<br />
transform: translate(-36px, 36px) rotate(-90deg);<br />
border-color: #373737 #373737 #FFF #FFF;<br />
}<br />
<br />
<br />
/* Styling for minecraft style tooltip */<br />
#minetip-tooltip {<br />
position: fixed;<br />
top: 0;<br />
left: 0;<br />
background-color: #100010;<br />
background-color: rgba(16, 0, 16, 0.94);<br />
padding: 0.375em;<br />
font-family: Minecraft, sans-serif;<br />
font-size: 16px;<br />
word-spacing: 4px;<br />
white-space: nowrap;<br />
line-height: 1.25em;<br />
margin: 0.125em 0.25em;<br />
pointer-events: none;<br />
z-index: 9999;<br />
color: white;<br />
}<br />
<br />
#minetip-tooltip::before {<br />
content: "";<br />
position: absolute;<br />
top: 0.125em;<br />
right: -0.125em;<br />
bottom: 0.125em;<br />
left: -0.125em;<br />
border: 0.15em solid #100010;<br />
border-style: none solid;<br />
border-color: rgba(16, 0, 16, 0.94);<br />
}<br />
<br />
#minetip-tooltip::after {<br />
content: "";<br />
position: absolute;<br />
top: 0.125em;<br />
right: 0;<br />
bottom: 0.125em;<br />
left: 0;<br />
border: 0.125em solid #2D0A63;<br />
border-image: -webkit-linear-gradient(rgba(80, 0, 255, 0.31), rgba(40, 0, 127, 0.31)) 1;<br />
border-image: linear-gradient(rgba(80, 0, 255, 0.31), rgba(40, 0, 127, 0.31)) 1;<br />
}<br />
<br />
#minetip-tooltip > .description,<br />
#minetip-tooltip > .minetip-description {<br />
display: block;<br />
margin-top: 0.25em;<br />
}<br />
<br />
/*<br />
* Calculation container<br />
*/<br />
.calculator {<br />
border: 1px solid #3d3e40;<br />
display: flex;<br />
}<br />
@media only screen and (max-width: 767px) {<br />
.calculator {<br />
flex-direction: column;<br />
}<br />
}<br />
<br />
.calculator-input, .calculator-output {<br />
padding: 1em;<br />
flex: 1;<br />
}<br />
<br />
.calculator-output {<br />
display: flex;<br />
}<br />
<br />
.calculator-output code {<br />
font-size: 2em;<br />
margin: auto;<br />
}<br />
<br />
.calculator-input-field + .calculator-input-field {<br />
margin-top: 1em;<br />
}<br />
<br />
<br />
/* Put anything you mean to be a sitewide addition above the TemplateStyles<br />
* comment above.<br />
*/</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=MediaWiki:Common.css&diff=29MediaWiki:Common.css2025-02-20T20:04:13Z<p>Mr.Norwood: </p>
<hr />
<div>/* CSS placed here will be applied to all skins */<br />
:root {<br />
--lt-color-background-default: #37383e;<br />
--background-color-base: #37383e;<br />
--font-color: #fff;<br />
--color-progressive: #a4b9d6;<br />
}<br />
<br />
#vector-appearance {<br />
display: none;<br />
}<br />
<br />
/* Change background color */<br />
body {<br />
background-color: #730c0c !important;<br />
color: var(--font-color) !important;<br />
}<br />
<br />
h1, h2, h3, h4, h5, h6 {<br />
color: var(--font-color);<br />
}<br />
<br />
/* Set background image */<br />
body {<br />
/*background-image: url('/images/custom-background.png');*/<br />
background-size: cover;<br />
background-attachment: fixed;<br />
}<br />
<br />
/* Hide some stuff on main page */<br />
.page-Main_page .toc {<br />
display: none;<br />
}</div>Mr.Norwoodhttp://wiki.warfactory.co/index.php?title=MediaWiki:Common.css&diff=28MediaWiki:Common.css2025-02-20T20:02:25Z<p>Mr.Norwood: </p>
<hr />
<div>/* CSS placed here will be applied to all skins */<br />
:root {<br />
--lt-color-background-default: #37383e;<br />
--background-color-base: #37383e;<br />
--font-color: #fff;<br />
--color-progressive: #a4b9d6;<br />
}<br />
<br />
#p-cactions {<br />
display: none;<br />
}<br />
<br />
/* Change background color */<br />
body {<br />
background-color: #730c0c !important;<br />
color: var(--font-color) !important;<br />
}<br />
<br />
h1, h2, h3, h4, h5, h6 {<br />
color: var(--font-color);<br />
}<br />
<br />
/* Set background image */<br />
body {<br />
/*background-image: url('/images/custom-background.png');*/<br />
background-size: cover;<br />
background-attachment: fixed;<br />
}<br />
<br />
/* Hide some stuff on main page */<br />
.page-Main_page .toc {<br />
display: none;<br />
}</div>Mr.Norwood