Wed, 01 Jul 2015 22:21:58

Ask: How would one be able to access a dungeon? Or are dungeons just not yet implemented with V2? (I swear every time I hear V2 I think of a shitty motor engine...)

Not implemented.


Mon, 29 Jun 2015 18:52:12

Ask: Are our accounts on the old forums being moved to the new forums?

We originally wanted to copy posts and accounts over, but forumotion wouldn’t give us access to the database to do it.


Mon, 29 Jun 2015 09:56:55

Text Post: New forums!

Hi all, as part of making Overseer better, we’ve set up new forums!

http://forums.overseer2.com/

These forums will be used for both v1 AND v2 discussion.

You should also note that the current forums will be shut down and all threads locked in 48 hours. This is to let currently running threads finish out. If you think your thread will run for longer than that, you’re encouraged to migrate it to the new forum.


Sun, 28 Jun 2015 01:32:24

Text Post: Overseer v2 is going back to alpha

The short version is our organizational structure is terrible, a thing happened with miscommunication which caused the current problems, there are bugs everywhere, and the v2 release was primarily due to public pressure in the first place (it probably wasn’t ready when we put it out)

We’re going to need quite a bit more time to iron out some of the more pervasive issues and set up some good internal practices and other stuff that honestly should have been done ages ago and is coming back to bite us now.

I don’t think any of us had any experience with a major project before this and it’s a miracle nothing like this happened before. In the meantime v2 will stay up but in “alpha” state (which means it’s not guaranteed to be playable :/) and v1 will continue running as it has been. Testing and stuff on v2 remain appreciated.

I really am sorry about this, but I think it’s the best course of action at this stage given the state of v2 at present. We won’t be making any changes to reflect the new status, we’re just announcing that v2 isn’t really ready for public enjoyment at this stage. Hopefully we can turn this around over the next month or two.

No data is being lost anywhere, so no need to worry about that.


Sun, 28 Jun 2015 00:56:51

Text Post:

On another note - login may currently be broken for some users. We’re aware and fixing this as a priority. Sorry for any inconvenience!


Sun, 28 Jun 2015 00:53:43

Text Post:

image

502 errors usually mean “over capacity”. In our case, it’s an infinite loop somewhere in the code causing thing sto lock up so there’s no capacity available for new page loads. We’re working to locate the issue but for now we need to manually restart stuff whenever one happens.


Fri, 26 Jun 2015 18:37:46

Text Post:

Hi all, Thell here, one of the server guys for TOP!

We’ve been talking in the dev chat and after looking over the bug reports we’ve received we’ve decided that the game is… perhaps a BIT more broken than we thought it was. That’s fine. In fact it’s good, actually, that we have so many bug reports - it means people are not just finding them, but actually letting us know!

With this in mind though, we’re taking a new development direction for the moment. Below is a screenshot of the bug tracker:

As you can see, we a) Do indeed know Quick Item Creation doesn’t work and b) Have quite a few to get through. So we’ve decided, as a team – we’re not adding any new features until the majority of these are fixed.

So this is all well and good, but how can YOU help? First things first, take a look through the open bugs first. If you’re posting duplicates, this slows us down a LOT. Even worse is when you’re posting a bug that we already fixed – we have a seperate, internal development build we’ve set up that we use to test fixes now. It might be committed there, but not on live yet – this is normal! Lots of developers do this. I’m not 100% sure if we have a set day for pushing patches out, but leave re-making a bug report until we’ve announced it and put the fix in the changelog, and THEN see if it still works.

Secondly, reporting itself – when you report a bug, there’s a few things you need to tell us. First, what it is – is it a gameplay bug? Interface? If so, put it in the appropriate category. For anything else, General is fine. Next is reproducibility. Does it happen often? Is there a set process that will make it happen? If so, click always. Does it only happen some of the time? Click sometimes. Does it happen at random? … You get the idea. If it IS reproducible, make a note of how to do it – this helps us a lot!

Next, severity. There’s 4 main ones that should be used for bug reports – minor, major, crash, and block. Minor is for things that aren’t a huge issue, you can still play with the bug there. Major is for things that make things much, much harder, or are quite clearly out of the ordinary. Gameplay mechanics not working right (for example, fatigue not applying penalties) go into major. Crash is for things that are just utterly broken. Block is for things that stop the game/site as a whole from working.

Next up, Priority. Ordinarily you can leave this as normal, we go through every so often and assign based on need. If it’s a crash or block severity, you can set this to a higher one. Really, use your best judgement – reporting a specific item won’t alchemise as urgent and block will result in us moving that to the end of the queue and slapping you. Platform, OS, and OS version are irrelevant unless it’s an interface bug – but your browser details here.

Now for the important stuff. Summary, Description, and Steps to Reproduce. These are the three singular most important fields on the bug report form. Summary should be enough that we know at a glance what the bug is. Description is for more in depth detail – what, where, what you were doing, etc. Reproducibility, if you fill this in, is an absolute godsend to us – it gives us a good idea of WHAT causes it. Bugs with this properly filled in usually get fixed the fastest.

Now you know how to properly fill in a bug report, what’s the third thing you can do to help? Well…

Avoid things like this. Anonymity was enabled on the bug tracker so you could let us know about bugs, not so you can spam us with useless comments berating us for not fixing it quicker. We DO know the bug exists, but please remember – we have jobs, school, life stuff etc that takes priority over the game. This is a beta that we released because people wanted it – there WILL be bugs, some serious. That’s sort of the point.

Regardless of that last point, we’re really pleased that people are letting us know where things are going wrong! For those who don’t know, the bug tracker is at http://bugs.overseer2.com/ which is the best place to report them. Thanks, and hope you’re enjoying the game!


Thu, 25 Jun 2015 23:25:09

Ask: So, I was thinking, and not having a submit button on the quick submission form for items makes it kind of useless, wouldn't you agree?

It’s not yet finished.


Thu, 25 Jun 2015 08:01:01

Ask: Where can you get a Cloak?? I've been looking everywhere to get it to make Blank God Tier Pajamas.

The base item catalogue may very well have what you seek.


Thu, 25 Jun 2015 06:49:43

Ask: Are you going to include a way to undo server client chains in V2, at some point?

Yes.

Copyright © 2013 ARG Loop & The Overseer. All rights reserved.
Homestuck is copyright © Andrew Hussie.
Page executed in 0.25670099258423 seconds.