FreeScriptsDocsSupport

Browse

  • Documentation
    • FAQ
  • 📱 Phone
    • 🧠 Installation
    • 🦄 Unique phones
    • 💿 Configure
      • 💄 Additional Features
      • 📸 Camera
      • 📹 Video Calls
      • 🍏 Apps
      • 🪵 Logs
      • 🔋 Battery System
      • 🖼️ Media Customization
      • 🗣️ Multi-Language Support
      • 🗃️ SIM Cards
      • 🚗 Valet System
      • 🖼️ Wallpapers App
      • ⛅ Weather Widget
    • ⏭️ Exports
      • Client side
        • 👁️‍🗨️ General
        • 📞 Calls
        • ☀️ Groups
        • 🏢 Companies
        • 🔧 Misc
        • 🗼 Signal Towers
      • Server side
        • 🆔 Identify Player
        • ☎️ Sim Cards
        • 📞 Calls
        • 💬 Messages
        • ☀️ Groups
        • 🌐 Cell Broadcast
        • 💸 YPay
        • 📧 Mail
        • 📪 Notifications
        • 📵 Screen Damage
        • 🗯️ Dark Chat
        • 🔧 Misc
    • 🪛 Commands
    • 📡 Events
      • Server side
        • 📨 Messages
        • 📱 Social Media
        • ☎️ Calls
    • 🍎 Custom apps
    • 🏦 Banking App
    • 📈 Markets App
    • 👜 State bags
  • ☎️ Boomer Phone
    • 🧠 Installation
    • 🦄 Unique phones
    • ⏯️ Exports
      • Client side
  • 🏠 Properties
    • 🧠 Installation
    • 💿 Configure
    • 🔗 Compatibility
      • Phones
        • YSeries
        • LB Phone
    • 📖 Guides
      • 🛏️ Starter Apartments
      • 🐚 Add More Shells
      • 🔑 Physical Keys
      • 🪑 Furniture As Items
      • 🛠️ Fix Interactable Points
      • 📋 Discord Logs Setup
    • ⏭️ Exports
      • Client side
        • GetCurrentPropertyId
        • GetCurrentProperty
        • IsPointInsideProperty
        • OpenPropertyMenu
        • AddKey
        • RemoveKey
        • SetWaypointToProperty
        • GetAllProperties
        • GetKeyHolders
        • PoliceRaidDoor
        • WrapIntoProperty
        • GetClosestDoor
        • GetEntryCoordinates
        • UseLockpick
        • PoliceRaidDoor
      • Server side
        • GetAllProperties
        • GetPropertyData
        • AddKey
        • RemoveKey
        • ToggleDoorlock
        • GetPlayersInProperty
        • GetKeyHolders
        • DeleteProperty
        • AddStarterApartment
        • SellProperty
        • TransferProperty
    • 🪝 Hooks System
      • buyProperty
      • rentProperty
      • sellProperty
      • deleteProperty
      • createDoor
      • saveSettings
      • setInteractablePoint
      • canEnter
      • canExit
    • 👜 State bags
  • 🏦 Banking
    • 🧠 Installation
    • 🪛 Commands
    • ⏯️ Exports
      • Client side
      • Server side
    • 🪵 Logs
    • 🪝 Hooks
    • 🏦 Banking App
  • 💸 Billing
    • 🧠 Installation
    • ⏭️ Exports
      • Client side
      • Server side
  • 📊 Hud
    • 🧠 Installation
    • ⏭️ Exports
      • Client side
  • 📦 Storage Units
    • 🧠 Installation
  • 🎰 Slots
    • 🧠 Installation
    • 📱 Phone app
  • 🎃 Minigames
    • 🎯 Exports and Usage
    • 🔧 Commands

🛠️ Fix Interactable Points

This guide explains how to use the FixShellOffsets configuration option to fix interactable points that are incorrectly positioned on the Z-axis (vertical axis) in shell properties.

What is FixShellOffsets?

Create a database backup before running the command!!!!

The FixShellOffsets feature is a migration tool designed to fix interactable points (such as inventory, wardrobe, etc.) that are positioned incorrectly on the Z-axis in shell properties. This issue can occur when upgrading from older versions of nolag_properties to version 2.4.0 or later.

When to Enable FixShellOffsets

Enable this feature if:

  • You are upgrading from an older version to 2.4.0+ - this is a one-time migration that should be run after updating.
  • Interactable points are positioned incorrectly - if you notice that interactable points (inventory, wardrobe, etc.) appear higher or lower than they should be in shell properties.
  • Points are floating or underground - when interactable points are not aligned with the shell's interior floor level.

Configuration

Enable the feature in your config.lua:

config.lua
FixShellOffsets = true, -- Enable the shell offsets fix

Important: After running the fix command, you can disable this setting again as it's only needed for the one-time migration.

How to Use

  1. 1

    Enable the Configuration

    Make sure FixShellOffsets is set to true in your config.lua file.

  2. 2

    Restart the Resource

    Restart the nolag_properties resource to load the configuration:

    Server console
    restart nolag_properties
  3. 3

    Run the Fix Command In-Game

    Join your server and run the command in-game (chat or F8 console):

    In-game command
    /getShellOffsetsFixed

    This command will:

    • Spawn all shell types at the configured Z-level (Config.ShellZLevel)
    • Calculate the offset difference between shells spawned with and without offset
    • Automatically send the calculated offsets to the server
    • Fix all shell properties with incorrect interactable point positions

    Note: The command will spawn shells temporarily to calculate offsets. This may cause brief visual effects in-game.

  4. 4

    Wait for Completion

    The command will process all shell properties and fix their interactable points. You'll see progress messages in the server console:

    Server console output
    Fixing offsets for all properties
    Updated offset for point X in property Y with coords {...}
    Finished fixing offsets for all properties

    You'll also receive an in-game notification when the process completes.

  5. 5

    Disable the Feature (Optional)

    After successfully running the fix, you can disable FixShellOffsets in your config:

    config.lua
    FixShellOffsets = false, -- Disable after migration is complete

What Gets Fixed

The fix command:

  • Processes all properties with type shell
  • Updates interactable points that have coords stored (old format)
  • Converts them to use offset format (new format)
  • Applies the correct shell offset to ensure points are positioned correctly on the Z-axis
  • Saves the updated property metadata to the database

Troubleshooting

If you encounter this error, it means the offset calculation failed for a specific shell type. This can happen if:

  1. The shell model cannot be loaded
  2. The shell hash is invalid or missing

To fix this:

  1. Verify the shell exists in your ShellsData configuration
  2. Check that the shell's hash/model is valid
  3. Ensure the shell model is available in your game files
  4. Run /getShellOffsetsFixed again - the command will skip shells that fail to load and continue with others

The command automatically calculates offsets for all available shells and only processes properties with successfully calculated offsets.

If points are still incorrectly positioned after running the fix:

  1. Verify that the property type is shell (not ipl or mlo).
  2. Check that the interactable points have the type == 'inside' in the configuration.
  3. Ensure the shell was successfully calculated during the offset finder process (check server console for errors).
  4. Verify that the points had coords stored (old format) - if they already use offset format, they won't be modified.
  5. Check server console for any error messages during the fix process.

Related Commands

  • /getShellOffsetsFixed - In-game command to calculate shell offsets and automatically fix all shell properties (only available when FixShellOffsets is enabled)

See Also

  • Physical Keys Setup Guide

On this page

  • What is FixShellOffsets?
  • When to Enable FixShellOffsets
  • Configuration
  • How to Use
  • What Gets Fixed
  • Troubleshooting
  • Related Commands
  • See Also

All Rights Reserved

TeamsGG © 2026

Pages

FreeScriptsDocsSupport

Legal

Terms of ServiceRefunds

Tebex

Tebex ImpressumTebex TermsTebex Privacy

Socials

DiscordYouTube