Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Zones Issue #3

Open
mallic opened this issue May 8, 2020 · 2 comments
Open

Zones Issue #3

mallic opened this issue May 8, 2020 · 2 comments

Comments

@mallic
Copy link

mallic commented May 8, 2020

Documentation in the zones.ini example isn't particularly clear, but so far I am aware that myself, cur7 and probably vincetti have experienced the following issue, so I am assuming that it's a coding issue and not a config issue. Though we could all just be messing up the same way. Also for vincetti, I am assuming he is having the same issue since on his server, all of his ATMs were still physical NPCs instead of spaces you could walk through and use the function as the zone explanation suggests should be the case.

When trying to put zones into the ini, it just causes every single door entity to show the zone instead of the first zone outlined in the zones.ini. For instance if I try to create a zone for an ATM using the following example (default coordinates from the example file):

Zones.ini
"ATM"
{
"boundaries1" "-198 -39 36",
"boundaries2" "155 -306 36"
}

npcs.ini
type "atm"
name "ATM Machine"
origin "687 437 -347"
model "models/pellet.mdl"
zone "ATM"
[END]

or

type "atm"
name "ATM Machine"
;origin "687 437 -347"
;model "models/pellet.mdl"
zone "ATM"
[END]

Here is the end result: https://i.imgur.com/fF5Ga3c.png
To be clear, the origin coordinates for the ATM are nowhere near that door.

Also, the zone.ini and npc.ini don't actually mention how to tie a zone to a particular NPC. I assume it's just zone "ZONENAME" like I did above, but the NPC.ini just says to put zone there. In either case, doing it either the way I assumed it was supposed to work, or just by only setting up one zone and putting that zone in the file has the same outcome.

Also, for your coordinates on the zones, are you doing a 3d square from top-left to bottom-right, or are you doing a simple two coordinate horizontal space between two points?

Here are the only instructions in the configs for setup:

NPC.ini:
; A zone is a place where a player can stand and talk to an NPC. Global to all NPCs.
; A zone is unsolid and is not rendered, so the player simply has to stand around
; the origin instead of looking at a model.
zone

Zones.ini:
; The name of the zone.
"Zone Name"
{
; The first boundaries.
"boundaries1" "-198 -39 36",
; The second boundaries. Note that these can be out of order.
; The zone plugin will sort out which one should go where.
"boundaries2" "155 -306 36"
}

@DouglasSherk
Copy link
Owner

FYI I sent Vincetti a message several days ago and have not heard back. I'll report as soon as I hear something or see what I can do myself this weekend.

@DouglasSherk
Copy link
Owner

Unfortunately, Vincetti replied that he made no progress in fixing this problem. This bug was a known problem back in the day. If I were to dive in and fix the problem myself, I would need hours just to set up Windows, TS, etc., to refamiliarize myself with the code, and then test that the fix worked. After reviewing the cost and number of people affected, which is a total of two that I'm aware of, I decided that I will not fix this bug. I appreciate that you're still using ARP after all these years and I'm sorry to hear you're having this problem. I will keep on the lookout if anyone else tries to or does fix this bug, and I will either ask them to report back or do so myself if that happens.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants