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
! This is an issue tracker, not a helpdesk !
What is the Version you're running?
Version: ## Replace this with version - If not reported Issue will be
deleted without comment. Choose other template for feature request##
(1) In Game User Name: rootz
(2) What is your issue?
Problem with mission, on www.umadbro.db. In Profile database doesn't exist Donya Joyner. I tryed reset mission, restart game client, nothing helps.
Mission ID: 1391189363M7832145
Mission Title: Businesses Fight Dirty
Mission Date: 2014-01-30 11:29:23
Mission Description: Our client is interested in shutting down a rival company.
The rival recently stole a major contract from the client, one which the
client believes would have helped expand the business. We are being paid to
modify the tax records of the rival owner with data which will cost the company
far more than it made from the contract. Access the tax records on the target
server and edit them.
Mission Objectives: Locate : (Donya Joyner)
Target Data: (Tax) Records.
Server: (www.umadbro.db)
Use Data Editor to inject this data.
(Encrypted: 253742359483)
(3) What steps will reproduce the problem?
Just try to find Donya Joyner on www.umadbro.db
(4) What is the expected output? What do you see instead?
(5)Please provide additional information below.
a) what where you doing when you discovered the problem?
b) are you able to retrace your steps in order to reproduce the problem?
Original issue reported on code.google.com by [email protected] on 31 Jan 2014 at 4:22
The text was updated successfully, but these errors were encountered:
A database record for Donya Joyner exists on umadbro. I suspect you were
spelling it incorrectly, or adding a space or bracket at the beginning or end
while copying. On some random occasions records will come up blank. I've
never determined a pattern as to why this occurs, but usually searching a
second time will find the record.
Original issue reported on code.google.com by
[email protected]
on 31 Jan 2014 at 4:22The text was updated successfully, but these errors were encountered: