You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
40 lines
2.7 KiB
Plaintext
40 lines
2.7 KiB
Plaintext
<!--201210,201029-->
|
|
<h1>tidying up my skill phases </h1>
|
|
november 12, 2020<br>
|
|
#programming #skills<br>
|
|
<br>
|
|
In Godot Engine, you can call methods from a parent class by prefixing it with a period (.). So to access the <code>move()</code> method from a parent, call <code>.move()</code>. This is called a <b>super method</b>. <br>
|
|
<br>
|
|
Being called super doesn't mean there isn't a better way, though. I used to use super methods to build customs skills in blessfrey, but subfunctions is tidier. <br>
|
|
<br>
|
|
(Just so you know, blessfrey's skills have a number of phases of effects that must happen in order: skill press > activation > initial phase > main phase > end phase > cooldown.) <br>
|
|
<br>
|
|
<br>
|
|
<h2>the old way </h2><br>
|
|
Initially, I used super methods to give each phase custom effects and call the next phase. This was messy. If I ever redesigned the flow of the skill phases, I'd have to edit every single skill script. It also causes a lot of repetitive code in the individual skill scripts while the base script is tiny. The one-time script being the small one is no fair. <br>
|
|
<br><center>
|
|
<img src="/static/img/ent/supermethod_old.png" alt="(image: GDscript code using old method)"><br>
|
|
</center>
|
|
(You can see the old method's code on <a href="https://pastebin.com/DDu1Q7Q6">Pastebin</a>.)
|
|
<br>
|
|
<br>
|
|
<h2>the new way </h2><br>
|
|
<br>
|
|
Instead, I can bring all the repetitive steps into the base class, sandwiching in a subfunction where the custom effects would take place. Now I only need to add what makes my skill unique inside the subfunction. <br>
|
|
<br>
|
|
I named the subfunction after its main function and added an underscore to the front. So in the base script, I fit <code>_functionality(user, action_target)</code> into <code>functionality(user, action_target)</code>. Then the individual skill scripts only need the subfunction, none of the other repetitive code from before. The subfunction is empty in the base class and filled with unique code in the child classes. Since skills inherit, the unique <code>_functionality</code> subfunction will be called automatically from the base script's <code>functionality</code>. <br>
|
|
<br>
|
|
<center>
|
|
<a target="_blank" href="/static/img/ent/supermethod_old.png">
|
|
<img src="/static/img/ent/supermethod_new.png" alt="(image: GDscript code using new method)" width="500" height="355.36">
|
|
</a>
|
|
</center>
|
|
(You can see the new method's code on <a href="https://pastebin.com/teeYn9jP">Pastebin</a>.)
|
|
<br>
|
|
<br>
|
|
<h2>problem solved! </h2><br>
|
|
<br>
|
|
The base script holds all the lengthy code in one place, while I only need to write the unique effects in all the hundreds of skill scripts. That saves me time making, refactoring, and maintaining skills. Yay. <br>
|
|
<br>
|
|
|