Jump to content
The Official QONQR Community Forums

Silver

Moderators
  • Content count

    1,235
  • Joined

  • Last visited

  • Days Won

    159

Everything posted by Silver

  1. QONQR black

    QONQR black is now available for Windows Phone. Android and iPhone should hopefully complete development in the next week or two. http://blog.qonqr.com/post/93507594207/qonqr-black At the moment we see that all our WP7 devices receive a download error when trying to get the app from the store, but the app has worked for all our WP8 devices. Download issues are not uncommon, but if it doesn't auto-resolve soon, we will contact Microsoft.
  2. QONQR Music [get it here]

    We have had several requests to obtain the original QONQR theme music. Previously we had not let this out, but GungHo and I talked this morning and decided we would publish the original file for our fans to use. We anticipate players will want the music mostly for ring tones, or to incorporate in their own QONQR related movies and animations. A couple of our players have inquired about getting the music for YouTube videos. We fully support our players creating viral videos of their QONQR activities, recruitment campaigns, or "battle correspondent" reports. However we request that all such videos reflect positively on QONQR's brand. If you want to use the QONQR music in those videos, keep it family friendly. Here are the legal terms of use for the music which I just made up. My attorney may want me to modify them later. QONQR hereby grants limited usage rights to the QONQR theme music. These terms of use may be modified at anytime, without notice. QONQR reserves the right to revoke usages rights to any person, company, or application at any time. QONQR retains full ownership and copyright to the music. QONQR theme music may only be used in original media productions created to positively promote QONQR. Pure audio productions (such as ring tones) must include "QONQR" in the media/file name. Film, animation, games, and other visual media productions that incorporate the QONQR theme music, must include a link to "www.QONQR.com" in the credits. QONQR theme music may not be used in any product or service that is not free to the public. QONQR requests that any public usage of the QONQR theme music be posted on this thread. QONQR_Theme.mp3
  3. I've had some very angry emails today from a couple users who are upset their rival achieved the ability to switch factions freely having played for one of the factions for only 1 hour. I've been accused of doing favors, changing the rules, and various other backhanded deals. It appears it comes down reading the rules. You do not have to play for every faction for 60 days in order to earn free switching status. Here is a common scenario many players have used to achieve free switching status and avoiding playing for one faction they despise. 1. Start with Swarm 2. Switch to Legion (earn Spy) play for 60 days 3. Switch back to Swarm (earn Double Agent) play for 60 days 4. Switch to Faceless (earn Mercenary) immediately switch back to Swarm or Legion Below is the complete text on the switch nanobots screen. It is the same text that has been there from Day 1 with the exception of the level 100 rules that went into place earlier this year, where you could switch as much as you want before level 100 , but those switches don't count towards the medals. This text has been part of this description since Jan 15, 2013. "Players that earn all three spy awards, may once again switch factions at any time as they could during the training levels 1 through 99." Prior to Jan 15, the text said this. "Players that earn all three awards may be given the opportunity to switch factions more quickly in future updates (contact support for more information)" I pulled that right out of source control, which includes the entire change history. Here is the complete text from this page. http://portal.qonqr....r/SwitchFaction WARNING: Defection has consequences! Self-destruct will be initiated on all your nanobots. Without the self-destruct, you would be required to battle against your former self to regain control of your zones. You will lose the capture and leadership of any zones you currently hold. Lifetime captures will be unaffected. If you are still completing the training levels and have not reached Level 100, you may switch as often as you like to find the faction that suits you best. Once you have reached Level 100 switching factions has rewards, but also has additional consequences beyond the self-destruct of all your nanobots. Defection will usually result in a demotion in rank. This is accomplished through awards with negative rank points. Those awards are: Spy - First switch to an opposing faction (-20 points) Double Agent - Return to a faction from which you had previously defected (-20 points) Mercenary - Become a member of all three factions (-20 points) Other Faction Change Details: You may not switch factions again until at least 60 days have passed since your last faction switch. Defection point penalties are applied only once per award Players that earn all three spy awards, may once again switch factions at any time as they could during the training levels 1 through 99. The decision to switch factions is one that must be made with strong determination. Nanobots cannot be reanimated once destroyed. You will retain your earned experience, level, formations, qredits, cubes, and upgrades. However, as far as your zones go, you will be starting over.
  4. Creating bases

    OH!!! I see. Well no one else can see your bases. Is this a problem Cane? We have always stored the exact location of your base in the database, but until now we never showed them on the map, just listed them in a list by zone name. Some day in the very distant future, there may be a feature that makes the exact location of your base relevant (but never public unless you explicitly allow the base to be seen by other players). We have some ideas about how we could make bases more interesting in Version 3.0, but nothing solid. If that ever happens, you'll probably want to move your bases down the block from your home or work before you made them public. BUT AGAIN, it will be a very long time before we would allow you to make your base location public, if we ever do at all.
  5. Scope aggressively wants to reset

    Awesome, appreciate the response. So far the response to Scope Reset (once the reasons are understood) has been "Positive" to "Neutral -1".
  6. This one is a bit tricky due to the way we store dispatches. I agree we should do it, but this will have to be a feature added later.
  7. I believe QONQR Classic on Android had no expiration of of a GPS location. In theory, you could be running off a location from hours/days ago. Too many Android users on QONQR Classic get flagged for location spoofing and are put into 24 hour maximum overheat because they deploy in their old location, then travel (airplane) deploy in new city with old location, then get a GPS fix and deploy in new city. This looks like you instantaneously traveled hundreds of miles. Now a GPS will not be considered valid if the last location was more than 15-30 minutes old. We will see how this morning's update goes. Not sure if this will make things better or worse. By default QONQR uses "coarse" location preferences, which should help with battery life. Coarse should allow you to get your location based on the network. If you are connected to a network or cell tower, I think you should be able to get your location using coarse. Location services in Android is a very tough thing to get right. The API is messy. I added alot of code to this and hopefully it makes things better. Additionally, there is now an option to use "High Accuracy" location under settings. This will drain your battery, but in rural areas where you may only have 1 cell tower in the area, your location could be off by many miles if you don't turn on the GPS antenna (this new setting).
  8. This is a performance issue with Xamarin + Android. Performance is good on iOS and WP. We probably can't fix this but will investigate.
  9. We have looked into estimating a font size based on width. It is on our todo list.
  10. I'll look into this. I'm not sure the Google Maps control has a background color we can set.
  11. Blue crashes on re-launch

    App resume is a tricky one. We have crash reporting that is helping to pinpoint these. Android was never made to handle suspend/resume. Developers have always had to hack their way around it. We want GPS to turn off when you suspend the app, and a few other things we want to stop and restart to save battery life. Something in that code must be breaking. I think we can find it from the crash reports.
  12. This is an ongoing issue with the draw events. We may need to handle the way we do popups differently.
  13. On Zone search

    I've added a bug to try and get Android to behave properly
  14. Oh, you are correct. And it shows a QR code. I forgot about that. We will probably add that at some point.
  15. Believe it or not, programmatic access to the clipboard is not allowed on Windows 8.1. So stupid. We try not to build features that don't work on all phones. BUT... I do have plans to allow you to "link" a zone in chat. Right now I think what ever zone is the preview zone (highlighted blue on map, show display in lower left) we will have an option to link to [Zone] when you compose a chat message, then insert the high lighted zone id to the chat dialog with a tap. In chat you would be able to hashtag a zoneid #2349352 and all users would see it as a link to jump to that zone. If you don't want to use the built in chat, you could copy out the zoneid from the entry box, and then paste into GroupMe. It is a hassle if your goal is to use GroupMe, but it is my plan for now.
  16. This is a Xamarin bug. I have a ticket open. We may have to try a work around if they don't fix it soon.
  17. You are prompted to enter your recruiter if you "Customize Enlistment" at registration. After enlistment you can only do it via the portal, same with adding email, changing password, etc. Currently can only be done on portal (Same in QONQR Classic)
  18. Are there any chances for root support?

    We understand the pain that root blocking causes for some players, and we understand that root detection isn't 100% certain for those who can manipulate the Android kernel. Of the Android players that we have had to ban since the beta started, 90% (perhaps 95%) were on a rooted Android device. This of course does not mean that everyone running an android phone is trying to cheat or abuse the game. But we have caught a disproportionately higher percentage of attempts to cheat on rooted Android than jailbroken iOS, which is even more unexpected when you aren't anonymously downloading the game via the App Store, but instead need to register with us in Google+ to play. It is worth noting, we also ban dozens of jailbroken iPhones every month for attempting to cheat. Roots have historically been very expensive for us to deal with. They have consumed a high percentage or our time for Gadgerson (who handles QONQR support) and often pull me away from building new features and fixing bugs. The app is more tightly locked down right now. It is easier for us to loosen restrictions as we go, than to add new restrictions later. You are correct that we could look for "illegal" apps, but that list would be long and I could never do that in every country. That however, isn't the greatest concern that is driving root blocking. I hope you understand if I don't share what is my biggest security concern with rooted devices.
  19. Yes we know. We tried a black gradient under the text, but didn't like the way it looked on the standard Google Maps. We are still playing with this.
  20. Loading first zone takes a while

    Yes, currently we load all the interfaces on first use, then reuse them after that. We will get to optimizing the UI once we have it functionally working the way we want. Launch Wheel will probably be the first UI we create in the background.
  21. Unlocked base wording

    good suggestion
  22. Facebook integration blank

    Android (or maybe Facebook) change this. It now appears that we must implement the Facebook SDK into our app to support sharing with context, which would mean you need to authenticate with Facebook through the QONQR app. Previously you could launch the Facebook/Twitter apps with a message to show on a share post. We don't want to do authentication for Facebook and Twitter inside our app. We are looking for work arounds. We left the buttons there for now until we know what we can do one way or the other.
×