Skip to main content

News

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - DaVince

1006
GMail thinks that Spherical emails are spam. It should be obvious why if you check the attached screenshot... The addresses mismatch or they're not verified to belong to each other or whatever. This should be fixed.
1007
Game Development / Re: The Screenshot Thread

History was made in this post :P

Screenshots from a side scroller detective rpg that me and my friend have been working on. Opinions?

(edit - now the official screenshot thread +Neo)

Looks freakin' sweet. Any special reason you decided to use Sphere's internal map engine?
1008
Site Comments / Re: What about botters?

Are we protected from bot accounts? Already we have one: http://forums.spheredev.org/index.php?action=profile;u=7

I'm just curious. Now that N E O (neologix) is an admin, I'm sure everything he wanted to do to combat such attempts can now be done. I hope, that is.

I saw that account, but how can you tell it's an actual bot? The only thing weird about it so far is the nickname, and people are known for making weird nicknames, too...
1009
Site Comments / Re: Wiki

I want to amend a bit the editing procedure we'll use for Sphere's API on the wiki. I want functions to be tagged with the earliest possible version of Sphere in which they appeared and if they're deprecated in 1.6 and later. You can probably use extra categories for both, but let's be consistent throughout.

For pre-1.5, say its version is 1.1; 1.5 is 1.5, 1.6 is 1.6, and 1.7 (however alpha or beta it may still be) is 1.7. TurboSphere will be considered a version, and any functions marked as such will only consider the latest working version of TurboSphere until TS actually reaches at least Sphere 1.5 parity, then those after that will have TurboSphere version numbers.

Good idea. What's going to be the standard way to do this? I'm thinking a bar at the top of the article reserved for indicating what version it was introduced in, and if it should still be used. Something like:

Code: [Select]
[ Introduced in 1.0 | Removed in 1.6 onward; do not use! ]
1010
Site Comments / Re: Wiki
As far as I'm concerned, go ahead and put them on there. :)

Which articles? (Not like it matters much, all of them are useful.) Are they in HTML or wikisource? Might need to do some conversion there.
1011
Site Comments / Spherical Wiki
I figured it would be a good idea to make a new thread regarding discussion of the new wiki.

To start out, I salvaged and copied over the function reference page from the old wiki (thank you, WayBackMachine!):
http://wiki.spheredev.org/Functions

Also started porting over my tutorial, though the subpages which contain the bulk of the content hadn't been cached so I have to manually restyle everything (will finish this later):
http://wiki.spheredev.org/DaVince_scripting_tutorial
1012
Spherical News / Re: Welcome Back!!!
Awesome.