设为首页收藏本站同能贴吧 切换语言 繁体中文
开启辅助访问 切换到窄版
扫描二维码关注官方公众号
返回列表
+ 发新帖
查看: 80|回复: 0

[制作教程] Alternate setting up method for disable-able scripts

[复制链接]
累计送礼:
0 个
累计收礼:
1 个
  • TA的每日心情
    开心
    前天 04:10
  • 签到天数: 209 天

    连续签到: 2 天

    [LV.7]常住居民III

    4453

    主题

    864

    回帖

    2万

    积分

    管理员

    Rank: 9Rank: 9Rank: 9

    VIP
    7
    卡币
    22913
    OK点
    16
    推广点
    0
    同能卷
    50
    积分
    28260

    灌水之王

    发表于 3 天前 | 显示全部楼层 |阅读模式
    Foreword

      This is more of for static set-ups (cannot be changed in-game), and also more of just an optimization (I think) from the normal way we set-up scripts in a way that would allow the user to disable it via a setting on the script itself.

    Normal Way

    Normally, you would do something like this

    module SET  USE=trueendclass Game_Battler  alias initialize_sample initialize  def initialize    initialize_sample    if SET::USE      #do other things    end  endendPROS: If you swap the module's constant with a game variable/switch for example, then you could dynamically enable/disable the script's works. Again, that is not the purpose of this.Alternate way

    Given that the constant could never be changed in-game, it seems a waste to actually do that check everytime, isn't it?

    So, take a look at this

    module SET  USE=trueendif SET::USE  class Game_Battler    alias initialize_sample initialize    def initialize      initialize_sample      #do other things    end  endendHere, we enclosed the whole class itself within an if. This way, the class itself will only exist if the constant was true (AFAIK, based on minor tests and my limited knowledge). AFAIK, it will only be evaluated once per session, when the scripts are initialized by the engine.Q: Why not just delete the whole script?

    A: What if you're just testing yet, and might need to put it back later? This will make that easier to achieve

    Q: There's select all then comment out method

    A: The examples uses only 1 class, and in that case, yes, the method would suffice. But imagine if you have a script like

    module SET  USE_1 = true  USE_2 = true  #and so onendif SET::USE_1  class one  endendif SET::USE_2  class two  endendthen your user would need to go inside the script and find the specific parts to comment out, you would want to avoid that.Closing

    I know this might not really be useful, but I figured I'd present it anyway for the benefit of knowledge. If somebody has a more in-depth tests about this matter, feel free to comment.  



    本贴来自国际rpgmaker官方论坛作者:Engr. Adiktuzmiko处,因国际论坛即将永久关站,为了存档多年珍贵资料,署名转载到本论坛存档,由于官方帖子为英文原帖,需要中文翻译请点击论坛顶部切换语言为中文就可以将帖子翻译成中文浏览,方便大家随时查看,原文地址:https://forums.rpgmakerweb.com/threads/alternate-setting-up-method-for-disable-able-scripts.35871/

    本帖子中包含更多资源

    您需要 登录 才可以下载或查看,没有账号?立即注册

    x
    天天去同能,天天有童年!
    回复 送礼论坛版权

    使用道具 举报

    文明发言,和谐互动
    文明发言,和谐互动
    高级模式
    您需要登录后才可以回帖 登录 | 立即注册

    本版积分规则

    简体中文
    繁體中文
    English(英语)
    日本語(日语)
    Deutsch(德语)
    Русский язык(俄语)
    بالعربية(阿拉伯语)
    Türkçe(土耳其语)
    Português(葡萄牙语)
    ภาษาไทย(泰国语)
    한어(朝鲜语/韩语)
    Français(法语)
    关闭

    幸运抽奖

    社区每日抽奖来袭,快来试试你是欧皇还是非酋~

    立即查看

    聊天机器人
    Loading...

    QQ|Archiver|手机版|小黑屋|同能RPG制作大师 ( 沪ICP备12027754号-3 )

    GMT+8, 2026-7-14 15:35 , Processed in 0.062452 second(s), 56 queries .

    Powered by Discuz! X3.4

    Copyright © 2001-2020, Tencent Cloud.

    快速回复 返回顶部 返回列表