![]() |
|
#41
|
||||
|
Quote:
| |||
|
|
||||
|
#42
|
|||
|
Devs don't have access to the server code. They also don't have access to the database.
| ||
|
|
|||
|
#43
|
||||
|
Quote:
How is that development btw?
__________________
![]() Part of me says I can't keep drinking like this. The other part of me says, "Don't listen to that guy. He's drunk" | |||
|
|
||||
|
#44
|
|||
|
they do have access to everything they need through ingame commands tho
| ||
|
|
|||
|
#45
|
|||
|
everything, except.... pathing
| ||
|
|
|||
|
#46
|
||||
|
Quote:
| |||
|
|
||||
|
#47
|
|||
|
exact npc stats would probably be pretty beneficial
| ||
|
|
|||
|
#48
|
|||
|
Alright... Obviously this thread is getting canned for the major reason that this involves a staff member and an internal investigation.. an internal investigation that has been in discussion for a few days via various members of the staff including the management. You all know how I am when it comes to the privacy of internal matters.
Having said that, you guys are jumping to conclusions that a developer account on our development server may be gathering information for.. whatever reason you would give that he would be doing it. I'm not here to fight that claim.. The original thread was created for us to look into it in the first place (albeit in the wrong section of our staff forums for staff members that shouldn't have been able to see it.. but that is a seperate issue, as is how it got leaked). With that said, Nilbog will be writing a post to address some of those concerns either tonight or tomorrow. The result of what happens internally obviously will not be made public, but I will assure you that if we felt someone was abusing developer information, it would be handled.. and it is currently being investigated and handled if appropriate.
__________________
| ||
|
|
|||
|
#49
|
|||
|
As for the other part of the thread involving any banned players.. There are no forum rules against leaked posts from guild private forums, however you will need to create a separate thread if you wish to continue discussing that. We will of course have no part in those discussions.
__________________
| ||
|
|
|||
|
#50
|
|||
|
Greetings,
This leaked information, drama, or inquisition.. whatever you may call it has produced the troll poster's intent; uproar and discrimination. This thread, created by a staff member in the wrong area of the CSR forums, was investigated days ago. I will try to cover some of the key points here to assure you the sky is indeed not falling and that witch trials are unnecessary. A developer's command usage is what is in question. Additionally, it is in question if these commands were used for the purpose of creating another, non-p99 version of Veeshan's Peak. My investigation leads me to believe that is not the case and I assure you... I take issues like this VERY seriously. As far as the posted commands, the event log indicates commands being used to confirm loot, aggro range, and hp amounts. I see a developer testing out an upcoming zone to ensure statistical accuracy and aggro. Months ago, this same developer posted their bug reports of this zone. From an integrity standpoint, this developer has consistently brought bugs, exploits, and anything deemed 'easy' directly to the other developers. Now here is a crucial part... all of the information I utilized to create Veeshan's Peak has at one time or another been posted on these forums. There is no super secret VP info contained within the database. VP is a simple zone from a database perspective comprised of 9 npc types. It could be created within a day or two using the same maps, links, and loot lists I have posted previously. To that end, I fully believe that anyone with basic game development experience and internet research capabilities could do the same. The developer being scrutinized here does not even have database access, merely in-game commands for creating pathing, casting spells, and some in-game statistics of npcs. It is unfortunate that the thread was written in the tone of a.. damning inquisitor. Management investigates a variety of issues involving the staff and players. This is a great example as to why internal investigations are internal. Choosing portions of evidence and filling in the gaps with condemning uncertainty leads to drama. We operate with full evidence and a non-discriminatory approach to these situations so appropriate action is taken if necessary. | ||
|
|
|||
![]() |
|
|