george / king bore haha
@kingborehaha.bsky.social
who lowercased my game
November 23, 2025 at 10:33 PM
who lowercased my game
Bonus pisaca fun fact: you can backstab them, apparently.
November 22, 2025 at 6:56 PM
Bonus pisaca fun fact: you can backstab them, apparently.
press o to take the oath of hippocrates
November 22, 2025 at 5:39 AM
press o to take the oath of hippocrates
i couldnt remember how i handled this in SOTE, so i checked - and yeah not only did i fix the bug, i also did a bunch of other stuff that made the concept a lot more functional. good job, me
![REGISTER_GOAL(GOAL_Pisaca_Sisters333001_Battle, "Pisaca_Sisters333001Battle")
REGISTER_GOAL_NO_UPDATE(GOAL_Pisaca_Sisters333001_Battle, 1)
function Pisaca_Sisters333001Battle_Activate(ai, goal)
local targetDist = ai:GetDist(TARGET_ENE_0)
local fate = ai:GetRandam_Int(1, 100)
local fate2 = ai:GetRandam_Int(1, 100)
local fate3 = ai:GetRandam_Int(1, 100)
local GetWellSpace_Odds = 0
local Act01Per = 0
local Act02Per = 0
local Act03Per = 0
--[[
if 5 <= targetDist then
Act01Per = 0 --leave target
Act02Per = 0 --move to point. was 100
Act03Per = 100 --wait. was 100
elseif 1.5 <= targetDist then
Act01Per = 85
Act02Per = 15
Act03Per = 0
else
Act01Per = 15
Act02Per = 85
Act03Per = 0
end
--]]
--new
if 2 <= targetDist then
Act01Per = 0 --leave target
Act02Per = 100 --move to point. was 100
Act03Per = 0 --wait. was 100
else
Act01Per = 85 --leave target
Act02Per = 15 --move to point. was 100
Act03Per = 0 --wait. was 100
end
local fateAct = ai:GetRandam_Int(1, Act01Per + Act02Per + Act03Per)
if fateAct <= Act01Per then
--goal:AddSubGoal(GOAL_COMMON_Wait, ai:GetRandam_Float(1, 2), TARGET_NONE, 0, 0, 0)
goal:AddSubGoal(GOAL_COMMON_LeaveTarget, ai:GetRandam_Float(1, 3), TARGET_ENE_0, 20, TARGET_ENE_0, true, -1) --max time: 3-5 -> 1-3
elseif fateAct <= Act01Per + Act02Per then
local farPoint = Find_far_Point(ai, goal)
ai:SetEventMoveTarget(farPoint)
local walkBool = false --new. default is off
--[[
if fate <= 50 and targetDist <= 3 then--new
walkBool = false
end
--]]
goal:AddSubGoal(GOAL_COMMON_ApproachTarget, ai:GetRandam_Float(3, 5), POINT_EVENT, 1, POINT_EVENT, walkBool, -1) --max time was 5
--else
--goal:AddSubGoal(GOAL_COMMON_Wait, ai:GetRandam_Float(1, 3), TARGET_NONE, 0, 0, 0)
end
return
end](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:kb4xvdmqxtswtgpewmhr7bef/bafkreicqljznns3ioqkqufazbl7z4nltosgepsnap5y5fsyxaqxfqxi6m4@jpeg)
November 22, 2025 at 3:56 AM
i couldnt remember how i handled this in SOTE, so i checked - and yeah not only did i fix the bug, i also did a bunch of other stuff that made the concept a lot more functional. good job, me
When the typo in AI is fixed, you can see this behavior once again work properly. They will run towards whichever corner is furthest from the player (at the time of the check).
...however, because they are told to run towards the corner for EXACTLY 5 seconds they usually stop halfway anyway. oops.
...however, because they are told to run towards the corner for EXACTLY 5 seconds they usually stop halfway anyway. oops.
November 22, 2025 at 2:16 AM
When the typo in AI is fixed, you can see this behavior once again work properly. They will run towards whichever corner is furthest from the player (at the time of the check).
...however, because they are told to run towards the corner for EXACTLY 5 seconds they usually stop halfway anyway. oops.
...however, because they are told to run towards the corner for EXACTLY 5 seconds they usually stop halfway anyway. oops.
This is the lua AI script used to determine which region is furthest away.
The furthest position is stored as "maxDist" var. However, the code then checks "minDist" var, which does not exist. This results in the logic only ever picking the back-right region.
That's right. This is caused by a typo.
The furthest position is stored as "maxDist" var. However, the code then checks "minDist" var, which does not exist. This results in the logic only ever picking the back-right region.
That's right. This is caused by a typo.
November 22, 2025 at 2:16 AM
This is the lua AI script used to determine which region is furthest away.
The furthest position is stored as "maxDist" var. However, the code then checks "minDist" var, which does not exist. This results in the logic only ever picking the back-right region.
That's right. This is caused by a typo.
The furthest position is stored as "maxDist" var. However, the code then checks "minDist" var, which does not exist. This results in the logic only ever picking the back-right region.
That's right. This is caused by a typo.
What C is MEANT to do is check which of the 4 corner regions is furthest away from the player, and then the Pisaca will run towards that furthest region for exactly 5 seconds.
But due to a bug in AI, only one very specific region is chosen no matter what, making them not run away properly.
But due to a bug in AI, only one very specific region is chosen no matter what, making them not run away properly.
November 22, 2025 at 2:16 AM
What C is MEANT to do is check which of the 4 corner regions is furthest away from the player, and then the Pisaca will run towards that furthest region for exactly 5 seconds.
But due to a bug in AI, only one very specific region is chosen no matter what, making them not run away properly.
But due to a bug in AI, only one very specific region is chosen no matter what, making them not run away properly.
After being attacked, their special AI tells them to do one of three things depending on how far away the player is:
A: Nothing
B: Retreat backwards away from the player
C: For 5 seconds, run towards one of four box regions in each corner of the large cell (pictured)
C is where the bug happens.
A: Nothing
B: Retreat backwards away from the player
C: For 5 seconds, run towards one of four box regions in each corner of the large cell (pictured)
C is where the bug happens.
November 22, 2025 at 2:16 AM
After being attacked, their special AI tells them to do one of three things depending on how far away the player is:
A: Nothing
B: Retreat backwards away from the player
C: For 5 seconds, run towards one of four box regions in each corner of the large cell (pictured)
C is where the bug happens.
A: Nothing
B: Retreat backwards away from the player
C: For 5 seconds, run towards one of four box regions in each corner of the large cell (pictured)
C is where the bug happens.
Dark Souls 1 datamining: bugged fear logic of the Pisaca sisters
In the Duke's Archives, there are 2 special Pisaca (internally called "Pisaca_Sisters") that are not aggressive. By default, they do not move and only cry.
However, when attacked they will begin to run away... but it's a bit bugged.
In the Duke's Archives, there are 2 special Pisaca (internally called "Pisaca_Sisters") that are not aggressive. By default, they do not move and only cry.
However, when attacked they will begin to run away... but it's a bit bugged.
November 22, 2025 at 2:16 AM
Dark Souls 1 datamining: bugged fear logic of the Pisaca sisters
In the Duke's Archives, there are 2 special Pisaca (internally called "Pisaca_Sisters") that are not aggressive. By default, they do not move and only cry.
However, when attacked they will begin to run away... but it's a bit bugged.
In the Duke's Archives, there are 2 special Pisaca (internally called "Pisaca_Sisters") that are not aggressive. By default, they do not move and only cry.
However, when attacked they will begin to run away... but it's a bit bugged.
nightmare scenario. i have no mouth and must post
November 21, 2025 at 2:28 AM
nightmare scenario. i have no mouth and must post
help i think im the shadow realm
November 21, 2025 at 2:28 AM
help i think im the shadow realm
dont wanna jinx it again but
November 20, 2025 at 11:24 PM
dont wanna jinx it again but
post your getaway vehicle
mine is BALL
mine is BALL
November 20, 2025 at 3:35 AM
post your getaway vehicle
mine is BALL
mine is BALL
behold my creation.
behold and despair
behold and despair
November 20, 2025 at 1:51 AM
behold my creation.
behold and despair
behold and despair
apparently i made this last night but i dont really remember doing it
November 19, 2025 at 10:33 PM
apparently i made this last night but i dont really remember doing it
jump attacks are actually extremely stressful for a frampt, and can cause them to fight back with cut content
November 19, 2025 at 8:42 PM
jump attacks are actually extremely stressful for a frampt, and can cause them to fight back with cut content