Lets learn from Spring and think about the future of Wesnoth
Moderator: Forum Moderators
Re: Lets learn from Spring and think about the future of Wes
I am currently developing the reference implementation of a GameServer using my new WesScriptLayer.beetlenaut wrote: That doesn't look like a joke, but why?
I can already load a scenario and play a very simplified Wesnoth game.
But the game play is hacking things like
Code: Select all
kernel\execute_command("move" 12, 13, 12, 14)
kernel\debug!
That was fine for the first time of development, but I am reaching a point where it makes sense to get a better grip of what is going on on the map.
Implementing a quick ascii client is fun and will help immensely with establishing the protocols and apis.
"Wesnoth has many strong points but team and users management are certainly not in them." -- pyrophorus
"The thing a project in the true spirit of open source has to fear is not forking, but clean-room re-implementation. When that happens, you know something is wrong."
"The thing a project in the true spirit of open source has to fear is not forking, but clean-room re-implementation. When that happens, you know something is wrong."
- Pentarctagon
- Project Manager
- Posts: 5564
- Joined: March 22nd, 2009, 10:50 pm
- Location: Earth (occasionally)
Re: Lets learn from Spring and think about the future of Wes
Wesnoth: Dwarf Fortress edition.beetlenaut wrote: That doesn't look like a joke, but why?
99 little bugs in the code, 99 little bugs
take one down, patch it around
-2,147,483,648 little bugs in the code
take one down, patch it around
-2,147,483,648 little bugs in the code
Re: Lets learn from Spring and think about the future of Wes
Slaves to Armok: Sea of Blood Chapter I: Battle for WesmerePentarctagon wrote:Wesnoth: Dwarf Fortress edition.beetlenaut wrote: That doesn't look like a joke, but why?
"Wesnoth has many strong points but team and users management are certainly not in them." -- pyrophorus
"The thing a project in the true spirit of open source has to fear is not forking, but clean-room re-implementation. When that happens, you know something is wrong."
"The thing a project in the true spirit of open source has to fear is not forking, but clean-room re-implementation. When that happens, you know something is wrong."