BryceCanyonCounty / bcc-doorlocks

GNU General Public License v3.0
7 stars 12 forks source link

error finding iterator for doorlock #35

Open yaboibutt3r opened 2 months ago

yaboibutt3r commented 2 months ago

seems to be causing a issue with creating houses or doors in general because it doesn't show that a door is there when you try to set one, for housing aim at it or press e doesn't work sends back this error in f8 console but not on tx console... unless its feather menu or housing causing that error but my assumption based on what its stating is the doorlocks 20240913233252_1

iseeyoucopy commented 2 months ago

I think that door doesnt exist in doorhashes.lua thats why you have that erroor, but ill double check myself

yaboibutt3r commented 2 months ago

ahh, very possible. I didn't actually think about that I just had the issue for multiple doors but they could've been doors on added ymaps didn't look into it much. Just sent after I got the error on a couple doors. ill try it on some I know should work. sorry for any possible inconveniences.

AndrewR3K commented 2 months ago

@yaboibutt3r Did that resolve the issue for you? If so I will be closing out this ticket.

Thanks!

yaboibutt3r commented 2 months ago

@AndrewR3K you see I'm a idiot and forgot to change the steam identifier so I haven't had that issue anymore but after I changed it I was still getting a error.. but I'm gonna update it first now and see if that continues

yaboibutt3r commented 2 months ago

so this is the error I'm getting now, I just updated and went to a door that's put in the door hashes and it still doesn't want to work for me lol 218_14

AndrewR3K commented 2 months ago

Did you restart the script and server after adding the doorhash?

yaboibutt3r commented 2 months ago

uhh after updating the script I restarted the server, looked in the doorhashes.lua for a door that is already in there and tried but that's the error I got, door locks used to work for me until recently and im not exactly sure why

iseeyoucopy commented 1 month ago

There is a fix in here #37 please update to latest release