eXiGe

  • Content count

    25
  • Joined

  • Last visited

Community Reputation

47 Excellent

2 Followers

About eXiGe

  • Rank
    Junior Member

Recent Profile Visitors

335 profile views
  1. Currently runs away from any hostile creature / monster and any shadow creature with a target local function ShouldRunAway(target) return not (target.components.health ~= nil and target.components.health:IsDead()) and (not target:HasTag("shadowcreature") or (target.components.combat ~= nil and target.components.combat:HasTarget())) end Shouldn't run away from any shadow creature or any hostile creature / monster without a target? local function ShouldRunAway(target) return not (target.components.health ~= nil and target.components.health:IsDead()) and (not target:HasTag("shadowcreature") and (target.components.combat ~= nil and target.components.combat:HasTarget())) end shadowmaxwellbrain.lua line 112
  2. 2 of my favorites from Wolfgang. BERRYBUSH_JUICY = { BARREN = "I need to poop on it to make juicy again.", LICHEN = "I'm lichen this!",
  3. ThePlayer:DoPeriodicTask(1, function() print("Control "..tostring(TheInput:IsControlPressed(CONTROL_MOVE_RIGHT))) print("Key "..tostring(TheInput:IsKeyDown(KEY_D))) end) When holding down a key, D in this case, and alt-tabbing from the game, both key and control will continue to hold as expected. Once returning to the game, the control will be released, whereas the key will remain stuck on.
  4. FPS Starts at 60, Then drops to 30

    This is a Windows issue that was finally resolved in a recent Windows update. https://support.microsoft.com/en-us/help/4074588/windows-10-update-kb4074588 Specifically: Addresses issue where, in certain hardware configurations, the frame rates of DirectX Games were unintentionally limited to a factor of the display's vertical synchronization.
  5. FPS troubleshooting

    This is a Windows issue that was finally resolved in a recent Windows update. https://support.microsoft.com/en-us/help/4074588/windows-10-update-kb4074588 Specifically: Addresses issue where, in certain hardware configurations, the frame rates of DirectX Games were unintentionally limited to a factor of the display's vertical synchronization.