You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 6, 2026. It is now read-only.
The main purpose of this pull request is to fix any issues that stood out to me during the testing of the user interface overhaul of ps-realtor.
Details
Fix "imgs" key being set instead of "extra_imgs" when editing/adding or removing property images in ps-realtor through UpdateImgs event.
Fix prematurely granting a potential buyer access to an MLO interior which uses ox-doorlock before the purchase has even been confirmed
Remove an unused config option that has 0 references in the codebase ShowCustomizerWhenNoStartingApartment
If this is used somewhere please let me know and i'll revert it
Change price column to be an unsigned integer, this prevents negative values being stored and doubles the available pricing amount
Don't think this is completely necessary, it's a database change, I've added sql script to be ran after the initial one which alters the column for existing setup, without migrations this is probably the best I can do.
UI Changes / Functionality
No UI changes, shouldn't affect existing functionality other than allowing higher prices properties I guess.
Testing Steps
Did you test the changes you made?
Did you test core functionality of the script to ensure your changes do not regress other areas?
Did you test your changes in multiplayer to ensure it works correctly on all clients?
Run the additional sql script after the initial one (or apply to existing setup)
I've been doing some testing with this, hopefully these will be easy fixes:
For MLOs using OX, showcase doesn't work (seems there's a mismatch between server and client variables passed, but no errors). I'd expect the doors to be unlocked for a period of time.
After a house is deleted, outdoor furniture that was placed in the garden is still present.
Additional keyholders can still unlock properties after their access is revoked (and confirmed so in the database).
I'll keep going. :-)
For tracking purposes, this is SpiffingRich from the PS Discord server.
I've been doing some testing with this, hopefully these will be easy fixes:
For MLOs using OX, showcase doesn't work (seems there's a mismatch between server and client variables passed, but no errors). I'd expect the doors to be unlocked for a period of time.
After a house is deleted, outdoor furniture that was placed in the garden is still present.
Additional keyholders can still unlock properties after their access is revoked (and confirmed so in the database).
I'll keep going. :-)
For tracking purposes, this is SpiffingRich from the PS Discord server.
are these issues present in the current ps-housing aswell? or are they caused by this pr?
because I don't see how this pr could have caused these issues at all.
I've been doing some testing with this, hopefully these will be easy fixes:
For MLOs using OX, showcase doesn't work (seems there's a mismatch between server and client variables passed, but no errors). I'd expect the doors to be unlocked for a period of time.
After a house is deleted, outdoor furniture that was placed in the garden is still present.
Additional keyholders can still unlock properties after their access is revoked (and confirmed so in the database).
I'll keep going. :-)
For tracking purposes, this is SpiffingRich from the PS Discord server.
Thank you for testing, I appreciate that!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
None yet
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
The main purpose of this pull request is to fix any issues that stood out to me during the testing of the user interface overhaul of ps-realtor.
Details
ShowCustomizerWhenNoStartingApartmentpricecolumn to be an unsigned integer, this prevents negative values being stored and doubles the available pricing amountUI Changes / Functionality
Testing Steps
Did you test the changes you made?
Did you test core functionality of the script to ensure your changes do not regress other areas?
Did you test your changes in multiplayer to ensure it works correctly on all clients?
Run the additional sql script after the initial one (or apply to existing setup)
Use ps-realtor to add/delete/change images