Using Mathematical Expressions for Skill Pages

Haven't seen you here in a while. Welcome back.

Originally, this was a plan to minimize the amount of editing when it came to updating these skills. After switching to this new format, the amount of editing required to update a recently patched (updated) skill takes up to 5 minutes on average compared to the hours it took before updating each individual value. But I understand what you are suggesting.

I was planning on making a widget that included all levels of the skill, but I encountered a few problems.

Ideally, it would display something similar to the per level Statistic growth as shown on the League of Legends typical champion page. When given a mathematical expression, it would solve the for the values provided, either by a for loop or by being given two values as a arguments stored as variables. However, a few problems arose.

• I couldn't figure out how MediaWiki stores integers as values for parameters to be plugged into an upper limit for the widget or the #expr expression.
• Certain skills such like  Aerial Fire and  Lesser Spirit: Stalker had set levels to which which bonuses were unlocked. I wasn't sure if the numbers were based off of the typical rounding numbers rule or by ceil or floor calculations. Additionally, other skills like  G-0 Battleroid doesn't seem to have a consistent growth pattern for these attributes (the Lock-On Missile Targets).
• Other skills like  Core Shield,  Energy Shield, and  Light of Divinity do not have a consistent growth pattern when it comes to Shield Health. Most skills tend to follow some kind of arithmetic sequence, and are rarely geometric. These ones are a bit different. I viewed the growth pattern through other sequences, Fibonacci, Triangular Numbers, and Partial Sums, but they do not yield the expressions I required.

Eventually, due to these problems (mostly the latter), I just figured we just write down the expressions.

Perhaps we can meet somewhere in the middle. We could display three parts: n, Min Lv. (Base Lv 1), Max Lv. (According to Lv. Cap) and default to either n or Min Lv. We could separate the values by tabs, and manually input the Min/Max Lv. values. However, I'm worried that the SkillGrowth section may become a bit too cluttered.

Altair (talk)