Grid 12 Wiki

[amitp]

Thanks Rob. Would this be a reasonable model for Viking's DPS?

25 damage per shot; 600ms between shots = 41.67 dps burst (up to 8 shots)

8 shots per clip; 2000ms between clips = (25 * 8) damage over (600 * 7 + 2000 ms) = 32.26 dps sustained

Does it reload when not firing or only when you go through the 8 shots?

Does the reload happen during the cooldown for the 8th shot, or is cooldown in addition to the reload time?

Thanks — I hadn't been taking cooldown/reloadms into account at all and will code that up.

[Ood]

@amit's question not to me... (;

That's how I do it.
Reload after clip has been emptied.
Not sure if cooldown, then reload. I'd assume they overlap.

[rob]

They overlap.

[amitp]

Thanks Rob-who-should-be-vacationing! I've updated the tank viewer to use overlapping reload/cooldown.

[lights]

Is it ok if I upload some pictures and make some of the pages prettier without changing content?

[Ood]

It's a wiki, all constructive help is appreciated.

[Ood]

Added my take on convoys:
grid12.wikia.com/wiki/Convoy_Basics
It's in the guides section.

[gingerbear]

Jul 24, 2013 10:11:54 GMT -5 Ood said:

Added my take on convoys:
grid12.wikia.com/wiki/Convoy_Basics
It's in the guides section.

Instead of recommended tanks I'd suggest with recommended tactics.

For example at most of the convoys if you have a good shield or stunner in the first line (venge, pally, corsair), then suddenly other dps tanks (viking, wildfire) are viable too instead of the propagated spectre/cutlass/hornet trio.

Just saying this because that wiki page seems to suggest that only about 5 tanks are viable. Well, probably those 5 tanks are the best, but people will focus on getting the tank instead of getting the idea behind it.

What I would do (instead of actually doing it since I don't want to rewrite that page without asking) for the page:

1. Describe the general way of convoy behavior (spawning rate, movement, etc.)
2. Describe each tank of what it can add to the battle, maybe using bold text or underline for the main ones.

3. Describe killing tactics (shielded trailing, chain stun-lock, flux "injection", etc.) with suggestions of team composition, e.g.:

Shielded trailing means following the Convoy with durable tanks on the front to soak damage, while the DPS tanks withering down the individual units. Corsairs in the front line are a generally good idea; 3 corsairs can more-less infinitely cover a gunfire of a trailed enemy. DPS tanks can be anything that have enough range to attack while staying behind the corsairs - if these are bold enough to go deep, then practically any of them would do the job.

Shielded trailing is best against baryonic and flux convoys; At the former because the close and elongated form of the convoy gives opportunities for easy cover and also efficient shears, while at the latter the raw damage output of the convoy can be greatly reduced by the impregnable armor the corsairs have to offer.

The advantage of this tactic is that the players don't lose attack time with catching back up to the convoy after singling out a target (like at the chain stun-lock tactic), however, this advantage only shows if the convoy passes through enough cleared area. For this reason shielded trailing is generally mixed up with other techniques so the "special" tanks of those can safely prepare their triggers.

And so on.

[Ood]

@gb
It's a personal guide to whoever wants to use it. Yes it's on the wiki, but it's my opinion, not 'just the facts' like the rest of the wiki.

If you'd like to make a guide suggesting different things and going into more detail, by all means, please do.

Don't get me wrong, I'm open for suggestions on how to improve... but the newbies I see not knowing what to do for a convoy are more often confused about what tank to use than anything.

I expect to change some things around in the future (pictures describing instead of words describing).

[gingerbear]

Ah, so it's basically a TLDR version of how to do stuff. While I agree that it's useful for newcomers, it's not encouraging them to think or to understand much. Well, that is of course not the intention of a wiki in any case, but... yeah, it's just me rambling about guides in general. Don't mind me.

[Ood]

Nono, thanks for the advice GB, I might not add things like that right away... but eventually it might get put in there... or perhaps in a separate 'Advanced Convoying' guide.

[Ood]

So...

Been a while since the wiki had any updates.

Trying to make it easier on myself by putting more volitle infos into a template instead of typing it all out. It's significantly easier, so unless there are any major objections, in the coming days, tank pages will start to resemble this:

grid12.wikia.com/wiki/Avenger

If there is anything you would like to be added (in particular to the new 'infobox') please say so NOW, not after they are all finished. I can also delete things if they are deemed unnecessary.

Note: Trigger infos will be there in terms of 'AoE Stun' or 'On-hit Paralyze', etc.

What will almost certainly be included also will be pulched hp/shield/dps.

[delsy]

Well, I'm preparing to jump back into wiki-ing, but as I do, I'd like to re-open discussion on how we go about it. Namely, what should we do with articles on features phased out of the game? Gridshards and VP certainly aren't coming back.

What kind of content do we want new readers to find on the wiki?
1: The usual on mechanics, tanks, etc. plus the older features of Grid, with articles explaining the scrapped things that led up to the current game.
2: The current state of the game only, and let the build notes page interest the curious.
3: Some of 1 and 2, with people picking notable builds or "eras" and writing articles on them.

1 and 3 would be interesting if they could be managed, 2 is the most within our means.

[Justin]

I'd only be able to add onto the newer information because I barely know anything about VP/gridshards besides what is put into the wiki.

[Crunch]

delsy, I personally like the inclusion of the history in a wiki, but perhaps it should be included in some type of archive section. I think that updating the recent build notes would be a good start. Also, David was looking at porting the wiki over to Github so that we could more easily auto-update details after Rob dumps the latest build data, like Amit's viewer does. I've been porting some things over, specifically the tank info, but I can only do so many at a time before I bore myself to death.