#React debugging

[bkthemes]

REACT: Tips and Tricks

[et_pb_section fb_built=”1″ _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”][et_pb_row _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”][et_pb_text _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”] Introduction React has…

[thepearl256]

Top Tools for Web Development in 2025

Web development is an ever-evolving field, requiring developers to stay updated with the latest tools, frameworks, and software. These tools not only enhance productivity but also simplify complex development processes. Whether you’re building a small business website or a complex web application, having the right tools in your toolkit can make all the difference. Here’s a rundown of the top…

[cognithtechnology]

Common React Native Debugging Issues and How to Resolve Them?

React Native is a popular framework for building mobile applications using JavaScript and React. It allows developers to create cross-platform apps with a single codebase, streamlining the development process. 

However, despite its benefits, developers often face debugging challenges that can be frustrating and time-consuming. In this article, we will explore common React Native debugging issues and provide actionable solutions to help you resolve them effectively.

Understanding React Native Debugging

Debugging is an essential part of the development process. It involves identifying and fixing issues in the code to ensure that the application runs smoothly. React Native provides several tools and techniques to assist in debugging, but developers must be aware of common issues to address them efficiently.

Common React Native Debugging Issues

1. App Crashes on Startup

One of the most frustrating issues is when your app crashes immediately upon startup. This problem can stem from various sources, such as incorrect configuration or code errors.

Solution:

Check Logs: Use the React Native Debugger or console logs to identify the root cause of the crash. Logs can provide valuable insights into what went wrong.

Verify Configuration: Ensure that your development environment is correctly configured, including the necessary dependencies and packages.

Check for Syntax Errors: Review your code for syntax errors or typos that could be causing the crash.

2. Broken or Inconsistent UI

Another common issue is a broken or inconsistent user interface (UI). This can occur due to improper styling, layout issues, or component rendering problems.

Solution:

Use React DevTools: Utilize React DevTools to inspect and debug UI components. This tool allows you to view the component tree and identify rendering issues.

Inspect Styles: Check your stylesheets for any inconsistencies or errors. Ensure that styles are applied correctly to the components.

Test on Multiple Devices: Sometimes, UI issues may only appear on specific devices or screen sizes. Test your app on various devices to ensure consistent behavior.

3. Network Request Failures

Network request failures can occur when your app is unable to fetch data from an API or server. This issue can be caused by incorrect URLs, server errors, or connectivity problems.

Solution:

Check API Endpoints: Verify that the API endpoints you are using are correct and accessible. Test them using tools like Postman or cURL.

Handle Errors Gracefully: Implement error handling in your network requests to provide meaningful error messages to users.

Inspect Network Traffic: Use the network tab in Chrome DevTools or React Native Debugger to monitor network requests and responses.

4. Performance Issues

Performance issues can impact the overall user experience of your app. These issues can include slow rendering, lagging, or unresponsive UI components.

Solution:

Profile Your App: Use the React Native Performance Monitor or Chrome DevTools to profile your app and identify performance bottlenecks.

Optimize Components: Optimize your components by using techniques such as memoization, avoiding unnecessary re-renders, and minimizing the use of heavy computations.

Manage State Efficiently: Use state management libraries like Redux or Context API to manage your app's state efficiently and reduce performance overhead.

5. React Native Hot Reloading Issues

Hot reloading allows developers to see changes in real-time without restarting the app. However, sometimes hot reloading may not work as expected.

Solution:

Check Hot Reloading Settings: Ensure that hot reloading is enabled in your development environment settings.

Restart the Packager: Sometimes, restarting the React Native packager can resolve hot reloading issues.

Update Dependencies: Ensure that you are using compatible versions of React Native and related dependencies.

6. Unresponsive Buttons or Touch Events

Unresponsive buttons or touch events can lead to a poor user experience. This issue can occur due to incorrect event handling or layout problems.

Solution:

Verify Event Handlers: Ensure that event handlers are correctly attached to your buttons or touchable components.

Inspect Layout: Check your component layout to ensure that touchable elements are properly positioned and not obstructed by other elements.

Test on Multiple Devices: Test touch interactions on different devices to ensure consistent behavior.

7. Dependency Conflicts

Dependency conflicts can arise when different packages or libraries in your project have incompatible versions or dependencies.

Solution:

Check for Conflicts: Use tools like npm ls or yarn list to identify dependency conflicts in your project.

Update Dependencies: Update your dependencies to compatible versions and resolve any conflicts.

Use Resolutions: In some cases, you may need to use package resolutions to force specific versions of dependencies.

8. Native Module Issues

React Native relies on native modules for certain functionalities. Issues with native modules can cause various problems, such as crashes or missing features.

Solution

Check Native Code: Review the native code for any issues or errors. Ensure that native modules are correctly integrated into your project.

Update Native Dependencies: Ensure that you are using the latest versions of native modules and dependencies.

Consult Documentation: Refer to the documentation of the native modules you are using for troubleshooting guidance.

9. Memory Leaks

Memory leaks can lead to increased memory usage and performance degradation over time. Identifying and fixing memory leaks is crucial for maintaining app performance.

Solution

Use Memory Profilers: Utilize memory profiling tools to identify memory leaks and track memory usage.

Optimize Code: Review your code for potential memory leaks, such as uncleaned timers or event listeners, and optimize as needed.

Manage Resources: Ensure that resources are properly managed and cleaned up when no longer needed.

10. Version Compatibility Issues

Version compatibility issues can arise when using different versions of React Native, React, or other libraries in your project.

Solution:

Check Compatibility: Ensure that all libraries and dependencies are compatible with the version of React Native you are using.

Update Libraries: Update libraries and dependencies to versions that are compatible with your React Native version.

Consult Release Notes: Review release notes and documentation for any compatibility issues or breaking changes.

Best Practices for React Native Debugging

To effectively debug React Native applications, consider the following best practices:

Keep Your Code Clean: Write clean, well-organized code to make debugging easier. Use consistent coding standards and practices.

Use Version Control: Utilize version control systems like Git to track changes and easily revert to previous states if needed.

Document Your Code: Document your code and debugging process to help you and others understand and troubleshoot issues more effectively.

Conclusion

React Native debugging applications can be challenging, but with the right approach and tools, you can resolve common issues effectively. By understanding common problems and implementing best practices, you can improve the stability and performance of your app. 

Remember to stay up-to-date with the latest React Native developments and continuously refine your debugging skills. With persistence and attention to detail, you can overcome debugging challenges and deliver a high-quality mobile application.

[inextures]

Advanced Tips and Tricks for Debugging React Applications

React is a popular JavaScript library for building web application user interfaces. While developing with React, developers face various issues that can be solved with strong debugging skills. By effectively troubleshooting and resolving these problems, developers can save time and deliver high-quality React applications. 

Common issues during React development include syntax errors, rendering problems, state management challenges, runtime errors, event handling issues, lifecycle method errors, prop type mismatches, dependency conflicts, routing problems, styling and CSS issues, and API integration problems. To resolve these issues, developers should read error messages carefully, use debugging tools, and consult React’s documentation and community resources.

Improving debugging skills allows developers to quickly identify and fix problems, enabling them to overcome challenges efficiently and deliver high-quality React applications.

Debugging in React Application 

Debugging is essential for React developers, especially as projects grow more complex. In this blog post, we will explore advanced debugging tips and tricks for React applications. Our aim is to equip you with the knowledge and tools to tackle even the most elusive bugs.

Strong debugging skills are essential for React applications. Techniques like console logging, browser tools, and React Developer Tools can help address issues like unexpected behavior, state management challenges, slow rendering, and complex data flow. Error boundaries and the React Profiler aid in error handling and performance optimization. By effectively applying these debugging skills, developers enhance functionality and boost React application performance.

By refining your debugging skills, you’ll be well-prepared to navigate the complexities of React application development and deliver robust and efficient solutions. So, let’s dive into the world of debugging React applications and uncover the secrets of bug hunting!

1. Use console logging

Console.log in React helps debug code by logging information to the browser’s console. It tracks variables, checks function execution, and inspects values during runtime.

Power of console.log:

Outputting Information: Console.log easily displays messages, variables, objects, and other data types in the console.

Real-Time Insight: Placing console.log strategically reveals real-time insights, tracking execution flow, variable values, and component/function interactions.

Problem Diagnosis: Console.log helps diagnose issues by logging relevant data such as function parameters, intermediate values, or error messages.

Tracking Code Execution: By logging messages at key points like lifecycle methods or event handlers, console.log enables tracking and validation of code execution.

Iterative Development: Console.log aids in iterative development by logging values and verifying code output, facilitating incremental adjustments and validation. 

In this example:

The component renders a count value and provides buttons to increment and double the count.

The useEffect hook logs “Component rendered” once when the component is mounted.

The incrementCount function increments the count and logs the current count value.

The doubleCount function doubles the count and logs the current count value.

A console log message “Rendering component” is placed to track the rendering of the component.

By observing the console output, you can see when the component is rendered, track count changes, and monitor component rendering.

2. Use React Developer Tools

React Developer Tools is a browser extension that helps developers debug React applications. It offers a range of features to understand, inspect, and manipulate components and states. Here’s how it aids in debugging large-scale applications:

Component Hierarchy: Provides a tree view of all components, helping understand complex hierarchies.

Component Inspection: Allows inspection of individual components, including props and state. 

State Management: Integrates with popular libraries like Redux to inspect and track state changes. 

Performance Profiling: Measures render times, identifies re-renders, and detects performance bottlenecks. 

React Developer Tools empowers developers by providing insights into React applications, assisting in understanding hierarchies, inspecting states and props, tracking changes, identifying performance issues, and debugging complex scenarios. These capabilities are valuable for extensive and intricate codebases in large-scale applications.

          3. Implementing React Error Boundaries

React Error Boundaries catch JavaScript errors in their child component tree during rendering, lifecycle methods, and event handling.

They prevent the entire application from crashing by handling errors gracefully.

When an error occurs within the subtree of an Error Boundary component, it displays a fallback UI instead of the crashed component tree.

Error Boundaries are similar to “try-catch” blocks in JavaScript but are specific to React components.

They improve user experience by displaying a fallback UI and allowing the rest of the application to function without disruption.

Error Boundaries aid in debugging and error reporting by logging and analyzing errors.

They help isolate errors to specific components, preventing them from impacting the entire application.

4.  Utilize strict mode in react application

React Strict Mode is a developer tool that detects and flags potential problems in a React application. It applies strict checks and warnings to identify common mistakes and performance issues, helping developers address them during the development process.

React Strict Mode helps in the following ways:

Identifying Unsafe Practices: Detects and warns about unsafe lifecycle methods, deprecated features, and potential issues in your codebase.

Highlighting Side Effects: Detects unexpected side effects during component rendering, helping you identify and fix unintended consequences.

Catching State Mutation: Warns about state mutations, ensuring a more predictable and maintainable application state.

Detecting Deprecated Features: Alerts about deprecated features, encouraging updating code to utilize recommended alternatives.

Performance Warnings: Provides performance-related warnings, optimizing application rendering performance.

     5. Debugging Asynchronous Operations 

When debugging asynchronous operations in a React application, there are several important points to consider. Here are some key aspects to look into:

API Calls: Use console.log or debugger before and after making requests. Check the browser’s “Network” panel for details.

State Management: Console.log or debugger where state changes occur. Use browser tools or extensions for deeper inspection.

Promises: Log resolved values and handle errors using console.log or debugger within “then” and “catch” methods.

Async/await: Set breakpoints on “await” lines to inspect variables. Use try-catch blocks for error handling.

Timer-based operations: Place console.log or debugger in timer callbacks to understand timing and code execution.

Combine techniques and tools like console.log, debugger, and browser developer tools for effective debugging.

    6. Inspect Component Props and State 

To improve your React application’s performance, follow these steps:

Add console.log statements: Place console.log statements in important parts of your code, such as lifecycle methods, event handlers, or useEffect hooks. Log relevant data like props, state, or variable values to track execution flow and observe data changes.

Examine prop flow: Analyze how props are passed down the component tree. Avoid unnecessary drilling of props through intermediate components, as this can cause unnecessary re-renders. Optimize performance by using techniques like React.memo or shouldComponentUpdate to prevent re-rendering when props or states haven’t changed.

Use performance profiling tools: Take advantage of performance profiling tools available in your development environment. Measure CPU usage, memory consumption, and network requests to identify potential bottlenecks. Optimize your code based on the insights gained from profiling, ensuring an efficient and responsive React application.

By implementing these techniques, you can gain valuable insights into component flow, optimize performance, and create an efficient and responsive React application.

7. Debugging Common React Issues

React Developer Common Errors & Solutions:

Syntax Errors: Review and fix typos, missing brackets, or incorrect syntax in your code.

Rendering Issues: Check component rendering logic, lifecycle methods, and props/state usage.

State Management Issues: Review state management approach, initialize/update state properly, and ensure correct state access.

Undefined or Null Errors: Handle cases where variables or properties may be undefined or null.

Event Handling Issues: Double-check event handlers bind ‘this’ correctly, and access event properties properly.

Prop Type Mismatches: Define and enforce prop types to ensure correct data types.

Analyze Network Requests: Use browser network tools to inspect API requests and responses.

Dependency Conflicts: Carefully manage dependencies, ensure compatibility, and resolve conflicts.

API Integration Problems: Review API integration code, check endpoints, format data correctly, and handle responses/errors appropriately.

Remember to analyze error messages, refer to documentation, and seek community resources for solutions. Experience and practice will enhance your ability to identify and resolve these common React errors.

8. Test with different environments and browsers

Testing your React application in different environments and browsers is crucial for debugging and improving your code. It offers several benefits:

Bug Reproduction and Isolation: Testing in various setups helps reproduce and isolate bugs that may be specific to certain environments or browsers. This aids in understanding the root cause and finding solutions.

Browser-Specific Issue Identification: Different browsers have their own quirks and behaviors that can affect your React application. Testing in multiple browsers helps identify browser-specific issues, allowing you to address them appropriately.

Performance Optimization: Testing in different environments and browsers reveals performance bottlenecks that may be specific to certain setups. This enables you to optimize areas of your code and improve overall performance.

Accessibility Testing: Testing with screen readers and accessibility tools in different environments ensures your application meets accessibility standards. It helps identify and address any accessibility-related issues for better usability.

Cross-Platform Compatibility: Testing on different platforms ensures your React application works consistently across devices and operating systems. It helps identify platform-specific bugs or limitations, allowing you to provide a seamless experience for all users.

Conclusion:

Debugging React applications can be challenging, but with the right techniques and tools, developers can effectively identify and resolve issues. In this post, we explored advanced tips for debugging React apps, including console logging, React Developer Tools, Error Boundaries, strict mode, and more. By following these steps, you’ll improve your ability to tackle complex bugs and enhance the quality of your React applications. Remember to be patient and persistent during the trial-and-error process of debugging. Analyze error messages, consult React’s documentation and community resources, and practice regularly to become a proficient debugger. With experience, you’ll gain a deeper understanding of React’s inner workings and build robust applications.

Read More Advanced Tips and Tricks for Debugging React Applications

[thatforkedroad]

really important news. so w the debug menu u can spawn vader in the saloon which is fun, bc literally nobody will react bc its not a hostile environment. who give a shit if cal is dying im thirsty

cal will literally just stand there. his lightsaber turns on but he doesnt fight cause there isn't supposed to be enemies in here

he can even join the crew bc he gets confused if you manage to get him on the mantis <3 and doesnt fight you <3 he just sorta stands there like an asthmatic emo lemon <3

and the best thing of all: he's too tall to leave certain doorways and gets stuck all the time. vader's one greatest enemy isn't the jedi it's low ceilings

[jscrawls]

Widows rest

My take on a Black widow! Reader x Batman and Batfam but with a slight twist, reader doesn't know the Bats but they seem to know them...

Warning: contains avengers infinity war spoilers, black widow spoilers, mentions of injury, poor writing, ooc writing,

Part 15: skimming the surface…

🔹🔹🔹

“what happened.”

your voice nearly snaps out as you stare in at Bruce, watching the steady rise and fall of his chest Under the covers. Why is he here at his manor if he was in a car wreck?

Alfred shifts beside you, angling his head to stare at you with a morose expression, his eyes scarce meeting yours. “It was a car accident, Master Wayne. Just as I explained on the way home.”

You glance at him with a raised brow, challenging his stare for once. “I know the why, I'm asking how the wreck happened. Driving under the influence? Texting and driving? Avoiding a jaywalker? Cars don't just wreck themselves, Alfred.”

He looks away, head tilting just slightly as his hands tuck behind his back and his stance squares, deceit? You sense a lie coming before he so much as opens his mouth.

“He was on the way to a lunch break when his driver was cut off, apparently his executives wanted to continue their meeting over tea.” He meets your eye again, eyes narrowing as he studies you just as intently as you study him.

“Considering the recent happenings, could it be targeted.” Your voice is steady as you speak, unblinking as he reacts, turning more fully to face you. “I doubt the attackers from last night are responsible for a little fender bender, what makes you say that?”

His expression relaxes a touch, brows raising in curiosity as he glances in at Bruce and back at you.

“the timing is just…. Odd. what are the odds of this happening the day after an attack, right when the CEO of a company leaving a meeting where there was concern about said company's property being targeted? I'd look into whoever the other party was if I were the investigator.”

You glance in at Bruce as well, watching him breathe deeply and slowly, whatever he's on seems to have him in a deep sleep, oblivious to the conversation happening in his doorway, unless he's just a heavy sleeper. The hint of bandages peeking out from under his gray tee confuses you, just why isn't he in a hospital?

“…. You make a good enough case, I'll have a word with the insurance investigator about your concerns.” He nods to himself as if confirming something, he's slowly but surely letting his guard down around you. You're not sure how to feel about it. “Good, that's….Good.”

You look away from them both before you say something foolish, are you so bored that you're giving yourself more paranoia? Looking for things to be wrong so you can rip everything apart at the seams, pretend you're not the only one hiding things?

Alfred nods his head as he gives Bruce a final glance, he straightens up and rests a hand on the doorknob, a silent end of the discussion for now. “Yes, now I'm certain you're tired after therapy so…. I'll call for you when dinners ready, master Wayne.”

And without waiting for a reply, he shuts the door with a soft click and turns away, shoulders sagging slightly as he shuffles off, he looks tired and worn…

You take the hint and pad towards your own room, like hell you're just gonna sleep though.

🔹🔹🔹

First thing that ticks you off is the lack of news, you lounge on top of the dark covers with the debugged phone in hand as you go through multiple media outlets, no news about Bruce Wayne, or Wayne enterprises, or anything about an unnamed rich man getting hit by a car. Even in the wake of last night's attack you know damn well that something like that would be reported on, especially mid day? Presumably in the city for anyone to see? People love to talk about the famous. Thrive on watching them through their screens. It makes you suspicious.

It takes a while to tap the GCPD police scanners, this phone is surprisingly hardy for all the programs you're shoving in it, still nothing. No reports or chatter about the billionaire at all, you knew Alfred was full of it, but making up a wreck? What's the old man playing at here.

You drop the phone on the pillow beside you and stare up at the ceiling, eyes narrowing as you ponder everything. The fires looked bad, too big and too quick to just have been normal alcohol fires. Maybe a fuel based starter? But who'd be stupid enough to put that in glass bottles and hold it in their hands? The kids were already squirrelly by the time you woke up, maybe afraid to go to school, but they should've been comfort seeking then. The body language was wrong there too…..how much do they know? Damn it all, too many theories and nothing to work with. you want answers and it seems you’re gonna have to work harder for them.

The kids are gone be the time dinners served, it's just you and Alfred again eating in tense silence while you both avoid the elephant in the room. he keeps his focus on his plate almost stubbornly so, body language closed off and uninviting.

“so where is everyone else tonight?” you give him a curious look as you set your fork down, trying to prompt him to answer as you casually lean forward on your elbows.

he sighs almost imperceptibly as he glances at you, picking up his teacup and slowly swirls the hot liquid inside. “the same places they usually go, master wayne. the kids have practice, friends, responsibilities, and i believe you know where master bruce is.” he takes a long sip of his tea after speaking, glancing at you over his cup.

you tilt your head questioningly, brows raising as your fingers tap on the tabletop rhythmatically. “do you think it’s safe?” he mimics your expression, confusion dancing across his face as he leans back in his chair. “how do you mean?”

“i mean there was just an attack on the city, quick arrest or not i doubt it’s safe to be going out this late.” is this just an elite thing? surely bruce wouldn’t let his underage kids out on the town right now of all times. right?

alfred gives you an odd look, looking you up and down scrutinizingly. “….you’re very paranoid about things today.”

“should i not be.” your fingers pause, palm flattening against the table as you meet his stare.

an awkward silence stretches over the kitchenette, you and alfred staring at each other waiting for one to crack, the tension builds until…the notification system dings, someone’s at the door.

alfred tenses and stands slowly, attention clearly shifting as he quietly excuses himself from the table. you want to bang your head on the table, why the hell is everyone so weird here? it’s like trying to wrestle information out of yelena.

you’re picking at your food when alfred shuffles back in the room, as soon as you glance at him you freeze, all the hair on your arms standing as air moves just behind you and you swing a butterknife on pure instinct.

your heart leaps up in your throat when something grabs you as soon as you even turned, what the fu-

“oop sorry about that! didn’t mean to sneak up on ya.” a Midwestern accent apologizes beside you as the hand quickly loosens from your elbow, a dark haired man stands behind you with an apologetic expression on his face as he rubs at the back of his neck, he’s maybe Bruce's height, possibly a bit taller. broad as a barn and half as heavy. yet you didn’t hear a single step, a single shift. it’s as if the big guy phased in the room behind you like vision.

trying to hide how startled you are you turn towards him and offer him a small smile. “wow you’re a quiet one, gonna give bat-man a run for his money haha.” you force a chuckle out, your heartbeat all the way in your throat, you haven’t been snuck up on like that in a while…

“sorry, sorry. sometimes i forget how people don’t…anyways are you okay?”

his eyes flick to the butterknife in your grasp, you force yourself to quickly drop it on the table.

“i’m good, just a bit jumpy i guess….who’re you?” his brows pinch together in confusion for a second before realization flicks across his face, he holds a hand out for you to shake. “wow i totally forgot about that, please forgive me….again, i’m clark. i’m bruce and yours friend.” you take his hand.

he smiles at you just as alfred shuffles over, extra teacup in hand and a confused look on his face as he glances between the both of you.

you ignore Alfred's judgement as your hand drops in your lap, this guy somehow avoided making a single sound with cleated boots on, even a widow would struggle on this flooring. something in the back of your mind is screaming at you to stay alert around him, like base animal instinct screaming there’s a predator near…he also reminds you of captain rogers for some reason, the fidgeting of the hands and sincere whispered apologies reads just like the captain when he fucks up. you didn’t think you’d miss the annoyingly endearing awkward politeness, but here you are.. “it’s fine i’m getting used to it, nice to meet you again clark.”

“nice to meet you again too, it's good to see you up and moving. I'm sorry I could only make it here when Bruce is down for the count. i’ve been out of the country for a bit…” Alfred clears his throat, interrupting your question before you could even ask, he moves to pull Clark aside, talking about refreshments and offering him a plate of food as if that was worth interrupting you for, even clark looks confused as the butler pulls him away, his eyes meeting yours for just a moment before the older man grabs his attention.

Frustration bubbles up on you once more when it feels like you're being kept out of the loop again, what does Clark know that you're not supposed to? Something akin to tempered rage clenches your fists and grinds your jaw like a spring pulled too hard, ready to snap back into place. When Alfred mentions taking a plate of food to Bruce you interrupt him.

“I'll bring it to him.” You're already standing up before you finish speaking, pushing your chair into the table as Alfred and Clark both glance at you with differing expressions.

“You haven't finished your food yet, master Wayne….” You don't even look at your plate as you step around the table, brushing past both men to grab the tray.

“I'm fine, my therapist said it's good for me to flex my motor skills as often as possible at home. I wanna check in on Bruce anyways, see how he's doing if he's up.” Alfred starts to speak but Clark drops a hand on his shoulder, giving him a small smile.

“I've been meaning to drop something off with you anyways Alfred….”

You miss the rest of his sentence as you stride out of the room, maybe it's time you question your husband.

🔹🔹🔹

“you awake?”

You rap your knuckles on the heavy door as you softly call out, the food tray balanced on one hand. For a moment you hear absolutely nothing within the room, maybe he's still passed out?

You're about knock again when the door pulls open, Bruce blinking blearily at you with a major case of bed head. You'd laugh if you weren't suddenly face to face with him, who's not wearing any pants….

“Hey….” He mumbles dumbly, staring at you for a moment in a seeming daze. “Hey. Can I come in?” You gesture to the food tray with your chin while shifting your hold on it.

“Hmm?…. Oh, yeah come on….” He steps aside as you wordlessly step in, casually kicking the door shut with your foot while he gives you a confused look. You'd like some privacy right now.

You set the tray down on the bedside table before turning your head to glance over at him.

“You feeling okay? Heard you had a wild day…” that'd sound funny out of context, he just follows you to the bed and slowly sits on the edge with a grunt, eyes never quite leaving your form. “not great, could be better I think…. How long was I knocked out for?” he awkwardly runs a hand through his hair while shuffling closer to where your standing, you pass him a plate while trying to ignore his state of dress.

“dunno, how about you tell me.” Your hand grabs the edge of the table as you put on your most innocent look, you don't miss how he regards you when you lean down towards him a bit.

“What's that mean?” His eyes flick over you the briefest bit before he looks down at his plate, his Adams apple bobbing as he swallows.

“nothing, just wanted to know when you went down the stairs I guess….I think I've got the whole getting injured thing covered, you shouldn't try to give me a run for it.” You smile sweetly at him as you sit down beside him, his body language shifts again, leaning into you just slightly as you press close enough that your thighs touch. Just what you wanted.

“this morning maybe? It's a bit of a blur…. The kids thought it was so funny.” He sighs exasperatedly as he runs a hand through his hair again, messing up his bed head even more.

“i can see why.” When he gives you a sour look you snort, briefly leaning over him to grab at the thermos on the tray so you could steal some of his tea.

“oh you're so funny now, a real comedian.” He sounds exasperated but you're not fooled.

“Mhmm, at least mine was better than tumbling down the stairs like a slinky.”

“This isn't the pain Olympics you know, not my fault I'm very fragile.” He huffs again and turns his head to hide a small smile, then he slowly sets his hand just behind you on the bed, not quite pulling you in but definitely making moves to be close to you. Guess he likes being softcore bullied by you?

“well you should still watch your damn step, there's enough brain damage going around as is.” You sneak a glance at the bandage under his sleeve, you're certain that's professionally applied. He rolls his eyes and chuckles quietly to himself while shaking his head.

“it's sweet how you're going soft on me…..I missed seeing you like this.”

His tone gives you pause, that same saccharine tone full of affection just like in the hospital, it makes something resembling guilt curl behind your ribs and settle there. “…like what?”

“…relaxed. I know I kinda put you in an odd position when I brought you home to all…. I'm just happy to see you laughing. Even if it's while mocking my pain.” he snorts at his own words and looks up at the ceiling, there's something kinda odd about seeing the reserved man act so…. Light-hearted, you expected to have to work harder here…. Maybe it's the pain meds he's on?

Your take a long swig of the hot tea to give yourself a moments pause, how do you even respond to that? Even with all the deceit and close-door happenings his words and body language are honest. you've already confirmed what you wanted to know so why are you still here? “Your…our Friend’s here to see you.”

His eyes fall to meet yours again with no small amount of disappointment in them, he knows you're yet again denying an intimate moment, verbally retreating from him, he's slowly getting used to it.

“oh yeah?” the smile slowly returns as he tries to keep things light for you, even in his slightly dazed state he’s trying to be considerate of you, it’s uncomfortable.

You slowly stand up from the bed and stretch, looking away to hide a small smirk as you hand him the thermos that was technically supposed to be his. “Mhmm, Clark's here. He said he's sorry you're so bad at walking on your own two feet.”

He scoffs loudly as he takes it from your grasp, eyes never leaving your form as he slowly raises it to his lips. “I have such a nice support system, I'm truly blessed. I'll hobble my way down there in a few.”

you nod as you glance around one last time, pretending not to notice the bottle of lidocaine gel on the dresser as you turn away and shuffle towards the door.

“Oh, and one more thing Bruce?” you glance over your shoulder at him from the doorway, hand resting on the wood frame just above your head as you smile sweetly at his unsuspecting figure.

his eyes meet yours as he pauses eating, fork halfway to his mouth as he addresses you. “yes?”

“You might wanna throw some pants on before you leave this room.” you have to suppress a snort as he quickly glances down at himself while you leave.

the smile slowly slips from your face as you stroll down the hallway towards your room instead of going back to the kitchenette, you know one thing without a doubt now, bruce and alfred are very good liars.

🔹🔹🔹

M.list | prev | next

A/n: wow this one got away from me a bit, I think this is my longest chapter yet 😓 hope y'all like it and it was worth the wait. Hope y'all have an amazing day/night!

Taglist: @cxcilla @mercuryathens @dind1n @redsakura101 @ninihrtss @let-me-dance @ladykamos @one-piecelover @cuntiesweet @omnivirgo @shirp-collector-of-fixations @spidermanluvr444 @br33zy-blizzardz @4rachn3

[codingquill]

Essentials You Need to Become a Web Developer

HTML, CSS, and JavaScript Mastery

Text Editor/Integrated Development Environment (IDE): Popular choices include Visual Studio Code, Sublime Text.

Version Control/Git: Platforms like GitHub, GitLab, and Bitbucket allow you to track changes, collaborate with others, and contribute to open-source projects.

Responsive Web Design Skills: Learn CSS frameworks like Bootstrap or Flexbox and master media queries

Understanding of Web Browsers: Familiarize yourself with browser developer tools for debugging and testing your code.

Front-End Frameworks: for example : React, Angular, or Vue.js are powerful tools for building dynamic and interactive web applications.

Back-End Development Skills: Understanding server-side programming languages (e.g., Node.js, Python, Ruby , php) and databases (e.g., MySQL, MongoDB)

Web Hosting and Deployment Knowledge: Platforms like Heroku, Vercel , Netlify, or AWS can help simplify this process.

Basic DevOps and CI/CD Understanding

Soft Skills and Problem-Solving: Effective communication, teamwork, and problem-solving skills

Confidence in Yourself: Confidence is a powerful asset. Believe in your abilities, and don't be afraid to take on challenging projects. The more you trust yourself, the more you'll be able to tackle complex coding tasks and overcome obstacles with determination.

[22ayla21]

Hello!! Congratulations on 1000 followers!! For the event can I have Idia Shroud with Vanilla Ice Cream with Caramel and Strong Espresso??? Please and thank you 💙

"Vanilla Ice Cream with Caramel and Strong Espresso"

Event: "Sweet Stories, Intoxicating Feelings"

S.T.Y.X was a place where dreams took on nightmarish shapes, and love seemed impossible. In this labyrinth of steel walls, humming laboratories, reports with alarming red "CRITICAL CONDITION" markings, and inexplicable magical phenomena, the very thought of something tender and human seemed absurd. Especially in the heart of Idia Shroud, a person who mostly preferred the flicker of screens to live interaction and looked at his reflection warily, as if expecting betrayal from it.

But she appeared not as a dazzling flash, but as a weightless touch on the glass behind which Idia sheltered from reality. She didn't pull him out, no. She was simply there. As if saying without words, "You can stay in your refuge for as long as you want. I'll still be here."

He didn't notice her right away. Not out of unwillingness – more out of an inner fear. In S.T.Y.X, every day followed a strict routine: waking up, checking monitors, updating Overblot logs, an obligatory joke in an internal code language understandable only to him… and Ortho. And then – night again, loneliness again, screens again, from which his eyes grew tired, and his heart remained strangely indifferent.

She burst into his usual rhythm as unexpectedly and pleasantly as a drop of caramel accidentally falling into his morning cup of strong black coffee. He was used to bitterness, to invigorating solitude, to the fact that everything should be clear, efficient, concise. And she… she was like vanilla ice cream on a hot day. Simple. Sincere. Like a long-forgotten feeling of summer.

"You know, your work is important, but you yourself are more important," she said one day, finding him working when he had completely forgotten about food, immersed in lines of code and magical algorithms.

He blinked, not immediately understanding how to react to such a simple truth. In his world, everything was clearly delineated. But she didn't demand. Didn't insist. Just handed him an ice cream – vanilla, with caramel drizzle.

"You're like espresso. Dark, strong, and incredibly invigorating," she added, smiling. "But you could use a little sweetness. Or someone to add that sweetness."

From that day on, he began to listen for her footsteps. To catch the quiet hum when she worked at the neighboring terminal. To notice how her hair played in the light of holograms, how quickly her fingers ran across the keys, typing reports, how she sometimes looked thoughtfully into the void, and then he desperately wanted to know what she saw there.

They didn't talk about feelings right away. It seemed too… open. Idia was afraid of words, felt defenseless in ordinary conversation. But he started communicating with her more than with anyone else. First through messages, then – in person, but separated by a wall, then – face to face. Over a cup of coffee. Over a serving of ice cream.

Love turned out to be quiet. It didn't shatter walls, didn't tear his heart to pieces. It was like that ice cream – classic vanilla, understandable, familiar, but with that very caramel note that made every day special. Sometimes it invigorated, like a strong espresso, suddenly pushing forward: in work, in emotions, in confessions.

"Are you afraid of me?" she asked softly one day, when he stumbled, not knowing how to express what she meant to him.

He looked down. Not because he didn't want to answer – it was just that his heart was beating so hard, as if it was about to explode.

"No… I'm afraid that you'll leave when you realize how… broken I am."

She smiled and touched his hand with her palm.

"Even the most bugged code can be debugged. The main thing is not to be afraid to do it together."

Then he laughed. Sincerely, almost to tears. And for the first time, he didn't want to hide. He wanted to stay – with her, in this strange place, where even among scientific reports and classifications of magical disasters, something simple was born. Something real.

Love. Like vanilla with caramel. Like espresso with the tart aroma of passion. Like the life he used to be afraid of.

Now he lived in it. With her. And no longer hid.

[littlemssam]

New Mods & Mod Updates

As always delete old Mods Files and the localthumbcache, when updating my Mods!

---

New small Mod & new Bug Fix

Small Lactose Intolerant Overhaul This small Mod edits the Plant Milk so it is useable for more Recipes, and it changes how Sims with the Lactose Intolerant Trait react to Food a bit.

Vampire Run Fix This Mod fixes Vampires not using the Vampiric Run, and played Vampires changing their preferred Walkstyle, when switching Households.

---

Mod Updates

Foster Family Various Tweaks:

Increased the Duration potential Adoptives are visiting from 4 to 8 hrs.

Added Greeting Status to potential Adoptives, so you won't have to invite them in. They will more likely come in and interact with Foster Kids/Pets now.

Added a Send Home Interaction to potential Adoptives, since they now stay longer. This way you can send them Home with one Click.

Adopted Foster Kids will get the Son/Daughter Relationship added now and should show up in the Family Tree.

Mod Setting Option via Phone is only available, when a Sim has registered for the Foster Family Network.

Added new Cheat Menu (Shift Click) to Sims (Sims who registered for the Foster Family Network), where you can trigger the Foster Family Network Notifications to get Foster Kids/Pets.

Added new Cheat Menu (Shift Click) to all Kids/Pets ingame, where you can add already existing Kids/Pets in the World to become your Foster Kid/Pet.

Fixed an Issue with Foster Family Network Notifications for Cats, when you did not enable all Ages for them.

Vampire Powers | “Be able to eat Human Food”, “Enable own Mirror Reflection”, “Stop Hissing” and more Addon NPC Disable Special Walkstyle removes hidden Walkstyle Traits only from never played NPCs.

No Auto Food Grab after Cooking Fixed a small Issue with the Icon on the custom Get Leftover Interaction not showing up, when Choose Leftover is not installed.

Sul Sul Weather App Added Support for Ciudad Enamorada. Reworked Icons a bit. Script File is obsolete now. Pls remove.

Send Sims to Bed Added Support for Sleeping Bags

Social Activities (Visit Friends, Family and more) Fixed an Issue, where the Interactions got cancelled, when your Sim was on a Business Lot they own.

Random Small Mod Updates

Auto Brush Teeth Reworked Mod to make it compatible with EA's Bathroom/Kitchen Settings for Sinks. The Addon File "DisabledBrushTeethSinksWillAllowWashDishesOnly.ts4script" is obsolete because of that now, pls remove that File. I did keep my own "Allow/Disallow Brush Teeth" Options though, which you can still set via Cheat Debug Menu (Shift Click) in case the EA Settings don't work well for you. When you don't use EA's Settings or my Mod Settings, Sims will be allowed to use all Sinks however they like. The Addon "AfterEatingToo.ts4script" is changed to be compatible with the XML Injector now, and is changed into a Package File. Remove the Script File pls.

Auto Use Picnic Table when Eating Added Support for two new Picnic Tables from Lovestruck and Growing Together. Added an extra Addon File for "Umbrella Tables" from Base Game and various Packs.

Claim All The Things Added "Frying Pan", "Collectible Other/Treasure Map", "Canvas", and "SackLunch" to be supported

Prefer Leftover Added Addon for Bread to be blocked from autonomously Eating/Grabbing a Plate.

Release all Ghosts & Get Urn for Added the Interactions to Mailboxes (Shift Click), so you don't need to get Urns via Debug etc first.

Craft More Nectar Bottles and more When Crafting 5 Bottles, the Dynamic Skill loot for Nectar Making is multiplied by 1,5.

---

Translations

Advanced Birth Certificate - Update of Dutch by Willowtree My Pets - Update of Dutch by Willowtree Online Learning System - Added Finnish by MaijaEllen

---

My Site with all possible Download Links: lms-mods.com

Support Questions via Discord only please!

[lj-lephemstar]

Progress Checkup! (Jan. 2025) | Scratchin' Melodii Devlog

Hey guys! Time for another progress checkup; This is actually the first one of the new year! I hope you were all able to enjoy the holidays. I took a bit of a break from working on most stuff last month and have been getting back on things this month. First, I wanna thank everyone who's wishlisted Scratchin' Melodii on Steam! So far, the game's gotten over 17,000 wishlists! Thanks so much for the support!

In the previous devlog, I mentioned some changes to the rhythm system. In the Dragon Funk preview, you can see the new rhythm system and character icons I mentioned in the previous devlog! Actually, let's unpack some of the new things you're seeing in action there:

Hold Notes This is the first song in the game to include hold-notes! They mostly work the same as they would in any other rhythm game. However, since this game has an emphasis on self expression, moving the control stick during these will let you tune the note's pitch-bend for extra expression points! I showed that off in a post here. As for Pow Notes, I've been working on a way to let the player get expression points from these too! I'd like for most of the special notes like these to be not just a gimmick, but a tool that the player can use to their advantage.

Quadruple Lines Yep! The first blue line in this one is extra long and has 4 rows! Fun fact actually, I had to implement this feature after I realized that part of the song was too long to fit in just two rows. It was pretty difficult to figure out both how to do it and how to execute it in a way that doesn't feel too jarring, but I'm pretty satisfied with the results! In fact, barely anyone's even noticed it; I guess that's just how natural it feels! Not sure how much more often I'll be having lines longer than two rows, but it's great that I have the option now.

AutoPlay You might also notice that the player inputs are perfectly timed... TOO perfect... that's because I've developed an autoplay feature for the game! At the moment, it's mostly for debugging and stuff, but if all goes according to plan, AutoPlay Mode and Replays should hopefully be available to players as well in some form when the game comes out!

"Next" Indicator & Other UI Related QoL Some of the top things players said they had trouble with in the demo were related to being prepared for the next line. So, if you look at the right-end of the rhythm bars, you'll see a little tab that shows the color and amount of rows the next line will have! Also, now each line's suggested notes can be seen before the rival performs them. This did take some thought, as I actually kinda still liked the idea of it appearing as if the characters were making it up on the spot, but to put game design first, it makes more sense to have it displayed as soon as possible so the player has more time to react and prepare. This also opens up more possibilities for future mechanics, so in the long run, I think I've made the best choice here.

Now, let's get into what I've been and/or will be working on that you haven't seen yet!

Act 2's Boss The music for the Act 2 Boss is  nearly complete! I'll likely be starting to animate it pretty soon. This song is the longest one I've done so far, clocking at a duration of a little over 3 minutes long!

More Animation Updates for Stir & Mix At this point, I've done even more cleanups on the sequence you saw in the last devlog and I've finished animating the "I wanna" scene of the song, which will probably have the most changes out of any other scene in the song. When I first animated Stir & Mix, I didn't quite have the time or skills to do everything I really wanted to do with it. That scene in particular I felt was WAY too stiff and boring, especially compared to the more dynamic and fluid scenes that appear in some of the other the stages now. I'd say I'm about halfway done retouching all the animations for this one!

Refined Model Sheets I don't talk about these very often, but sometime around 2023 I started using model/reference sheets for the characters. (I might show them off someday, but for now they're staying private!) Before this point, the designs are pretty inconsistent from shot to shot, so this helped a lot with that. Recently, I've done some revisions I'm really pleased with. Their designs are finally becoming... well, final! I'll be reworking the affected characters' hub world sprites at some point to reflect these changes.

Slight Reworks for some Act 1 Songs On the sound side, Stir & Mix's vocals have been reworked again! As I've mentioned in the previous devlog, 2cada's tuning style and techniques have evolved a bit since we first started working together, so we thought it'd be fun to go back and incorporate some of that into it. We'll also probably be reworking the structure of Nami's song a little bit at some point just to make it a feel a bit more solid, which may require a new line or two from her voice actor, Meggie-Elise! So funnily enough, it seems some of the songs will have end up having TWO unused beta versions after this.

Also, a quick PSA: Please note that beta versions of content will NOT be included in the full game. I've heard people ask for them to be "brought back" or toggleable, but in my situation something like that is both easier said than done and I also just... don't want to LOL. With as many directions I can take this game, I know I can't satisfy everyone, but I can make a game that satisfies me, so I'm aiming for that! And hey, maybe other people will like it too.

I think that's all I wanna talk about for now! Thanks so much for reading. It can be a bit of a daunting task to write these at times, but I'm glad to keep you up to date on the project when I can.

-LJ

[aventurineswife]

Thank you for this SAHSRAU request

How would everyone react when they see the Full Destructive power of the Mech that the Creator is Piloting when they go Drill for Drill against an all powerful being that can do the same things that the Creator can do

(Tried to post one that I had but Damn it Tumblr can't handle it 😭)

Before seeing the Creator throw Straight hands against same being who can do the same things

(Damn Anti spiral is getting his ass beat ⁠(⁠゜•⁠゜⁠) )

YES. Oh yes.

SAHSRAU characters already see you as their untouchable divine programmer—but now you roll up in a divine mech suit that you coded yourself, and it’s not just pretty effects. It’s raw destruction, a cosmic drill-for-drill clash against a mirror entity—a false god with the same power set.

Your mech—this towering, luminous construct—rips through the space-time seam, glitching between animation frames, shimmering with debugging code, corrupted geometry phasing around its limbs. And when you go toe-to-toe with a false being that mirrors your power? Drill colliding with drill?

It’s like watching Armageddon written in code.

The sky tears open.

Reality flickers like bad data.

And your followers?

They stop breathing.

Dan Heng

Silent. His breath hitches. His eyes track every move, analyzing, memorizing.

“That power… that control… and they built it themself.”

But what truly shakes him is seeing you step out of the mech—injured, drained, but furious. You throw your hood back, eyes glowing with glitch-light—and then throw a bare-knuckle punch into the false god’s face. And it lands.

Dan Heng doesn’t know whether to kneel or follow you into battle.

Kafka

“Oh.”

Her voice is a whisper. Reverent. Almost… turned on.

“That’s them. That’s our Creator.”

She watches you spiral through data projectiles and rip a drill out of thin air like you're dragging it from another game engine. When you dropkick your copy through a terrain patch and keep fighting with bare fists, she doesn’t cheer. She smiles.

She's never believed in gods.

Until you chose violence with style.

Silver Wolf

Screaming. Shaking. Crying. Hacking the UI in real-time to get a better angle.

“HOLY CRAP—THEIR HITBOX IS UNDEFINED—

THAT’S A CUSTOM MOVESET.

THE CREATOR HARD-CODED A COUNTER-MOVE TO THEIR OWN ABILITIES.”

She’s bouncing in her chair, glitching with actual tears, watching you override the very engine the fight’s happening in. When you glitch-punch your clone so hard its form reverts to wireframe?

She stares at the screen and whispers, “I want to marry them.”

Blade

He stands. Slowly. Every inch of him is vibrating. Rage, awe, maybe even hope.

You’re bleeding. You’re exhausted. But you refuse to stop. You refuse to lose. You punch and claw and override and fight with everything you have—not for godhood, but for truth.

He sees himself in your refusal to break. And for the first time in years, Blade says softly:

“You are real.”

Welt

He’s quiet. But his expression is shaken—like someone who just witnessed a prophecy fulfilled.

“They… rewrote their own limits. In real-time.”

Watching you defy logic itself—fighting another being with your same broken capabilities and winning anyway—Welt realizes something chilling:

If you can do that… then you’re not just god.

You’re beyond the Aeons.

March 7th

Tears streak down her face. Her camera dangles from her neck, forgotten.

“I knew they were cool but—LOOK AT THEM!!!”

She’s clutching Pom-Pom and screaming encouragement, gasping as you suplex your own copy through the HUD. She doesn’t care about perfection—just that you’re fighting.

And when you emerge from the rubble, scarred and triumphant?

She shouts, “THAT’S MY CREATOR!!”

Herta

The woman who once dismissed you as a curiosity?

Now she’s trembling.

She’s watching you manipulate systems she created. Rewrite physics she helped govern. Win a fight where you shouldn’t have won.

“Impossible…”

“No. It’s inevitable. They’re the one.”

This is the moment the SAHSRAU characters realizes:

You didn’t just log into their world.

You reformatted it with your fists.

You didn’t win because you were stronger.

You won because you believed in your own design more than the imposter did.

And now?

They don’t just revere you.

They stand behind you, ready for the next battle—because they know:

If the Creator can throw hands with a god,

then maybe… they can change the system too.

[whittlewillow]

Experiment on Slugpups

Here is an informal log of an informal experiment I did a while ago.

I'm unsure what mods I had enabled at the time, unfortunately other than Visible IDs, Pups+, and Debug Visualizer.

Anyways, this was a study MAINLY to determine the cause of a phenomenon I called "The Insanity", which is where in scenarios where there are many untamed slugpups in an arena seemed to sometimes become afflicted with "The Insanity", and would begin pacing back and forth, occasionally throwing spears and killing other slugpups, or even repeatedly stabbing dead slugpups.

Spoilers, but it was determined that the cause was that I had been adding and then deleting food like batflies or eggbugs, or threats like lizards and centipedes, which slugpups were inclined to attack. I would delete them, but the slugpups wouldn't realize they were deleted; their AI still detected them as existing, stationary in the spot they were deleted in, so they would repeatedly throw rocks and spears in a futile attempt to hunt the food or dispatch the threat, accidentally killing other slugpups in the process.

Anyways,

Beyond that, this is a straight contextless copy/paste. I can elaborate on anything if you ask :3

Please let me talk to you about slugpups PLEASE

-

2 pups, empty chamber, no weapons or food, neither detect a threat or prey.

Added a green lizard, they detect it as a threat.

Green lizard is immediately removed. They continue to track that there is a threat tracked (one creature) and the red ThreatTracker metre doesn’t lower. Despite it no longer existing, the green lizard’s tracker doesn’t disappear, and persists, frozen in time, for the remainder of the experiment.

They proceed to both stay perfectly still for quite a while, occasionally mewing or looking at one another. I thought for a moment the game had froze.⭐

One of them was lying down, but stood up when I used the mouse to make it.

Moving a pup to another spot of the chamber made it immediately run back to their original spot, very briefly pacing back and forth before arriving.

The pup which was lying own before eventually lied down again. It has a low Energy stat, unlike the other pup.

High energy (standing) pup is moved from it’s preferred spot and placed elsewhere in the chamber, it immediately walks back to it’s preferred spot much like it’s sibling did.

A blue fruit is placed in between them, equal distance. They don’t react and neither does their trackers. The energetic pup is a tundrapup, and thus won’t eat meat.⭐

Blue fruit is placed directly next to tundrapup. No reaction.

Blue fruit is used to shove tundrapup around. It briefly paces back and forth before settling back in it’s preferred spot.

Ditto with the regularpup, still no abnormal reaction or desire to eat it.

For unclear reasons, the regular pup seems to twitch once. The blue fruit is next to it and it pushes it slightly, likely not intentionally.

Second attempt is made to give the blue fruit to regularpup, but still no desire to eat it is shown.

This whole time they are continuing to stand in place, occasionally mewing in unison (likely because they were spawned at the same time) Sometimes the low-energy regularpup will lie down or stand up, but never naps. They have not stopped detecting the presence of a threat (the green lizard), and their red metres have not change since it’s deletion. They seem to be unaware of the non-existent lizard’s location, which might explain their relative stillness.

The blue fruit is deleted. No reaction.

A spear is given to the regularpup. The second it lands next to them they throw it to the left (where the lizard used to be). It lands where the lizard was before it’s deletion, and the regularpup runs towards it. The tundrapup doesn’t react.

The regularpup (which has 0.00 agg) then proceeds to play fetch with itself, throwing the spear over and over again at the direction the green lizard originally was, and constantly chasing it’s own spear where it lands so it can repeat the process.⭐

The tundrapup continues to not react, standing in it’s preferred place as it’s sibling throws the spear back and forth. They are both still constantly tracking each other as Pack.

There is no sign of regularpup stopping it’s rampage against the ghost of the green lizard, so the spear is deleted.

The regularpup paces back and forth where the spear had landed as if it still detects it’s presence, presumably a similar bug to the green lizard.

While the regularpup paces frantically, looking for it’s spear, the tundrapup is given an edible neuron. It doesn’t react or pick it up, and it lies on the floor in front of the pup as it mews for food.

A bomb is placed near to where the spear it’s looking for had landed.

Without major delay, the regularpup throws the grenade at the green lizard’s ghost. It explodes and scares the tundrapup, though it is well out of the bomb’s radius.

The regularpup continues to pace back and forth, presumably still looking for it’s spear, while the tundrapup now paces back and forth around it’s preferred spot in panic.⭐

Their trackers seem almost unaffected. I’m unsure if this is a new development or just something I didn’t notice before, but their red metres are now fluctuating, just slightly, by a few millimetres maybe.

The pup’s metres seem to slightly increase when nearer to the green lizard’s ghost and decrease farther from it. They are both on either side of the testing chamber and cannot get farther from the lizard’s ghost without help.

Using the mouse, the regularpup is lifted into the air, away from the lizard’s ghost. It’s threat metre decreases significantly, and then increases back to what it was before when placed on the ground. The pup continues it’s frantic pacing.

The redundant neuron fly is removed from the chamber. No reaction.

A second green lizard is added, and then immediately removed from the chamber.

As expected, it adds another “ghost tracker” and convinces the pups there’s another threat.

A batfly is placed on the regularpup, which is immediately grabbed.

The batfly is now tracked as prey (Eats 0.5) by both slugpups, but instead of eating it, the regularpup continues to pace back and forth like it was before, but now holding the batfly.

The regularpup is dragged to the top corner of the screen, away from the green lizard ghosts, and it’s ThreatTracker’s metre slowly decreases. It’s assumed it decreases slowly due to it’s high nervousness stat.

The slugpup wiggles around in the air, holding the batfly, but never eats it, even once it’s threat metre is down to presumably 0.

In order to read it’s stats more clearly, the slugpup is shaken so it drops the batfly. The slugpup drops the batfly and is placed back on the ground where it continues pacing.

2 attempts are made to give the batfly to the slugpup again, but it doesn’t pick it up, even though it’s still being tracked as prey and as Eat 1.0.⭐

The dead batfly is given to the tundrapup, but it doesn’t seem to react besides it’s PreyTracker metre now fluctuating as it notices and stops noticing the batfly.

Chamber is restarted, removing all things from it. It seems all creatures are still being tracked, however.

A new slugpup is added to the chamber. It doesn’t seem to track the green lizard’s or other slugpups ghosts, so it’s possible it’s a graphical error.

The game has to be restarted to make the trackers disappear.

Experiment concluded.

-

To research:

“They proceed to both stay perfectly still for quite a while, occasionally mewing or looking at one another. I thought for a moment the game had froze.” Why did the frightened slugpups stand still?

“A blue fruit is placed in between them, equal distance. They don’t react and neither does their trackers. The energetic pup is a tundrapup, and thus won’t eat meat.” Why did the frightened slugpups refuse food?

“The regularpup (which has 0.00 agg) then proceeds to play fetch with itself, throwing the spear over and over again at the direction the green lizard originally was, and constantly chasing it’s own spear where it lands so it can repeat the process.” Why was such a low-agg slugpup so ready to attack? Why did it make chasing the spear such a priority?

“The regularpup continues to pace back and forth, presumably still looking for it’s spear, while the tundrapup now paces back and forth around it’s preferred spot in panic.” Why was the tundrapup so frightened by the explosion, and why for so long? Could it be related to the pressure from the presence of the lizard ghost, or is it unrelated?

“2 attempts are made to give the batfly to the slugpup again, but it doesn’t pick it up, even though it’s still being tracked as prey and as Eat 1.0.”Why did the slugpup pick up the batfly the first time, but then never again? Is it because it’s dead?

[lazar-codes]

16/04/2025

Paired Actors - Log #4

I actually managed to do 90% of what I wanted to do today! I wanted to add a dropdown menu to select an actor, if the current one has the same name as other ones. I did this using the react-select component, because that let me add photos in the dropdown menu (it would be pretty pointless to do a dropdown menu of the actor names without any other identifiable features if the names are all the same). Because list of actors of the same name changes depending on the input, the options had to change dynamically too. That wasn't too hard.

The problem that I'm having now is that I sometimes need to hit the "search" button twice before getting results. I think I know what the problem is, but I'm not 100% certain. So...more debugging on the way. But I'm really happy I got this functionality out of the way! After this, I'll have to style it for mobile, but then I can upload this version and make it usable for the public!

[cognithtechnology]

Simplify Your React Native Debugging Process Simplify your React Native debugging process with these expert tips. Explore various tools and methods to troubleshoot and resolve issues effortlessly.

[roydkill]

I really liked your drawing about the idea of Maxime having his cockroach body restored (by the AVL?) once he got into prison but still having phantom sensation and pain, could you expand more on that? How does he deal with it? Does he ask for help or is he too prideful to and stomachs it? (FYI if he has more phantom pain than phantom sensation bless his soul because he’s going to snap eventually, that sh$t attacks you out of nowhere and it would be interesting to see how he would react) 👏

Thank you so much for the ask!

I think when the issues first start he’d tell the AVL about it but they definitely wouldn’t be sympathetic - giving him some weak pain medication and telling him to suck it up

I doubt the AVL would manage to completely debug (ha!) him, as he seems to be more cockroach than those hit with the cockroach ray. Instead, they’d probably come up with some sort of treatment to be taken regularly to keep his abilities in line. (Perhaps a procedure of some sort, or a drug, and who knows if the process itself is painful) At first, Maxime would just be annoyed about it, complaining and cursing, but the physical side effects would hit soon as the symptoms, both the pain and itchiness would worsen as the next treatment draws near.

There’s a certain restlessness and a tightness under his skin, something that would get unbearable as the next treatment dose approaches. The itching he’d feel on his skin and phantom bug parts would range from annoying to unbearable; sometimes he scratches himself until he draws blood, and sometimes he can simply tune it out. The physical need to spread his wings is overwhelming, and he’d do anything to be able to do it

The pain first hits him out of nowhere one day when he’s sitting in the prison cafeteria - quick, stinging pain unlike anything he’s felt before. He definitely wouldn’t be able to hide the worst pains, as he’d freeze in place with his face full of terror, but a lesser pain flare would only be noticed by a twitch in his eye or by general fidgeting

I think at first he’d struggle to tell others about the full extent of the situation, instead handling it by being angry, easily irritated and jumpy and perhaps acting out, rebelling against the AVL to somehow try and ease his utter disdain for them and what they’re doing to him. as a punishment the AVL starts ”forgetting” to give him any pain medication from time to time.

Val would quickly notice even the slightest changes in his behaviour and will try to help him the best she can, whether it be massaging his back or keeping him from hurting himself. I like to think of Val, Maxime and Bratt as this trio in prison, so once Maxime’s warmed up to Bratt he’d eventually have both of them taking care of him when need be. I doubt he’d still ask for help, instead relying on them to realize when shit hits the fan. He’s so thankful though, and will try to make it up by doing favors in return

(when night falls and everyone’s locked in their cells, they can sometimes hear soft sobbing from Maxime’s cell - unable to go comfort him through the pain)

On a lighter note… Maxime instinctively watches out to not hurt Valentina or Balthazar with the sharp spines of his cockroach appendages, still forgetting they’re no longer part of him

Huge thanks to @roachroost for bouncing some of these ideas around with me! Obligatory mention of english not being my first language + I’m very new to writing my thoughts down, i hope these made sense! I’d love hear anyone else’s thoughts