1
General (but related to Code::Blocks) / Re: Please patch PHP2Shell before this forum gets hacked
« Last post by ollydbg on Today at 01:25:44 pm »I will send an email to our site manager about this issue, thanks.
News:
As usual while waiting for the next release - don't forget to check the nightly builds in the forum.
Recent Posts
2
Using Code::Blocks / Re: U4GM Arc Raiders Tactics for Breaking Contact Safely
« Last post by Miguel Gimenez on Today at 11:25:55 am »All you spams have been reported to moderator.
3
General (but related to Code::Blocks) / Re: Welcome Newcomers - PLEASE READ!!!
« Last post by 1fuhd on Today at 07:50:22 am »here I am
4
Using Code::Blocks / U4GM Arc Raiders Tactics for Breaking Contact Safely
« Last post by Benniehench03 on Today at 04:33:27 am »In ARC Raiders, a firefight can be won and still leave you in a losing position when another squad controls the safest exit. The key is recognizing when trading shots has stopped creating progress and has started shrinking your choices. Reviewing ARC Raiders BluePrints can sharpen your sense of risk before you enter a contested area.
Retreating early is not automatically cautious play; it preserves options. Check armor, healing supplies, and nearby cover, then compare them with the enemy's angle. If every movement leads into the same firing lane, the fight is no longer mainly about aim. It has become a route-planning problem, and leaving together may be strongest.
Recognize When the Exit Has Closed
Read the exit before committing to another burst. A squad holding high ground or a narrow doorway can make a push costly even after you damage one opponent. Check whether their cover overlaps your path, and move before they can reset.
Sound reveals more than a health bar. Footsteps, reloads, and sudden silence can show whether the other team is rotating or waiting. Do not sprint after hearing danger; pause behind cover, identify the next safe break, and avoid a blind turn.
Let Terrain Break the Fight
Use terrain to change the angle instead of simply increasing distance. Move from one solid cover piece to the next, cross only when line-of-sight is broken, and favor walls, slopes, or elevation changes over exposed ground. The goal is to deny a clean shot.
Judge alternative routes by cover, noise, and timing, not distance. A longer path through dependable terrain is better than a rumored map shortcut that leaves you visible. Before moving, decide where the next sight break will be so the retreat stays deliberate.
Keep the Retreat Cohesive
Small squads are safest when they retreat as a compact group with enough spacing to avoid one burst hitting everyone. Keep one teammate watching the rear while others move to cover, then switch roles. Scattering in different directions gives the opposing squad isolated targets.
For a solo player, choose one escape line and protect it with patience. Break sight, wait for footsteps or shots to shift away, and move only after the nearest threat loses a clear angle. A small squad can use a quick call to regroup before crossing open space.
Use Pressure Only to Create Space
A brief counterattack can create space when an opponent overextends, reloads, or exposes the player watching the exit. Fire only long enough to force them behind cover; do not turn the opening into a chase. As attention shifts, take the planned route and keep moving.
Successful disengagement is measured by preserved options, not distance traveled. Alone or with teammates, favor clear decisions, shared movement, and terrain that interrupts sight. Players who choose to buy ARC Raiders BluePrints should treat preparation as support for better judgment, then leave before the fight demands a perfect escape.
Retreating early is not automatically cautious play; it preserves options. Check armor, healing supplies, and nearby cover, then compare them with the enemy's angle. If every movement leads into the same firing lane, the fight is no longer mainly about aim. It has become a route-planning problem, and leaving together may be strongest.
Recognize When the Exit Has Closed
Read the exit before committing to another burst. A squad holding high ground or a narrow doorway can make a push costly even after you damage one opponent. Check whether their cover overlaps your path, and move before they can reset.
Sound reveals more than a health bar. Footsteps, reloads, and sudden silence can show whether the other team is rotating or waiting. Do not sprint after hearing danger; pause behind cover, identify the next safe break, and avoid a blind turn.
Let Terrain Break the Fight
Use terrain to change the angle instead of simply increasing distance. Move from one solid cover piece to the next, cross only when line-of-sight is broken, and favor walls, slopes, or elevation changes over exposed ground. The goal is to deny a clean shot.
Judge alternative routes by cover, noise, and timing, not distance. A longer path through dependable terrain is better than a rumored map shortcut that leaves you visible. Before moving, decide where the next sight break will be so the retreat stays deliberate.
Keep the Retreat Cohesive
Small squads are safest when they retreat as a compact group with enough spacing to avoid one burst hitting everyone. Keep one teammate watching the rear while others move to cover, then switch roles. Scattering in different directions gives the opposing squad isolated targets.
For a solo player, choose one escape line and protect it with patience. Break sight, wait for footsteps or shots to shift away, and move only after the nearest threat loses a clear angle. A small squad can use a quick call to regroup before crossing open space.
Use Pressure Only to Create Space
A brief counterattack can create space when an opponent overextends, reloads, or exposes the player watching the exit. Fire only long enough to force them behind cover; do not turn the opening into a chase. As attention shifts, take the planned route and keep moving.
Successful disengagement is measured by preserved options, not distance traveled. Alone or with teammates, favor clear decisions, shared movement, and terrain that interrupts sight. Players who choose to buy ARC Raiders BluePrints should treat preparation as support for better judgment, then leave before the fight demands a perfect escape.
5
Using Code::Blocks / U4gm Hero Siege Defensive Gear Evaluation Guide
« Last post by Benniehench03 on Today at 04:18:21 am »In Hero Siege, defensive gear earns its place when it lets a character keep attacking instead of stopping to recover or retreat. When comparing Hero Siege Items, read each modifier against the damage you actually take, the distance you fight from, and the skills you need to land reliably.
A higher damage figure can look decisive on a character sheet, but it does not show how often attacks are interrupted. A modest defensive trade may produce steadier damage over a full encounter, while the same trade may add little for a character that already avoids most incoming hits.
Read modifiers in the context of your build
Start with the exact item text. An increase to maximum health gives room to survive a mistake, while resistance helps against the damage type it names. Damage reduction can soften repeated hits, and block or dodge chance depends on the character's mechanics and the attacks faced. These effects are not interchangeable.
Then identify what is ending your damage windows. If a close-range character repeatedly loses health before completing a skill sequence, extra durability may help more than another offensive modifier. A ranged build that rarely takes hits may gain more from damage, provided it can maintain safe positioning.
Compare damage on equal terms
To judge an offensive setup against a defensive one, keep the character, skills, difficulty, and encounter as consistent as possible. Record how long it takes to finish several similar groups, how often you must retreat, and whether key attacks complete. A single fast run can hide the cost of a fragile setup.
Compare the same measures with the defensive item equipped. If clear times rise slightly but interruptions and recovery breaks fall, the practical damage gap may be smaller than the character sheet suggests. If the defensive modifier does not change how long you stay active, its opportunity cost may not be worthwhile for that build.
Ordinary enemies reward a different balance
During routine clearing, enemies may be spread out and deal manageable damage. A setup focused on offense can remove threats before they surround the character, making added toughness less valuable. This is especially relevant when attacks cover a wide area and ordinary encounters end quickly.
But close-range characters can face repeated contact while moving between groups. A little more health or relevant resistance may prevent a forced pause after each pack. Judge the result across several rooms: smoother movement and fewer retreats can make a defensive choice feel faster, even if each enemy takes longer to defeat.
Boss fights test reliable execution
A boss encounter places greater weight on surviving predictable attack patterns and finishing skills during safe openings. If a character must leave range after one mistake, defensive modifiers can create more chances to deal damage. Resistance is useful only when it matches the threat; health or avoidance may serve better against another pattern.
Repeat the same boss attempt with each setup and note completed skill sequences, time spent repositioning, and survival. Avoid drawing a firm conclusion from one run, since movement and timing vary. Choose the gear that supports your actual approach, not a stat that is assumed to benefit every class.
The best defensive modifier is the one that addresses a real weakness without costing more damage than it returns through steadier play. Recheck your needs as skills and encounters change, and consider Hero Siege Items for sale only as part of that broader comparison.
A higher damage figure can look decisive on a character sheet, but it does not show how often attacks are interrupted. A modest defensive trade may produce steadier damage over a full encounter, while the same trade may add little for a character that already avoids most incoming hits.
Read modifiers in the context of your build
Start with the exact item text. An increase to maximum health gives room to survive a mistake, while resistance helps against the damage type it names. Damage reduction can soften repeated hits, and block or dodge chance depends on the character's mechanics and the attacks faced. These effects are not interchangeable.
Then identify what is ending your damage windows. If a close-range character repeatedly loses health before completing a skill sequence, extra durability may help more than another offensive modifier. A ranged build that rarely takes hits may gain more from damage, provided it can maintain safe positioning.
Compare damage on equal terms
To judge an offensive setup against a defensive one, keep the character, skills, difficulty, and encounter as consistent as possible. Record how long it takes to finish several similar groups, how often you must retreat, and whether key attacks complete. A single fast run can hide the cost of a fragile setup.
Compare the same measures with the defensive item equipped. If clear times rise slightly but interruptions and recovery breaks fall, the practical damage gap may be smaller than the character sheet suggests. If the defensive modifier does not change how long you stay active, its opportunity cost may not be worthwhile for that build.
Ordinary enemies reward a different balance
During routine clearing, enemies may be spread out and deal manageable damage. A setup focused on offense can remove threats before they surround the character, making added toughness less valuable. This is especially relevant when attacks cover a wide area and ordinary encounters end quickly.
But close-range characters can face repeated contact while moving between groups. A little more health or relevant resistance may prevent a forced pause after each pack. Judge the result across several rooms: smoother movement and fewer retreats can make a defensive choice feel faster, even if each enemy takes longer to defeat.
Boss fights test reliable execution
A boss encounter places greater weight on surviving predictable attack patterns and finishing skills during safe openings. If a character must leave range after one mistake, defensive modifiers can create more chances to deal damage. Resistance is useful only when it matches the threat; health or avoidance may serve better against another pattern.
Repeat the same boss attempt with each setup and note completed skill sequences, time spent repositioning, and survival. Avoid drawing a firm conclusion from one run, since movement and timing vary. Choose the gear that supports your actual approach, not a stat that is assumed to benefit every class.
The best defensive modifier is the one that addresses a real weakness without costing more damage than it returns through steadier play. Recheck your needs as skills and encounters change, and consider Hero Siege Items for sale only as part of that broader comparison.
6
General (but related to Code::Blocks) / U4gm POE2 Boss Guide to Better Damage Uptime
« Last post by Benniehench03 on Today at 04:07:53 am »Boss damage in Path of Exile 2 is less about pressing every skill as soon as it is ready than recognizing when an opening can support a complete sequence. Whether you are preparing gear with POE 2 Orbs or refining a current setup, the decisive skill is reading recovery rather than forcing a rehearsed pattern into every fight.
A safe window is more than a pause. Watch what happens after the boss commits to a heavy move, how soon it can act again, and whether hazards linger during recovery. These details reveal how long you can attack without guessing.
Read the Opening Before Spending It
Watch for a committed animation: a charge ending in a fixed direction, a slam followed by a pause, or a projectile pattern that leaves a clear lane. The opening begins when the threat has passed, not when its windup starts. Acting too early can mean your skill is interrupted before damage registers.
Estimate the full cost of a sequence, including targeting, travel, and recovery. If the boss starts another attack before it ends, use one reliable skill and a quick follow-up. A window is safe enough only when you can finish and still react.
Match Your Range to the Risk
Close-range builds must account for the return path as well as the opening. A heavy strike may connect, yet leave you inside a sweeping follow-up. Favor skills with short animation locks while the boss remains active, and step in only after its attack has committed.
Ranged characters have more room, but distance is no guarantee. Tracking shots, ground effects, and arena edges can close a comfortable lane. Keep an escape route clear, and avoid dodging every minor cue; needless movement spends stamina or a repositioning skill and may cost the next clean cast.
Save Cooldowns for Real Opportunities
Treat movement skills as part of the damage plan, not as reflexes. Save a fast reposition for attacks that cannot be sidestepped safely, while ordinary footwork preserves it for a dangerous phase. Hold major cooldowns if the boss is about to leave or become untargetable, then spend them when a longer opening appears.
Recovery matters on both sides. After a high-commitment skill, leave time to move or guard, and be ready to stop if the boss signals another attack. A smaller burst that ends with control can yield more damage across the encounter than an impressive sequence followed by a long retreat.
After each attempt, review interrupted skills, movement that carried you away from a safe target, and time spent waiting despite an available action. Change one decision at a time and test it against the same cue. If you choose to buy POE 2 Orbs, treat the upgrade as support for sound timing, not a substitute for it.
A safe window is more than a pause. Watch what happens after the boss commits to a heavy move, how soon it can act again, and whether hazards linger during recovery. These details reveal how long you can attack without guessing.
Read the Opening Before Spending It
Watch for a committed animation: a charge ending in a fixed direction, a slam followed by a pause, or a projectile pattern that leaves a clear lane. The opening begins when the threat has passed, not when its windup starts. Acting too early can mean your skill is interrupted before damage registers.
Estimate the full cost of a sequence, including targeting, travel, and recovery. If the boss starts another attack before it ends, use one reliable skill and a quick follow-up. A window is safe enough only when you can finish and still react.
Match Your Range to the Risk
Close-range builds must account for the return path as well as the opening. A heavy strike may connect, yet leave you inside a sweeping follow-up. Favor skills with short animation locks while the boss remains active, and step in only after its attack has committed.
Ranged characters have more room, but distance is no guarantee. Tracking shots, ground effects, and arena edges can close a comfortable lane. Keep an escape route clear, and avoid dodging every minor cue; needless movement spends stamina or a repositioning skill and may cost the next clean cast.
Save Cooldowns for Real Opportunities
Treat movement skills as part of the damage plan, not as reflexes. Save a fast reposition for attacks that cannot be sidestepped safely, while ordinary footwork preserves it for a dangerous phase. Hold major cooldowns if the boss is about to leave or become untargetable, then spend them when a longer opening appears.
Recovery matters on both sides. After a high-commitment skill, leave time to move or guard, and be ready to stop if the boss signals another attack. A smaller burst that ends with control can yield more damage across the encounter than an impressive sequence followed by a long retreat.
After each attempt, review interrupted skills, movement that carried you away from a safe target, and time spent waiting despite an available action. Change one decision at a time and test it against the same cue. If you choose to buy POE 2 Orbs, treat the upgrade as support for sound timing, not a substitute for it.
7
General (but related to Code::Blocks) / U4gm Aion 2 Sorcerer Tips for Verifying Skill Fixes
« Last post by Benniehench03 on Today at 04:00:19 am »Elevation can turn a straightforward Sorcerer rotation into a question of geometry, which is why preparing useful Aion 2 Items can be worthwhile before returning to difficult encounters. A spell that looks reliable on level ground may deserve a closer look when the caster, target, and impact point occupy different heights.
The October 14 update addressed reported Sorcerer skill issues involving elevation differences, including Fire Wall and other affected skills. The practical lesson is not to assume every positioning problem has disappeared, but to check how those abilities behave in the current client and separate a corrected interaction from an ordinary execution mistake.
What the October 14 Update Means in Practice
Fire Wall is a practical starting point because its effect is easy to observe against a visible target. Watch whether the cast completes, whether the visual effect appears where expected, and whether an eligible enemy interacts with it. Those observations are more useful than judging the spell from one damage number.
Keep the patch detail in perspective. The confirmed change concerns reported skill behavior around elevation; it does not establish an undocumented increase or reduction in damage. If numbers seem different, record the conditions and repeat the test before drawing a balance conclusion.
Find Terrain That Makes Differences Visible
An open area with level ground, a short ledge, and a visible slope offers useful comparisons without too many variables. Avoid crowded fights, moving platforms, or enemies that change distance quickly. The goal is a clear view of the connection between position and result.
Begin on level ground and choose a fixed landmark for casting distance. Then move only the caster or the target to a higher or lower surface. Keep the camera angle similar, since a poor view can make a successful effect look misplaced even when the ability worked correctly.
Test the Skill, Then Test Your Assumptions
A failed result is not automatically an elevation issue. The target may have stepped outside the area, become invulnerable, or been selected too late. A spell can also be interrupted before its effect appears. Check cast completion, target status, distance, and movement before blaming the slope.
For a repeatable check, use one skill and comparable targets. Make several casts from level ground, then repeat them from the same horizontal distance while changing only the elevation. Note whether the effect appears and whether the target is affected each time. If the result changes only after the height changes, terrain deserves attention; if the same miss occurs on level ground, timing or targeting is more likely.
After the October 14 fix, Sorcerers have a stronger reason to retest elevation-sensitive skills with patience. Controlled comparisons can show whether Fire Wall is functioning as intended, whether the issue is ordinary timing, or whether a particular terrain shape still deserves attention. Players preparing for that test can review cheap Aion 2 Items while keeping every conclusion grounded in observable, current gameplay.
The October 14 update addressed reported Sorcerer skill issues involving elevation differences, including Fire Wall and other affected skills. The practical lesson is not to assume every positioning problem has disappeared, but to check how those abilities behave in the current client and separate a corrected interaction from an ordinary execution mistake.
What the October 14 Update Means in Practice
Fire Wall is a practical starting point because its effect is easy to observe against a visible target. Watch whether the cast completes, whether the visual effect appears where expected, and whether an eligible enemy interacts with it. Those observations are more useful than judging the spell from one damage number.
Keep the patch detail in perspective. The confirmed change concerns reported skill behavior around elevation; it does not establish an undocumented increase or reduction in damage. If numbers seem different, record the conditions and repeat the test before drawing a balance conclusion.
Find Terrain That Makes Differences Visible
An open area with level ground, a short ledge, and a visible slope offers useful comparisons without too many variables. Avoid crowded fights, moving platforms, or enemies that change distance quickly. The goal is a clear view of the connection between position and result.
Begin on level ground and choose a fixed landmark for casting distance. Then move only the caster or the target to a higher or lower surface. Keep the camera angle similar, since a poor view can make a successful effect look misplaced even when the ability worked correctly.
Test the Skill, Then Test Your Assumptions
A failed result is not automatically an elevation issue. The target may have stepped outside the area, become invulnerable, or been selected too late. A spell can also be interrupted before its effect appears. Check cast completion, target status, distance, and movement before blaming the slope.
For a repeatable check, use one skill and comparable targets. Make several casts from level ground, then repeat them from the same horizontal distance while changing only the elevation. Note whether the effect appears and whether the target is affected each time. If the result changes only after the height changes, terrain deserves attention; if the same miss occurs on level ground, timing or targeting is more likely.
After the October 14 fix, Sorcerers have a stronger reason to retest elevation-sensitive skills with patience. Controlled comparisons can show whether Fire Wall is functioning as intended, whether the issue is ordinary timing, or whether a particular terrain shape still deserves attention. Players preparing for that test can review cheap Aion 2 Items while keeping every conclusion grounded in observable, current gameplay.
8
General (but related to Code::Blocks) / Re: crash at copy&paste on wsl
« Last post by Kayn on Yesterday at 05:31:17 pm »Hi,
I'm happy to confirm that the proposed fix is effective. Works like a charm
👍
Kayn
I'm happy to confirm that the proposed fix is effective. Works like a charm
👍Kayn
9
General (but related to Code::Blocks) / Please patch PHP2Shell before this forum gets hacked
« Last post by Михаил Агарков on Yesterday at 04:15:16 pm »A new vulnerability in PHP allows remote code execution. As a result, all active websites that use PHP have temporarily shut down their site to protect themselves until a patch is out. From what I understand, this forum also uses PHP. Please take action before it gets nuked.
https://www.php.net/archive/2026.php#2026-10-21-5
https://nvd.nist.gov/vuln/detail/CVE-2026-109618
https://nvd.nist.gov/vuln/detail/CVE-2026-109619
https://www.php.net/archive/2026.php#2026-10-21-5
https://nvd.nist.gov/vuln/detail/CVE-2026-109618
https://nvd.nist.gov/vuln/detail/CVE-2026-109619
10
Development / Re: svn rev 13798 issue?
« Last post by Miguel Gimenez on October 20, 2026, 11:31:14 am »Profile spammer reported to moderator.