Search results

issue for i, area in pairs(AreaData.combatAreas) do if area.name == name then return processArea(area, i, 'combat') end end for i, area in pairs(AreaData

local pm = require("Module:CombatAreas/AreaTables") local p = {} local AreaData = mw.loadData('Module:CombatAreas/data') local Constants = require('Module:Constants')

local areas = GameData.sortByOrderTable(GameData.rawData.combatAreas, GameData.rawData.combatAreaDisplayOrder) for i, area in ipairs(areas) do result

with user added descriptions, and detects if the underlying data has changed. If the data has not changed or if the page does not contain any user made

pages The Dungeon Template, Slayer Area Template, and Combat Area Template on Dungeon, Slayer Area, and Combat Area pages respectively The Prayer Template

each non-combat Skill page. Toggle Combat Minibar - Default: Enabled If enabled, the Combat Minibar will display upon entering Combat. Display Combat Minibar

accidental save data loss when loading these saves without the expansions installed. If you still wish to load these saves at risk of data loss, you may

Data is pulled from Module:GameData/data

Artisan Skills should now update the information panel dynamically when game data changes (Like quantities and percentages). Astrology now correctly updates

frame local area = p.getArea(areaName) if area == nil then return Shared.printError('No area named "' .. areaName .. '" exists in the data module') end

the Familiars are classed as "Combat Familiars" and provide general benefits to assist within Combat. On top of this, Combat Familiars also have the ability

local ShopData = mw.loadData('Module:Shop/data') local ConstantData = mw.loadData('Module:Constants/data') -- Data instead of Module:CombatAreas to avoid

accidental save data loss when loading these saves without the expansions installed. If you still wish to load these saves at risk of data loss, you may

cannot be encountered normally, as it does not appear within any Combat Area, Slayer Area, or Dungeon. Instead this monster may only be encountered randomly

over the cumulative values reported in the sections below. A link to the raw data used for the calculations in this section can be found here. Like before

successful, the game data should appear within the console Copy the game data & update Module:GameData/data and Module:GameData/data2 accordingly

:GameData/data') local GameData2 = mw.loadJsonData('Module:GameData/data2') -- Combine data into a single object local GameData = {} for _, data in ipairs({GameData1

ameData/data') local GameData2 = mw.loadData('Module:Sandbox/GameData/data2') -- Combine data into a single object local GameData = {} for _, data in ipairs({GameData1

require('Module:GameData') local Icons = require('Module:Icons') local areaDataKeys = { 'combatAreas', 'dungeons', 'slayerAreas' } -- Compute combat pet sources

local p = {} local ItemData = mw.loadData('Module:Sandbox/Items/data') local SkillData = mw.loadData('Module:Sandbox/Skills/data') local Constants = r