4HONOR: forum

[image: i.imgur.com]

YouTube video Q5E10-v2gtQ

*This post is satire and is purely for entertainment.  It includes language some may find offensive.

Click here for the uncensored version.

Bug Report: Bounty ID-10t Error.

Category: Game Mechanics

Priority: equivalent to intelligence. Currently Low

Issue:

Torn provides a fully functional bounty system with no exceptions coded in. However, if a player dares to use this working as intended feature on a staff member, they are swiftly informed that this is not allowed Due to an “ID-10t error”. Essentially, the system executes perfectly, but the moment you follow its logic, you trigger a manual exception: Because We Said So™.

This creates an interesting contradiction where the system encourages an action that is later deemed a violation, Like providing a perfectly documented API, then banning developers for making requests.

To make things even more ridiculous, the Reason text field happily accepts blank submissions, meaning I can place a now-forbidden staff bounty without even pretending to justify it. No input validation, no error handling—just pure, unfiltered oops. If staff bounties are so forbidden, why does the system roll out the red carpet and throw in a free null pointer exception?

Steps to Reproduce:

1. Open a Torn Staff member’s profile. Brace for smells.

2.  Click the “Bounty” button. Oh look, it works!
   
   

3. Enter literally anything—or better yet, leave the reason field blank because Torn apparently operates on a “no context needed” policy.
   
   

                 4. Place the bounty. Caution: Staff are temperamental when hungry.

                 5. Get told, possibly with great passive aggression, that this is not allowed despite the game’s clear and enthusiastic                                       encouragement to do exactly that.

           

Compounding errors:

Once a user tries to debug the problem by speaking with staff, the ever-elusive ID-10t error strikes, causing a fatal exception in staff logic. As the bug propagates, responses become increasingly vague, paradoxical, and—when the error reaches critical severity—borderline philosophical. At this stage, debugging is impossible, as any attempt to seek clarification is met with a recursive loop of 'Because we said so' statements, eventually resulting in a stack overflow of nonsense. 

Steps to Reproduce:

1. Confront staff about permissions to bounty. (Staff may acknowledge that bounties are indeed a player mechanic and thus can be placed on anyone, including themselves.)
   
    
   
   
   

2. Wait a bit longer. (At this stage, an ID-10t error begins to manifest.)
   
   [image: i.imgur.com]

3. Observe the shift in staff response. You’ll likely receive a vague statement such as:

"Players are free to place bounties… except when they aren’t."

"We cannot confirm nor deny the existence of a bounty-related rule, but if one did exist, it would be subject to interpretation."    

                 4. Ask for further clarification. This will trigger another ID-10t error loop, potentially resulting in a Schrödinger’s Bounty scenario, where the bounty is both valid and invalid at the same time. Eventually, staff may attempt to resolve the conflict by making an unclear ruling, which in turn contradicts previous statements. This ruling may or may not be reversed at a later date, depending on how well your passive aggressive report is received.


   

if target == "staff" or target == "player":
user.bounty(target)     



 ID-10t Error causing a very strange crash.

 

 

System timed out. 

Expected Result:

-Place bounty button only works on those players that are accessible to have bounties placed on them.

-The reason for bounties are imperative because we have to input one, If they are allowed to stay blank it would logically mean the motivations for placing a bounty are completely irrelevant.

-Clear, consistent communication on whether placing a bounty on staff is allowed or not.

Actual Result:

-The button works on staff members who play warranting staff intervention, which in turn illuminates hypocrisy.  

-The "reason text field" allows a beautiful, poetic blank space, symbolizing the void in Torn’s logic.

-Staff agree until the ID-10t error throws an unhandled exception straight into stdout.

Possible fix:

-The bounty button should self-destruct upon attempting to click it, or at least trigger a pop-up that says, “Nice try, peasant.”

-The "reason text field" should force me to write “Bountied because actual asshole that happens to be staff” before submission.

 
-Have staff members roll a D20 before responding to these queries. A natural 20 results in a clear answer, while any other roll defaults to "It depends."

-Possibly not allowing players to also be staff.

*some conversations are abridged. This post is satire except when it isn't.

We want you to apply,

We are looking for active players that will chain and participate in wars.
We are also looking for members who will sign up to our discord and that communicate.
 
Yup, That's all! 

We pay for war hits, we provide Xanax for chaining and occasionally for training!
Our chains go up to 250! We offer help with earning merits and we love helping new players!
 
  
Move well, study well, play well, eat well, and rest well... That is the Turtle Master way!

[APPLY HERE]

[image: i.imgur.com]

YouTube video mlex9EndkgA

[image: i.imgur.com]

Additional notes:

Original post.

This post is not an appeal. It is not meant to provoke anyone to break the rules.
It IS an attempt to entertain you. If anything, use my experience as a cautionary tale. 

I *think* this is the reason for the warning.

[image: i.imgur.com]
Again it was never really explained what *the warning* is for and a request for clarity from me is now a "federal" offense. :)

I did ask Deep thought why it was a big deal and they came up with this.
[image: networkingnerd.net]
[image: i.imgur.com]

Real solutions:

The Initial Problem (and real reason my bounty was returned), putting unflattering descriptions so easily available to see.>

-Players can only see bounties from the newspaper unless they have a certain job, or bought the perk with points.
This would drive more traffic to the newspaper, as well encourage buying points.

Staff favoritism>
-Pay them, Remove the ability to do it, like it is on Devs. Make them choose between providing their services for money or playing the game.

-Or maybe give them an alternate Staff account that is flagged if these accounts (staff/player) interacts with the same user or themselves.

Song used: Imogen heap Earth

If this does gain any traction I feel the need to share the spotlight with a legitimate uncontroversial* cause.

California victim relief

(not sure if its against the rules to link to charities or not. But! if you ever were try to donate, I recommend find a safe charity. One you know will actually get money to the real victims)

*
...Slava Ukraini
...Free Palestine
...Her body, her choice
...Knibb High school football rules!

I think you guys are missing the point. I just want to be able to bounty "racist" on anybody's profile, staff included. I'm doing this for us.

ShieT! well at least you know it wasn't AI.

Here is an image Sugar put in the newsletter today. I believe it was inspired by my art last year. Then he used AI to rip me off... 
https://www.torn.com/newspaper.php#!/articles/2802

Here is my art posted a year ago:

https://www.torn.com/forums.php#/p=threads&f=2&t=16438369&b=0&a=0&start=320&to=25465337
 

This is a tale as old as time. 
This post has a very informed educational take on the subject:https://www.torn.com/forums.php#/p=threads&f=2&t=16450028&b=0&a=0

Happens...Here's a decent video essay on it.  

https://www.torn.com/forums.php#/p=threads&f=2&t=16450028&b=0&a=0

IDK but I feel like bumping this.

Here's an interesting piece on just that 

I've decoded it:

I wasn't even sure Chat GPT could say it. It turns out it can!
 

[image: media4.giphy.com]

Is there no honor in TORN anymore?

They letting you bag groceries now?

 "I'm sure i didn't learn anything,"

You may have a learning disability, and that's the nicest way I know how to say it. 

You right now.

*Just because you don't understand the words doesn't mean a computer wrote it, and yes I am a machine. 

[image: media2.giphy.com]

[image: i.imgur.com]

YouTube video Q5E10-v2gtQ

*This post is satire and is purely for entertainment.  It includes language some may find offensive.

Click here for the uncensored version.

That's fine bogie. Thank you for letting me speak my mind.

[image: i.imgur.com]

YouTube video mlex9EndkgA

[image: i.imgur.com]

Additional notes:

Original post.

This post is not an appeal. It is not meant to provoke anyone to break the rules.
It IS an attempt to entertain you. If anything, use my experience as a cautionary tale. 

I *think* this is the reason for the warning.

[image: i.imgur.com]
Again it was never really explained what *the warning* is for and a request for clarity from me is now a "federal" offense. :)

I did ask Deep thought why it was a big deal and they came up with this.
[image: networkingnerd.net]
[image: i.imgur.com]

Real solutions:

The Initial Problem (and real reason my bounty was returned), putting unflattering descriptions so easily available to see.>

-Players can only see bounties from the newspaper unless they have a certain job, or bought the perk with points.
This would drive more traffic to the newspaper, as well encourage buying points.

Staff favoritism>
-Pay them, Remove the ability to do it, like it is on Devs. Make them choose between providing their services for money or playing the game.

-Or maybe give them an alternate Staff account that is flagged if these accounts (staff/player) interacts with the same user or themselves.

Song used: Imogen heap Earth

If this does gain any traction I feel the need to share the spotlight with a legitimate uncontroversial* cause.

California victim relief

(not sure if its against the rules to link to charities or not. But! if you ever were try to donate, I recommend find a safe charity. One you know will actually get money to the real victims)

*
...Slava Ukraini
...Free Palestine
...Her body, her choice
...Knibb High school football rules!

test

I think you guys are missing the point. I just want to be able to bounty "racist" on anybody's profile, staff included. I'm doing this for us.

Bug Report: Bounty ID-10t Error.

Category: Game Mechanics

Priority: equivalent to intelligence. Currently Low

Issue:

Torn provides a fully functional bounty system with no exceptions coded in. However, if a player dares to use this working as intended feature on a staff member, they are swiftly informed that this is not allowed Due to an “ID-10t error”. Essentially, the system executes perfectly, but the moment you follow its logic, you trigger a manual exception: Because We Said So™.

This creates an interesting contradiction where the system encourages an action that is later deemed a violation, Like providing a perfectly documented API, then banning developers for making requests.

To make things even more ridiculous, the Reason text field happily accepts blank submissions, meaning I can place a now-forbidden staff bounty without even pretending to justify it. No input validation, no error handling—just pure, unfiltered oops. If staff bounties are so forbidden, why does the system roll out the red carpet and throw in a free null pointer exception?

Steps to Reproduce:

1. Open a Torn Staff member’s profile. Brace for smells.

2.  Click the “Bounty” button. Oh look, it works!
   
   

3. Enter literally anything—or better yet, leave the reason field blank because Torn apparently operates on a “no context needed” policy.
   
   

                 4. Place the bounty. Caution: Staff are temperamental when hungry.

                 5. Get told, possibly with great passive aggression, that this is not allowed despite the game’s clear and enthusiastic                                       encouragement to do exactly that.

           

Compounding errors:

Once a user tries to debug the problem by speaking with staff, the ever-elusive ID-10t error strikes, causing a fatal exception in staff logic. As the bug propagates, responses become increasingly vague, paradoxical, and—when the error reaches critical severity—borderline philosophical. At this stage, debugging is impossible, as any attempt to seek clarification is met with a recursive loop of 'Because we said so' statements, eventually resulting in a stack overflow of nonsense. 

Steps to Reproduce:

1. Confront staff about permissions to bounty. (Staff may acknowledge that bounties are indeed a player mechanic and thus can be placed on anyone, including themselves.)
   
    
   
   
   

2. Wait a bit longer. (At this stage, an ID-10t error begins to manifest.)
   
   [image: i.imgur.com]

3. Observe the shift in staff response. You’ll likely receive a vague statement such as:

"Players are free to place bounties… except when they aren’t."

"We cannot confirm nor deny the existence of a bounty-related rule, but if one did exist, it would be subject to interpretation."    

                 4. Ask for further clarification. This will trigger another ID-10t error loop, potentially resulting in a Schrödinger’s Bounty scenario, where the bounty is both valid and invalid at the same time. Eventually, staff may attempt to resolve the conflict by making an unclear ruling, which in turn contradicts previous statements. This ruling may or may not be reversed at a later date, depending on how well your passive aggressive report is received.


   

if target == "staff" or target == "player":
user.bounty(target)     



 ID-10t Error causing a very strange crash.

 

 

System timed out. 

Expected Result:

-Place bounty button only works on those players that are accessible to have bounties placed on them.

-The reason for bounties are imperative because we have to input one, If they are allowed to stay blank it would logically mean the motivations for placing a bounty are completely irrelevant.

-Clear, consistent communication on whether placing a bounty on staff is allowed or not.

Actual Result:

-The button works on staff members who play warranting staff intervention, which in turn illuminates hypocrisy.  

-The "reason text field" allows a beautiful, poetic blank space, symbolizing the void in Torn’s logic.

-Staff agree until the ID-10t error throws an unhandled exception straight into stdout.

Possible fix:

-The bounty button should self-destruct upon attempting to click it, or at least trigger a pop-up that says, “Nice try, peasant.”

-The "reason text field" should force me to write “Bountied because actual asshole that happens to be staff” before submission.

 
-Have staff members roll a D20 before responding to these queries. A natural 20 results in a clear answer, while any other roll defaults to "It depends."

-Possibly not allowing players to also be staff.

*some conversations are abridged. This post is satire except when it isn't.