RPGnet - User contributions [en]

AnglerStudios:Main Page

2007-10-14T07:33:01Z

G01d HaCkEr:

=Angler Studios Main Page=

==NB: This project is no longer active, due to lack of motivation by all 3 participants.==

Welcome to the main page for Angler Studios! The name 'Angler' is derived from the initials of the 2 programmers (AN and GL) and the first initial of the creative guy (R). It consists of 3 friends and other contributors, whose aim is to make an as-yet unnamed RPG game that has an interesting story, and potentially new, interesting gameplay mechanics. It's also a great first foray into making computer games, which is something at least 2 of us want to go into when we graduate from uni.

The team consists of:

* Richard S - character (and other stuff) artist, story writer, primary map designer / content generator
* Greg L - programmer #1
* Andrew N - programmer #2

==Links==
Here are some suggested links to pages which may not exist yet, to anticipate some possible areas we want to work on.

[[AnglerStudios:News|News]] | [[AnglerStudios:Story|Storyline]] | [[AnglerStudios:Battle_System|Battle System Design]] | [[AnglerStudios:Editor|Editor Design]] | [[AnglerStudios:Map|Map Issues]] | [[AnglerStudios:Coding|Coding Discussion]] | [[AnglerStudios:Art|Art Discussion]] | [[AnglerStudios:Files|Uploaded Files]] | [[AnglerStudios:Links|Links to Resources]] | [[AnglerStudios:Misc|Miscellaneous Discussion]]

That's all for now, if a page doesn't exist, create it! Also, if you are not on the team and you stumbled across this page, and want to help out, please use the [[AnglerStudios:How_can_I_help|How can I help?]] page.

Thanks!

User:G01d HaCkEr

2006-08-02T03:33:09Z

G01d HaCkEr:

Moo cow.

AnglerStudios:Battle System

2006-08-02T03:32:33Z

G01d HaCkEr: Minor points about poison.

Back to the [[AnglerStudios:Main_Page|Main Page]].
=Battle System Design Issues=

I've had an idea about a fairly useful battle system idea type concept thingy...

If you played Final Fantasy 8, do you remember how enemies were scaled in strength according to your party's level? They would jump up a few levels if you were too high for them, and vice versa. Obviously there were limits, but this ensured that enemies always posed something resembling a challenge anyways (stopped you steamrolling through the same lowbie monsters every time like a zombie just grinding for XP...)

We could implement a similar idea... we could have say an instance of the enemy npc class for each monster, but have it contain like a level parameter, and how strong it is. We can then introduce paramaters for how much strength they gain per level, so their base strength at level 5 is say... 15... and it jumps up 2 points per level. A level 15 group encounters this monster so it scales itself up from level 5 to anywhere between level 12 - 18 (im using broad numbers here since we havent decided on damage scales and stuff yet. Can a level 15 beat a level 18??). So lets say it chooses level 12 (for example's sake). its scaled itself up from its base level by 7 so we add 7 X 2 (7 levels times 2 str per level for scaling) and get a more evenly matched fight. Obviously this would take a bit of fine tuning to ensure the monster didn't become too uber too quickly etc, but that's got to be done anyways.

This would also reduce tedium when your party obviously overpowers the enemies in the area.

Alternatively we could simply reduce encounter rate when your party's too strong for the monsters in the area (monsters too scared to attack... slightly WoW-like but yeah) but this could be fun. Anyways, thats just an idea. Any thoughts? [[User:Natoli|Natoli]] 20:03, 5 June 2006 (PDT)

----

If we went with the first suggestion, the monsters would have to scale up in such a fashion that they would be stronger, but still weaker (relative to the level difference) so there would be an actual benefit in going up levels.

The second one sounds good, though - except it prevents players simply leveling up by slogging through heaps of low levels if they want to. Do we want to prevent that?

RichardS

----

Spose there's pros and cons to it.
For the first idea, I suggest if we go with it that we could cap the amount that the enemy scales up in difficulty... say 5 levels or so only, so that eventually you'll still OMGWTFPWN them, but they'll still pose a challenge if say, someone gets lost in the forest and ends up in so many random battles that they level up too much. I agree that they'd have to scale to be weaker eventually as you said, but its not like the slime that is attacking you for revenge since you killed his family, friends and 99.9% of his entire race is going to still be as pathetically weak as the others... right?

The other idea... after a few levels in an area, chances are the player's going to start steamrolling through the monsters anyway. Maybe we could/should scale the amount of XP required to level up so that if they decide to continue training there (pure grinding for xp until they're so awesomely powerful that they can one-shot the final boss or something...) that it'll take forever to make any progress. More like dissuading someone from spending 12 hours of their life in one zone killing monsters to get to level 99 or something.

Obviously this needs more thought, but as far as Im concerned continually training on mobs that are too weak is kinda pointless anyway.
[[User:Natoli|Natoli]] 04:44, 7 June 2006 (PDT)

----

Maybe we could scale the XP gain to lower according to some scale the higher your level is, sort of like Diablo 2, where you'd only get full XP if you were within 5 lvls of the monsters you were killing, and then would get less and less for monsters too high or low.

RichardS

----

Lot of good discussion here.

My initial thought is: Why are we talking about dissuading people from playing our game? Crikey, if someone wants to grind for 12 hours in our game to one-shot the final boss, good for them! That's one way of playing we didn't necessarily foresee, but it's a valid possibility. I fear that RPGs, especially ones like these of such length are already over-prone to repetitive grinding and partial-completion, not to mention they are not as accessible as more arcade-style games. I have the feeling I'm going to have to try really hard when it's done to convince my friends to play it, rather than them wanting to play it. For some, they will only play because I insist, not because they love in-depth RPGs... so if they do play, why make them frustrated and force them to play a particular way?

I think it's quite possible to define a way of modifying the stats of a monster based on level. Perhaps we have an equation field that we can see that determines how to change the stats per level? Perhaps a base stats attributes, then another set of stats that has how much to add per level up to a cap? e.g. perhaps only HP changes as the level goes up, so the fights last longer...

Also, just sort of back to my first point, do we want battles to always be balanced and long? I know I personally '''like''' if I can find a nice low level area to blitz through, with a few quick battles that net me a few items and a handful of exp. Sure, that may not be the conventional playstyle, but hey, it's mine, and it's valid. You don't make games to tell people how to play them. You create something they can play however they darn well feel like. If you limit them too much, it sucks, and people stop playing your game.

I'm not totally against your arguments, though. I'm just bringing up a contrary POV. -[[User:G01d HaCkEr|G01d HaCkEr]] 05:58, 7 June 2006 (PDT)

----

That's a good point - the feeling of godlike supremacy that rushes up your spine as your shatter a group of frail slime monsters with the force of your mightiest weapons is a major selling point in these games.

[[User:RichardS|RichardS]] 05:36, 8 June 2006 (PDT)

---
Yeah I'll give you that much... farming Deadmines in WoW in the space of 20 minutes is still fun occasionally :P [[User:Natoli|Natoli]] 10:34, 9 June 2006 (PDT)

=Status Effects=

Do we want multiple status effects to be on a character at once? I'd say yes... but do we want a limit to this?
An idea I had for status effects is to have a spell that can remove ANY status effect (except death of course) - but the catch is it will only remove one - whether its a negative effect or a positive effect even! This can add some more strategy to the battle too... if you have beneficial effects and no negative ones, casting the spell is stupid since you will lose a benefit.

Now, the question to this is... do we select the removed effect at random or have a priority system (so it removes "worse" negative effects before less serious negative effects before beneficial effects)?

What say you? [[User:Natoli|Natoli]] 20:33, 6 July 2006 (PDT)

I don't think they should be removed at random, but I think we'll have to choose between a priority system or a choice. Random seems to arbritary to be fun. A priority system wouldn't be bad or anything, but a choice can be strategic. But then again, maybe its too much freedom (and perhaps hard to program).

At any rate, I think we definately need more than one status effect at a time. In fact, that been incorporated conceptually into the battle system design we discussed (I'll get around to putting that all up eventually...).

And I reckon we could have more than one type of spell - one which cures only one effect, and one which clears everything, good or bad. And perhaps one that erases one at random?

[[User:RichardS|RichardS]] 00:35, 18 July 2006 (PDT)

Hmm... every RPG I've ever played seems to have a spell for each status effect, so I assume we're going to do that too anyways... but adding one uber-status repair spell that can backfire could be fun :)

Another idea for this sort of thing is, admittedly, something I saw in WoW but its still cool. Basically they group their status effects in different ways... like there are different types of poisons that can be removed with the cleanse poison spell... many types of diseases that can be removed with cure disease... and a spell that works on all of the same type.

Only thing is that we probably wouldn't have enough status effects to warrant that... unless we created multi-purpse spells that cleaned say... 3 effects but ONLY if they were of 3 selected types... (say one that can cure poison, drunk and paralyse, and a different one to dispel sleep, confuse and slow or something like that).

[[User:Natoli|Natoli]] 20:25, 1 August 2006 (PDT)

Some quick, good points on stats, especially ''poison'':
* Poison should take a percentage of your health off per 'tick'/turn, rather than a fixed amount. This makes it always affect your characters the same.
* Natoli suggested that we have a minimum health level where Poison cannot kill your character for a few turns, since that can be a particularly frustrating thing to happen. So, say Poison takes 3% of your HP per turn, if you are on 3% or less of your max HP when Poison goes to do it's thing and subtract the 3%, it instead adds one to, say, a 'grace' counter, and doesn't subtract HP. Just an idea.

--[[User:G01d HaCkEr|g01d_HaCkEr]] 20:32, 1 August 2006 (PDT)

=Levelling and stat increases=

Quick question... what style of stat increase do we want as the characters develop?
I was thinking that different characters could have a different multiplier for stats... so that we could get something like a swordsman's strength increasing by a factor of say... 2 or 3 per level... while a mage's strength could be equal to half (or even less than half) times his level.
This would be fairly easy to program (and could possibly result in storing less data since the stat calculations can be done "on the fly"), but it results in a linear character progression. This may or may not be a bad thing... though it could cause balancing issues end-game. Of course... if enemies progressed in the same fashion the balancing issue could be nonexistent. Just wanted to see how you guys felt abouot it... because its probably REALLY inefficient to say, store stats per character per level to a max level of 100 or something. Another bonus to my propsed idea would be that we wouldn't need to have a level cap... well... not until we start getting overflow errors on character's strength values at level 704657 anyway :P
Any other ways we could possibly see character progression? Even a more complex formula or such? (maybe randomising it to a degree that they get stronger in their primary stats, but not always by the same amount?)

Discuss :) [[User:Natoli|Natoli]] 21:25, 6 July 2006 (PDT)

That's an interesting idea I hadn't thought of... if we did go that way, it'd have to be a slightly more complicated formula than 'x2', at least some of the time. I reckon we'd still want a cap, but now we can put it whereever we want and not have to write out the stats all individually. We might even move the cap as the characters progress.

Balance would be an issue, but that can be overcome in playtesting. I hope.

And the slightly randomised stats is a good idea too... I think that, if you could do it, you should go for that.

[[User:RichardS|RichardS]] 00:34, 18 July 2006 (PDT)

AnglerStudios:Code Global

2006-08-02T03:19:30Z

G01d HaCkEr:

Back to the [[AnglerStudios:Main Page|Main Page]].

Back to the [[AnglerStudios:Coding|Coding Discussion Page]].

=class global=
Name: global
==Members==
BITMAP *dbuffer; // double buffer to draw to for all graphics calls

// Linked list declarations, such as
* add
* remove
* search
* sort
Will upload what I have so far for this. Have all but completed the header file for the linkedList class (it's big enough to warrant it's own file, we can just include the header in the global.h header file.

Still to write the implementation/CPP file. Plan to do this by Friday 11th August, 2006.
--[[User:G01d HaCkEr|g01d_HaCkEr]] 20:19, 1 August 2006 (PDT)

AnglerStudios:Coding

2006-08-02T03:16:31Z

G01d HaCkEr:

Back to the [[AnglerStudios:Main_Page|Main Page]].
=Coding Discussion=

The game classes so far we have to implement.

'''NB:''' Due to our decision to modularize the code as much as possible, if you decide your listed class needs 5 companion classes, you are responsible for these as well, unless they are sufficiently large to warrant delegation.

{|
|-
|'''Module'''
|'''Programmer'''
|'''Status'''
|'''.h Due'''
|'''.cpp Due'''
|-
|[[AnglerStudios:Code Global|Global]]
|Both
|Started
|Ongoing
|Ongoing
|-
|Character
|Natoli
|Not done
|-
|Party
|Natoli
|Not done
|-
|Weapon
|Natoli
|Not done
|-
|Item
|Natoli
|Not done
|-
|Grid
|Greg w/ Natoli
|Not done
|-
|World / Game Map
|Greg
|Not done
|-
|Battle
|Natoli
|Not done
|-
|NPC
|Greg
|Not done
|-
|Dialogue
|Greg
|Not done
|-
|DialogueNode
|Greg
|Not done
|-
|[[AnglerStudios:Code Stats|Stats]]
|Natoli
|Started
|-
|Menu
|Greg
|Not done
|-
|MenuNode
|Greg
|Not done
|-
|Cutscene
|Greg
|Not done
|-
|Inventory
|Natoli
|Not done
|-
|InventoryNode
|Natoli
|Not done
|-
|Aspect
|Natoli
|Not done
|-
|Animation
|Greg
|Not done
|-
|Projectile
|Natoli
|Not done
|-
|Text
|Greg
|Not done
|}

AnglerStudios:Coding

2006-08-02T03:14:50Z

G01d HaCkEr: Added columns to table

Back to the [[AnglerStudios:Main_Page|Main Page]].
=Coding Discussion=

The game classes so far we have to implement.

'''NB:''' Due to our decision to modularize the code as much as possible, if you decide your listed class needs 5 companion classes, you are responsible for these as well, unless they are sufficiently large to warrant delegation.

{|
|-
|'''Module'''
|'''Programmer'''
|'''Status'''
|'''.h Due'''
|'''.cpp Due'''
|-
|[[AnglerStudios:Code Global|Global]]
|Both
|Started
|-
|Character
|Natoli
|Not done
|-
|Party
|Natoli
|Not done
|-
|Weapon
|Natoli
|Not done
|-
|Item
|Natoli
|Not done
|-
|Grid
|Greg w/ Natoli
|Not done
|-
|World / Game Map
|Greg
|Not done
|-
|Battle
|Natoli
|Not done
|-
|NPC
|Greg
|Not done
|-
|Dialogue
|Greg
|Not done
|-
|DialogueNode
|Greg
|Not done
|-
|[[AnglerStudios:Code Stats|Stats]]
|Natoli
|Started
|-
|Menu
|Greg
|Not done
|-
|MenuNode
|Greg
|Not done
|-
|Cutscene
|Greg
|Not done
|-
|Inventory
|Natoli
|Not done
|-
|InventoryNode
|Natoli
|Not done
|-
|Aspect
|Natoli
|Not done
|-
|Animation
|Greg
|Not done
|-
|Projectile
|Natoli
|Not done
|-
|Text
|Greg
|Not done
|}

AnglerStudios:Code Global

2006-07-07T03:30:02Z

G01d HaCkEr:

Back to the [[AnglerStudios:Main Page|Main Page]].

=class global=
Name: global
==Members==
BITMAP *dbuffer; // double buffer to draw to for all graphics calls

// Linked list declarations, such as
* add
* remove
* search
* sort

AnglerStudios:Code Global

2006-07-07T03:28:30Z

G01d HaCkEr:

Back to the [[AnglerStudios:Main Page|Main Page]].

=class global=
Name: global
==Members==
BITMAP *dbuffer; // double buffer to draw to for all graphics calls

// Linked list declarations

AnglerStudios:Code Global

2006-07-07T03:25:59Z

G01d HaCkEr:

Back to the [[AnglerStudios:Main Page|Main Page]].

=class global=
Name: global
==Members==
BITMAP *dbuffer; // double buffer to draw to for all graphics calls
// Linked list declarations

AnglerStudios:Coding

2006-07-07T03:23:25Z

G01d HaCkEr:

Back to the [[AnglerStudios:Main_Page|Main Page]].
=Coding Discussion=

The game classes so far we have to implement.

'''NB:''' Due to our decision to modularize the code as much as possible, if you decide your listed class needs 5 companion classes, you are responsible for these as well, unless they are sufficiently large to warrant delegation.

{|
|-
|[[AnglerStudios:Code Global|Global]]
|Both
|Started
|-
|Character
|Natoli
|Not done
|-
|Party
|Natoli
|Not done
|-
|Weapon
|Natoli
|Not done
|-
|Item
|Natoli
|Not done
|-
|Grid
|Greg w/ Natoli
|Not done
|-
|World / Game Map
|Greg
|Not done
|-
|Battle
|Natoli
|Not done
|-
|NPC
|Greg
|Not done
|-
|Dialogue
|Greg
|Not done
|-
|DialogueNode
|Greg
|Not done
|-
|[[AnglerStudios:Code Stats|Stats]]
|Natoli
|Started
|-
|Menu
|Greg
|Not done
|-
|MenuNode
|Greg
|Not done
|-
|Cutscene
|Greg
|Not done
|-
|Inventory
|Natoli
|Not done
|-
|InventoryNode
|Natoli
|Not done
|-
|Aspect
|Natoli
|Not done
|-
|Animation
|Greg
|Not done
|-
|Projectile
|Natoli
|Not done
|-
|Text
|Greg
|Not done
|}

AnglerStudios:Coding

2006-07-07T03:22:41Z

G01d HaCkEr:

Back to the [[AnglerStudios:Main_Page|Main Page]].
=Coding Discussion=

The game classes so far we have to implement.

'''NB:''' Due to our decision to modularize the code as much as possible, if you decide your listed class needs 5 companion classes, you are responsible for these as well, unless they are sufficiently large to warrant delegation.

{|
|-
|[[AnglerStudios:Code Global|Global class]]
|Both
|Started
|-
|Character
|Natoli
|Not done
|-
|Party
|Natoli
|Not done
|-
|Weapon
|Natoli
|Not done
|-
|Item
|Natoli
|Not done
|-
|Grid
|Greg w/ Natoli
|Not done
|-
|World / Game Map
|Greg
|Not done
|-
|Battle
|Natoli
|Not done
|-
|NPC
|Greg
|Not done
|-
|Dialogue
|Greg
|Not done
|-
|DialogueNode
|Greg
|Not done
|-
|[[AnglerStudios:Code Stats|Stats]]
|Natoli
|Started
|-
|Menu
|Greg
|Not done
|-
|MenuNode
|Greg
|Not done
|-
|Cutscene
|Greg
|Not done
|-
|Inventory
|Natoli
|Not done
|-
|InventoryNode
|Natoli
|Not done
|-
|Aspect
|Natoli
|Not done
|-
|Animation
|Greg
|Not done
|-
|Projectile
|Natoli
|Not done
|-
|Text
|Greg
|Not done
|}

AnglerStudios:Coding

2006-07-07T02:40:58Z

G01d HaCkEr:

Back to the [[AnglerStudios:Main_Page|Main Page]].
=Coding Discussion=

The game classes so far we have to implement.

'''NB:''' Due to our decision to modularize the code as much as possible, if you decide your listed class needs 5 companion classes, you are responsible for these as well, unless they are sufficiently large to warrant delegation.

{|
|-
|Character
|Natoli
|Not done
|-
|Party
|Natoli
|Not done
|-
|Weapon
|Natoli
|Not done
|-
|Item
|Natoli
|Not done
|-
|Grid
|Greg w/ Natoli
|Not done
|-
|World / Game Map
|Greg
|Not done
|-
|Battle
|Natoli
|Not done
|-
|NPC
|Greg
|Not done
|-
|Dialogue
|Greg
|Not done
|-
|DialogueNode
|Greg
|Not done
|-
|Stats
|Natoli
|Not done
|-
|Menu
|Greg
|Not done
|-
|MenuNode
|Greg
|Not done
|-
|Cutscene
|Greg
|Not done
|-
|Inventory
|Natoli
|Not done
|-
|InventoryNode
|Natoli
|Not done
|-
|Aspect
|Natoli
|Not done
|-
|Animation
|Greg
|Not done
|-
|Projectile
|Natoli
|Not done
|-
|Text
|Greg
|Not done
|}

AnglerStudios:Coding

2006-07-07T02:13:14Z

G01d HaCkEr:

Back to the [[AnglerStudios:Main_Page|Main Page]].
=Coding Discussion=

The game classes so far we have to implement.

'''NB:''' Due to our decision to modularize the code as much as possible, if you decide your listed class needs 5 companion classes, you are responsible for these as well, unless they are sufficiently large to warrant delegation.

{|
|-
|character
|Natoli
|Not done
|-
|party
|Natoli
|Not done
|-
|weapon
|Natoli
|Not done
|-
|item
|Natoli
|Not done
|-
|grid
|Greg w/ Natoli
|Not done
|-
|world / game map
|Greg
|Not done
|-
|battle
|Natoli
|Not done
|-
|NPC
|Greg
|Not done
|-
|Dialogue
|Greg
|Not done
|-
|DialogueNode
|Greg
|Not done
|-
|Stats
|Natoli
|Not done
|-
|Menu
|Greg
|Not done
|-
|MenuNode
|Greg
|Not done
|-
|Cutscene
|Greg
|Not done
|-
|Inventory
|Natoli
|Not done
|-
|InventoryNode
|Natoli
|Not done
|-
|Aspect
|Natoli
|Not done
|-
|Animation
|Greg
|Not done
|-
|Projectile
|Natoli
|Not done
|-
|Text
|Greg
|Not done
|}

AnglerStudios:Coding

2006-07-07T02:12:11Z

G01d HaCkEr:

Back to the [[AnglerStudios:Main_Page|Main Page]].
=Coding Discussion=

The game classes so far we have to implement.

'''NB:''' Due to our decision to modularize the code as much as possible, if you decide your listed class needs 5 companion classes, you are responsible for these as well, unless they are sufficiently large to warrant delegation.

{|
|-
|character
|Natoli
|Not done
|-
|party
|Natoli
|Not done
|-
|weapon
|Natoli
|Not done
|-
|item
|Natoli
|Not done
|-
|grid
|Greg w/ Natoli
|Not done
|-
|world / game map
|Greg
|Not done
|-
|battle
|Natoli
|Not done
|-
|NPC
|Greg
|Not done
|-
|Dialogue
|Greg
|Not done
|-
|DialogueNode
|Greg
|Not done
|-
|Stats
|Natoli
|Not done
|-
|Menu
|Greg
|Not done
|-
|MenuNode
|Greg
|Not done
|-
|Cutscene
|Greg?
|Not done
|-
|Inventory
|Natoli
|Not done
|-
|InventoryNode
|Natoli
|Not done
|-
|Aspect
|Natoli
|Not done
|-
|Animation
|Greg
|Not done
|-
|Projectile
|Natoli
|Not done
|-
|Text
|Greg
|Not done
|}

AnglerStudios:Coding

2006-07-07T02:10:00Z

G01d HaCkEr:

Back to the [[AnglerStudios:Main_Page|Main Page]].
=Coding Discussion=

The game classes so far we have to implement.

'''NB:''' Due to our decision to modularize the code as much as possible, if you decide your listed class needs 5 companion classes, you are responsible for these as well, unless they are sufficiently large to warrant delegation.

{|
|-
|character
|Natoli?
|Not done
|-
|party
|Natoli?
|Not done
|-
|weapon
|Natoli?
|Not done
|-
|item
|Natoli?
|Not done
|-
|grid
|Greg w/ Natoli
|Not done
|-
|world / game map
|Greg?
|Not done
|-
|battle
|Natoli?
|Not done
|-
|NPC
|Greg?
|Not done
|-
|Dialogue
|Greg?
|Not done
|-
|DialogueNode
|Greg?
|Not done
|-
|Stats
|Greg?
|Not done
|-
|Menu
|Programmer
|Not done
|-
|MenuNode
|Programmer
|Not done
|-
|Cutscene
|Greg?
|Not done
|-
|Inventory
|Natoli?
|Not done
|-
|InventoryNode
|Natoli?
|Not done
|-
|Aspect
|Natoli?
|Not done
|-
|Animation
|Greg?
|Not done
|-
|Projectile
|Natoli?
|Not done
|-
|Text
|Greg?
|Not done
|}

AnglerStudios:Coding

2006-07-07T02:06:58Z

G01d HaCkEr:

Back to the [[AnglerStudios:Main_Page|Main Page]].
=Coding Discussion=

The game classes so far we have to implement:
'''NB:''' Due to our decision to modularize the code as much as possible, if you decide your listed class needs 5 companion classes, you are responsible for these as well, unless they are sufficiently large to warrant delegation.

{|
|-
|character
|Natoli?
|Not done
|-
|party
|Natoli?
|Not done
|-
|weapon
|Programmer
|Not done
|-
|item
|Programmer
|Not done
|-
|grid
|Greg w/ Natoli
|Not done
|-
|world / game map
|Greg?
|Not done
|-
|battle
|Natoli?
|Not done
|-
|NPC
|Greg?
|Not done
|-
|Dialogue
|Greg?
|Not done
|-
|DialogueNode
|Greg?
|Not done
|-
|Stats
|Greg?
|Not done
|-
|Menu
|Programmer
|Not done
|-
|MenuNode
|Programmer
|Not done
|-
|Cutscene
|Greg?
|Not done
|-
|Inventory
|Natoli?
|Not done
|-
|InventoryNode
|Natoli?
|Not done
|-
|Aspect
|Natoli?
|Not done
|-
|Animation
|Greg?
|Not done
|-
|Projectile
|Natoli?
|Not done
|-
|Text
|Greg?
|Not done
|}

AnglerStudios:Coding

2006-07-07T02:00:54Z

G01d HaCkEr:

Back to the [[AnglerStudios:Main_Page|Main Page]].
=Coding Discussion=

The game classes so far we have to implement:

{|
|-
|character
|Natoli?
|Not done
|-
|party
|Natoli?
|Not done
|-
|weapon
|Programmer
|Not done
|-
|item
|Programmer
|Not done
|-
|grid
|Greg w/ Natoli
|Not done
|-
|world / game map
|Greg?
|Not done
|-
|battle
|Natoli?
|Not done
|-
|NPC
|Greg?
|Not done
|-
|Dialogue
|Greg?
|Not done
|-
|DialogueNode
|Greg?
|Not done
|-
|Stats
|Greg?
|Not done
|-
|Menu
|Programmer
|Not done
|-
|MenuNode
|Programmer
|Not done
|-
|Cutscene
|Greg?
|Not done
|-
|Inventory
|Natoli?
|Not done
|-
|InventoryNode
|Natoli?
|Not done
|-
|Aspect
|Natoli?
|Not done
|-
|Animation
|Greg?
|Not done
|-
|Projectile
|Natoli?
|Not done
|-
|Text
|Greg?
|Not done
|}

AnglerStudios:Coding

2006-07-07T01:44:32Z

G01d HaCkEr:

AnglerStudios:Coding

2006-07-07T01:43:39Z

G01d HaCkEr:

AnglerStudios:Coding

2006-07-07T01:29:26Z

G01d HaCkEr:

AnglerStudios:Coding

2006-07-07T01:28:06Z

G01d HaCkEr:

AnglerStudios:Coding

2006-07-07T01:26:22Z

G01d HaCkEr:

AnglerStudios:Coding

2006-07-07T01:23:47Z

G01d HaCkEr:

Back to the [[AnglerStudios:Main_Page|Main Page]].
=Coding Discussion=

The game classes so far we have to implement:

{|
|-
|character
|Programmer
|Not done
|-
|party
|Programmer
|Not done
|-
|weapon
|Programmer
|Not done
|-
|item
|Programmer
|Not done
|-
|grid
|Programmer
|Not done
|-
|world / game map
|Greg?
|Not done
|-
|battle
|Natoli?
|Not done
|-
|NPC
|Programmer
|Not done
|-
|Dialogue
|Programmer
|Not done
|}

AnglerStudios:Coding

2006-07-07T01:20:30Z

G01d HaCkEr:

Back to the [[AnglerStudios:Main_Page|Main Page]].
=Coding Discussion=

The game classes so far we have to implement:

{|
|-
|character
|Programmer
|Not done
|-
|party
|Programmer
|Not done
|-
|weapon
|Programmer
|Not done
|-
|item
|Programmer
|Not done
|-
|grid
|Programmer
|Not done
|-
|world / game map
|Programmer
|Not done
|-
|battle
|Natoli?
|Not done
|-
|NPC
|Programmer
|Not done
|-
|Dialogue
|Programmer
|Not done
|}

AnglerStudios:Coding

2006-07-07T01:16:21Z

G01d HaCkEr:

Back to the [[AnglerStudios:Main_Page|Main Page]].
=Coding Discussion=

The game classes so far we have to implement:

{|
|-
|character
|Programmer
|Not done
|-
|party
|Programmer
|Not done
|-
|weapon
|Programmer
|Not done
|-
|item
|Programmer
|Not done
|-
|grid
|Programmer
|Not done
|-
|world / game map
|Programmer
|Not done
|-
|battle
|Programmer
|Not done
|-
|NPC
|Programmer
|Not done
|-
|Dialogue
|Programmer
|Not done
|}

AnglerStudios:Misc

2006-06-11T07:51:00Z

G01d HaCkEr:

=Miscellaneous Stuff=
Back to the [[AnglerStudios:Main_Page|Main Page]]

==Voice Acting Discussion==

Voice acting? Yes or no?
Im inclined to lean towards a sorta compromised version... voices for important cutscenes or for battle only or somethin like that..
Major reason is it'll make the game a bit more... alive than pure text. Not to mention the fun of acting like an idiot on a microphone =P
~:-=Natoli

- I reckon that the voice acting would have to be done really well for it not to be teh suck. Bad voice acting would just drain the
drama out of any serious scene, and possibly ruin the comedy in a funny scene. Nobody really likes listening to a bunch of nuts on a
cheap mike trying to act, when they couldn't pull of a convincing character to save their lives.

Also, It would make it difficult to speed read through the cutscenes.

That's my opinion, anyway.

~:-=Richard

I can see both sides. I'd like to try and do some voice acting for it, just for the fun of it. But I think we should release 2 different versions: 1 with whatever voice acting we get to include, and one without, which would save file size (for those who get it off the net), and possible cheesiness.

See, for me this game is just gaining a whole lot of invaluable experience in most aspects of a game's design and development. Voice acting is a fun part of that. The more experiences and knowledge I can take from this one project to future ones, the better.

Oh, if we had loads of voice clips, we would probably need to distribute it on CD instead. Which is fine by me for friends and stuff. I know if we do it, it's the version I'll play.

And we should be able to handle the technicalities of still being able to skip the text. You just make it so if they press the 'skip' button, the associated sound stops playing as well. Maybe we could even have it fade out quickly, so it doesn't just abruptly stop. Not sure how to do that, though.

~:-=[[User:G01d HaCkEr|G01d HaCkEr]]

Well... even if we don't do voice acting, Im of the opinion that we should AT LEAST have a degree of voice acting that allows for say... "UMPH!" when someone gets hit in battle. More like cool/annoying grunting noises for battle.
[[User:Natoli|Natoli]] 04:46, 7 June 2006 (PDT)

Yeah, we should at least do the old Link screams and so on. Kyah! Hut! Hut! Kyah!
If we do two versions, that's cool.

RichardS

Oh Greg, probably not hard to do a fade-out... there's gotta be a volume parameter somewhere in any library that handles sound right? Set up a timer to bring the volume down to zero bit by bit in like 2 or 3 seconds... and once it hits zero stop the clip altogether.

2 Versions sounds like an alright idea... shouldn't be too hard either since the way were trying to modulate the code (for once) allows for easy addition/subtraction of sections.

[[User:Natoli|Natoli]] 10:38, 9 June 2006 (PDT)

I knew it wouldn't be hard, I just meant that at that very moment, I did not know off the top of my head, if it was possible or how it was possible in Allegro. Yeah, I like the idea of the 2 versions. Besides, if we just make sure it has proper error handling, we could just make the speech as seperate files, and if they can be found, load and play them, if not, just ignore them (or possibly play one of those annoying generic talking things where it's just sort of electronic mumbling). That would mean it's the same code, same compiled EXE, just different Zip / install files, and different sizes.

--[[User:G01d HaCkEr|g01d_HaCkEr]] 00:51, 11 June 2006 (PDT)

AnglerStudios:Misc

2006-06-11T04:21:47Z

G01d HaCkEr: Changed heading

User:RichardS

2006-06-09T08:14:02Z

G01d HaCkEr:

I will grind you into a million small pieces just for daring to click on my name.

Repent of your sins, and return from whence you came (press the Back button) before I make with the smiting!

AnglerStudios:Battle System

2006-06-07T13:01:52Z

G01d HaCkEr: Added main page link.

AnglerStudios:Battle System

2006-06-07T12:58:24Z

G01d HaCkEr: Adjusting levels response.

I've had an idea about a fairly useful battle system idea type concept thingy...

If you played Final Fantasy 8, do you remember how enemies were scaled in strength according to your party's level? They would jump up a few levels if you were too high for them, and vice versa. Obviously there were limits, but this ensured that enemies always posed something resembling a challenge anyways (stopped you steamrolling through the same lowbie monsters every time like a zombie just grinding for XP...)

We could implement a similar idea... we could have say an instance of the enemy npc class for each monster, but have it contain like a level parameter, and how strong it is. We can then introduce paramaters for how much strength they gain per level, so their base strength at level 5 is say... 15... and it jumps up 2 points per level. A level 15 group encounters this monster so it scales itself up from level 5 to anywhere between level 12 - 18 (im using broad numbers here since we havent decided on damage scales and stuff yet. Can a level 15 beat a level 18??). So lets say it chooses level 12 (for example's sake). its scaled itself up from its base level by 7 so we add 7 X 2 (7 levels times 2 str per level for scaling) and get a more evenly matched fight. Obviously this would take a bit of fine tuning to ensure the monster didn't become too uber too quickly etc, but that's got to be done anyways.

This would also reduce tedium when your party obviously overpowers the enemies in the area.

Alternatively we could simply reduce encounter rate when your party's too strong for the monsters in the area (monsters too scared to attack... slightly WoW-like but yeah) but this could be fun. Anyways, thats just an idea. Any thoughts? [[User:Natoli|Natoli]] 20:03, 5 June 2006 (PDT)

----

If we went with the first suggestion, the monsters would have to scale up in such a fashion that they would be stronger, but still weaker (relative to the level difference) so there would be an actual benefit in going up levels.

The second one sounds good, though - except it prevents players simply leveling up by slogging through heaps of low levels if they want to. Do we want to prevent that?

RichardS

----

Spose there's pros and cons to it.
For the first idea, I suggest if we go with it that we could cap the amount that the enemy scales up in difficulty... say 5 levels or so only, so that eventually you'll still OMGWTFPWN them, but they'll still pose a challenge if say, someone gets lost in the forest and ends up in so many random battles that they level up too much. I agree that they'd have to scale to be weaker eventually as you said, but its not like the slime that is attacking you for revenge since you killed his family, friends and 99.9% of his entire race is going to still be as pathetically weak as the others... right?

The other idea... after a few levels in an area, chances are the player's going to start steamrolling through the monsters anyway. Maybe we could/should scale the amount of XP required to level up so that if they decide to continue training there (pure grinding for xp until they're so awesomely powerful that they can one-shot the final boss or something...) that it'll take forever to make any progress. More like dissuading someone from spending 12 hours of their life in one zone killing monsters to get to level 99 or something.

Obviously this needs more thought, but as far as Im concerned continually training on mobs that are too weak is kinda pointless anyway.
[[User:Natoli|Natoli]] 04:44, 7 June 2006 (PDT)

----

Maybe we could scale the XP gain to lower according to some scale the higher your level is, sort of like Diablo 2, where you'd only get full XP if you were within 5 lvls of the monsters you were killing, and then would get less and less for monsters too high or low.

RichardS

----

Lot of good discussion here.

My initial thought is: Why are we talking about dissuading people from playing our game? Crikey, if someone wants to grind for 12 hours in our game to one-shot the final boss, good for them! That's one way of playing we didn't necessarily foresee, but it's a valid possibility. I fear that RPGs, especially ones like these of such length are already over-prone to repetitive grinding and partial-completion, not to mention they are not as accessible as more arcade-style games. I have the feeling I'm going to have to try really hard when it's done to convince my friends to play it, rather than them wanting to play it. For some, they will only play because I insist, not because they love in-depth RPGs... so if they do play, why make them frustrated and force them to play a particular way?

I think it's quite possible to define a way of modifying the stats of a monster based on level. Perhaps we have an equation field that we can see that determines how to change the stats per level? Perhaps a base stats attributes, then another set of stats that has how much to add per level up to a cap? e.g. perhaps only HP changes as the level goes up, so the fights last longer...

Also, just sort of back to my first point, do we want battles to always be balanced and long? I know I personally '''like''' if I can find a nice low level area to blitz through, with a few quick battles that net me a few items and a handful of exp. Sure, that may not be the conventional playstyle, but hey, it's mine, and it's valid. You don't make games to tell people how to play them. You create something they can play however they darn well feel like. If you limit them too much, it sucks, and people stop playing your game.

I'm not totally against your arguments, though. I'm just bringing up a contrary POV. -[[User:G01d HaCkEr|G01d HaCkEr]] 05:58, 7 June 2006 (PDT)

User:Natoli

2006-06-07T12:38:47Z

G01d HaCkEr: Complete summary of Natoli.

=I smell.=

User:Natoli

2006-06-07T12:38:31Z

G01d HaCkEr: Complete summary of Natoli.

I smell.

AnglerStudios:Misc

2006-06-05T11:43:50Z

G01d HaCkEr: Reformatting

=Miscellaneous Stuff=
Back to the [[AnglerStudios:Main_Page|Main Page]]

==Random Question==

Voice acting? Yes or no?
Im inclined to lean towards a sorta compromised version... voices for important cutscenes or for battle only or somethin like that..
Major reason is it'll make the game a bit more... alive than pure text. Not to mention the fun of acting like an idiot on a microphone =P
~:-=Natoli

- I reckon that the voice acting would have to be done really well for it not to be teh suck. Bad voice acting would just drain the
drama out of any serious scene, and possibly ruin the comedy in a funny scene. Nobody really likes listening to a bunch of nuts on a
cheap mike trying to act, when they couldn't pull of a convincing character to save their lives.

Also, It would make it difficult to speed read through the cutscenes.

That's my opinion, anyway.

~:-=Richard

I can see both sides. I'd like to try and do some voice acting for it, just for the fun of it. But I think we should release 2 different versions: 1 with whatever voice acting we get to include, and one without, which would save file size (for those who get it off the net), and possible cheesiness.

See, for me this game is just gaining a whole lot of invaluable experience in most aspects of a game's design and development. Voice acting is a fun part of that. The more experiences and knowledge I can take from this one project to future ones, the better.

Oh, if we had loads of voice clips, we would probably need to distribute it on CD instead. Which is fine by me for friends and stuff. I know if we do it, it's the version I'll play.

And we should be able to handle the technicalities of still being able to skip the text. You just make it so if they press the 'skip' button, the associated sound stops playing as well. Maybe we could even have it fade out quickly, so it doesn't just abruptly stop. Not sure how to do that, though.

~:-=[[User:G01d HaCkEr|G01d HaCkEr]]

AnglerStudios:Misc

2006-06-05T11:41:59Z

G01d HaCkEr: Response to Richard

Random Question:::

Voice acting? Yes or no?
Im inclined to lean towards a sorta compromised version... voices for important cutscenes or for battle only or somethin like that..
Major reason is it'll make the game a bit more... alive than pure text. Not to mention the fun of acting like an idiot on a microphone =P
~:-=Natoli

- I reckon that the voice acting would have to be done really well for it not to be teh suck. Bad voice acting would just drain the
drama out of any serious scene, and possibly ruin the comedy in a funny scene. Nobody really likes listening to a bunch of nuts on a
cheap mike trying to act, when they couldn't pull of a convincing character to save their lives.

Also, It would make it difficult to speed read through the cutscenes.

That's my opinion, anyway.

~:-=Richard

I can see both sides. I'd like to try and do some voice acting for it, just for the fun of it. But I think we should release 2 different versions: 1 with whatever voice acting we get to include, and one without, which would save file size (for those who get it off the net), and possible cheesiness.

See, for me this game is just gaining a whole lot of invaluable experience in most aspects of a game's design and development. Voice acting is a fun part of that. The more experiences and knowledge I can take from this one project to future ones, the better.

Oh, if we had loads of voice clips, we would probably need to distribute it on CD instead. Which is fine by me for friends and stuff. I know if we do it, it's the version I'll play.

And we should be able to handle the technicalities of still being able to skip the text. You just make it so if they press the 'skip' button, the associated sound stops playing as well. Maybe we could even have it fade out quickly, so it doesn't just abruptly stop. Not sure how to do that, though.

~:-=[[User:G01d HaCkEr|G01d HaCkEr]]

AnglerStudios:Links

2006-05-31T07:11:23Z

G01d HaCkEr:

=Links to Helpful Resources=

==RPG Design==
http://www.indie-rpgs.com/forum/index.php

==Technical Resources==
[http://www.gimp.org The GIMP]

[http://www.allegro.cc Allegro game library]

[http://www.mvps.org/directx/articles/selecting_timer_functions.htm Timer functions] etc page. May not be useful, but then again it might be. ~Natoli

Back to [[AnglerStudios:Main_Page | Main Page]].

AnglerStudios:Links

2006-05-31T07:10:57Z

G01d HaCkEr: Added link back to main page.

=Links to Helpful Resources=

==RPG Design==
http://www.indie-rpgs.com/forum/index.php

==Technical Resources==
[http://www.gimp.org The GIMP]

[http://www.allegro.cc Allegro game library]

[http://www.mvps.org/directx/articles/selecting_timer_functions.htm] Timer functions etc page. May not be useful, but then again it might be. ~Natoli

Back to [[AnglerStudios:Main_Page | Main Page]].

AnglerStudios:Editor

2006-05-24T02:52:20Z

G01d HaCkEr: Response to Richard

=Map Editor Design=

==First thoughts==
Have been trying to think about what to make the editor in. There are 2 choices in my mind:
# Visual Basic
## This has the advantage of potentially faster development, and easier development.
## It also has many disadvantages, such as me not knowing how to implement a large grid with multiple layers of pictures in each grid cell, etc. Also, not knowing how to do transparency, etc. Also, it would be harder to make a file format that is not just lines of text in a file that can be changed all too easily, and yet still have a C++ program read it in easily.
# Allegro
## This has the advantage of when working, also meaning that substantial parts of the game engine have also been written. Can use almost identical functions for loading the map in as saving it (an essential editor function!)
## Disadvantages are: more time taken to develop. Lots of coding needed before half-decent results achieved. GUI kind of sucks compared to drag-and-drop of VB. GUI is low res and ugly.

What do you think, Natoli? And how patient are you prepared to be, Richard?
--[[User:G01d HaCkEr|G01d HaCkEr]] 06:11, 20 May 2006 (PDT)

--

This is your department, I'm cool. 'Patience' equals more time to draw stuff. - Richard

--

I just glanced at the Allegro page. They've got a bunch of RPGs there, though I don't know how nice the code is or whatever... --Richard

--

Yes, in fact this was a nice bonus I had discovered by myself. I had a look at some of them, they are not too bad. Something to work off, maybe? Need to wait till Natoli has a look as well... But by the same token, I'd like to build our own custom classes as has been discussed, and then write an editor that can interface with those. And I think by writing the editor in Allegro, I/we will generate some valid code that can be used for some of the game itself as well. We may even be able to have the editor in-game as well, like some of the examples on that page. Thanks for your comments, though! Now we just gotta get Natoli on here, if he ever stops raiding in WoW... --[[User:G01d HaCkEr|G01d HaCkEr]]

AnglerStudios:News

2006-05-24T02:47:36Z

G01d HaCkEr: Responded to Richard's query.

=Latest News=

Add to the top of this page whenever you have new major news related to the development of the RPG game by Angler Studios.

==Friday, 19 May 2006. 6:30pm==
Started entries in the Wiki to help facilitate planning our game. Not ''entirely'' sure that this is what this Wiki is meant to be used for, since all the other RPGs seem to be tabletop systems, but anyways, hopefully they don't get too mad.
--[[User:G01d HaCkEr|G01d HaCkEr]] 01:36, 19 May 2006 (PDT)

==Tuesday, 20-something May 2006. Something o'clock==

Well, if we use a dice-roll system, then it'll be the same thing except on a computer. They'll be cool. I hope...

Hey, do you want me to transcribe my notes up here? Because they're done really nice-like on the paper and I used a lot of pictures and stuff I don't wanna go to all the effort of writing it up here...
== Richard

Not necessarily transcribe. Perhaps you could upload the files? Or scan them in and upload them as PDF? If you don't know how, send to me first via email.

Btw, if you actually register on these pages, it'll be much easier, for a start you can just do <nowiki> --~~~~ </nowiki> to have your 'signature' automatically inserted. Plus you can watch pages. --[[User:G01d HaCkEr|G01d HaCkEr]] 19:47, 23 May 2006 (PDT)

AnglerStudios:Editor

2006-05-20T13:11:56Z

G01d HaCkEr: Added first thoughts to how map editor will be made for our game.

AnglerStudios:Links

2006-05-19T08:58:15Z

G01d HaCkEr:

=Links to Helpful Resources=

==RPG Design==
http://www.indie-rpgs.com/forum/index.php

==Technical Resources==
[http://www.gimp.org The GIMP]

[http://www.allegro.cc Allegro game library]

AnglerStudios:Links

2006-05-19T08:57:48Z

G01d HaCkEr:

=Links to Helpful Resources=

==RPG Design==
http://www.indie-rpgs.com/forum/index.php

==Technical Resources==
[http://www.gimp.org|The GIMP]

[http://www.allegro.cc|Allegro game library]

AnglerStudios:Links

2006-05-19T08:57:23Z

G01d HaCkEr: Started links page

=Links to Helpful Resources=

==RPG Design==
http://www.indie-rpgs.com/forum/index.php

==Technical Resources==
[http://www.gimp.org|The GIMP]
[http://www.allegro.cc|Allegro game library]

AnglerStudios:News

2006-05-19T08:36:47Z

G01d HaCkEr:

AnglerStudios:News

2006-05-19T08:36:13Z

G01d HaCkEr: Kicked off news page.

AnglerStudios:How can I help

2006-05-19T08:23:36Z

G01d HaCkEr: Skeleton page for outside contributors.

=How Can I Help Out Angler Studios?=

If you found our little project from RPGnet or wherever, and think you can really help us out with some aspect of the game, please edit this page, or use the Discussion tab to indicate this. We appreciate all help, however sometimes smaller teams are easier to manage, the existing 3 person team meets up every Friday in person at our university to continue planning the game, and so remote help would be more difficult to assimilate into the team. But if you can help to make the game better, please don't hesitate to at least offer!

AnglerStudios:Main Page

2006-05-19T08:18:55Z

G01d HaCkEr:

=Angler Studios Main Page=

Welcome to the main page for Angler Studios! The name 'Angler' is derived from the initials of the 2 programmers (AN and GL) and the first initial of the creative guy (R). It consists of 3 friends and other contributors, whose aim is to make an as-yet unnamed RPG game that has an interesting story, and potentially new, interesting gameplay mechanics. It's also a great first foray into making computer games, which is something at least 2 of us want to go into when we graduate from uni.

The team consists of:

* Richard S - character (and other stuff) artist, story writer, primary map designer / content generator
* Greg L - programmer #1
* Andrew N - programmer #2

==Links==
Here are some suggested links to pages which may not exist yet, to anticipate some possible areas we want to work on.

[[AnglerStudios:News|News]] | [[AnglerStudios:Story|Storyline]] | [[AnglerStudios:Battle_System|Battle System Design]] | [[AnglerStudios:Editor|Editor Design]] | [[AnglerStudios:Map|Map Issues]] | [[AnglerStudios:Coding|Coding Discussion]] | [[AnglerStudios:Art|Art Discussion]] | [[AnglerStudios:Files|Uploaded Files]] | [[AnglerStudios:Links|Links to Resources]] | [[AnglerStudios:Misc|Miscellaneous Discussion]]

That's all for now, if a page doesn't exist, create it! Also, if you are not on the team and you stumbled across this page, and want to help out, please use the [[AnglerStudios:How_can_I_help|How can I help?]] page.

Thanks!

AnglerStudios:Main Page

2006-05-19T08:18:43Z

G01d HaCkEr: Did preliminary main page for new RPG project.

AnglerStudios:Main Page

2006-05-19T08:15:20Z

G01d HaCkEr: Did preliminary main page for new RPG project.

=Angler Studios Main Page=

Welcome to the main page for Angler Studios! The name 'Angler' is derived from the initials of the 2 programmers (AN and GL) and the first initial of the creative guy (R). It consists of 3 friends and other contributors, whose aim is to make an as-yet unnamed RPG game that has an interesting story, and potentially new, interesting gameplay mechanics. It's also a great first foray into making computer games, which is something at least 2 of us want to go into when we graduate from uni.

The team consists of:

* Richard S - character (and other stuff) artist, story writer, primary map designer / content generator
* Greg L - programmer #1
* Andrew N - programmer #2

==Links==
Here are some suggested links to pages which may not exist yet, to anticipate some possible areas we want to work on.

[[AnglerStudios:News News]] | [[AnglerStudios:Story Storyline]] | [[AnglerStudios:Battle_System Battle System Design]] | [[AnglerStudios:Editor Editor Design]] | [[AnglerStudios:Map Map Issues]] | [[AnglerStudios:Coding Coding Discussion]] | [[AnglerStudios:Art Art Discussion]] | [[AnglerStudios:Files Uploaded Files]] | [[AnglerStudios:Links Links to Resources]] | [[AnglerStudios:Misc Miscellaneous Discussion]]

That's all for now, if a page doesn't exist, create it! Also, if you are not on the team and you stumbled across this page, and want to help out, please use the [[AnglerStudios:How_can_I_help How can I help?]] page.

Thanks!