Skip to content
This repository has been archived by the owner on Dec 26, 2021. It is now read-only.

RPG Skills Feedback #158

Open
mtadayz opened this issue Mar 9, 2018 · 7 comments
Open

RPG Skills Feedback #158

mtadayz opened this issue Mar 9, 2018 · 7 comments

Comments

@mtadayz
Copy link
Collaborator

mtadayz commented Mar 9, 2018

Please post feedback, bugs, errors and suggestions here.

@mtadayz mtadayz added this to the Version 1.0.0 milestone Mar 9, 2018
@mtadayz mtadayz mentioned this issue Mar 9, 2018
@axelmine
Copy link

vendor npc does not work

@Risusama
Copy link
Collaborator

Risusama commented Mar 13, 2018

Not really a giant issue imo, but when upgrading from the previous commit, I could no longer log in to my previously created account, with the following console error:

[2018-03-12 18:09:55] LOGIN: (Everyone, Admin) DebexeL successfully logged in as 'DebexeL' (IP: 192.168.1.1 Serial: Nope, not going to get it!) [2018-03-12 18:09:58] WARNING: [DayZ]\DayZ\init\players\login_init.lua:239: Bad argument @ 'fromJSON' [Expected string at argument 1, got boolean] [2018-03-12 18:09:58] ERROR: [DayZ]\DayZ\init\players\login_init.lua:240: bad argument #1 to 'pairs' (table expected, got nil)

###EDIT### Removing internal.db fixed the problem. Though, if you do that on a bigger playerbase, it will most likely affects active players as all accounts on the server disappear when you delete this file.

@mtadayz
Copy link
Collaborator Author

mtadayz commented Mar 13, 2018

Did you accept a job prior to logging out?

@Risusama
Copy link
Collaborator

@mtadayz in case you answered to my comment, no.
I had previously installed the latest files from before this update. I tested the server with my account.
Then I updated to the current latest files. I was trying to test the update with my previous account, the credentials worked, but when I tried to spawn, I only got a black screen and the errors above were in my server console.

@mtadayz
Copy link
Collaborator Author

mtadayz commented Mar 13, 2018

Ah, yes, that's probably because if an existing account tries to log in, it won't have the "PlayerCurrentJob" data, so the login fails. Hopefully fixed it with the latest commit.

@Risusama
Copy link
Collaborator

Risusama commented Mar 16, 2018

Perhaps somehow slightly increase zombie spawnrate near the zombie extermination mission locations? It's kinda very time consuming killing 30 zombies when almost no zombies spawn at the location. I think it should be done (if possible) by upscaling the configured values like in the following example:

Extermination job in San Fierro. With the marker in the center, select a radius from between 100-175meters for which zombie spawnrates will be raised by like, 2 to 3 times the normal. Of course, if doable, the size of the area could also affect the multiplier for the zombie spawnrates.

@mtadayz
Copy link
Collaborator Author

mtadayz commented Mar 16, 2018

Good idea. I wanted to do that before pushing the update, but I forgot about it.

EDIT:
I've added the requested feature, though twice as many zombies will spawn regardless of whether or not you arrived at your destination. Figured the in-game reason for that could be because zombies are actively hunting you down.

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

No branches or pull requests

3 participants