I'm trying to Experiment on my own concept..
Its not gonna be a fully IDE Editor.. Just Experimental.
I can't make a fully IDE Editor with my current knowledge.
And Even If I can.. I prefer not to atm.
Ill post something.. when I have something to demonstrate..
Im working on that as we speak..
just a suggestion : watch this video, again and again and again, until you grasp the idea : https://www.youtube.com/watch?v=VvHw7JP47ts
Thanks for the video.
- so you have done 80% of your game and then you grasp: fu... the toolbox I have choosen is not capable of doing what I need to do (networking, physics, ...)
- it is correct that "doing visible things" keeps up the motivation
- for IDEs there are plenty of IDEs around - some are truly customizable but the more hardcoals intented "workflow" differs from currently "common sense" the less the current IDEs will suit
- for many simple games the guy is right: just finish it - but who of us does not dream of "the super project" ;-)
- dude reminds me on "Kevin Heffernan" (Super Troopers)
(https://vignette.wikia.nocookie.net/marvelcinematicuniverse/images/0/06/Kevin_Heffernan.jpg)
Source: https://vignette.wikia.nocookie.net/marvelcinematicuniverse/images/0/06/Kevin_Heffernan.jpg
another one for Derron : https://www.youtube.com/watch?v=n5R8mR1ci3c
(btw, i partly agree with you that sometimes you need to code your own map editor or other custom tool because the existing ones don't have the functionalities that you need, and you waste too much time using workarounds, however his approach to create small games with essential functionalities and to make them accessible to a target group of players, to see if it is appreciated or not, if it is worth continuing or not, and adding more functionalities/details later, is a good advice imo)
At the end of the day, if we ask the question : after all these hours spent on the computer, what tools/games have you created ? are they appreciated by a group of players ? have you managed to earn some money with them ? (if this was your goal)
Personally, i admit to have wasted too much time in the wrong direction, in the past, (for example my obsession with realistic lighting/shading and shadows)
Remi.. I slightly agree with what you posted..
but Its my passion to try to build Editors :)
Its true I dont make Games..
but who said i only like Game making?
I did my mistakes.. long time ago.. I cant go back now..
I have other problems rather than only concentrating on making games..
it concerns screens..
You should do the targetgroup checks in all kind of products you create. Applications, books, ...
Only exception is: writing personal tools (as YOU know what YOU want). So if the game is mainly for YOU, then write it the way YOU like. Regarding this thread it means: Hardcoal is not accepting the current IDEs' mechanics, workflows ... and wants to change that. If that is mostly done "for himself", then OK. But if it is done to sell it at the end, then a prototype to checkout "acceptance" will help a lot.
Using "MaxGUI" seems indeed to be not the most perfect choice. You _will_ have to create many custom widgets - leading to a lot of stress. If you want to use BlitzMax for your GUI stuff you should really take a look at wxMax (and so wxWidgets) as they provide plenty of ready widgets you _will_ need later on. Starting with wxScintilla - which has a lot of inbuilt stuff compared to MaxGUIs custom textarea. Just checkout MaxIDEs undo problems (sometimes deletes the wrong text, redo pastes it into the wrong lines again and so on).
wxScintilla has undo/redo built into already.
But even if you use wxMax you will recognize that some widgets are "empty" (stubs). Had to extend the wxPropertyGrid as some functions were empty. Think Brucey gladly accepts pull requests if you extend wxMax to be more feature complete (read: doing "the tech" rather than "the game").
@ second video
Had this as suggested video already, but I prefer to code now - get too much distracted by video after video :-). Quantity vs Quality does not work for every person. I understand that "finishing something" is better than having only prototypes. But I for instance do not like to give something "unfinished" or "bugged". I cannot achieve perfection in all areas but I try to do so - while I know that it costs way more time (Pareto optimum... 80% quality in 20% of development time, missing 20% quality in 80% development time). But that's me and some others might think similar. "economically" wise this is not the smartest approach of doing things. Bring the stuff out and if it does not work? Who cares? The next project is already nearly completition.
Things of course change if you are a famous developer and people have high expectations. But think for now nobody of us plays in that league (yet ;-)).
bye
Ron
RemiD I totally agree with you on second thought..
Shame I didn't see this video long time ago..
I was trying to make games in the beginning..
But on blitz there was no map editor..
Which dragged me into building one..
I had stupidally great ambitions
@Hardcoal>>of course you do what you want, it is your life, your time, but i just wanted to post this here to make us think about why we do what we do...
This video is not targeted to you specifically, to me and to others developpers also...
I don't agree with everything this guy says... Sometimes it is necessary to make a custom editor/tool, to then waste less time building/editing things for your game. Or to code your own gameplay elements/mechanics (you can't make all types of gameplays using gamemaker/construct !)
But nonetheless, it is interesting to listen to others views, from time to time, because as developpers, we tend to become obsessed on things which are not necessarily important.
We do not just become obsessed - we also become "blind". We become used to how things in our tools, games, ... work, how to auto-circumvent annoyancies (we just do not recognize them annoyancies). So we always use "ctrl + c" plus "ctrl + v" to copy paste. Some people prefer using a mouse - so a context menu "cut, copy, paste, ..." helps them. We never thought of adding these as we were used to come along without them.
I never used the Hex-Color-picker in Geany (text editor) as I previsualize my CSS stuff in Photoshop before - so eyedropper is used there. Others blindly code and these little helper (hex color picker) speeds up _their_ workflow.
Regarding doing your own tools: the more individual-game-specific a tool becomes the less time you should spend on it. Make it work, and ok. Making it versatile can be done in the next project needing it. Nonetheless your code should be written and planned "adoptable" if you know that it will be used later again - in a non 1:1 way. While I overcomplicate many things in my code ("might be of use later on") I know that I would save a lot of time by just writing/prototyping stuff. On the other hand I had plenty of code I had to overhaul because it was not as extendible as planned. Eg. it lead to circular dependencies (a requires b, b requires c, c requires information from a). As this took some weeks to redo - several times in the last years - I tended to do things "more complicate now" to save the hassle later on.
Downside is that much of this stuff is BlitzMax - so I am kind of "bound" to the language.
Benefit of that is an easy reusage of GUIstuff and the likes. I can concentrate on the gameplay - and later on the time consuming stuff of connecting GUI to action (button click = do something, reacting on list selections and so on).
As I never really used "unity" (or other click-n-drop-or-code-by-hand toolboxes) I do not know how much hassle I would have there - I believe there is plenty of stuff not working as I expect them to work, or they are just non-existing. But it might also be the case that there are a lot of things available which I need to write in BlitzMax first.
Regardless of all this stuff: coding a line improves coding the second line. Doing some "tech"-stuff helps understanding things, helps auto-optimizing code you create months later. You avoid sloppy code, performance-desasters etc.
bye
Ron
Hey guys it's me.... :P
QuoteAt the end of the day, if we ask the question : after all these hours spent on the computer, what tools/games have you created ? are they appreciated by a group of players ?
So I have created a lot of different editors, from text, to graphics, to sound, to IDE, connected blueprint, etc. But I LIKE MAKING TOOLS and i enjoy the technical workout in learning new things and solving problems. Using pre-made tools you don't learn anything, you just fit into the way of working.
As to the second, I make them for myself, but I have very strict standards with an eye to being used by others. So far I have had 2 very good successes with apps being recommended for Ludum Dare and also some other mod sites and resource hunters.
I think the essence of not making tools is not a good one, as how do you learn deeper things. but if all you want is a mini game or two, then writing editors is not a good place to start.
writing EDITORS is HARD - probably significantly harder than a game, as you have to deal with engines, and UI's.
I was about to make games essentially but my ambitions for games were over the current games of those times..
There is nothing wrong in making editors..
and you learn for them a lot as well..
My main complaint is or maybe the only.. is about the screen tiredness that causes me to be very inefficient.
If I wanted to make simple games back than, than I would use directly programming..
If I went back in time.. i would probably change some of my tactics ..
I think that the advice of the guy is not to never make a custom editor/tool but rather to not waste too much time on unimportant things, when you are making a prototype / indie game, rather to focus on the essentials components/functionalities, and to focus on the details and to add more functionalities later, when you know that what you have made is appreciated and worth continuing (if your goal is to create games not only for yourself, but also for some players who like a specific subject/gameplay)
However, it is clear that those who have the understanding/skills to make unique gameplay elements/mechanics, original graphics, original sounds, can differentiate from the crowd of developpers who use tools like gamemaker/construct or templates/graphics/sounds from the unity/unreal stores...
Quote from: iWasAdam on February 04, 2018, 13:19:39
Hey guys it's me.... :P
QuoteAt the end of the day, if we ask the question : after all these hours spent on the computer, what tools/games have you created ? are they appreciated by a group of players ?
So I have created a lot of different editors, from text, to graphics, to sound, to IDE, connected blueprint, etc. But I LIKE MAKING TOOLS and i enjoy the technical workout in learning new things and solving problems. Using pre-made tools you don't learn anything, you just fit into the way of working.
As to the second, I make them for myself, but I have very strict standards with an eye to being used by others. So far I have had 2 very good successes with apps being recommended for Ludum Dare and also some other mod sites and resource hunters.
I think the essence of not making tools is not a good one, as how do you learn deeper things. but if all you want is a mini game or two, then writing editors is not a good place to start.
writing EDITORS is HARD - probably significantly harder than a game, as you have to deal with engines, and UI's.
It's subjective but I don't think writing an Editor is harder than writing a game. I guess it depends on the game and the editor. Writing something on the scale of Unity - of course - but just a level editor - definitely not. Just MHO.
Quote
i enjoy the technical workout in learning new things and solving problems. Using pre-made tools you don't learn anything, you just fit into the way of working.
I agree. And if you don't like something, or several things about the pre-made tool? Then that's frustrating, and you'll be less likely to want to produce a game with it.
But it's not for everybody, so people using pre-made tools can be more productive when it comes to games.
i just want to say.. that i did finish my editor long time ago.. (most of it)
And I can make games with it ..
so though i agree that Make Games and not techonology is the right approach
and i've sacrificed too much for this editor. I did manage to make it work..
its just what exactly this guy said in the video..
I got so mentally tired.. that i gave up even that I've reached almost the End..
I still didn't give up on it , but having no results is really frustrating.. and awfully idiotic approach which sadly i chose.
i just want to say.. that i did finish my editor long time ago.. (most of it)
And I can make games with it ..
so though i agree that Make Games and not techonology is the right approach
and i've sacrificed too much for this editor. I did manage to make it work..
its just what exactly this guy said in the video..
I got so mentally tired.. that i gave up even that I've reached almost the End..
I still didn't give up on it , but having no results is really frustrating.. and awfully idiotic approach which sadly i chose.
Also Funny, that even though i've reached the "end", its no longer really challenging.. its
just dull boring labor.
besides its too demanding and annoying in general..
I keep thinking of ways of how it will be better and its endless..
but i still didnt get to the point when its easy to make game with it..
so yea. im still behind
Quote
I got so mentally tired.. that i gave up even that I've reached almost the End..
i did the same thing when trying to create a 3d action rpg game with similar graphics than those of the dreamcast/ps2/xbox era, alone, you guess the end of the story : too much time / work required for one person, then you end up discouraged or real life constraints force you to stop.
But with a small game it is different, because you can finish it in a few weeks or in a few months, and each time you have accomplished something, so it is motivating (and you can reuse procedures/functions/systems for the next games).
(i am not saying to create mediocre games and to flood the online stores with more crap, but rather to get real about what is possible to achieve for a lone developper, and focus more on the gameplay / possibilities than on the graphics)
If properly done you can pretty "easy" replace visuals with better ones.
No need to have fancy walking, jumping, ... animations. Just make your character be able to have different animations at all and there you go.
Optimization and Improving presentation takes way way way more time than doing the actual gameplay.
Even connecting GUI stuff is more time consuming than the easy "AddItem(item, SLOT_WEAPON)" call alone.
Most of us developer will fail on their first projects: "pong"? nope I am way too smart to do such a beginners project!. So our first projects are damned to fail. Better accept what others say and do something little to "get the hang of it" (the "feel" on how to do things). As RemiD wrote already: all your little projects help creating bigger ones - as you can reuse stuff.
Once you did your basic gui stuff, you can use it in the next game - so your next game might have better menus. You wrote a scene manager with fadeOut, fadeIn, ... next game will benefit from it in way less time.
And the most appreciateable thing - a pity we get it way too rarely - is feedback from users. "Had a great time with that game" encourages you. "I liked the idea of controlling the virus instead of the scientist" helps you to improve your game ideas, gameplay mechanisms and so on.
Just think of: no game you finished is a failed project. It's always something to learn from.
bye
Ron
I always give feedback.. And I agree, people don't give enough..
Shame, i mean it.. Shame i wasn't more modest and going to make more simple games to begin my path..
Even in my modest state I would have done well..
Going back now is a problem..
I hope I'll find the middle path.. will see.
I remember seeing physix engine at blitz3d
And I was amazed..
I could have done many simple games already than..
but I still like my path :)
And i am back at creating a map editor lol ;D
What other choice do we have ? Either you need something to create maps (and its components), or you can generate the map procedurally (in code), but using existing tools is very restrictive... (especially when later you need to add nodes, a fast enough pathcalculation and pathfollowing system, a fast enough collisions detection / repositionning system, a fast enough occlusion culling / rendering system )
Even for a small game with simple graphics, it is never good to have to calculate pathfinding, collisions, rendering on all (even non visible) rooms and their components...
What I really wanted in an IDE Editor is not that of too much to ask..
in order to understand what is going on in a your project..
you need an ability to zoom in and out on it.
The reason im doing an example or an experiment is to try to see whether it will work..
Ill keep trying.
I Also find myself making sometimes Functions that i've already previously made..
that's due to the inability to reflect on all the project structure
This is one Concept.. But i'm thinking of something more Elaborate..
What i'm Really Trying to do is to Add Folding to the IDE that I can Choose Sections to Fold..
And not Only Functions and other Stuff.
So If I want some section to be folded under a name.. I can Do that.
Here is an Example of a Section Code
Section ProgramHead{
Global A=34
Graphics 800,600,32
Etc..
}
(A folded Section will look like this in the Code ---> [ProgramHead])
the section words wont be visible to the user.. only for the editor.. and will be removed before compiling..
This allows Folding of areas you decide..
What's good in it?
*Well.. Its Makes the code more readable
*you Can Rem Sections..
*You can copy paste Sections easily or remove them for experiments..
*You can plan your coding by doing section which will be empty..
*And More..
(https://i.imgur.com/BB2L04g.jpg)
In my IDE you would be able to open a function in a new window.. Edit it. and close back to the main IDE..
I have more Ideas.. but that's not for now..
I dont believe Ill finish such an Editor.. But i just want to share with you what bothers me the IDE im using which is Blide..
* I know it may sounds silly.. but zoom in and out in a code is possible.. (I mean with dragging the mouse up and down like you do in a graphic editor)
when you zoom in and out you can get the code to fold and unfold.. very convenient and much better than pressing areas to fold and unfold them constantly.
This is a good way to see the whole picture of you project.
some ide's are better