Skip to content
View in the app

A better way to browse. Learn more.

LCPDFR.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Section136Callouts v1.12.1913.8 (Build 1913)

(25 reviews)

5 Screenshots

Could contain: dance, screenshot, person

 

Section136Callouts is a LSPDFR callout package featuring a verity of callouts which spice up your LSPDFR experience. Developed over nearly two years now, it certainly has the content to keep you on your feet in the city of Los Santos!

 

Support the pack!

99% of players will enjoy the pack for free. That's fine! However, if you'd like to chip in an financially support future development of the pack, then please consider taking out my Section136Callouts Early Access Club membership! For just £5.00 a month, you will receive all Section136Callouts beta builds with the freshest functionality, plus get a massive influence on what comes next! Get started at https://www.buymeacoffee.com/maxplayle

 

Join the conversation!

For discussion, information about upcoming updates, and more regarding Section136Callouts, LSPDFR in general and more - join my Discord server! You can join using the link: https://discord.gg/3bq88pY

 

Current Callouts

  • Area Search
  • Armed Suspect
  • Attempted Sexual Assault
  • Detainee Transport Required
  • Interior Burglary
  • Mental Health Patient Escaped
  • Officer Panic Button 
  • Person With Knife
  • Prisoner Transfer
  • Racing Vehicles
  • COVID-19 Self Isolation Violation
  • Shoplifting
  • Stolen Emergency Vehicle
  • Stolen Vehicle (disabled by default)
  • Suicidal Subject
  • Theft from Person
  • Traffic Stop Backup Required
  • Metro Station - Assistance Requested 
  • Airport Security Threat
  • Commercial Vehicle Theft
  • Concern for Welfare 

 

Copyright and Legal Stuff

This mod (compiled plugin, compiled patch to Grand Theft Auto V source, henceforth "Mod" or "The Mod"), is the sole property of the Mod author (Max Playle, henceforth "Owner" or "The Owner"). By default it may only be distributed on its own from https://lcpdfr.com. It may not be distributed on its own from any other source unless given explicit permission. It may be included in any video as long as it does not attempt to make money off The Owner's Mods. URL shorteners or other attempts to make money off The Owner's Mods are strictly forbidden without advance written permission. Attempts to modify the Mod, and distribute modified versions are Strictly Prohibited, regardless of the modifications in question.

 

YouTube Content Creators / Twitch Streamers

You can include this script in any of your YouTube videos or Twitch Streams. However, I politely request that you include a link to this page (or to https://section136.maxplayledev.org, which will redirect here) in the description/show notes of your video. Please do send me a link to any videos that include Section136Callouts, I'd be curious to know your thoughts and to see playback of the callouts from a third party perspective!

 

AV False Positive

Section136Callouts will trigger some online virus searching engines, such as VirusTotal. This is because the engines used to scan files submitted to sites such as VirusTotal use extremely aggressive heuristics to determine whether something contains a virus. However, as a side effect of this - binaries such as GTA plugins, which make use of memory hooking to achieve a large amount of what they do, will be flagged up. Section136Callouts does not contain any malicious code whatsoever, and you can safely ignore any warnings you receive as a false positive. 

 

Section136Callouts should not flag up in any desktop antivirus engines, however may - on occasion, when a new version is released. 

 

Dependencies

Whilst every effort is made to keep the dependencies bundled with the Section136Callouts download up-to-date, sometimes - being human - I do miss things. As such, you can download the following Section136Callouts dependencies externally:

 

RageNativeUI - https://github.com/alexguirre/ragenativeui/releases (you may need to update this library after a game update)

Newtonsoft.Json - https://www.newtonsoft.com/json

 

Section136Callouts may interact with maxplayledev.org Online Services to report plugin issues, authenticate users against Early Access Club and perform update checks.

If you'd rather Section136Callouts not reach out to the network whatsoever, just enable Prohibit Network Transmission in the configuration file. More information on that is at https://maxplayledev.org/section136callouts/configuration. All currently active network functionality is toggleable using the main configuration file. 

 

 

 

 

 

 

Edited by thatmaxplayle
Update banner

What's New in Version v1.12.1913.8 (Build 1913)

Released

Spoiler

Hotfix Changelog - Build 1913

 

This build has been published following issues reported by the community.

 

  • Fixed an issue resulting in a NullReferenceException which was spamming the log (it seems the previous patch didn't quite fix this). 

 

Known issues:
Not 100% sure if the Player Statistics Menu works on this build. I will assume not many people use it, so have gone ahead and fixed the underlying issue anyway - but please note that you may experience bugs with this functionality if you use it. I'll be patching them soon. 

 

 

Spoiler

Hotfix Changelog - Build 1912

 

This build has been published following issues reported by the community. 

 

  • Fixed an issue relating to the obfuscation of the Player Statistics file preventing deserialization, causing a crash.
  • Fixed an issue with NullReferenceException's being spammed to the log during initialization of the Statistics Menu.
  • Added a fallback which will disable the statistics menu for this session if something goes wrong during initialisation.

 

Hopefully this will fix the issues reported to me by the community. I've been made aware of another bug just today, and will push a silent update sorting that shortly. 

 

 

 

Section136Callouts v1.12 is finally here!

 

External 

The new Section136Callouts configuration utility is now live. You can check it out at https://maxplayledev.org/apps/section136callouts/configurator if you're having trouble modifying the new configuration file, now in JSON format.

 

New Content

  • Added callout: Concern for Welfare
    • This is quite a beefy callout, and because of its nature, it delayed this update from release significantly. 
    • This callout is playable now, however I'm already looking at adding some new content and improvements to it over the next couple of weeks/months.
    • This callout has a number of situations, and for patrols in Blaine County, only some will fire. The callout will not fire all scenarios in Blaine County as this would involve a long drive. I'll be adding more county-based scenarios soon, however at present the callout does work throughout the entire map. 
  • Added Setup Assistance functionality to the Section136Callouts in-game Settings Menu. This menu contains "one-time-fix" and can reconfigure other plugins when selected if it will aid Section136Callouts to work.
    • An example of this is the "Disable ELS Traffic Control" option which can cause some conflictions with the Player Tail scenario used within the new Concern for Welfare callout.
  • If the user is using an old configuration file, they will now be prompted to reset it on startup. This will appear automatically, and will allow the user to reset and regenerate their configuration file at the touch of a button.
  • Added "Reset Configuration File" functionality to the Section136Callouts menu. Please note that this will require an LSPDFR restart to take effect.
  • Made the "S136.ReloadLSPDFR" command public, which allows you to remove any problematic entities and restart LSPDFR in case of a soft-lock within a callout from any plugin.

 

Existing Feature Overhauls

  • The Coroner service has been entirely rewritten, refreshing code I wrote 3 years ago - safe to say it's been optimised a fair bit too.
  • Rewrote the Police Radio menu for the Section136Callouts menu, updating it to use the new Section136Callouts Menu base classes, and updating functionality within it also.
  • Rewrote the update checker, following internal systems restructuring on the server-side. 
  • Rewrote the Early Access Club authentication manager, following internal systems restructuring on the server-side.

 

Default Configuration Changes

  • The "COVID-19 Self Isolation Violation" callout is now disabled by default. It may be removed in a future release.
  • Removed the following unused configuration options from the configuration file:
    • ENABLE_FEATURES > EnablePursuitOptionsInRadioMenu
    • ENABLE_FEATURES > EnableEndCalloutButtonInPoliceRadioMenu
    • ENABLE_FEATURES > Ambient Features
  • The following configuration options have had their default values changed: 
    • ENBABLE_CALLOUTS > SelfIsolationViolation | Now has a default value of false - previously true
    • AI_SETTINGS > AiOfficersUseLethalForce | Now has a default value of true - previously false
  • Added the following new settings:
    • ENABLE_CALLOUTS > ConcernForWelfare | Used to control whether the Concern for Welfare callout is registered, provided IgnoreCalloutEnableStatus is not enabled.
  • Restructured settings:
    • CALLOUT_SETTINGS > WELFARE_CALLOUT_GROUP has been renamed and is now shared between the following callouts:
      • Mental Health Patient Escaped
      • Suicidal Subject
      • Concern for Welfare

 

Bug Fixes

  • Fixed a bug causing the Protest callout to periodically fail with error message "Value cannot be null" - this was due to a buggy world location check.
  • Fixed a bug in the Protest Callout causing excessive log output. This logging has now been removed, and the logic related to tasking free members of the RIOT Squad has now been improved.
  • Removed the Legacy Police Radio option from the Section136Callouts menu.
  • Fixed a bug causing the Attempted Sexual Assault callout to crash if entities related to the Ambulance became invalid whilst en route to your location.
  • Fixed a bug which caused Section136Callouts to crash if Early Access Club Authentication failed.
  • Fixed a bug which caused Section136Callouts to crash if Update Checking could not be completed successfully.
  • Fixed a bug involving an invalid call to a GTA native which could cause LSPDFR, or the game entirely, to crash.
  • Fixed a typo in the PluginConfigVersion setting in the main configuration file, used to determine an out-of-date configuration file. 

 

Quality of Life Fixes

  • If the Coroner (or another service unit) encounters an error because related peds/vehicles go invalid due to increasing proximity to the player, these errors are no longer displayed on-screen if the player has left the scene.
  • Section136Callouts will now fade the game screen in when it loads, to prevent the need to restart the game if it, or another plugin, encounters an issue during a previous session.
  • Added the "Oops" command which can now be used to circumvent the need to restart the game if a callout goes wrong whilst player controls are disabled, or the game screen is faded to black. This will also work if another plugin caused one of these issues to occur.
  • The configuration file is now in JSON format, making it easier to edit. I've also just launched a neat new Online Configurator which explains all configuration properties and allows you to customise them using a GUI - and download a completed configuration file.

 

 

Spoiler

Previous update changelog: 

 

Bug Fix Update - Changelog

 

BUILD 1796 - MINOR COMPATIBILITY UPDATE

This update fixes a bunch of bugs with regards to the Update Checking and Early Access Club authentication systems. This is required because the server-side software was recently rewritten, meaning it broke the endpoints used by previous versions of the pack.

 

If you're looking for new functionality, it's on the way - however recent game updates have made it incredibly difficult to test this (even on a rather beastly computer) so I'm not really sure where to go from here...

 

BUILD 1553 - HOT FIX + MINOR FEATURE UPADTES:

Attention was brought to bugs in previous builds with the help of the Automatic Bug Reporting system. If you haven't yet enabled this functionality, do so today! It helps everybody in the Section136Callouts community. If it weren't for users who use the ABR system, these bugs would not have been fixed - and it's likely I would never have known about them.

 

Bug Fixes:

  • Fixed a bug involving a small 1 second hang when callouts are accepted whilst Live Activity is enabled. This functionality is now utilised on a new thread, to remove any impact on the time taken to load a callout.
  • Fixed a bug causing the Stolen Commercial Vehicle callout to crash during instances where the passenger wasn't spawned.
  • Fixed a bug causing a crash if the mainconfig.xml configuration file wasn't deleted and allowed to regenerate after updating to v1.11.* from any previous version.

 

Feature Updates:

  • Automatic Bug Reporting (Network Bug Reporting) settings are now accessible via the Section136Callouts Menu. Press X (by default) and head into the Settings Menu to see these options. It can now be toggled in-game, and you can learn more by selecting the corresponding button in the menu.
  • Live Activity now supports an Anonymous Mode, allowing you to utilise the functionality without broadcasting your in-game username.
  • Live Activity settings are now accessible via the Section136Callouts Menu. Press X (by default) and head into the Settings Menu to see these options. You can enable/disable Live Activity, enable/disable Anonymous Mode, and learn more about how Live Activity works with the Learn More link displayed in the menu.
  • You can now enable/disable individual callouts from the pack via the Section136Callouts Settings Menu. Hit X (by default) and click Settings Menu > Callouts to individually enable or disable callouts. Bare in mind that your changes from within this menu are not applied until you reload LSPDFR.

 

Removed Functionality:

  • Removed the "Automatic Bug Reporting" information screen which appears when you first install Section136Callouts (or clear the data folder) as this functionality is now stored within the Settings Menu.

 

Default Configuration Options:

  • Network Bug Reporting is now enabled by default, but can easily be disabled from within the Section136Callouts menu.
  • Live Activity is now enabled by default, however in the new Anonymous Mode. You can disable it altogether if you wish, or disable Anonymous Mode to show your player's name from within the Section136Callouts menu.

 

BUILD 1478 - HOTFIX:
Fixed an urgent bug which broke the serialization code for the configuration XML file.

 

BUILD 1465 - RELEASE:

 

A relatively small update containing a brand new callout, some bug fixes, along with a requested feature.

 

🆕 New Features

- Added a brand new (optional) system, called Section136Callouts Live Activity. Using this, you can see what your fellow Section136Callouts officers are doing (where enabled) by broadcasting it to my Discord Server, along with https://beta.maxplayledev.org/section136callouts/liveactivity. This functionality is disabled by default, however can be enabled via the standard, main_config.xml file you're all used to editing. Privacy information and a sample network request is included in the above URL. Note that this functionality will only run if the callout accepted is from the Section136Callouts pack.

 

- Added a brand new callout, Commercial Vehicle Theft.

 

- Added a brand new dependency checker, replaing the old one, which checks all dependencies when you start LSPDFR with the pack - and will notify you if something is wrong.

- The configuration file now contains a reference to the build it was created using, and Section136Callouts will warn you if you are using an out-of-date configuration file. If you see this warning, be sure to delete your configuration file, and let the plugin regenerate it when it next loads. That way, you'll have access to all the latest and greatest settings!

 


Short Description

High quality, customisable callouts based on both new ideas and ideas from our old favourites!

User Feedback

Recommended Comments

Olting66

Members

On 12/22/2021 at 10:22 AM, YuiMukanshin said:

 

I am getting it too.

Me too also

YuiMukanshin

Members

Suicidal Subject callout always crashes and makes LSPDFR crash also but sometimes its prevented by Rageplugin.

RagePluginHook.log

thatmaxplayle

Members Author

On 12/24/2021 at 6:48 AM, YuiMukanshin said:

Suicidal Subject callout always crashes and makes LSPDFR crash also but sometimes its prevented by Rageplugin.

RagePluginHook.log 228.54 kB · 2 downloads

 

This is an issue with the Audio Engine used by Section136Callouts. It's something I am aware of, and am working on changing for other reasons. Don't worry, there's a fix coming soon.

 

Sidenote: That's Section136Callouts preventing those crashes, not RPH

ATTENTION - Before you comment about dependency checks failing!

 

I am aware of an issue due to a renamed library. This slipped under my radar and I didn't notice this whilst packaging the newest version of Section136Callouts. 

 

But, there's more to it.

I've been looking into changing which Sound Engine I use within the pack, to cut down on the amount of files you have to download to play Section136Callouts. So, instead of simply repackaging this build with a file which won't really work because the existing Audio Engine is a bit rubbish, I'm half-way through changing which Audio Engine is being used within the pack, this way the next release will feature new audio systems which are a lot more stable.

 

Long story short - ignore these messages for now. 

I am aware they're inconvenient and I can only apologise for them at this moment in time. With Christmas, and work, I've had very little time to monitor and test things like this - which I am sure you will understand. A new build will be out soon. Hopefully today, but if not - in the coming days. 

 

yogurt2

Members

Can't get in and rob the inside ,Is it possible to provide door opening plug-in,thx~

Ricky001

Members

I recently faced a game crash shortly I finished a callout from this pack - Self Isolation Violation, to be specific.

So the call just ended normally (that's what seemed while playing) and once I was Code 4, shortly after roaming around a bit more, my game crashed (RPH crash, not the lspdfr.dll plugin crash) I did notice the stack trace for this callout pack in the log and hence I'm writing here, to figure out if anything in here cause the crash. Log attached.

RagePluginHook.log

thatmaxplayle

Members Author

On 1/12/2022 at 10:58 AM, Ricky001 said:

I recently faced a game crash shortly I finished a callout from this pack - Self Isolation Violation, to be specific.

So the call just ended normally (that's what seemed while playing) and once I was Code 4, shortly after roaming around a bit more, my game crashed (RPH crash, not the lspdfr.dll plugin crash) I did notice the stack trace for this callout pack in the log and hence I'm writing here, to figure out if anything in here cause the crash. Log attached.

RagePluginHook.log 570.39 kB · 1 download

 

Hi, 

 

Thank you for this comment - although in this instance, I cannot find anything in your log file alone to suggest that Section136Callouts caused your game to crash.

 

I believe the log line you are referencing is the one I've attached below, although this is printed whenever a Section136Callouts callout has it's End function called. 

image.thumb.png.a234384465b41f6a2478cb2fdef1b0af.png

 

This is simply to narrow down "why a callout was asked to end" and can sometimes help troubleshoot bugs within callouts. However, like I said - I cannot find anything that is necessarily out-of-the-ordinary here.

 

Thank you, however, for reporting something you believe to be wrong. 👍

Enjoy your day. 🙂

Ricky001

Members

(edited)

55 minutes ago, thatmaxplayle said:

 

Hi, 

 

Thank you for this comment - although in this instance, I cannot find anything in your log file alone to suggest that Section136Callouts caused your game to crash.

 

I believe the log line you are referencing is the one I've attached below, although this is printed whenever a Section136Callouts callout has it's End function called. 

image.thumb.png.a234384465b41f6a2478cb2fdef1b0af.png

 

This is simply to narrow down "why a callout was asked to end" and can sometimes help troubleshoot bugs within callouts. However, like I said - I cannot find anything that is necessarily out-of-the-ordinary here.

 

Thank you, however, for reporting something you believe to be wrong. 👍

Enjoy your day. 🙂

Thanks for taking the time to respond! 🙂 Actually, I did read that the stack trace was given for whatever reason the callout may end. 

I just sent it here as the game crashed JUST AFTER the call, just so that you could check it out. However, as you say, it must have been something else then. 

 

However, in the Self isolation call, the ped (suspect) doesn't seem to enter my vehicle. Idk if this is also something specific to me... I'll share my experience.

It happened both with vanilla cars as well as add on vehicles. On the game for which the crash log I sent you, I used STP to grab the ped and force him into my vehicle. 

Today, I played it again and the GPS waypoint to ped's home updated when I got into the car (but the ped did not).. so I just drove off XD The conversation at the suspect's home also took place (but the suspect remained where I left him and drove away) Once the call ended, though, I got a notification "LSPDFR.dll crash prevented successfully" (didn't crash, though, thanks to your handled exceptions 🙂) Just attaching a small snap of the log file.. if you please

image.thumb.png.6f0f7905f792c808d0b8fd91a860a40a.png

Don't know if something needs your attention, but nonetheless, loved your work and the calls! ❤️ 

Edited by Ricky001

thatmaxplayle

Members Author

8 hours ago, Ricky001 said:

Thanks for taking the time to respond! 🙂 Actually, I did read that the stack trace was given for whatever reason the callout may end. 

I just sent it here as the game crashed JUST AFTER the call, just so that you could check it out. However, as you say, it must have been something else then. 

 

However, in the Self isolation call, the ped (suspect) doesn't seem to enter my vehicle. Idk if this is also something specific to me... I'll share my experience.

It happened both with vanilla cars as well as add on vehicles. On the game for which the crash log I sent you, I used STP to grab the ped and force him into my vehicle. 

Today, I played it again and the GPS waypoint to ped's home updated when I got into the car (but the ped did not).. so I just drove off XD The conversation at the suspect's home also took place (but the suspect remained where I left him and drove away) Once the call ended, though, I got a notification "LSPDFR.dll crash prevented successfully" (didn't crash, though, thanks to your handled exceptions 🙂) Just attaching a small snap of the log file.. if you please

image.thumb.png.6f0f7905f792c808d0b8fd91a860a40a.png

Don't know if something needs your attention, but nonetheless, loved your work and the calls! ❤️ 

 

Sometimes, peds become invalid - as happened here. We can't really do a whole lot about it. Depending on the specs of your computer, the memory pools can get full up relatively quickly which causes this to happen. The game might spawn the ped, but if RAGE Plugin Hook doesn't give me a handle (which is a number which I can give to the game to tell it which ped to manipulate) I cannot do anything about this.

 

Sadly, it's just one of those things that happen. We cannot expect this to change, because we have to remember this was a game built without modding in mind. 

 

The only thing us developers can do is handle it properly to stop it becoming a major issue. If you notice these popping up frequently, a game restart is generally enough to sort them out. If you've got a lot open on your computer - restart your computer, then launch the game. That is how you avoid these types of issues 🙂 

Manike

Members

LSPDFR crashes when going on duty.

thatmaxplayle

Members Author

2 hours ago, Manike said:

LSPDFR crashes when going on duty.

 

Coming on here and saying that helps nobody. Send your RagePluginHook.log so I can actually tell what went wrong (and if it's 136 at fault)

AikoCutie

Members

is it possible to change the keybinds? because this callout conflicts with stop the ped, so i was wondering where is the .ini file?

Ricky001

Members

Hi, I just faced a crash while on being one of the calls in this pack - attempted sexual assault - to be specific.

Idk if something in that call itself caused the crash, but it did encounter a handled exception nonetheless. Attaching the log for reference.

 

Ps.: Doesn't make this pack any less awesome! Please keep up the great work! 🙂 

RagePluginHook.log

thatmaxplayle

Members Author

On 1/24/2022 at 1:11 AM, phatcow7 said:

is it possible to change the keybinds? because this callout conflicts with stop the ped, so i was wondering where is the .ini file?

 

I use StopThePed and have experienced no conflicts. Either way, yes you can - use mainconfig.xml in plugins\lspdfr\section136callouts (I use XML files instead of INI files for automatic config generation)

On 1/27/2022 at 2:58 PM, Ricky001 said:

Hi, I just faced a crash while on being one of the calls in this pack - attempted sexual assault - to be specific.

Idk if something in that call itself caused the crash, but it did encounter a handled exception nonetheless. Attaching the log for reference.

 

Ps.: Doesn't make this pack any less awesome! Please keep up the great work! 🙂 

RagePluginHook.log 347.48 kB · 1 download

I'll look into it 🙂 

AikoCutie

Members

On 2/1/2022 at 7:38 AM, thatmaxplayle said:

StopThePed

could you be more specfic please? i cant seem to find the mainconfig

thatmaxplayle

Members Author

On 2/4/2022 at 8:25 AM, phatcow7 said:

could you be more specfic please? i cant seem to find the mainconfig

 
Sorry, but how can I be more specific when I’ve literally quoted the location and name of the file.

 

GTA V/Plugins/LSPDFR/Section136Callouts/mainconfig.xml

 

 

AikoCutie

Members

(edited)

 

got it

 

Edited by phatcow7

thatmaxplayle

Members Author

1 hour ago, Katie P said:

great callout pack

 

Thank you so much for the feedback, if you have time, consider leaving a review on the pack (click Reviews at the top of the comments section)

 

Thank you for playing, and enjoy the plugin! 🙂

manu450

Members

Any plans on adding callout interface support from Opus49 for more immersion? 

thatmaxplayle

Members Author

10 hours ago, manu450 said:

Any plans on adding callout interface support from Opus49 for more immersion? 


I can happily announce this is on the To-Do list! 😄

manu450

Members

2 hours ago, thatmaxplayle said:


I can happily announce this is on the To-Do list! 😄

Awesome!😀

thatmaxplayle

Members Author

(edited)

Well, development for the next version of Section136Callouts is underway! I've just published the first bug-test update for my Early Access Club! I've not forgotten about the pack by any means, whatsoever! 

 

The first bug-test release includes:

- One of the callouts, but rewritten in my new format. This improves stability, and allows for things such as automatic entity deletion/dismissal. Not to mention, new spawn locations and storyline possibilities!

- Many bugs fixed around the pack!

- Better integration for Callout Interface by opus49.

 

I'm excited to share these updates with you, they're coming soon. I'm looking to update the pack a little more often. I hope you're as excited as I am for the new changes to come around, as I'm feeling particularly motivated to get the pack patched up and back on the trending list! 😉

 

Yes, I did rewrite a callout - a day and a bit after writing an entirely new callout. Call me mad, but when you're motivated, you're motivated.

 

Enjoy your week guys!

Edited by thatmaxplayle

Create an account or sign in to comment

Latest Mods

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.