Jump to content
The Official QONQR Community Forums


  • Content count

  • Joined

  • Last visited

  • Days Won


Posts posted by skybolt

  1. In the Chat Depot, I can purchase text colors (click takes me to paypal) but cannot purchase chat background colors (clicking on the $.99c box in Blue Background, for example, does not open paypal.

    Here is a comparison of events:

    Click on Orange Text purchase: hover-over shows #, click starts a browser loading event immediately, followed by a progress bar)

    Click on Blue Background purchase, hovoer over shows # but a click does not cause the browser loading event and no progress bar).

    I see no meaningful differences in the page post, so it's probably the hosted_button_ID that's not working.

    Here is Orange Text:

    <form id="FormSku_FG_Orange_Text" action="https://www.paypal.com/cgi-bin/webscr" method="post" target="_top">
    <input type="hidden" name="cmd" value="_s-xclick">
    <input type="hidden" name="hosted_button_id" value="FHLBAV2U5DYLQ">
    <input type="hidden" name="notify_url" value="https://api.qonqr.com/PayPal/Verify/6061">
    <img alt="" src="https://www.paypalobjects.com/en_US/i/scr/pixel.gif" width="1" height="1">

    And Blue Background (also repros on Faceless, etc., but since that may be tied to faction, I used generic colors and backgrounds)

    <form id="FormSku_BG_Blue_Background" action="https://www.paypal.com/cgi-bin/webscr" method="post" target="_top">
    <input type="hidden" name="cmd" value="_s-xclick">
    <input type="hidden" name="hosted_button_id" value="6B4899P48AG7U">
    <input type="hidden" name="notify_url" value="https://api.qonqr.com/PayPal/Verify/6061">
    <img alt="" src="https://www.paypalobjects.com/en_US/i/scr/pixel.gif" width="1" height="1">

  2. As a Faceless operative, I came across some data fragments while performing forensics on an erratically behaving cloud cluster. The system was marked BLUE. I don't know if it's authentic or not, and the grammar isn't even consistent. Personally, I doubt it's authenticity, but, here's what I found ...

    ---- A3D700C3 sec read $.

    QONQR origins

    When QONQR first appeared on consoles and in systems, no one was sure if it was extraterrestrial, if it was a radio signal beamed back in response to Earth’s SETI signals, if it was an AI project of Nagumo Industries, or if it was a mutated computer virus, or a mixture of all of these that became sentient. Using an internet that never turned off, was never rebooted and was always connected, QONQR thrived.

    Nagumo appeared to be at the center of all the activity, and first used nanobots to extend QONQR geographically from its origin somewhere in east Asia, creating what we now understand to be “zones”. As these bots were used to extend Qonqr's influence, the basic tactic of “qonqoring” a zone with these bots became the Zone Assault.

    It was members of military leadership, the military-industrial complex and intelligence arms of the most powerful nation-states that first described the threat of QONQR. The Turing Task Force used the French Foreign Legion as a base of operations -- as it was the only military organization outside the control of nations-states. It was this Legion that first called people who helped Qonqr — whom they considered traitors to humankind — “the Swarm”.

    The Legion’s first contribution was to increase the destructive power of nanobots. After the Legion detected the spread of nanobots from zone to zone, they needed a way to stop the spreading of what they considered a malignancy. This new offensive weaponry were useful for destroying bots -- but at a cost. They called it "Shockwave", and while it was an offensive powerhouse, by sacrificing defense. It was not as efficient as traditional assault bots for qonqoring zones, but this suited the Legion well, since their primary goal was to destroy QONQR by destroying bots.

    The Swarm faced extinction, and had to defend against the Legion and their new shock bots, so Swarm, (likely Kimyo Nagumo, who was emerging as one of the leaders) reconfigured the bot to deflect energy -- the first defense bot! Or, was the Swarm directed by Qonqr in order to defend itself? Swarm may be enhancing QONQR, or QONQR may be developing the Swarm.

    Those now known as the Faceless grew out of disparate “occupy” movements, WTO protesters, and various anonymous hacking groups. “Prometheus” emerged as their shadowy leader … until people began to realize there might not be a ... or not just one ... Promethus. Was it the same Prometheus that made a statement in October was the same Prometheus who released a video in November? How could a leader setting strategy in Berlin also be running small-scale covert ops in Los Angeles? Over time different appearances of this Prometheus began to strain credulity, if it were one person. Prometheus always appeared behind a complex electronic jamming mask, so almost any of the Faceless could be Prometheus. It is assumed they often are. One person? One thousand? Who knows?

    Faceless created the next innovation, by hacking QONQR itself, and used the AI's built in communications to find a way to attack zones with pure energy! By using an information matrix, Faceless were able to use the resonant frequency of qonqr AI to send an energetic plasma pulse into enemy bots already in a zone. No bots required as it involved hacking enemy bots already in the zones and sending a powerful pulse of destructive power. With the Legion they perfected the technology, making it reliable when paired with a Plasma Core resonant focuser.

    Legion wanted to stamp out the Swarm and needed to extend their ability to attack. Qonqr was spreading! This work led to nanotechnology missiles, not bots themselves but carriers -- to attack enemies at long distance. Like Shockwave before it, this came at a price — removing more armor in order to provide a lightweight, long range devastating attack.

    The Faceless then hacked Swarm's new defense bots - by now called the Deflector - to execute a first strike against incoming bots, the live Seeker. Legion accused the Faceless of teaming with the Swarm to create the Seeker, since it's essentially a Deflector modified with Shockwave-style attack tactics.

    Legion created the Absorber to allow cover for their shock tactics, to concentrate on other deployment. This allowed them to take over swarm infested areas, deploy their fragile Shock bots and take time to build elaborate booster arrays as the absorbers took all the punishment.

    Swarm found a special way to layer bots; like a biofilm almost, or a crystalline lattice. The rigid structure gave strength to surrounding bots, to a point.

    Faceless hacked deflection bots again, rendering them invisible and used this stealth technology to hide their deployment strategies ... and their ultimate goals?

    Legion further explored destructive force and in doing so boosted the energy significantly, so powerful it almost destroyed half the city during early tests before they learned to control it.

    Swarm countered this with a new bot forge, subjecting the bots to tremendous heat and pressure -- before deployment -- creating a strong armor shell. This became the basis of all Strengthen deployments.

    (Fragment ends here)

  3. On main launch wheel, select BOOSTERS

    Observe remaining ordinance at bottom of screen

    Range / Bots required / Energy Required / Remaining Ordinance (or the plus)

    On relaunch screen, observe required bots, required energy, and relaunch (or energy refresh/bot refresh). Need remaining ordinance. Suggest putting it after the deployment type name, like Boosters: 100 (but HL might not fit). Other good location, in the launched/survived/enemy dest box (under enemy dest), or perhaps the zone impact box.

  4. Silver/Gadgerson:

    Do you use the Google maps control for all three versions of Blue? If so I'm going to look into how you might be able to present it as a globe by calling the control; I find the standard mercator projection in all maps terrifically irritating, nothing to do with Qonqr and everything to do with maps. The best control of all of course is Google Earth, because only Google Earth is rendered as a true 3D object, whereas all other globe renderings are a cylindrical projection set on an axis, wrapped onto a sphere (you can tell this by rotating the globe, if it becomes fixed around the north or south pole, it's a distorted cylinder. If you try this same trick on Google Earth, you are basically playing with a ball and can move it any way you want. Then it's easy to see how close Halifax is to the UK, or how easy it is to fly from Seattle to Tokyo.

    OK, totally off topic .... hope you needed a distraction while trying to get THREE versions of Blue out the door!

  5. The other day I was prowling around, looking for zones, and I found a zone in Antarctica, due south of Tierra Del Fuego at the south end of South America. It's on what's called the Antarctica Peninsula (clever name, that one), just north of the area called Palmer Land. Palmer Base (US) and Rothra Base (UK) are in the area, but now I can't find the zone anymore! And, Antarctica isn't a region I can search.

    Anyone else find this zone, either using Qonqr or the Windows Qonqr command center? I'll nab a screen shot of it if I see it again.

    Love to get that one on my base list. I'll have to settle for London and Tokyo.

  6. You bet

    I'm suggesting a mod to the comm screen, that could address the double-notification issue Soupist is describing. If I understand Soupist he's asking to suppress the comm notification, since the user already sees it when leveling up, and shouldn't have to mark the comm message as read -- leaving the novelty of unread messages for more important things. The problem I see with surpassing the comm message is the user may want an archive, which is always a good thing.

    So, my suggestion is to break out the COMM center screen with additional options. Today there are two lead items (dispatches and chat rooms/refresh) and four chat rooms. My initial assumption was this was designed to fit on one page -- but now that I see the "noob" room, I'm assuming the expectation will be additional rooms, even custom, creating a long list that scrolls off the screen, so pushing the rooms (global, noob, nation, region) off the bottom of the page wouldn't be an issue.

    That said, now onto my suggestion:

    Instead of just "dispatches [view all] followed by "chat rooms [refresh]", I'd make that section larger and create new categories similar to classic Qonqr's wire pages, Command Wire and Personal Wire. These would be my suggested categories, and their functions, in this order:

    Dispatches (your current category for what used to be personal wire and command wire)

    Qonqr Messages (could be called Achievements, is a category for part of the old Command Wire, for level ups, rank increases, elite status, other system generated kudos or even manually generated Qonqr staff kudos )

    Qonqr Alerts (part of the old Command Wire, specifically "your zone is under attack/has been captured")

    Team Blasts would be a message to send to all Faceless inside a certain radius, but now that I think further that would invite spam, so kill this one. But, the concept of "n" categories above the chat room list.

    If I'm correct and you intend it to scroll off the bottom of the screen, I'd suggest moving the worldwide/country/region above the list. It's also possible I don't understand the organization of the chat rooms so after i type this I'm going to go test creating rooms and see if I can place the rooms inside a certain region.

    My comment about a heavy workload is that my solution might require heavy re-architecture of the Comm Center, and if that's the case I wouldn't prioritize it very high, that sounds to me more like a post-release upgrade, since the core problem (a few unread dispatches) isn't much of a problem at all. If on the other hand, the framework is flexible and it's just a matter of creating or modifying an XML-like tree structure, then I'd prioritize it higher as a great comm experience would be, well, great.

  7. +1 on this. It's not great to have to mark a message as "read" that you've already read. If it weren't a heavy workload I'd suggest a separate achievements tab/entry in the comm window.

    Like this:

    Chat Rooms [*]

    Achievements [*]

    Team Blasts [*]

    Would this push the USA/Washington/Zone off of the screen to the bottom? yes, but it already looks like a scroll box to me.

    For anyone reading this: please vote on the comm box and whether or not it's OK to scroll off the bottom of the screen. Options include country/region/zone at the top and the above categories at the bottom.

  8. Recommend adding a progress bar to the load screen that shows tips ... Why?

    On multiple occasions now my muscle memory has kicked in and I've hit the android BACK button to clear the tip, being antsy to start the app. The behavior here is of course to exit the app, as it should be, but now I've been hoist by my own petard as it were.

    A progress bar (even if it's completely fake and advances at a fixed rate) lets the user know "hold on, Charlie, we're getting there."

    I would also add text, such as "connecting to QONQR grid ..." or "reading QONQR pulses, detecting zones", something immersive.

    Tips are fine, but most startup tips in other apps are designed to be closed, so we don't want to change expectations on people.

    I'd rate this as fairly important and a UIX issue. importance 3 of 5.

  9. My thoughts, which don't really matter as I'm an end user/beta tester as well.

    1. That has not been my experience. In cases like this you should list your software version (os) as well. My OnePlus One is smooth. Haven't tested this version on HTC one yet.

    2. QONQR theme water background: I get it, they thought it was too dark before they added stripes. I'm on the fence here, but I do like darker. I'm sure there were complaints about it being too dark.

    3. Please be more specific -- is it the white text on the striped water that's at issue? Can you provide a screen print? My text is quite small but looks terrific.

    4. That's an anti-tech measure to keep bots from auto-launching which is still a problem.

    5. Not sure what you're saying here would be your proposed fix .... make the square move around the screen? Also, DHD? Is that a Stargate reference?

    6. Interesting, custom color theme. When suggesting something major like this, please also attach an importance factor, as all features/bugs/fixes need to be prioritized. Also, are you certain you want this? Color was central to classic QONQR, and I assume central to new QONQR. Are you suggesting a complete set of color changes, or more like a change to the common blue color, like red for nighttime, green for night-vision, white for simulating a CRT, etc?

    Welcome to the club!

  10. Current

    1: see new enemy zones on map

    2: tap on enemy zone

    3. bring up launch screen

    4. tap slider

    5. make mistake, hit tactical instead of bot leaders

    6. See bot leader, but you really only wanted to see who took over zone


    1. See new enemy zone on map

    2. tap on enemy zone

    3. Brings up launch screen, please show either highest bot leader or whoever took it over

    Possible places for real estate to show data:

    1. Under faction bars, but above faction badge

    2. On the right side of screen across from the attacking bot type

  11. Device had different OS on it in the past (cyanogen 10), probably was rooted, so if you keep a database that would do it. Had dev options on, now dev options are off but device has not been reset since then. Mock locations were never enabled. Device currently locked, stock boot, recovery and system, only irregularity was turned dev options on, then turned them back off via deleting saved settings in "settings" app.

    Can try factory reset if you think it merits testing.